[Nix-dev] RFC for RFCs

[Maarten Hoogendoorn]

Also see the notes that Arian took during the BoF session at FOSDEM:

We had a very spontaneous NixOS discussion panel at FOSDEM.
>
> I took minutes.  I must say they're a bit rushy at times, so add stuff to
> it
> you think isn't clear or is lacking in content.  Thanks!
>
>
> http://piratepad.net/1nHg65LMQj
>

2017-02-12 19:46 GMT+01:00 Thomas Hunger <tehunger at gmail.com>:

> That would be amazing! I actually have an email sitting in my draft folder
> proposing Nix Enhancement Proposals (NEPs).
>
> IMHO one of the things we aren't very good at is getting larger changes
> merged or rejected. We attract a lot of smart people because Nix is pretty
> awesome. These smart people then do substantial work, submit a PR and the
> PR bitrots. This is highly demotivating.
>
> An RFC process would allow us to get to an accept / reject early on, with
> the expectation that accepted RFCs will be merged when the technical work
> is done.
>
> I'll add more specific comments to your PR.
>
> ~
>
> On 12 February 2017 at 15:12, zimbatm <zimbatm at zimbatm.com> wrote:
>
>> Hi all,
>>
>> we discussed of introducing a RFC process during FOSDEM. The goal is to
>> help discussion for large or controversial changes which typically grind to
>> a halt.
>>
>> Here is an initial proposal based on the one from the Rust community:
>> https://github.com/zimbatm/rfcs/pull/1 . Please let me know what you
>> think.
>>
>> Cheers,
>> z
>>
>> _______________________________________________
>> nix-dev mailing list
>> nix-dev at lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
>>
>
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.science.uu.nl/pipermail/nix-dev/attachments/20170212/32754e2b/attachment.html>