Re: Bug#573745: ping

2011-03-09 Thread Ian Jackson
Steve Langasek writes ("Re: Bug#573745: ping"): > Do you mean that you would get a *private* ack from the current maintainer, > but no public one? I am assuming that we are likely to get no ack at all. > As commented in my previous mail, I don't believe that a maintenance *team* > can be formed w

Re: Bug#573745: ping

2011-03-09 Thread Stefano Zacchiroli
On Wed, Mar 09, 2011 at 12:56:34PM -0800, Steve Langasek wrote: > Do you mean that you would get a *private* ack from the current > maintainer, but no public one? But as long as we have the current > maintainer's agreement (in whatever form), this concern is null. I didn't mean to imply that I ca

Re: Bug#573745: ping

2011-03-09 Thread Steve Langasek
On Wed, Mar 09, 2011 at 07:18:16PM +0100, Stefano Zacchiroli wrote: > Fair enough, I'll consider starting myself a discussion about a > potential Python maintenance team on -python. It's still only a > "consider" as the tricky part is that, for various reasons already > mentioned in this bug log,

Bug#573745: ping

2011-03-09 Thread Ian Jackson
Stefano Zacchiroli writes ("Bug#573745: ping"): > Let's assume for a moment (very hypothetically!) that a team can be > found which both includes the current maintainer and has rough consensus > on -python. Would the CTTE be willing to establish such a team as > Python interpreter maintainers, eve

Bug#573745: ping

2011-03-09 Thread Stefano Zacchiroli
On Sat, Mar 05, 2011 at 11:55:06AM -0800, Russ Allbery wrote: > I think, and have for some time, that the ideal situation would be a > maintenance team that includes Matthias (assuming that Matthias still > cares deeply about the Python packaging and wants to continue to > participate). If such a