[prev in list] [next in list] [prev in thread] [next in thread]
List: nix-dev
Subject: Re: [Nix-dev] Too many open issues
From: obadz <obadz-nix () obadz ! com>
Date: 2016-07-23 12:23:24
Message-ID: CAFB71a45BqF2ROaYj4Mcg+3WyH8YnyEipbzG5q3QC9oRBHXfoQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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, f=
eel
>> 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 alternative is for all of us to troll through every issue and of course
decide that most of them aren't things we are best positioned to resolve.
That's O(n_issues * n_reviewers).
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Jul 23, 2016 \
at 2:19 AM, Benno Fünfstück <span dir="ltr"><<a \
href="mailto:benno.fuenfstueck@gmail.com" \
target="_blank">benno.fuenfstueck@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span class=""><div class="gmail_quote"><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div \
class="gmail_quote"><div><span style="font-size:13px">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".</span></div></div></div></div></blockquote></div><div><br></div></span><div>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.</div></blockquote></div><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).</div><div \
class="gmail_extra"><br></div><div class="gmail_extra">The alternative is for all of \
us to troll through every issue and of course decide that most of them aren't \
things we are best positioned to resolve. That's O(n_issues * \
n_reviewers).</div></div>
_______________________________________________
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