Re: Maintainership

Le vendredi, 2 décembre 2016, 16.00:36 h CET Ian Jackson a écrit : > On debian-project I posted a suggestion in respose to Zach in the > thread about maintaintainership. See below. I've answered to parts of the debian-project thread. > Do the TC think a resolution such as that below would pass

Re: Maintainership

Ian Jackson writes: > On debian-project I posted a suggestion in respose to Zach in the > thread about maintaintainership. See below. > > Do the TC think a resolution such as that below would pass ? > > Supposing such a resolution were passed, would it make a

Maintainership

016 15:42:58 + Stefano Zacchiroli writes ("Re: Replace the TC power to depose maintainers"): > On Thu, Dec 01, 2016 at 03:46:05PM +, Ian Jackson wrote: > > 3. Abolish maintainership entirely. > > This is the obviously right solution. Hey, I have an idea that maybe

Bug#573745: marked as done (Please decide on Python interpreter packages maintainership)

Your message dated Fri, 5 Oct 2012 12:03:32 -0700 with message-id 20121005190332.ge8...@rzlab.ucr.edu and subject line Re: Bug#573745: Call for votes on Python Maintainer Question has caused the Debian Bug report #573745, regarding Please decide on Python interpreter packages maintainership

Bug#573745: Please decide on Python interpreter packages maintainership

On Sat, May 12, 2012 at 09:32:33AM +0200, Sandro Tosi wrote: On Sat, May 12, 2012 at 3:34 AM, Michael Gilbert mgilb...@debian.org 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)?

Re: Bug#573745: Please decide on Python interpreter packages maintainership

On Sun, May 13, 2012 at 8:59 AM, Steve Langasek vor...@debian.org 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 mgilb...@debian.org wrote: I wonder if the core issue at hand here is simply that the python VCSs are on a

Re: Bug#573745: Please decide on Python interpreter packages maintainership

Hello Michael, On Sat, May 12, 2012 at 3:34 AM, Michael Gilbert mgilb...@debian.org 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:

Bug#573745: Please decide on Python interpreter packages maintainership

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

Bug#573745: Please decide on Python interpreter packages maintainership

On Sat, Apr 28, 2012 at 21:36, Jakub Wilk jw...@debian.org wrote: * Russ Allbery r...@debian.org, 2012-04-27, 20:20: Stefano Zacchiroli lea...@debian.org writes: [...] Considering the potential incompatibilities, it seems that the possible maintenance teams boil down to: - a maintenance

Bug#573745: Please decide on Python interpreter packages maintainership

* 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 formed

Bug#573745: Please decide on Python interpreter packages maintainership

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

Bug#573745: Please decide on Python interpreter packages maintainership

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 with

Bug#573745: Please decide on Python interpreter packages maintainership

On Tue, Mar 20, 2012 at 02:46:58PM -0700, Russ Allbery wrote: Stefano Zacchiroli lea...@debian.org 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

Bug#573745: Please decide on Python interpreter packages maintainership

Stefano Zacchiroli lea...@debian.org 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

Bug#573745: Please decide on Python interpreter packages maintainership

Hello Russ, On Mon, Mar 19, 2012 at 05:57, Russ Allbery r...@debian.org 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

Re: Bug#573745: Please decide on Python interpreter packages maintainership

On Sun, Mar 18, 2012 at 09:57:02PM -0700, Russ Allbery wrote: Okay, this isn't going to make anyone happy, but here goes. Thanks. D. The Technical Committee exercises our power under 6.1.2 of the Constitution to designate: - Luca Falavigna dktrkr...@debian.org - Josselin

Re: Bug#573745: Please decide on Python interpreter packages maintainership

On Mon, Mar 19, 2012 at 03:26:50PM -0700, Russ Allbery wrote: Andreas Barth a...@ayous.org 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

Bug#573745: Please decide on Python interpreter packages maintainership

Stefano Zacchiroli lea...@debian.org 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 dktrkr...@debian.org - Josselin Mouette j...@debian.org -

Bug#573745: Please decide on Python interpreter packages maintainership

* 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

Bug#573745: Please decide on Python interpreter packages maintainership

Andreas Barth a...@ayous.org 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

Bug#573745: Please decide on Python interpreter packages maintainership

* Russ Allbery (r...@debian.org) [120319 22:27]: Andreas Barth a...@ayous.org 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

Bug#573745: Please decide on Python interpreter packages maintainership

Andreas Barth a...@ayous.org 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

Bug#573745: Please decide on Python interpreter packages maintainership

On Tue, Nov 22, 2011 at 14:56, Sandro Tosi mo...@debian.org 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

Bug#573745: Please decide on Python interpreter packages maintainership

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-ctte-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Bug#573745: Please decide on Python interpreter packages maintainership

Sandro Tosi mo...@debian.org writes: On Tue, Jul 6, 2010 at 05:22, Russ Allbery r...@debian.org wrote: I agree with the statement that maintainers of those packages need to be active in these discussions and be clear about what their requirements are and not block other work that's going on

Bug#573745: Please decide on Python interpreter packages maintainership

* 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*-default

Re: Bug#573745: Please decide on Python interpreter packages maintainership

would hand the maintainership of these packages to the new team. We still don't have a new team. The only coherent team that has been suggested has been the four people who emailed the TC to start with. As they wrote: Luca Falavigna Josselin Mouette Sandro Tosi Bernd Zeimetz

Re: Bug#573745: Please decide on Python interpreter packages maintainership

* 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: I don't think we are considering adding

Re: Bug#573745: Please decide on Python interpreter packages maintainership

Russ Allbery r...@debian.org writes: I'm disturbed by the tone of some of the recent traffic which seems to imply that Matthias must either personally respond to people's e-mail or be completely removed from any role with the Python packages in order for this complaint to be satisfied. To be

Re: Bug#573745: Please decide on Python interpreter packages maintainership

Hi all, I'll reply to all emails here, just to not spam that much the list. On Mon, Jul 5, 2010 at 14:44, Ian Jackson ijack...@chiark.greenend.org.uk wrote: Sandro Tosi writes (Re: Bug#573745: Please decide on Python interpreter packages  maintainership): Also, an additional level

Re: Bug#573745: Please decide on Python interpreter packages maintainership

Sandro Tosi mo...@debian.org writes: On Mon, Jul 5, 2010 at 23:50, Russ Allbery r...@debian.org wrote: Russ Allbery r...@debian.org writes: I'm disturbed by the tone of some of the recent traffic which seems to imply that Matthias must either personally respond to people's e-mail or be

Re: Bug#573745: Please decide on Python interpreter packages maintainership

Hi Russ, On Tue, Jul 6, 2010 at 00:12, Russ Allbery r...@debian.org wrote: Sandro Tosi mo...@debian.org writes: On Mon, Jul 5, 2010 at 23:50, Russ Allbery r...@debian.org wrote: Russ Allbery r...@debian.org writes: I'm disturbed by the tone of some of the recent traffic which seems to imply

Re: Bug#573745: Please decide on Python interpreter packages maintainership

Sandro Tosi mo...@debian.org writes: 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? Right, yes. I was referring instead to the current situation where

Re: Bug#573745: Please decide on Python interpreter packages maintainership

On Tue, Jul 06, 2010 at 12:00:53AM +0200, Sandro Tosi wrote: I'm disturbed by the tone of some of the recent traffic which seems to imply that Matthias must either personally respond to people's e-mail or be completely removed from any role with the Python packages in order for this

Re: Bug#573745: Please decide on Python interpreter packages maintainership

him for it directly. I don't think it's reasonable to require Matthias to give a general response to a broad-ranging attack on his maintainership of the Python packages as input to the TC's decisionmaking process. -- Steve Langasek Give me a lever long enough and a Free OS Debian

Re: Bug#573745: Please decide on Python interpreter packages maintainership

- as it should be.) ah so the maintainership is reduced to a please release a new package button? :) what you describe it ALL that he did for the transition. I don't call it helping, I call it passive blocking it, personally I'd expect more from him: are you really fine with a superb maintainer

Re: Bug#573745: Please decide on Python interpreter packages maintainership

to adopt the same technique. So you think the only acceptable option is to take away the maintainership from Matthias? And even if we would do that, how can we be sure that this resolves all the issues we have? Let's turn this way: we already know what it's like with him maintaining python

Bug#573745: Please decide on Python interpreter packages maintainership

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

Bug#573745: Please decide on Python interpreter packages maintainership

* 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

Bug#573745: Please decide on Python interpreter packages maintainership

Hello, we apologize for the delay in our reply. On Wed, Mar 17, 2010 at 23:50, Bdale Garbee bd...@gag.com wrote: On Sat, 13 Mar 2010 17:24:51 +0100, Sandro Tosi mo...@debian.org wrote: Package: tech-ctte Severity: normal Hello Technical Committee, we'd like you to decide about how the

Re: Bug#573745: Please decide on Python interpreter packages maintainership

On Thu, Mar 18, 2010 at 10:31:03PM +0100, Andreas Barth wrote: * 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

Bug#573745: Please decide on Python interpreter packages maintainership

[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

Bug#573745: Please decide on Python interpreter packages maintainership

* 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 for

Bug#573745: Please decide on Python interpreter packages maintainership

On Sat, 13 Mar 2010 17:24:51 +0100, Sandro Tosi mo...@debian.org 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

Bug#573745: Please decide on Python interpreter packages maintainership

. Therefore, we.d like to move the maintainership of pythonX.Y* (interpreters and related packages) and python-defaults (due to its specific role in the Python environment) packages to a team of people that already showed their involvement in Python in Debian, their ability to work in a team

Bug#573745: Please decide on Python interpreter packages maintainership

On Sat, 13 Mar 2010 17:24:51 +0100, Sandro Tosi mo...@debian.org 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.

Bug#573745: Please decide on Python interpreter packages maintainership

Hello, thanks for the fast reply. On Sat, Mar 13, 2010 at 21:02, Bdale Garbee bd...@gag.com wrote: On Sat, 13 Mar 2010 17:24:51 +0100, Sandro Tosi mo...@debian.org wrote: Package: tech-ctte Severity: normal Hello Technical Committee, we'd like you to decide about how the Python interpreter

Functionality of the committee, and maintainership disputes

Many of you will have already seen that I have decided to unilaterally re-add myself to the list of dpkg maintainers and unilaterally remove Guillem Jover. My reasons are explained in that mail there and I don't want to go into them in detail here. But there are two issues that are relevant to

Re: Functionality of the committee, and maintainership disputes

On Sun, Mar 09, 2008 at 12:17:18PM +, Ian Jackson wrote: Firstly, I think the committee is not doing its job. I've been very frustrated with the lack of progress. I think we need to fix this. I'm all ears for suggestions but I think more is needed than promises to try harder. One