Path: csiph.com!goblin3!goblin2!goblin.stu.neva.ru!aioe.org!bofh.it!news.nic.it!robomod
From: Sandro Tosi <morph@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: Maintainer vs. Uploaders
Date: Wed, 30 Sep 2015 11:30:02 +0200
Message-ID: <qelS2-Ol-11@gated-at.bofh.it>
References: <qe1gC-53J-13@gated-at.bofh.it> <qe1gC-53J-11@gated-at.bofh.it> <qe3s8-85D-57@gated-at.bofh.it> <qe4eu-Oh-33@gated-at.bofh.it>
Old-Return-Path: <sandro.tosi@gmail.com>
MIME-Version: 1.0
Sender: robomod@news.nic.it
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Approved: robomod@news.nic.it
Lines: 59
Organization: linux.* mail to news gateway
Xref: csiph.com linux.debian.maint.python:7366

On Tue, Sep 29, 2015 at 3:30 PM, Piotr O=C5=BCarowski <piotr@debian.org> wr=
ote:
> [Barry Warsaw, 2015-09-29]
>> How should the change be acknowledged by the
>> maintainer?  Should I Cc the mailing list when I contact the maintainer?=
  Is
>
> do we really need a written policy how to contact fellow co-maintainer?
> Ping on IRC, send an email, send a message via xmpp or phone, ... use
> whatever you usually use to contact any other Debian maintainer.
>
> An example message:
> "I just commited some changes in foo related to bar. Please take a look,
> I plan to upload it to unstable in a day or two. Let me know if I should
> wait a bit longer or if you're not OK with these changes. Thanks"
>
> I think such message to all Uploaders who clearly know more about given
> package than I do is a good practice even if team is listed in
> Maintainer field. I don't think sending such message after fixing a typo
> is needed, but it's definitely a must when someone replaces dh with
> cdbs or vice versa.
>
>> it okay to commit to vcs but not upload?  How long do you wait for feedb=
ack
>> before you can do the upload?
>
> yes, it's always OK to commit changes (which can be reverted). It's not O=
K
> to force someone else to maintain these changes by uploading it.
>
>> Should we have some automated tools to help out here?  I'm not sure wher=
e to
>
> no, we already have -commits mailing list which nobody reads. Yet
> another reason why team should be in Uploaders and not in Maintainer
> field.
>
>> Do all team members understand the implications when they set the two fi=
elds?
>> Some maintainers may not really care and may have been less conscientiou=
s
>> about setting the fields.
>
> Maintainer vs Uploaders rules needs to be moved to policy. I will
> propose a patch to the policy soon (I'd prefer a native speaker to do
> it, though)
>
>> The wiki says that the general rule of thumb is to set the team as Maint=
ainer,
>> to which I agree.
>
> I don't (due to "package and forget" issue)

+1 on everything you wrote

--=20
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi