[Nix-dev] Git conversion of NixOS and Nixpkgs

[Michel Alexandre Salim]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On 05/29/2012 04:02 PM, Ludovic Courtès wrote:
> Hello,
> 
> Michel Alexandre Salim <michel at sylvestre.me> skribis:
> 
>> will you require contributors to have Github accounts in the
>> future if they want to be able to commit to nixpkgs directly?
> 
> That wouldn’t scale well, and there’d probably be lots of merge
> commits if everyone can push, leading to a needlessly twisted
> history.
> 
As I understand it, since the NixOS account on Github is an
"organization", not a normal user, team management features are
available -- so instead of everyone having to push, everyone currently
granted direct access to SVN could just have their GitHub account given
the right permission to the right project under NixOS:

  https://github.com/features/projects

It does require people sign up to GitHub though.

> Having Eelco have to approve every single commit would avoid that,
> but it wouldn’t scale well.  ;-)
> 
> So it would be great if something similar to the Patch Queue
> Manager (PQM) of Arch/Bazaar could be used.  And eventually some
> sort of PQM coupled to Hydra, which would merge iff nothing
> breaks.
> 
There's Gerrit, which we can probably use for this (Google uses it to
manage their Android source tree). You can require commits to be
reviewed and signed before they get merged -- and then have Gerrit push
to the GitHub public repos. It's a Java web application though, and
(AFAIR) uses JGit instead of the normal git so I'm not sure if the
latest Git features are supported.

Might be overkill if GitHub's team management features are sufficient.
I've never managed a GitHub organization before so I can't say much on
this. The five members in https://github.com/NixOS likely know more.

- -- 
Michel Alexandre Salim
µblog:      http://identi.ca/hircus
            http://twitter.com/hircus
GPG key ID: A36A937A

()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPyZrJAAoJEEr1VKujapN6pJ8H/2bLvmpCTi7h5GbVM2t13hjX
AZRYS5nSx1wLOKeFxtVhXqdfsxh+rhbHfC/ohGfhUry4al8kTMLNuUl/CBWlWRGb
T5LGhTQs6sAWmQM3QvPDwQ8Bh4ak4OyahmQwHqKunQn3cPaIgzioEdZstiWMWSQS
eeQXueqjehI7SnFQDEMtd94BStPgZ+4iRAwI7BaNWdRY6juEXrkHqM2d/gH18WND
3NX6si438keSEZlb8h0YYXh4OBjmdoTHUyDy8jR4A59OoXE//NOMCP0GhWect5aD
RRaZnFOFdY6SRhpFBpIhhCs+xQOT1PNrieFDVtIONeUkOynY+QUBjQT0SMgDGYg=
=ZlBl
-----END PGP SIGNATURE-----