[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: New-Maintainer



On Mon, Jan 03, 2000 at 01:24:11PM +0100, Stephane Bortzmeyer wrote:
> > 2) There is a sponsorship program going on, which while on the website
> > as "official" is listed nowhere in the Consitution.
> 
> Grassroot initiative by Raphaël Hertzog.

Good stuff!

> > 4) Sponsored packages are officially maintained by the sponsor, not the
> > original developer who packaged it, in the eyes of Debian.
> 
> Note that packages.debian.org displays the real maintainer.

I didn't know this.  That's good too.

> > 7) The Debian Developer's Reference makes NO comment about any of this.
> 
> People at new-maintainer do not do their jobs, other people have to act, 
> wether it is written in the Debian Developer's Reference or not.

They're not bound to continue doing their jobs, according to the
Constitution.  They can quit at any time with a public announcement.  It
goes back to your response to #2.

> > #3 means that those of us either being sponsored, or as in my own case,
> > one who's already contacted a developer and asked to be sponsored, are
> > in a precarious state. 
> 
> Unfortunately, yes. Several sponsors are a bit overloaded and do not have the 
> time to do a proper "tutor" job. That's why the whole idea of "internship" is 
> broken. The sponsorship program is therefore a good way to test new 
> new-maintainers schemes.

If the "internship" and the "sponsorship" are set up the same, that'd be
alright.  It's an added level of complexity that shouldn't be required,
since we're all working on the *unstable* portion of the distribution
anyway... I think some of the issues that arise are due to the slow
release cycle causing folks to run unstable as their daily-use machines
and once that becomes commonplace, the quality level of unstable has to
be higher than it really should need to be by design.

Thanks for the feedback.  You straightened out one of my misconceptions
about how the sponsorship system's working.

-- 
Nate Duehr <nate@natetech.com>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.

Attachment: pgpJDMuXrAZgG.pgp
Description: PGP signature


Reply to: