[Nix-dev] Limiting access to only maintained packages and ensuring core packages are maintained

[Shea Levy]

maintainers.nix contains email addresses and for many of us uses the
same as our github handles. So users should be told to ping on github
*and* email when they find an issue, and then if someone is unresponsive
through that we can (if we're sticking with 3) remove them after some
time.

Hydra will email you if the build status of a package you maintain
changes.


Thomas Hunger <tehunger at gmail.com> writes:

> I'm mostly worried about leaning that I need to fix a package that I'm
> maintaining. I care about fixing bugs and purging unmaintaned packages, but
> most of the time I don't even see the report, or I know it's broken in
> hydra until I test again locally.
>
> Do you have any ideas around getting word out to maintainers sooner?
>
> On 2 September 2016 at 21:22, Shea Levy <shea at shealevy.com> wrote:
>
>> Hi all,
>>
>> I think a few changes might improve package stability a bit:
>>
>> 1. Add a nixpkgs config setting to throw an error on packages with no
>>    meta.maintainers
>> 2. Work to reach a point where a significant subset of nixpkgs (say,
>>    release-small) is allowed on this list.
>> 3. Remove maintainers after X weeks without reply on issues they're
>>    tagged in about packages they maintain
>> 4. (Optional) Separate out maintainers by system
>>
>> Thoughts on these?
>>
>> ~Shea
>>
>> _______________________________________________
>> nix-dev mailing list
>> nix-dev at lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.science.uu.nl/pipermail/nix-dev/attachments/20160903/e7a2e16d/attachment.sig>