There's a bit of drama going on right now. Here's what I wrote in a private mail to Steve Simon:
I don't think anybody really liked hg from a technical standpoint. There were two reasons behind choosing it: 1. It would be trivial to get a 9vx nix distro up and running on Macs and Linux machines. 2. Codereview would ensure a transparent and open development process. Patch can be used for 1 to some extent (via the tarball) but it fails for 2. It makes some members of the community "more equal" than others. I think those of us sticking with hg are doing so more for social reasons than technical ones. Noah On Mon, Apr 16, 2012 at 7:23 PM, Aram Hăvărneanu <ara...@mgk.ro> wrote: > Noah Evans wrote: >> To clarify, Nix development will be continuing at both >> nix-...@googlegroups.com and http://code.google.com/p/nix-os as well. >> The project has forked. > > I don't understand what is going on. I though some people were very > unsatisfied with the rietveld code review tool offered by Google Code, > and Nemo created some new tools to be used instead of rietveld and > mercurial. Of course Nemo's tools don't work with Google Code hosting > so the project is moved at lsub, and by design the old mailing list, > nix-...@googlegroups.com, is tied with the Google Code project, so a > new mailing list has to be used instead. > > So what's this fork I'm hearing about? Someone wants to maintain the > mercurial repository independent of the work done at lsub? Who? Why? > > If this is not the case, and I hope it isn't, destroy the Google Code > project. Delete it, there's no point for this confusion. Personally I > would have preferred that the mercurial repository would have remained > the place where nix development would happen. I believe the problems > people felt with rietveld could be solved by running a private > instance of rietveld, instead of the generic one at Google, but > whatever, I have no say in this. Just keep it in one place if there's > no schism happening. > > So what's happening? John's message on nix-dev@ adds more to this confusion... > > -- > Aram Hăvărneanu >
