Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Barry Warsaw Newsgroups: linux.debian.maint.python Subject: Re: team vs individual as maintainer (was: radical changes) Date: Wed, 07 Oct 2015 15:30:03 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Oct 7 13:24:16 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5 Organization: The Organization of Unorganized Woozalists X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailing-List: archive/latest/12838 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20151007092359.4b339fb9@limelight.wooz.org Approved: robomod@news.nic.it Lines: 31 Sender: robomod@news.nic.it X-Original-Date: Wed, 7 Oct 2015 09:23:59 -0400 X-Original-Message-ID: <20151007092359.4b339fb9@limelight.wooz.org> X-Original-References: <20151001231800.GC3965@p1otr.com> <878u7luu4j.fsf@thinkpad.rath.org> <1444218873.13176.16.camel@debian.org> <20151007121817.GE6768@sar0.p1otr.com> <20151007143326.Horde.n1qHfeOxlgytNsuomI5iMDp@webmail.in-berlin.de> Xref: csiph.com linux.debian.maint.python:7527 On Oct 07, 2015, at 02:33 PM, W. Martin Borgert wrote: >Quoting Piotr O=C5=BCarowski : >> I assume you all like other ideas, like no team in Maintainer, right? > >To me, "team maintenance" would mean, that the team appears in the >"Maintainer" field. In "Uploaders" it doesn't make sense, so where >would the team appear? > >Personally, I prefer to have the team in "Maintainer" to encourage >others to intervent. > >How about leaving it as is? I.e. people in the team decide what is >more appropriate for a package? I agree. I think the recently restated way of interpreting those two fields made the most sense to me, and gives team members the choice of how to hand= le those packages. * Team in Maintainers is a strong statement that fully collaborative maintenance is preferred. Anyone can commit to the vcs and upload as needed. A courtesy email to Uploaders can be nice but not required. * Team in Uploaders is a weak statement of collaboration. Help in maintain= ing the package is appreciated, commits to vcs are freely welcomed, but before uploading, please contact the Maintainer for the green light. Cheers, -Barry