Re: [9fans] nix at lsub

[Noah Evans <noah.evans@gmail.com>]

I'd like to correct one more misunderstanding and expand a bit more.
Nix is not just work done at lsub (although I'll be the first to admit
that most of the recent work has been done at lsub), it was a
collaboration between Bell Labs, Sandia and lsub (of which my
technical contributions have been very small).

One of the goals in using google code and codereview is to establish a
place to collaborate independent of all parties, the codereview
process was established that all parties were represented and there
was a clear and transparent process where *anyone* who wanted to
contribute could and feel that their contributions were being
considered for technical rather than political reasons.

Noah



On Mon, Apr 16, 2012 at 7:32 PM, Noah Evans <noah.evans@gmail.com> wrote:
> 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 <aram.h@mgk.ro> wrote:
>> Noah Evans wrote:
>>> To clarify, Nix development will be continuing at both
>>> nix-dev@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-dev@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
>>