Re: Publicly submittable repository

Hi,

this is a pre-announce about ATrpms going multi-developer!

There are already several people contributing rpms to ATrpms which I
manually fold into ATrpms. I am now setting up developer accounts to
ATrpms' systems to allow direct inclusion of new or updated rpms
without any intervention on my behalf.

I haven't come up with any better policy for submission/acceptance for
now than "relayed to each developer's conscience". First built
packages will fall into the "experimental" section and be
automatically promoted to higher stability classes depending on time
waiting in repo w/o any blocking mechanisms (e.g. each developer will
be able to hold back the package into "experimental" or whatever repo
will be chosen). I deliberately want a very simple model based mainly
on trust to co-developers.

I'm posting this into this thread, because I believe (or hope, which
is the same for me ;) that ATrpms will soon become a publicly
submittable repository in the spirit Link described in his mail.

All the above are suggestions from my behalf, I will let the interested
developers/packagers decide on what methods/policies etc. to use.

Currently I am under the hood preparing this setup, mainly involved
with enlarging disk and network capacities :)

On Tue, Apr 20, 2004 at 10:22:59AM -0700, Link Dupont wrote:
> On Tue, 2004-04-20 at 11:17 +0200, Axel Thimm wrote:
> > On Tue, Apr 20, 2004 at 01:53:30AM -0700, Link Dupont wrote:
> > > I've recently gotten into Debian packaging, and the Debian community has
> > > put together a public repository for packages not in the main
> > > archive[1].
> > 
> > > If I get enough positive response from this I will draft up a more
> > > formal proposal. This would have to be a volunteer & cooperative effort.
> > > For example, I do not have bandwidth nor server space to host anything,
> > > but I am willing to put in time to develop a website & submission system
> > > (possibly even package submission tools, like shell scripts and such
> > > that upload).
> > > So what do you guys think?
> > 
> > I'd love package submission tools! Maybe the ones there can be used directly?
> 
> Off-hand, I'd say we'd need a fixed archive (repository) structure. Or
> possibly write it into a config file. I've written up a series of
> scripts I've titled spc-rpm-<function> like, spc-rpm-build,
> spc-rpm-release, etc. They're along the same lines as package submission
> tools. Submission tools could theoretically allow multiple users to add
> packages to one archive. mentors.debian.net uses machine accounts for
> each user and scp. Its possible to use anonymous upload, and have a
> script run on the server that checks package signatures, and possibly
> some other validation, and then adds them to the repository. Like
> always, just brainstorming.
> 
> > > 1: http://mentors.debian.net/

-- 
Axel.Thimm at ATrpms.net

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAl14CQBVS1GOamfERAgjjAJ9eariQM4uOWvVjnZj6QYDqAV+oSQCcDMQk
E195VWW24lkbI99OiX+b784=
=1kAm
-----END PGP SIGNATURE-----