[prev in list] [next in list] [prev in thread] [next in thread]
List: nix-dev
Subject: Re: [Nix-dev] Too many open issues
From: Wout Mertens <wout.mertens () gmail ! com>
Date: 2016-07-22 13:26:13
Message-ID: CAO3V83Kc6B84nUW2kQL86Y7ku_TyYaq24fG8qAbd90XzMPQYLA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Ok, how about this: We split nixpkgs in nixpkgs-core and nixpkgs-community
For any package or service, there need to be at least 3 active maintainers,
or it goes out of nixpkgs-core into a nixpkgs-community repo.
Hydra builds nixos from nixpkgs-core, and nixpkgs from both combined.
nixpgks-core issues are mostly solved by the maintainers or of course any
PR that is good enough.
In the nixpkgs-community we implement the
http://rfc.zeromq.org/spec:42/C4/ process,
meaning that any PR that fulfills all the objective goals gets merged. It
worked well for ZeroMQ, and takes the guesswork out of PRs. Tree
maintainers only need to evaluate the C4 objectives
<http://rfc.zeromq.org/spec:42/C4/#23-patch-requirements> of the PR, and if
they are fulfilled, merge.
Packages get moved between the two repos as support status changes.
That way, we have a small "trust base" for server systems, and a large
"community base" for the latest and greatest. NixOS is so flexible that you
can mix and match as you wish.
On Fri, Jul 22, 2016 at 3:12 PM Kevin Cox <kevincox@kevincox.ca> wrote:
> On 22/07/16 08:55, Alexey Shmalko wrote:
> > This one: https://www.codetriage.com/nixos/nixpkgs
> >
>
> That's it! I have subscribed to get a couple issues a day so hopefully I
> can help a bit. This site seems like a nice way to spread the load.
>
> It's open source too, and I just opened an issue asking them to
> implement filters as I'm not really interesting in seeing in-progress
> issues.
>
> https://github.com/codetriage/codetriage/issues/498
>
>
> _______________________________________________
> nix-dev mailing list
> nix-dev@lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
[Attachment #5 (text/html)]
<div dir="ltr">Ok, how about this: We split nixpkgs in nixpkgs-core and \
nixpkgs-community<div><br></div><div>For any package or service, there need to be at \
least 3 active maintainers, or it goes out of nixpkgs-core into a nixpkgs-community \
repo.<div><br></div><div>Hydra builds nixos from nixpkgs-core, and nixpkgs from both \
combined.</div><div><br>nixpgks-core issues are mostly solved by the maintainers or \
of course any PR that is good enough.</div><div><br></div><div>In the \
nixpkgs-community we implement the <a \
href="http://rfc.zeromq.org/spec:42/C4/">http://rfc.zeromq.org/spec:42/C4/</a> \
process, meaning that any PR that fulfills all the objective goals gets merged. It \
worked well for ZeroMQ, and takes the guesswork out of PRs. Tree maintainers only \
need to evaluate the C4 <a \
href="http://rfc.zeromq.org/spec:42/C4/#23-patch-requirements">objectives</a> of the \
PR, and if they are fulfilled, merge.</div></div><div><br></div><div>Packages get \
moved between the two repos as support status changes.</div><div><br></div><div>That \
way, we have a small "trust base" for server systems, and a large \
"community base" for the latest and greatest. NixOS is so flexible that you \
can mix and match as you wish.</div></div><br><div class="gmail_quote"><div \
dir="ltr">On Fri, Jul 22, 2016 at 3:12 PM Kevin Cox <<a \
href="mailto:kevincox@kevincox.ca">kevincox@kevincox.ca</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">On 22/07/16 08:55, Alexey Shmalko \
wrote:<br> > This one: <a href="https://www.codetriage.com/nixos/nixpkgs" \
rel="noreferrer" target="_blank">https://www.codetriage.com/nixos/nixpkgs</a><br> \
><br> <br>
That's it! I have subscribed to get a couple issues a day so hopefully I<br>
can help a bit. This site seems like a nice way to spread the load.<br>
<br>
It's open source too, and I just opened an issue asking them to<br>
implement filters as I'm not really interesting in seeing in-progress<br>
issues.<br>
<br>
<a href="https://github.com/codetriage/codetriage/issues/498" rel="noreferrer" \
target="_blank">https://github.com/codetriage/codetriage/issues/498</a><br> <br>
<br>
_______________________________________________<br>
nix-dev mailing list<br>
<a href="mailto:nix-dev@lists.science.uu.nl" \
target="_blank">nix-dev@lists.science.uu.nl</a><br> <a \
href="http://lists.science.uu.nl/mailman/listinfo/nix-dev" rel="noreferrer" \
target="_blank">http://lists.science.uu.nl/mailman/listinfo/nix-dev</a><br> \
</blockquote></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