Re: pythonX.Y maintenance team

2012-08-10 Thread Jakub Wilk
* Jakub Wilk , 2012-04-13, 20:24: That said, I don't believe that forcibly changing the maintainer of Python interpreter packages is the correct course of action. I'm not personally happy with the way they are maintainer, but it's not nearly as bad as to justify such action. I have changed my

Re: pythonX.Y maintenance team

2012-05-13 Thread Sandro Tosi
On Mon, May 14, 2012 at 5:41 AM, Scott Kitterman wrote: > You rather miss my point.  Sorry for not being clear.  The point isn't that > the current maintenance of the python interpreter packages is great. at least we do agree on something ;) > It's > not.  The point is whining about something tw

Re: pythonX.Y maintenance team

2012-05-13 Thread Scott Kitterman
On Saturday, May 12, 2012 09:46:55 AM Sandro Tosi wrote: > On Fri, Apr 13, 2012 at 3:26 PM, Scott Kitterman wrote: > > On Friday, April 13, 2012 08:37:26 AM Sandro Tosi wrote: > >> On Thu, Apr 12, 2012 at 23:35, Scott Kitterman wrote: > >> > On Thursday, April 12, 2012 11:04:33 PM Sandro Tosi w

Re: pythonX.Y maintenance team

2012-05-12 Thread Sandro Tosi
On Fri, Apr 13, 2012 at 3:26 PM, Scott Kitterman wrote: > On Friday, April 13, 2012 08:37:26 AM Sandro Tosi wrote: >> On Thu, Apr 12, 2012 at 23:35, Scott Kitterman wrote: >> > On Thursday, April 12, 2012 11:04:33 PM Sandro Tosi wrote: >> >> On Thu, Apr 12, 2012 at 22:50, Scott Kitterman > wrote

Re: pythonX.Y maintenance team

2012-04-23 Thread Stefano Zacchiroli
On Tue, Apr 03, 2012 at 10:36:58AM +0200, Stefano Zacchiroli wrote: > Allow me be blunt then: do we have volunteers to maintain the pythonX.Y > packages? Can those volunteers manifest themselves on this list? > I understand there might be incompatibilities that make impossible for > potential volu

Re: pythonX.Y maintenance team

2012-04-14 Thread Scott Kitterman
On Saturday, April 14, 2012 05:12:54 PM Paul Wise wrote: > On Fri, Apr 13, 2012 at 9:26 PM, Scott Kitterman wrote: > > times when the only 'solution' available is a short term hack that's > > needed > > for Ubuntu's time based release schedule that isn't appropriate to > > Debian's > > approach of

Re: pythonX.Y maintenance team

2012-04-14 Thread Paul Wise
On Fri, Apr 13, 2012 at 9:26 PM, Scott Kitterman wrote: > times when the only 'solution' available is a short term hack that's needed > for Ubuntu's time based release schedule that isn't appropriate to Debian's > approach of doing things right and releasing when ready. Why are short term hacks O

Re: pythonX.Y maintenance team

2012-04-13 Thread Jakub Wilk
* Stefano Zacchiroli , 2012-04-12, 11:25: Allow me be blunt then: do we have volunteers to maintain the pythonX.Y packages? Can those volunteers manifest themselves on this list? So, ~10 days later this call, we've two volunteers: Sandro and Barry. If no one else show up, I'll relay the infor

Re: pythonX.Y maintenance team

2012-04-13 Thread Scott Kitterman
On Friday, April 13, 2012 08:37:26 AM Sandro Tosi wrote: > On Thu, Apr 12, 2012 at 23:35, Scott Kitterman wrote: > > On Thursday, April 12, 2012 11:04:33 PM Sandro Tosi wrote: > >> On Thu, Apr 12, 2012 at 22:50, Scott Kitterman wrote: > >> > On Thursday, April 12, 2012 10:20:04 PM Sandro Tosi wr

Re: pythonX.Y maintenance team

2012-04-12 Thread Sandro Tosi
On Thu, Apr 12, 2012 at 23:35, Scott Kitterman wrote: > On Thursday, April 12, 2012 11:04:33 PM Sandro Tosi wrote: >> On Thu, Apr 12, 2012 at 22:50, Scott Kitterman wrote: >> > On Thursday, April 12, 2012 10:20:04 PM Sandro Tosi wrote: >> >> To give a (fresh) example and what I meant above, you c

Re: pythonX.Y maintenance team

2012-04-12 Thread Scott Kitterman
On Thursday, April 12, 2012 11:04:33 PM Sandro Tosi wrote: > On Thu, Apr 12, 2012 at 22:50, Scott Kitterman wrote: > > On Thursday, April 12, 2012 10:20:04 PM Sandro Tosi wrote: > >> To give a (fresh) example and what I meant above, you can try to > >> answer this provocative question: Why Ubuntu

Re: pythonX.Y maintenance team

