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

Handling of sponsorship requests



Hello list,

as sponsor I realy welcome the decission and changes to handle
sponsoring requests about our bugtracker, but there are still two
questions/disadvantages from my side:

a) How should we handle requests, where the maintainer *may* be MIA?
Just for an example #658114 - a realy simple question is unanswered for
about 6 months!
IMO they should be pinged one more time, maybe they have overseen the
response, but if I want to see a package in Debian, I would track it, so
I also would see such "maintainers" as possible MIA candidates just
after their first uploads. So on they may be not qualified to maintain
packages/bugs within a distribution.

b) Should we assume that the uploader is aware about freeze and realy
delay typical "new upstream release" uploads to unstable? IMO I do not
think so. The process is a bit more complicated but it is still possible
to update testing packages without unstable upoads.
Surely it is not the cleanest way but sponsorship requests should be
processed :)


Personaly I would not sponsor packages in the a) case, so on I think
they should be closed and some more active and interested mentor could
do this job.

b) is controverse when testing is freezed, but the number of requests
will just grow and grow! Maybe also some warning to the uploader like
"we are frozen, please only upload important bugfixes to sid if
required, if not please use experimental"

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatthaei@debian.org
        patrick@linux-dev.org
*/

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: