Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod From: Barry Warsaw Newsgroups: linux.debian.maint.python Subject: Re: [DPMT] radical changes: automation, carrot and stick Date: Fri, 02 Oct 2015 16:40:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Oct 2 14:36:00 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.9 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -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/12733 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20151002103543.238dafe2@limelight.wooz.org Approved: robomod@news.nic.it Lines: 23 Sender: robomod@news.nic.it X-Original-Date: Fri, 2 Oct 2015 10:35:43 -0400 X-Original-Message-ID: <20151002103543.238dafe2@limelight.wooz.org> X-Original-References: <20151001231800.GC3965@p1otr.com> <20151002074118.GD3965@p1otr.com> <87k2r565tt.fsf@zoro.exoscale.ch> <20151002084710.GA5056@virginsteele.home.trueelena.org> <20151002092804.GU6768@sar0.p1otr.com> Xref: csiph.com linux.debian.maint.python:7422 On Oct 02, 2015, at 11:28 AM, Piotr O=C5=BCarowski wrote: >well, then you will not gain much from maintaining this package within a >team It's not just the maintainer that wins by maintaining the package within the team. The team also wins because it is now empowered to fix problems when = the need arises. That's what being in a team is about - I can help when I have the need, time, interest, and ability, and you can do the same, within the established and agreed upon rules. That's the heart of collaboration. We've explored the downsides, but I think it's important to also recognize = the upsides to being in a team. Let's not optimize for the worst case scenario. It's good that this thread reiterated the expected best practices for team members -- and we should do that periodically to remind old-timers and info= rm newcomers. Who else remembers those old Usenet group monthly FAQs that used to get posted? Cheers, -Barry