Re: The current hurd development system - or: optimizing for fun

[Alfred M\. Szmidt]

   o Use a better revision control system.
      Cvs is outdated in several aspects. Most notably truly atomic
      commits and file moving are missed, thus not allowing -Ofun to
      be relized.  Easy merging and branching are also required.

This implies that -Ofun was never possible for any project using CVS.
Thing is that CVS is actually quite good, despite its small quirks,
none of which are so immensly important that it is crucial to change
VCS (not to mention the huge job of converting history!).

   o Make commits easy and straight forward.
      Revising all code by a handful of core developers is a serious
      bottleneck and source of frustation.

The reason why it is frustrating is because the set of develoeprs who
can actually do anything is zero.  Not because one has to vet things
through them, which is quite a quick job in almost all cases.

      For the beginning it might be OK to give all frequent users of
      the list that ask for direct access to the repo (possibly in
      different branches), but commit rights must be casted far and
      wide.

That is how it already works.

   o Work on code.

Would you like to work on some code? :-)

   o Highly integrate the community.

The more people who work, the more people will join...

Cheers!