2012-04-12 Thread Sandro Tosi
On Thu, Apr 12, 2012 at 22:50, Scott Kitterman wrote: > On Thursday, April 12, 2012 10:20:04 PM Sandro Tosi wrote: >> To give a (fresh) example and what I meant above, you can try to >> answer this provocative question: Why Ubuntu has Python 2.7.3 since >> more than 2 days (even before it was publ

Re: pythonX.Y maintenance team

2012-04-12 Thread Scott Kitterman
On Thursday, April 12, 2012 10:20:04 PM Sandro Tosi wrote: > To give a (fresh) example and what I meant above, you can try to > answer this provocative question: Why Ubuntu has Python 2.7.3 since > more than 2 days (even before it was publicly announced) while Debian > is still stuck with a RC, Fin

Re: pythonX.Y maintenance team

2012-04-12 Thread Sandro Tosi
On Thu, Apr 12, 2012 at 16:36, Stefano Zacchiroli wrote: > clarifying what the incompatibilities among the (potential) volunteers > are. >From my side, I don't think i'll have problems working with Barry, but I honestly have to say we had few occasions to work together (that I can remember, there

Re: pythonX.Y maintenance team

2012-04-12 Thread Scott Kitterman
On Thursday, April 12, 2012 09:12:23 PM Sandro Tosi wrote: > On Thu, Apr 12, 2012 at 16:13, Scott Kitterman wrote: > > I don't think that the *-defaults packages and the interpreter packages > > fundamentally require the same maintainer, but I expect it to be > > problematic to have different team

Re: pythonX.Y maintenance team

2012-04-12 Thread Sandro Tosi
On Thu, Apr 12, 2012 at 16:13, Scott Kitterman wrote: > I don't think that the *-defaults packages and the interpreter packages > fundamentally require the same maintainer, but I expect it to be problematic > to have different teams maintain them if each team has the other as a member > as > they

Re: pythonX.Y maintenance team

2012-04-12 Thread Stefano Zacchiroli
On Thu, Apr 12, 2012 at 10:13:02AM -0400, Scott Kitterman wrote: > I will be direct. Thanks! I really appreciate. > So far, the solicitation has been for co-maintainers with morph. I think it > would only be fair to make a similar call for co-maintainers with doko. ... but hold right there :

Re: pythonX.Y maintenance team

2012-04-12 Thread Scott Kitterman
On Thursday, April 12, 2012 11:25:07 AM Stefano Zacchiroli wrote: > On Tue, Apr 03, 2012 at 10:36:58AM +0200, Stefano Zacchiroli wrote: > > Allow me be blunt then: do we have volunteers to maintain the pythonX.Y > > packages? Can those volunteers manifest themselves on this list? > > So, ~10 days

Re: pythonX.Y maintenance team

2012-04-12 Thread Luca Falavigna
Il 03 aprile 2012 10:36, Stefano Zacchiroli ha scritto: > If you volunteered in #573745 already, and you're still available, > please reiterate your availability here. I'm willing to help too, but I would limit by doing grunt work such as bug triaging and cleanup. I know this kind of work could a

Re: pythonX.Y maintenance team

2012-04-12 Thread Stefano Zacchiroli
On Tue, Apr 03, 2012 at 10:36:58AM +0200, Stefano Zacchiroli wrote: > Allow me be blunt then: do we have volunteers to maintain the pythonX.Y > packages? Can those volunteers manifest themselves on this list? So, ~10 days later this call, we've two volunteers: Sandro and Barry. If no one else show

Re: pythonX.Y maintenance team

2012-04-09 Thread Barry Warsaw
On Apr 03, 2012, at 10:36 AM, Stefano Zacchiroli wrote: >Allow me be blunt then: do we have volunteers to maintain the pythonX.Y >packages? Can those volunteers manifest themselves on this list? Apologies for not responding sooner, I was off-line for a while. I have no opinion on how the tech-ct

Re: pythonX.Y maintenance team

2012-04-09 Thread Bernd Zeimetz
Hi, > On Tue, Apr 3, 2012 at 10:36, Stefano Zacchiroli wrote: >> Allow me be blunt then: do we have volunteers to maintain the pythonX.Y >> packages? Can those volunteers manifest themselves on this list? >> >> If you volunteered in #573745 already, and you're still available, >> please reiterat

Re: Bug#573745: pythonX.Y maintenance team

2012-04-06 Thread Russ Allbery
Sandro Tosi writes: > The idea I have of a team is a group of equals, where it doesn't exist a > master and a group of servants, where no-one has a veto on anything if > not for valid technical reasons, where no-one has to ask permission to > upload or to perform any other activities (I'm not tal

Re: pythonX.Y maintenance team

2012-04-06 Thread Sandro Tosi
Hi Stefano, thanks for trying to push it forward. On Tue, Apr 3, 2012 at 10:36, Stefano Zacchiroli wrote: > Allow me be blunt then: do we have volunteers to maintain the pythonX.Y > packages? Can those volunteers manifest themselves on this list? > > If you volunteered in #573745 already, and you

pythonX.Y maintenance team

2012-04-03 Thread Stefano Zacchiroli
Dear all, I'm pretty sure tech-ctte bug #573745 does not need any introduction on this mailing list. The recent news [1] on it is that the tech-ctte seems to be inclined to have a vote on the matter, after having observed that the issue is pretty "stable" now and further spontaneous evolutions ar