Re: [DPMT] radical changes: automation, carrot and stick

On Fri, 2015-10-02 at 09:12 -0700, Nikolaus Rath wrote: > I always assumed that it was generally preferred to have Python > packages be maintained in the Python team, even if the maintainer has > little interest or time in contributing to other Python packages. Same here. I have a few packages in

Re: [DPMT] radical changes: automation, carrot and stick

I no longer think requiring contribution (the 3 months thing) is a good idea for DPMT (might be for a new team). I assume you all like other ideas, like no team in Maintainer, right? -- evil Piotr

Re: [DPMT] radical changes: automation, carrot and stick

On Wed, 2015-10-07 at 14:18 +0200, Piotr Ożarowski wrote: > I assume you all like other ideas, like no team in Maintainer, right? I kind of liked the differentiation between the two options: - I'm the primary maintainer and welcome other people working on my    packages (me in Maintainer, team

Re: [DPMT] radical changes: automation, carrot and stick

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-07 14:18, Piotr Ożarowski wrote: > I no longer think requiring contribution (the 3 months thing) is a > good idea for DPMT (might be for a new team). > > I assume you all like other ideas, like no team in Maintainer, > right? if that's

Re: [DPMT] radical changes: automation, carrot and stick

On Oct 07 2015, Piotr Ożarowski wrote: > I no longer think requiring contribution (the 3 months thing) is a good > idea for DPMT (might be for a new team). > > I assume you all like other ideas, like no team in Maintainer, right? > > * team only in Uploaders field, the main

Re: [DPMT] radical changes: automation, carrot and stick

On Wed, 07 Oct 2015, Piotr Ożarowski wrote: > I assume you all like other ideas, like no team in Maintainer, right? While I understand the desire to have one identified maintainer for each package, I don't agree with the rule. Changing maintainer means changing the flow of information and it is

Re: [DPMT] radical changes: automation, carrot and stick

On Sunday, October 04, 2015 11:54:18 PM Stefano Rivera wrote: >There's a fundamental question to ask here. Do we want to welcome Python >packages into the team, or do we want to put up barriers and require a >level of commitment before packages can be brought into the team? Thanks Stefano for

Re: [DPMT] radical changes: automation, carrot and stick

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-02 10:30, Piotr Ożarowski wrote: > it's 3 months to contribute to other packages (the ones where > you're not listed in Maintainer). hmm. if i - hypthotically, because i really currently do not - cared a so much about e.g. 30 DPMT

Re: [DPMT] radical changes: automation, carrot and stick

On Sunday, October 04, 2015 11:54:18 PM Stefano Rivera wrote: > This thread has had me thinking a bit. > > Hi Scott (2015.10.02_20:34:16_+0200) > > > Personally, I like the current approach where someone can either commit to > > either strong team maintainership (DPMT in maintainer) or weak team

Re: [DPMT] radical changes: automation, carrot and stick

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-10-02 18:12, Nikolaus Rath wrote: > On Oct 02 2015, Piotr Ożarowski wrote: >> I think that the main problem of our team is that we have over >> 300 members and only few people contribute to packages they >> didn't inject

Re: [DPMT] radical changes: automation, carrot and stick

This thread has had me thinking a bit. Hi Scott (2015.10.02_20:34:16_+0200) > Personally, I like the current approach where someone can either commit to > either strong team maintainership (DPMT in maintainer) or weak team > involvement (DPMT as uploader). If you'll check, I have done both and

Re: [DPMT] radical changes: automation, carrot and stick

On Mon, 5 Oct 2015 at 08:54 Stefano Rivera wrote: > There's a fundamental question to ask here. Do we want to welcome Python > packages into the team, or do we want to put up barriers and require a > level of commitment before packages can be brought into the team?

Re: [DPMT] radical changes: automation, carrot and stick

[Elena ``of Valhalla'', 2015-10-02] > +1: I also have packages that get new upstream releases very rarely (<1 > per year): they are not dead, just very stable and with limited scope, > so there is no need to work often on them. well, then you will not gain much from maintaining this package

Re: [DPMT] radical changes: automation, carrot and stick

On 2015-10-02 at 10:19:10 +0200, Vincent Bernat wrote: > ❦ 2 octobre 2015 09:41 +0200, Piotr Ożarowski  : > > * removal¹ of packages (not person) from the team if there's no > > contribution in 3 months in a row and no other team wants to take over > > given package > 3

Re: [DPMT] radical changes: automation, carrot and stick

❦ 2 octobre 2015 10:30 +0200, Piotr Ożarowski  : >> ❦ 2 octobre 2015 09:41 +0200, Piotr Ożarowski  : >> >> > * removal¹ of packages (not person) from the team if there's no >> > contribution in 3 months in a row and no other team wants to take over >> >

Re: [DPMT] radical changes: automation, carrot and stick

[Piotr Ożarowski, 2015-10-02] > * removal¹ of packages (not person) from the team if there's no > contribution in 3 months in a row and no other team wants to take over > given package or a warning after month of inactivity and team removal from all packages if number_of_commits_in_a_year /

Re: [DPMT] radical changes: automation, carrot and stick

On 2015-10-02 at 11:28:04 +0200, Piotr Ożarowski wrote: > [Elena ``of Valhalla'', 2015-10-02] > > +1: I also have packages that get new upstream releases very rarely (<1 > > per year): they are not dead, just very stable and with limited scope, > > so there is no need to work often on them. >

Re: [DPMT] radical changes: automation, carrot and stick

❦ 2 octobre 2015 09:41 +0200, Piotr Ożarowski  : > * removal¹ of packages (not person) from the team if there's no > contribution in 3 months in a row and no other team wants to take over > given package 3 months is quite short. I have packages that don't get updates that

Re: [DPMT] radical changes: automation, carrot and stick

On 10/02/2015 01:18 AM, Piotr Ożarowski wrote: > I think that the main problem of our team is that we have over 300 > members and only few people contribute to packages they didn't inject to > the repo (some people do not care even about those). Impressive that you write this after kicking me for

Re: [DPMT] radical changes: automation, carrot and stick

[Piotr Ożarowski, 2015-10-02] > * adding a package to the team (and getting all benefits, like > sponsoring, bug fixes, etc.) requires pushing at least one commit to > package without member's name in debian/control a month > (doesn't matter if it's a typo fix, RC bug fix or a tag which can