On Sun, May 13, 2012 at 8:59 AM, Steve Langasek wrote:
> On Sat, May 12, 2012 at 09:32:33AM +0200, Sandro Tosi wrote:
>> On Sat, May 12, 2012 at 3:34 AM, Michael Gilbert wrote:
>> > I wonder if the core issue at hand here is simply that the python VCSs
>> > are on a resource writable by only one
On Sat, May 12, 2012 at 09:32:33AM +0200, Sandro Tosi wrote:
> On Sat, May 12, 2012 at 3:34 AM, Michael Gilbert wrote:
> > I wonder if the core issue at hand here is simply that the python VCSs
> > are on a resource writable by only one person (meaning no one else can
> > contribute)? See:
> > ht
Hello Michael,
On Sat, May 12, 2012 at 3:34 AM, Michael Gilbert wrote:
> I wonder if the core issue at hand here is simply that the python VCSs
> are on a resource writable by only one person (meaning no one else can
> contribute)? See:
> https://code.launchpad.net/~doko/python/pkg2.7-debian
> h
I wonder if the core issue at hand here is simply that the python VCSs
are on a resource writable by only one person (meaning no one else can
contribute)? See:
https://code.launchpad.net/~doko/python/pkg2.7-debian
https://code.launchpad.net/~doko/python/pkg3.2-debian
If that's the case, then perh
On Sat, Apr 28, 2012 at 21:36, Jakub Wilk wrote:
> * Russ Allbery , 2012-04-27, 20:20:
>> Stefano Zacchiroli writes:
> [...]
>>>
>>> Considering the potential incompatibilities, it seems that the possible
>>> maintenance "teams" boil down to:
>>>
>>> - a maintenance team formed by Sandro
>>> - a
On Fri, Apr 27, 2012 at 08:20:33PM -0700, Russ Allbery wrote:
> > Considering the potential incompatibilities, it seems that the possible
> > maintenance "teams" boil down to:
> > - a maintenance team formed by Sandro
> > - a maintenance team formed by Matthias and Barry
> > - a maintenance team f
* Russ Allbery , 2012-04-27, 20:20:
Stefano Zacchiroli writes:
[...]
Considering the potential incompatibilities, it seems that the
possible maintenance "teams" boil down to:
- a maintenance team formed by Sandro
- a maintenance team formed by Matthias and Barry
Did Matthias even express h
On Apr 28, 2012, at 04:34 PM, Stefano Zacchiroli wrote:
>Barry is fine in joining the current "team", Jakub is not. (Of course
>they can provide different indications here, but that's my understanding
>of the situation at the time of last interactions with them.)
I would be fine joining a team wi
On Sat, Apr 28, 2012 at 01:00:16PM +0200, Andreas Barth wrote:
> If neither Barry nor Jakub would support removing Matthias as a
> maintainer, would there be the possiblity of both of them joining the
> maintainer team? (Barry, Jakub, Matthias: comments on that are
> appreciated - after all, if the
* Stefano Zacchiroli (lea...@debian.org) [120428 10:45]:
> On Fri, Apr 27, 2012 at 08:20:33PM -0700, Russ Allbery wrote:
> > This does, to me, raise the question of whether Jakub should be listed as
> > a separate option, or whether there's no meaningful distinction between a
> > maintenance team f
On Fri, Apr 27, 2012 at 08:20:33PM -0700, Russ Allbery wrote:
> This does, to me, raise the question of whether Jakub should be listed as
> a separate option, or whether there's no meaningful distinction between a
> maintenance team formed by Jakub and a maintenance team formed by Matthias
> and Ba
Stefano Zacchiroli writes:
> Not having heard other options, I've proceed with the verification
> mentioned above. Everything has happened publicly and is hence available
> for your review starting from [1]. My own conclusions on the potential
> teams, based on that thread have been posted on li
On Tue, Mar 20, 2012 at 02:46:58PM -0700, Russ Allbery wrote:
> Stefano Zacchiroli writes:
> > If the Technical Committee welcome that, I'll be happy to take the
> > burden of verifying (publicly, and on -python) who would be willing, at
> > present, to be part of an alternative Python maintenance
Sandro Tosi writes:
> On Mon, Mar 19, 2012 at 05:57, Russ Allbery wrote:
>> I would like this to not slip back into limbo again, since it's clear
>> that the problem is neither going to go away nor is provoking any
>> substantively new discussion. I think we should take some time to
>> craft a
Hello Russ,
On Mon, Mar 19, 2012 at 05:57, Russ Allbery wrote:
> I would like this to not slip back into limbo again, since it's clear that
> the problem is neither going to go away nor is provoking any substantively
> new discussion. I think we should take some time to craft a reasonable
> ball
Stefano Zacchiroli writes:
> On Sun, Mar 18, 2012 at 09:57:02PM -0700, Russ Allbery wrote:
>> D. The Technical Committee exercises our power under 6.1.2 of the
>>Constitution to designate:
>>
>> - Luca Falavigna
>> - Josselin Mouette
>> - Sandro Tosi
>> - Bernd Zeimetz
>>
Andreas Barth writes:
> You think it's worse than just orphan the package now and/or ask the DPL
> to choose a new maintainer? (I would say it's the least agressive one of
> the variants that do require a change of the maintainer, as Matthias has
> some say of the new maintainer team as long as i
* Russ Allbery (r...@debian.org) [120319 22:27]:
> Andreas Barth writes:
>
> > How about:
>
> > BC. The Technical Committee have been petitioned to decide on the
> > maintainership of the python packes. We agree with the substance of
> > the complaint, but do not feel able to directly s
Andreas Barth writes:
> How about:
> BC. The Technical Committee have been petitioned to decide on the
> maintainership of the python packes. We agree with the substance of
> the complaint, but do not feel able to directly select the replacement
> maintainers. Therefore:
>
>
* Russ Allbery (r...@debian.org) [120319 06:00]:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573745#335
>
> B. The Technical Committee have been petitioned to decide on the
>maintainership of the python packes. We agree with the substance of
>the complaint, but do not feel able to
Okay, this isn't going to make anyone happy, but here goes.
I don't think anything new is happening with this bug, and while I've
argued in the past that keeping things like this open for a while to see
what happens can be useful, I think we've long passed the point of that
here. We need to not l
On Tue, Nov 22, 2011 at 14:56, Sandro Tosi wrote:
> ping
2-years-old ping
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
ping
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.o
* Russ Allbery (r...@debian.org) [100706 08:02]:
> This is a community, cooperative project. That means that getting along
> with fellow developers *is actual work*, and is as important in some cases
> as the technical work expressed in the packages that we upload.
It's even worse: Within the rel
* Sandro Tosi (mo...@debian.org) [100706 00:24]:
> Ok, probably I didn't express myself clearly enough. you are talking
> about the future, when python will have co-maintainers
> (python*-default already has them), am I correct? I was referring
> instead to the current situation where python*-defau
* Ian Jackson (ijack...@chiark.greenend.org.uk) [100705 19:13]:
> Andreas Barth writes ("Re: Bug#573745: Please decide on Python interpreter
> packages maintainership"):
> > * Ian Jackson (ijack...@chiark.greenend.org.uk) [100705 15:02]:
> > > I wrote:
> >
* Ian Jackson (ijack...@chiark.greenend.org.uk) [100705 15:02]:
> I wrote:
> > I don't think we are considering adding an additional layer of
> > management. Currently the person in charge is Matthias; he is the
> > maintainer of python2.6 et al.[1]
Plus Scott Kitterman and Piotr Ożarowski.
> >
Sandro Tosi writes ("Re: Bug#573745: Please decide on Python interpreter
packages maintainership"):
> Also, an additional level of "management" has to be well received from
> who has to be managed: are we really sure Matthias will follow even
> controversial decisi
Hello,
I'm going to reply to some of the more recent emails of this thread:
please consider this as a personal reply, not meant to represent the
feelings/ideas of other original signers of this appeal.
On Wed, May 12, 2010 at 23:28, Andreas Barth wrote:
> * Josselin Mouette (j...@debian.org) [100
Hi,
As shown clearly in the past years, Python cannot be maintained by a
single developer, so I do think it should be maintain within a team to
allow fixes and new versions of upstream Python to be pushed
quickly. Therefore, I strongly second Sandro proposition.
Regards,
Arnaud
* Bdale Garbee (bd...@gag.com) [100318 00:00]:
> It bothers me that what you've brought to the TC is a rant about your
> frustrations culminating in a request to remove someone else from their
> role, rather than a crisper articulation of what's wrong and a plan that
> explains how we should move f
Hello,
we apologize for the delay in our reply.
On Wed, Mar 17, 2010 at 23:50, Bdale Garbee wrote:
> On Sat, 13 Mar 2010 17:24:51 +0100, Sandro Tosi
> wrote:
>> Package: tech-ctte
>> Severity: normal
>>
>> Hello Technical Committee,
>> we'd like you to decide about how the Python interpreter pac
* Piotr Ożarowski (pi...@debian.org) [100318 21:09]:
> [Andreas Barth 2010-03-18]
> > I agree. I tried to get one such meeting done some time ago (see
> > below)
>
> Here's my reply from that thread (Matthias or DPL never
> responsed, or at least I wasn't in the loop)
The DPL was only in the loop
[Andreas Barth 2010-03-18]
> I agree. I tried to get one such meeting done some time ago (see
> below)
Here's my reply from that thread (Matthias or DPL never
responsed, or at least I wasn't in the loop)
[Piotr Ożarowski, 2009-09-27]
> Adding Raphael Hertzog to Cc as he knows the beginning of py
* Bdale Garbee (bd...@gag.com) [100318 00:00]:
> I'm adding the DPL to this reply because it seems possible that the only
> way to achieve this objective might be an in-person Debian Python Summit
> meeting, moderated by members of the TC, where we can work through all
> the issues and come to cons
On Sat, 13 Mar 2010 17:24:51 +0100, Sandro Tosi wrote:
> Package: tech-ctte
> Severity: normal
>
> Hello Technical Committee,
> we'd like you to decide about how the Python interpreter packages
> should be maintained in Debian.
I've spent several hours since my last message communicating with th
Hello,
thanks for the fast reply.
On Sat, Mar 13, 2010 at 21:02, Bdale Garbee wrote:
> On Sat, 13 Mar 2010 17:24:51 +0100, Sandro Tosi wrote:
>> Package: tech-ctte
>> Severity: normal
>>
>> Hello Technical Committee,
>> we'd like you to decide about how the Python interpreter packages
>> should
On Sat, 13 Mar 2010 17:24:51 +0100, Sandro Tosi wrote:
> Package: tech-ctte
> Severity: normal
>
> Hello Technical Committee,
> we'd like you to decide about how the Python interpreter packages
> should be maintained in Debian.
Thank you for bringing this to the Committee's attention. However,
Package: tech-ctte
Severity: normal
Hello Technical Committee,
we'd like you to decide about how the Python interpreter packages
should be maintained in Debian.
The problems that we have with the current situation can mostly
be described by having a look at the way the Python 2.6
transition is be
39 matches
Mail list logo
