Re: Community repository proposal

> I've been wondering about this. So here's a proposal:
>
> There's a lot of stuff I think that various people have produced or
> are considering producing at this point that ought to be 'on track' to
> go into the standard library. Much of it does not warrant a project
> to itself (or may be a small part of an existing project), but is
> nevertheless useful. At present there is no formal mechanism for
> publishing this work, beyond this mailing list and the bug tracker,
> neither of which are really geared for community code review.
>
> I propose that we will host a Git[1] repository, to which we will grant
> write access to anyone (that we recognise) who asks for it. This
> repository will contain a scalax._ package tree containing the
> community-contributed code. We will set up a separate mailing list to
> discuss this code. A second repository will be writable only by a
> selection of 'influential' Scala users (list subject to nominations)
> and will contain the code that passes peer review. That repository will
> be published periodically via sbaz.
>
> The purpose of this repository will be to contain the same sort of code
> that is present in J2SE, the Haskell standard library, etc. and not
> anything too domain-specific (for which sbaz, Sourceforge, etc. would
> be a more appropriate channel). All code will be released under the
> same license as Scala, and code may be moved from the community
> repository into the main distribution as the Scala developers see fit.
>
> Would this be useful? Practical? ...?
>
> /J
>
> [1] For our own work, we use Darcs and are very happy with it. However
> Darcs has some problems that make it unsuitable for use with a publicly
> writable repository. Git seems a reasonable alternative. In any case, a
> distributed SCM (Darcs, Git, Mercurial, bzr, etc.) seems ideal for this
> purpose.
>