[Python-Dev] Two small PEP ideas
Georg Brandl
g.brandl at gmx.net
Wed May 5 03:40:45 CEST 2010
Am 03.05.2010 18:40, schrieb Guido van Rossum:
> On Mon, May 3, 2010 at 8:57 AM, Barry Warsaw <barry at python.org> wrote:
>> On May 01, 2010, at 07:12 AM, Martin v. Löwis wrote:
>>
>>>> IIRC in the IETF this is done by the committee chair. I think it's a
>>>> good idea to have this be a single person to avoid endless indecision.
>>>
>>>It then seems that this role should go to the release manager of the
>>>upcoming feature release. Assuming Georg can accept this additional
>>>responsibility.
>>
>> I do think it makes sense for the RM to assume these responsibilities where
>> Guido either can't or doesn't want to make the final decision. I think it
>> will fairly substantially increase the workload on the RM, so perhaps there
>> are ways to off-load some of the current responsibilities (e.g. updating the
>> website for each release). I also think that RMs should be term-limited so
>> that we can spread more experience within the community. And past-RMs can
>> provide a sort of consultation group where contentious decisions can be
>> discussed and advice gathered.
>
> While I certainly won't object if a release manager volunteers to also
> be the final PEP arbiter, I don't want to make it a job requirement
> (or even an implied expectation). The responsibility of a release
> manager is very much in the here and now and the near future --
> stability and consistency of the current release. Being PEP arbiter
> requires a somewhat different mindset, more focused on the long-term
> health of the language and its community.
I agree, and I wouldn't want to make these decisions. That person (or
group) needs to have some weight in the community, or there will be a
feeling of "... and who is he to decide anyway". We haven't emphasized
RMship in the past; it's not a special position, except when something
about a release goes wrong and blame must be placed ;) I think, being
Guido, you are still the best single person to do this job.
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.
More information about the Python-Dev
mailing list