RFD: Adding ability for maintainers to upload their own packages

[Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>]

I've been playing with the notion of allowing maintainers to upload
their own packages for some time.  Over the three day weekend, I started
implementing a method that I think will work.

I've set up a chrooted environment which contains a copy of the cygwin
release directory.  Every package in this environment belongs to its own
group.  Every maintainer belongs to all of the groups which constitute
their packages.

If a maintainer provides us with an ssh key, it will be added to the
list and given an "account" which will allow them to manipulate their
packages.  They can scp, sftp, or just login.  You can delete or add
packages, modify setup.hint's, etc.  A maintainer will access the site
via "ssh cygwin-staging@cygwin.com".  This will use their ssh key to
login to their account.

None of these changes will be made to the actual release itself.  There
will be some sanity checking applied to new packages before they are
copied to the real release directory and any package deletions will be
archived.

I am thinking that rather than sending email to cygwin-announce, the
announcements should somehow be added as text to the release directory
and automatically generated as cygwin-announce with a standard trailer.
You could even archive the announcements in the directory itself.

I think all of the above should help maintainers be more productive
and eliminate the need to ask for uploads.  However, I know how these
things work.  I'm trying to make things easier so I've probably caused
massive amount of pain to someone.  Think of the children after all.

Please send comments here.  Is this a positive thing?  Are there other
things that could be done in this scenario?

cgf