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

Re: NM status: separate DAM approval and account creation?



On Mon, Apr 04, 2005 at 11:10:42AM +0200, Steffen Moeller wrote:
> With > a year waiting time to become a developer, the maintainer of a
> package is likely to ask several times for sponsored uploads of new upstream
> version of his/her same package(s). Comments on the first packaging of some
> software are most helpful and - analogous to kernel patches - I am
> likely to continue asking my peers for comments prior to upload once I
> am accepted. With quite some packages in Debian already, though, the
> number of new upstream versions to go through a sponsoring becomes a
> burden. Maybe more importantly, the extra efforts annoy the sponsors,
> that do not even have a say in the NM process beyond initial advocation.
> 
> My way around this is to delay uploads whenever possible. Newer versions
> do not make it to my sponsors unless somebody complains or I find the
> upstream change of particular importance. Little changes to the packages I
> will not do untill I am accepted. I do not need a full account, really. I
> do not even need to do NMUs or the upload of novel packages.
> 
> Since my response time to requests particularly in the BTS is something
> the DAM evaluates for my acceptance, my behaviour may be a bit
> counterproductive. It should not be too bad, though.

I try to only ask my sponsor for an upload with every new upstream version
or very evil bugs(only once, touch wood), everything else waits. I do hope
that "knowing when to bother a busy sponsor" is a quality looked for in
potential DDs.

-- 
Brian Sutherland

It's 10 minutes, 5 if you walk fast.



Reply to: