Re: Again, seeking advocate
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Simon Law <sfllaw@engmail.uwaterloo.ca> writes:
> On Fri, Apr 04, 2003 at 11:00:11AM +0200, Marcus Brinkmann wrote:
> > On Fri, Apr 04, 2003 at 01:49:09AM -0500, B. Douglas Hilton wrote:
> > > I was at DebConf2 in Toronto last year, and spent about
> > > $1000USD to go there just to get my key signed. I'm a
> > > patient dude, but I want to get in before I die please.
> > >
> > > :-)
> >
> > Frankly, it totally escapes me what is required to become a Debian
> > maintainer, but usually it happens within a couple of years, as far as I
> > know (sometimes even months!).
>
> The wait time has gone down now. Most people get in within a
> year, especially if they are good hackers. I think it only took me 7
> months.
It took me about 12, of which 6-7 were waiting for DAM approval, and
my AM was quite slow (it took him over four months to review my
work--not that I'm complaining).
However, I think that the long wait is a good idea in general, since
it requires sponsoring of your work, which will hopefully pick up any
problems you have. While Michael Banck was sponsoring my packages for
the last six months, his testing of my packages did find some
problems, so it was certainly worthwhile. The wait also demonstrates
that applicants have at least a medium-term level of commitment to the
Project. In my case, I had been maintaining the Debian packages
upstream for over a year prior to my applying, so the NM process
wasn't exactly a challenge.
My only complaint is while awaiting DAM approval, there is absolutely
no feedback about the status of your application, reasons for delay
etc. A single mail could solve that.
- --
Roger Leigh
Printing on GNU/Linux? http://gimp-print.sourceforge.net/
GPG Public Key: 0x25BFB848 available on public keyservers
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 <http://mailcrypt.sourceforge.net/>
iEYEARECAAYFAj6R4iAACgkQVcFcaSW/uEjJ0QCfcxDX5VlpK3+9izTYKmCqfbCp
2J8AnRIMW2p+Ll0/dIqBD6rrw5uzjiC+
=4VRk
-----END PGP SIGNATURE-----
Reply to: