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

Re: python-xlrd

On Wed, Feb 6, 2013 at 10:24 PM, Thomas Kluyver <thomas@kluyver.me.uk> wrote:
> On 6 February 2013 19:30, Sandro Tosi <sandro.tosi@gmail.com> wrote:
>> please read our "unwritten policy" about Maintainer field at
>> http://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin
> "As a general rule of thumb, just set Maintainer to the team; there might be
> some exceptions, like in situations where the package is so complex that a
> check from a knowledgeable person is welcome before an upload but they are
> very rare."
> This is pretty much what I mean, but I think we should strengthen it a bit
> from what I think the current case is. Namely, if someone does an RFS for a
> package with themselves set as the Maintainer, the reviewer should encourage
> them to put the team there instead. Maybe reviewers are already doing that,
> although I don't remember seeing it.

if you deliberately skip the other part of my reply, you'd miss a
relevant rebuttal to your reasoning that having the team as maintainer
is always and will fix all the problems regarding desappearing
maintainers and team members doing changes to packages and then stop
caring about it.

> It's two months in which someone has to e-mail Thomas B several times, and
> in which what I've done will fall out of my memory. Maybe I'll forget about
> it by April, and someone will end up redoing the work. Maybe my laptop will
> kick the bucket in the meantime, and the changes that I couldn't commit to
> the centralised VCS will be lost. (Although in this case, they're in my PPA
> [1])

submit a but report with a patch attached

Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Reply to: