[Nix-dev] Too many open issues

[Benno Fünfstück]

> 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.

An alternative approach is to just ping the relevant persons in the issue.
This way, they'll get notifications on updates to the issue. But I think
this partly already happens right now through mentionbot.

What I would like to see, however, is a clear set of guidelines that list a
person who has the final say over changes in each subset of nixpkgs. It is
not uncommon for PRs to stay around for months because it is unclear who
may approve/disapprove them (and saying no to PRs sometimes is important as
well). For example, this guideline could list someone responsible for each
language currently supported by nixpkgs (python, haskell, etc) or for parts
of the nixos module system or for the stdenv and so on.

Just my two cents,
Benno

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.science.uu.nl/pipermail/nix-dev/attachments/20160723/06de91c4/attachment.html>