[arch-dev-public] Getting to New Arch SCM Layout and Repo Management

[Jason Chu]

I only really have one suggestion.

> JUNE: During June, the developers and I will build the system and
> get it ready for initial deployment. The source will be open to for
> anyone to observe and contribute, but we 4 will have commit access.
> 
> JULY: On July 1, we will launch the system and put some real
> packages in it. At that time, we will need MAINTAINERS to join the
> project.
> 
> We will deploy the system with REAL packages and REAL maintainers,
> just a small number of them. Any developer or TU wishing to
> participate will be allowed to contribute *AT MOST 4 PACKAGES OF
> RELATIVELY SMALL SIZE* to the test system and they will begin to be
> maintained in our system. It will be up to the individual developer
> or TU to decide if they will propagate the PKGBUILD changes from our
> system back into the official repos.
> 
> AUGUST: In August, we will evaluate how we have done. If all has
> gone well, we will hand our system to the Arch development community
> with a recommendation to enhance and deploy it for main site and AUR
> repo management.

Be careful not to make this system too big.  The main site and the AUR have
somewhat different requirements.  Don't let yourself get bogged down having
to implement all those features.

Jason
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://archlinux.org/pipermail/arch-dev-public/attachments/20070430/c62befad/attachment.pgp>