[prev in list] [next in list] [prev in thread] [next in thread]
List: nix-dev
Subject: Re: [Nix-dev] Too many open issues
From: Kevin Cox <kevincox () kevincox ! ca>
Date: 2016-07-25 2:52:40
Message-ID: CALUcMk0awsDBD0JvizaUy5WACdCye-ykOO0MtS-usOj1NtuzMQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Jul 23, 2016 08:23, "obadz" <obadz-nix@obadz.com> wrote:
>
> On Sat, Jul 23, 2016 at 2:19 AM, Benno F=C3=BCnfst=C3=BCck <
benno.fuenfstueck@gmail.com> wrote:
>>>
>>> The key here would be that we shouldn't get rattled if we get assigned
an issue/PR. All it means is "I think you know more about this than I do,
feel free to pass it on to someone else if aren't the right person or can't
handle this with the appropriate urgency".
>>
>>
>> I don't think that assignment is the right tool for this job. Assignment
in my opinion should be used for the purpose of avoiding duplicated work:
you assign yourself to an issue if you plan on working on it, so that
everyone else knows that they shouldn't work on that particular task
themselves.
>
>
> Fully agree that the purpose of assignment is to avoid duplicated work.
That is why I think the first person to ever review an issue (maybe that's
mentionbot) should assign someone to that issue. Once that's done, this
issue won't waste anyone's else's time until the current assignee decides
who would be a better assignee. This means the amount of reviewing work
done is about O(n_issues).
>
The nice thing about assignment is it is a little harder for things to get
lost. And I think asking the current assignee "I have time to take this
over, is that OK?" is an awesome question to ask if it appears that nothing
is being done.
[Attachment #5 (text/html)]
<p dir="ltr"></p>
<p dir="ltr">On Jul 23, 2016 08:23, "obadz" <<a \
href="mailto:obadz-nix@obadz.com">obadz-nix@obadz.com</a>> wrote:<br> ><br>
> On Sat, Jul 23, 2016 at 2:19 AM, Benno Fünfstück <<a \
href="mailto:benno.fuenfstueck@gmail.com">benno.fuenfstueck@gmail.com</a>> \
wrote:<br> >>><br>
>>> The key here would be that we shouldn't get rattled if we get \
assigned an issue/PR. All it means is "I think you know more about this than I \
do, feel free to pass it on to someone else if aren't the right person or \
can't handle this with the appropriate urgency".<br> >><br>
>><br>
>> I don't think that assignment is the right tool for this job. Assignment \
in my opinion should be used for the purpose of avoiding duplicated work: you assign \
yourself to an issue if you plan on working on it, so that everyone else knows that \
they shouldn't work on that particular task themselves.<br> ><br>
><br>
> Fully agree that the purpose of assignment is to avoid duplicated work. That is \
why I think the first person to ever review an issue (maybe that's mentionbot) \
should assign someone to that issue. Once that's done, this issue won't waste \
anyone's else's time until the current assignee decides who would be a better \
assignee. This means the amount of reviewing work done is about O(n_issues).<br> \
></p> <p dir="ltr">The nice thing about assignment is it is a little harder for \
things to get lost. And I think asking the current assignee "I have time to take \
this over, is that OK?" is an awesome question to ask if it appears that nothing \
is being done. </p>
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic