Eric Araujo (merwok) as Distutils commiter
Hello,
I don't want to maintain Distutils anymore for various reasons. I will focus for now on on Distutils2, shutil and sysconfig.
I would like to propose Eric (merwok on IRC) as a commiter to work on Distutils. He has done a great work in triaging the bugs and also has now a pretty good knowledge of the Distutils code. He's a GSOC student for distutils2 and has done a great coding work in there. I am pretty sure he would love to do this as I did.
If this proposal is accepted, I will ask Eric if he accepts it and wants to work on distutils maintenance, and follow his work until Distutils2 starts to be used.
Regards Tarek
Tarek Ziadé | http://ziade.org
Le mardi 27 juillet 2010 à 01:50 +0200, Tarek Ziadé a écrit :
Hello,
I don't want to maintain Distutils anymore for various reasons. I will focus for now on on Distutils2, shutil and sysconfig.
I would like to propose Eric (merwok on IRC) as a commiter to work on Distutils. He has done a great work in triaging the bugs and also has now a pretty good knowledge of the Distutils code. He's a GSOC student for distutils2 and has done a great coding work in there. I am pretty sure he would love to do this as I did.
Have any significant code patches by Éric been committed to Python core? I may be mistaken in my evaluation, but I'm not sure giving away distutils maintenance to an almost complete beginner is a good idea (since you are basically suggesting that he *replace* you in distutils maintenance).
Regards
Antoine.
On Tue, Jul 27, 2010 at 11:54 AM, Antoine Pitrou <solipsis@pitrou.net> wrote:
Le mardi 27 juillet 2010 à 01:50 +0200, Tarek Ziadé a écrit :
Hello,
I don't want to maintain Distutils anymore for various reasons. I will focus for now on on Distutils2, shutil and sysconfig.
I would like to propose Eric (merwok on IRC) as a commiter to work on Distutils. He has done a great work in triaging the bugs and also has now a pretty good knowledge of the Distutils code. He's a GSOC student for distutils2 and has done a great coding work in there. I am pretty sure he would love to do this as I did.
Have any significant code patches by Éric been committed to Python core?
Depending on your definition of core, none. He works on Distutils2 and helps me (and other) in the tracker.
I may be mistaken in my evaluation, but I'm not sure giving away distutils maintenance to an almost complete beginner is a good idea (since you are basically suggesting that he *replace* you in distutils maintenance).
I am not sure how you define a complete beginner. As far as Distutils is concerned, he's not. He's capable of maintaining Distutils, given the patches he provides for Distutils2 (see http://hg.python.org/distutils2). He's also now involved in most design discussions, so aware of the various issues.
Distutils2 is the old Distutils trunk FYI.
That said, this was just a suggestion to replace me for this maintenance because I don't want to do it anymore. Another option is to have you and other core devs take over the maintenance, but FWIW I think you are less able than him to maintain Distutils, given his experience in the package, and the fact that he work on the next gen.
Last, I think Guido's thoughts on giving commiter access earlier matches completely this case. I believe Eric has the qualities to become a good commiter.
If the proposal is accepted I'll help him. If you or someone else rejects it, then good luck with the 150+ Distutils issues and the various ML fights on the topic.
One last option of course would be to let the package rotten, and just fix critical bugs when they occur, and wait for distutils2 to take over.
Regards Tarek
-- Tarek Ziadé | http://ziade.org
Tarek Ziadé wrote:
On Tue, Jul 27, 2010 at 11:54 AM, Antoine Pitrou <solipsis@pitrou.net> wrote:
Le mardi 27 juillet 2010 à 01:50 +0200, Tarek Ziadé a écrit :
Hello,
I don't want to maintain Distutils anymore for various reasons. I will focus for now on on Distutils2, shutil and sysconfig.
I would like to propose Eric (merwok on IRC) as a commiter to work on Distutils. He has done a great work in triaging the bugs and also has now a pretty good knowledge of the Distutils code. He's a GSOC student for distutils2 and has done a great coding work in there. I am pretty sure he would love to do this as I did.
Have any significant code patches by Éric been committed to Python core?
Depending on your definition of core, none. He works on Distutils2 and helps me (and other) in the tracker.
I may be mistaken in my evaluation, but I'm not sure giving away distutils maintenance to an almost complete beginner is a good idea (since you are basically suggesting that he *replace* you in distutils maintenance).
I am not sure how you define a complete beginner. As far as Distutils is concerned, he's not. He's capable of maintaining Distutils, given the patches he provides for Distutils2 (see http://hg.python.org/distutils2). He's also now involved in most design discussions, so aware of the various issues.
Distutils2 is the old Distutils trunk FYI.
That said, this was just a suggestion to replace me for this maintenance because I don't want to do it anymore. Another option is to have you and other core devs take over the maintenance, but FWIW I think you are less able than him to maintain Distutils, given his experience in the package, and the fact that he work on the next gen.
Last, I think Guido's thoughts on giving commiter access earlier matches completely this case. I believe Eric has the qualities to become a good commiter.
If the proposal is accepted I'll help him. If you or someone else rejects it, then good luck with the 150+ Distutils issues and the various ML fights on the topic.
One last option of course would be to let the package rotten, and just fix critical bugs when they occur, and wait for distutils2 to take over.
I think there's a difference in granting commit access to the repo and taking over maintenance of a huge stdlib package.
The first is easy to grant. The second requires more support from the developer community to be successful. Without knowing how Eric works, I think it's difficult to judge whether he'd be a good maintainer or not. Why not start with giving him commit rights and then see how things work out for a few months. After that we could then assign the maintenance to Eric.
FWIW: I think you've done a great job at maintaining distutils and I'd like to thank you for that.
-- Marc-Andre Lemburg eGenix.com
Professional Python Services directly from the Source (#1, Jul 27 2010)
Python/Zope Consulting and Support ... http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::: Try our new mxODBC.Connect Python Database Interface for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/
On 27/07/2010 12:00, M.-A. Lemburg wrote:
Tarek Ziadé wrote:
On Tue, Jul 27, 2010 at 11:54 AM, Antoine Pitrou<solipsis@pitrou.net> wrote:
Le mardi 27 juillet 2010 à 01:50 +0200, Tarek Ziadé a écrit :
Hello,
I don't want to maintain Distutils anymore for various reasons. I will focus for now on on Distutils2, shutil and sysconfig.
I would like to propose Eric (merwok on IRC) as a commiter to work on Distutils. He has done a great work in triaging the bugs and also has now a pretty good knowledge of the Distutils code. He's a GSOC student for distutils2 and has done a great coding work in there. I am pretty sure he would love to do this as I did.
Have any significant code patches by Éric been committed to Python core?
Depending on your definition of core, none. He works on Distutils2 and helps me (and other) in the tracker.
I may be mistaken in my evaluation, but I'm not sure giving away distutils maintenance to an almost complete beginner is a good idea (since you are basically suggesting that he *replace* you in distutils maintenance).
I am not sure how you define a complete beginner. As far as Distutils is concerned, he's not. He's capable of maintaining Distutils, given the patches he provides for Distutils2 (see http://hg.python.org/distutils2). He's also now involved in most design discussions, so aware of the various issues.
Distutils2 is the old Distutils trunk FYI.
That said, this was just a suggestion to replace me for this maintenance because I don't want to do it anymore. Another option is to have you and other core devs take over the maintenance, but FWIW I think you are less able than him to maintain Distutils, given his experience in the package, and the fact that he work on the next gen.
Last, I think Guido's thoughts on giving commiter access earlier matches completely this case. I believe Eric has the qualities to become a good commiter.
If the proposal is accepted I'll help him. If you or someone else rejects it, then good luck with the 150+ Distutils issues and the various ML fights on the topic.
One last option of course would be to let the package rotten, and just fix critical bugs when they occur, and wait for distutils2 to take over.
I think there's a difference in granting commit access to the repo and taking over maintenance of a huge stdlib package.
The first is easy to grant. The second requires more support from the developer community to be successful. Without knowing how Eric works, I think it's difficult to judge whether he'd be a good maintainer or not. Why not start with giving him commit rights and then see how things work out for a few months. After that we could then assign the maintenance to Eric.
+1
FWIW: I think you've done a great job at maintaining distutils and I'd like to thank you for that.
+1
Michael
-- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
On Tue, Jul 27, 2010 at 1:00 PM, M.-A. Lemburg <mal@egenix.com> wrote: ...
I think there's a difference in granting commit access to the repo and taking over maintenance of a huge stdlib package.
The first is easy to grant. The second requires more support from the developer community to be successful. Without knowing how Eric works, I think it's difficult to judge whether he'd be a good maintainer or not. Why not start with giving him commit rights and then see how things work out for a few months. After that we could then assign the maintenance to Eric.
Sounds good.
FWIW: I think you've done a great job at maintaining distutils and I'd like to thank you for that.
Thanks !
-- Tarek Ziadé | http://ziade.org
Hi Tarek,
On Tue, Jul 27, 2010 at 12:36:12PM +0200, Tarek Ziadé wrote:
Depending on your definition of core, none. He works on Distutils2 and helps me (and other) in the tracker.
I support Antoine here. The core may not just mean the CPython interpreter, but the stdlib module too.
Simple patches (in the form of Code) is helpful before giving the commit access.
I have seen Eric interacting a lot in tracker but mostly in the form of words and less code. So, I think some patches will help us all to be favorable to him too.
Thanks, Senthil
On 27/07/2010 12:40, Senthil Kumaran wrote:
Hi Tarek,
On Tue, Jul 27, 2010 at 12:36:12PM +0200, Tarek Ziadé wrote:
Depending on your definition of core, none. He works on Distutils2 and helps me (and other) in the tracker.
I support Antoine here. The core may not just mean the CPython interpreter, but the stdlib module too.
Simple patches (in the form of Code) is helpful before giving the commit access.
I have seen Eric interacting a lot in tracker but mostly in the form of words and less code. So, I think some patches will help us all to be favorable to him too.
Tarek is saying that Eric has already contributed substantially to distutils2, which may not be part of the standard library *yet* but will be and is being developed as a standard library module. Perhaps Tarek could link us to a couple of these contributions, or those concerned could look at the distutils2 commit log to see his contribution.
So long as Eric is prepared to commit to our standard procedures (discussion and patches on issues before commit and general caution and regard for backwards compatibility) I would like to see him given commit rights under the watchful eye of Tarek and those who review checkins. We could see this as an "experimental" commit access in line with the lowered barrier proposed by Guido.
Michael
Thanks, Senthil
python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
-- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
So long as Eric is prepared to commit to our standard procedures (discussion and patches on issues before commit and general caution and regard for backwards compatibility) I would like to see him given commit rights under the watchful eye of Tarek and those who review checkins. We could see this as an "experimental" commit access in line with the lowered barrier proposed by Guido.
I'm fine with commit access for Éric (especially for documentation issues where his contribution has been quite useful).
The issue at hand is the fate of distutils maintenance.
Regards
Antoine.
On 27/07/2010 13:56, Antoine Pitrou wrote:
So long as Eric is prepared to commit to our standard procedures (discussion and patches on issues before commit and general caution and regard for backwards compatibility) I would like to see him given commit rights under the watchful eye of Tarek and those who review checkins. We could see this as an "experimental" commit access in line with the lowered barrier proposed by Guido.
I'm fine with commit access for Éric (especially for documentation issues where his contribution has been quite useful).
The issue at hand is the fate of distutils maintenance.
As indicated by my previous +1, I favour the approach suggested by Marc-andre Lemburg.
Michael
Regards
Antoine.
python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
-- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
Well like it or not Tarek is not going to do it. So who will? You, or a new volunteer?
--Guido (on Android)
On Jul 27, 2010 5:58 AM, "Antoine Pitrou" <solipsis@pitrou.net> wrote:
So long as Eric is prepared to commit to our standard procedures (discussion and patches on issues before commit and general caution and regard for backwards compatibility) I would like to see him given commit rights under the watchful eye of Tarek and those who review checkins. We could see this as an "experimental" commit access in line with the lowered barrier proposed by Guido.
I'm fine with commit access for Éric (especially for documentation issues where his contribution has been quite useful).
The issue at hand is the fate of distutils maintenance.
Regards
Antoine.
python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Le mardi 27 juillet 2010 à 07:15 -0700, Guido van Rossum a écrit :
Well like it or not Tarek is not going to do it. So who will? You, or a new volunteer?
Well, we don't even know if Éric actually volunteers for maintaining distutils. Otherwise the module will just rot as Tarek said, until distutils2 replaces it. This is certainly a less than optimal transition, but if distutils2 matures quickly enough it will not be as painful as it seems. (much less painful anyway than the state of distutils before Tarek started maintenance on it)
On 27 Jul, 2010, at 16:24, Antoine Pitrou wrote:
Le mardi 27 juillet 2010 à 07:15 -0700, Guido van Rossum a écrit :
Well like it or not Tarek is not going to do it. So who will? You, or a new volunteer?
Well, we don't even know if Éric actually volunteers for maintaining distutils. Otherwise the module will just rot as Tarek said, until distutils2 replaces it. This is certainly a less than optimal transition, but if distutils2 matures quickly enough it will not be as painful as it seems. (much less painful anyway than the state of distutils before Tarek started maintenance on it)
It won't really rot, it won't get as much attention as when Tarek did maintain it. We'll basicly revert to the situation before Tarek volunteered to maintain distutils (which he did very well)
Ronald
On Tue, Jul 27, 2010 at 11:19 AM, Ronald Oussoren <ronaldoussoren@mac.com> wrote:
On 27 Jul, 2010, at 16:24, Antoine Pitrou wrote:
Le mardi 27 juillet 2010 à 07:15 -0700, Guido van Rossum a écrit :
Well like it or not Tarek is not going to do it. So who will? You, or a new volunteer?
Well, we don't even know if Éric actually volunteers for maintaining distutils. Otherwise the module will just rot as Tarek said, until distutils2 replaces it. This is certainly a less than optimal transition, but if distutils2 matures quickly enough it will not be as painful as it seems. (much less painful anyway than the state of distutils before Tarek started maintenance on it)
It won't really rot, it won't get as much attention as when Tarek did maintain it. We'll basicly revert to the situation before Tarek volunteered to maintain distutils (which he did very well)
Ronald
I too, am for MaL's suggestion that we give Eric privs, and see how it goes before signing off on him being the long-term maintainer, but I am a strong -100 on allowing distutils to fall back to the way things were. We need more people assigned/associated/feeling ownership of stdlib modules, not less.
jesse
I too, am for MaL's suggestion that we give Eric privs, and see how it goes before signing off on him being the long-term maintainer, but I am a strong -100 on allowing distutils to fall back to the way things were. We need more people assigned/associated/feeling ownership of stdlib modules, not less.
I agree with the last sentence. I was just trying to be prudent as to how we handle maintenance of delicate parts of the stdlib.
As for "allowing distutils to fall back", the point is that Tarek and friends are working on its replacement. I hope it can be integrated sooner rather than later. Tarek used to develop features directly in the stdlib, but Guido decided at PyCon that it was too dangerous and that a separate project had to be started instead - leading to the recent reverting of distutils to its 3.1 state.
Regards
Antoine.
On Wed, Jul 28, 2010 at 4:18 AM, Antoine Pitrou <solipsis@pitrou.net> wrote:
I too, am for MaL's suggestion that we give Eric privs, and see how it goes before signing off on him being the long-term maintainer, but I am a strong -100 on allowing distutils to fall back to the way things were. We need more people assigned/associated/feeling ownership of stdlib modules, not less.
I agree with the last sentence. I was just trying to be prudent as to how we handle maintenance of delicate parts of the stdlib.
If it's just the maintainer issue concerning people, perhaps think of it as Tarek deputising to Eric - and I think we should allow active maintainers of modules to deputise people that *they* trust to do a good job.
+1 from me as well.
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Jul 28, 2010, at 10:23 PM, Nick Coghlan wrote:
If it's just the maintainer issue concerning people, perhaps think of it as Tarek deputising to Eric - and I think we should allow active maintainers of modules to deputise people that *they* trust to do a good job.
Excellent way to put in Nick. We trust Tarek, Tarek vouches for Eric. That's good enough for me.
Tarek, if things go sour with Eric, just watch your back for the PSU (which does *not* exist).
:) :)
-Barry
On Wed, Jul 28, 2010 at 4:21 PM, Barry Warsaw <barry@python.org> wrote:
On Jul 28, 2010, at 10:23 PM, Nick Coghlan wrote:
If it's just the maintainer issue concerning people, perhaps think of it as Tarek deputising to Eric - and I think we should allow active maintainers of modules to deputise people that *they* trust to do a good job.
Excellent way to put in Nick. We trust Tarek, Tarek vouches for Eric. That's good enough for me.
Thanks :)
So if everyone agrees Eric gets commit access, and works with me on Distutils, and I stay the official maintainer until the PSU does something bad to me. I have moved, changed my number and have placed my kids in a safe place so I sho
On 8/3/2010 10:33 AM, Tarek Ziadé wrote:
On Wed, Jul 28, 2010 at 4:21 PM, Barry Warsaw <barry@python.org> wrote:
On Jul 28, 2010, at 10:23 PM, Nick Coghlan wrote:
If it's just the maintainer issue concerning people, perhaps think of it as Tarek deputising to Eric - and I think we should allow active maintainers of modules to deputise people that *they* trust to do a good job.
Excellent way to put in Nick. We trust Tarek, Tarek vouches for Eric. That's good enough for me.
Thanks :)
So if everyone agrees Eric gets commit access, and works with me on Distutils, and I stay the official maintainer until the PSU does something bad to me. I have moved, changed my number and have placed my kids in a safe place so I sho
I am afraid Tarek has learned the hard way that it simply isn't wise to juxtapose the letters "P", "S" and "U" in any email handled by the python.org infrastructure. I guess this means we will have to rely on Eric for distutils maintenance right away.
there-*is*-no-psu-ly y'rs - steve
Steve Holden +1 571 484 6266 +1 800 494 3119 DjangoCon US September 7-9, 2010 http://djangocon.us/ See Python Video! http://python.mirocommunity.org/ Holden Web LLC http://www.holdenweb.com/
On Tue, Aug 3, 2010 at 10:33 AM, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
So if everyone agrees Eric gets commit access, and works with me on Distutils, and I stay the official maintainer
+1
-Fred
-- Fred L. Drake, Jr. <fdrake at gmail.com> "A storm broke loose in my mind." --Albert Einstein
Le mardi 03 août 2010 à 11:15 -0400, Fred Drake a écrit :
On Tue, Aug 3, 2010 at 10:33 AM, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
So if everyone agrees Eric gets commit access, and works with me on Distutils, and I stay the official maintainer
+1
Let me point out something fishy: “Fred Drake” is almost an anagram of “Tarek Ziadé”.
Regards
Antoine.
On Tue, Aug 3, 2010 at 11:23 AM, Antoine Pitrou <solipsis@pitrou.net> wrote:
Let me point out something fishy: “Fred Drake” is almost an anagram of “Tarek Ziadé”.
Shhh! Nobody's supposed to know that "F" is spelled "qZ" on my birth certificate!
-Fred
-- Fred L. Drake, Jr. <fdrake at gmail.com> "A storm broke loose in my mind." --Albert Einstein
On 03/08/2010 16:23, Antoine Pitrou wrote:
Le mardi 03 août 2010 à 11:15 -0400, Fred Drake a écrit :
On Tue, Aug 3, 2010 at 10:33 AM, Tarek Ziadé<ziade.tarek@gmail.com> wrote:
So if everyone agrees Eric gets commit access, and works with me on Distutils, and I stay the official maintainer
+1
Let me point out something fishy: “Fred Drake” is almost an anagram of “Tarek Ziadé”.
Antoine Pitrou however, is an anagram of:
Urinate Option
Unto a pointier
Auntie Iron Pot
No Petunia Riot
I Pure Notation
Untie piano rotActually your name has to be one of the most annagramable names I have ever seen.
http://wordsmith.org/anagram/anagram.cgi?anagram=Antoine+pitrou&t=1000&a=n <http://wordsmith.org/anagram/anagram.cgi?anagram=Antoine+pitrou&t=1000&a=n>
(oh, and +1)
Michael
Regards
Antoine.
python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
-- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
On Tue, Aug 3, 2010 at 5:39 PM, Michael Foord <michael@voidspace.org.uk> wrote:
On 03/08/2010 16:23, Antoine Pitrou wrote:
Le mardi 03 août 2010 à 11:15 -0400, Fred Drake a écrit :
On Tue, Aug 3, 2010 at 10:33 AM, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
So if everyone agrees Eric gets commit access, and works with me on Distutils, and I stay the official maintainer
+1
Let me point out something fishy: “Fred Drake” is almost an anagram of “Tarek Ziadé”.
Antoine Pitrou however, is an anagram of:
Urinate Option Unto a pointier Auntie Iron Pot No Petunia Riot I Pure Notation Untie piano rot
Actually your name has to be one of the most annagramable names I have ever seen.
http://wordsmith.org/anagram/anagram.cgi?anagram=Antoine+pitrou&t=1000&a=n
Love this site.
Guido is : A Doom GNUs Virus :)
On 03/08/2010 16:54, Tarek Ziadé wrote:
On Tue, Aug 3, 2010 at 5:39 PM, Michael Foord<michael@voidspace.org.uk> wrote:
On 03/08/2010 16:23, Antoine Pitrou wrote:
Le mardi 03 août 2010 à 11:15 -0400, Fred Drake a écrit :
On Tue, Aug 3, 2010 at 10:33 AM, Tarek Ziadé<ziade.tarek@gmail.com> wrote:
So if everyone agrees Eric gets commit access, and works with me on Distutils, and I stay the official maintainer
+1
Let me point out something fishy: “Fred Drake” is almost an anagram of “Tarek Ziadé”.
Antoine Pitrou however, is an anagram of:
Urinate Option Unto a pointier Auntie Iron Pot No Petunia Riot I Pure Notation Untie piano rotActually your name has to be one of the most annagramable names I have ever seen.
http://wordsmith.org/anagram/anagram.cgi?anagram=Antoine+pitrou&t=1000&a=n
Love this site.
Guido is : A Doom GNUs Virus :)
Barry Warsaw is Wary Bra Wars, whilst Steve Holden is Eleventh Sod. Mark Dickinson is Kid Conman Risk, whilst Raymond Hettinger is A Trendy Mothering. Hmm.. the alter egos of our Python super heroes needs work I think.
Naturally I am Firm Cool Head. :-)
Michael
-- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
On Tue, Aug 3, 2010 at 9:32 PM, Michael Foord <michael@voidspace.org.uk> wrote:
Barry Warsaw is Wary Bra Wars, whilst Steve Holden is Eleventh Sod. Mark Dickinson is Kid Conman Risk, whilst Raymond Hettinger is A Trendy Mothering. Hmm.. the alter egos of our Python super heroes needs work
I would just imagine that Raymond would come up with a ActiveState recipe for replacement of that site, of course using the collections module.
-- Senthil
On Tue, Aug 3, 2010 at 07:33, Tarek Ziadé <ziade.tarek@gmail.com> wrote:
On Wed, Jul 28, 2010 at 4:21 PM, Barry Warsaw <barry@python.org> wrote:
On Jul 28, 2010, at 10:23 PM, Nick Coghlan wrote:
If it's just the maintainer issue concerning people, perhaps think of it as Tarek deputising to Eric - and I think we should allow active maintainers of modules to deputise people that *they* trust to do a good job.
Excellent way to put in Nick. We trust Tarek, Tarek vouches for Eric. That's good enough for me.
Thanks :)
So if everyone agrees Eric gets commit access, and works with me on Distutils, and I stay the official maintainer until the PSU does something bad to me. I have moved, changed my number and have placed my kids in a safe place so I sho
Since no one has disagreed with giving Eric commit privileges, have him email his SSH 2 RSA key, his preferred email address for python-committers, and the proper spelling of his name in ASCII (along with telling him to read python.org/dev/ on what is expected, e.g. subscribing to python-checkins).
On Tue, Jul 27, 2010 at 3:24 PM, Antoine Pitrou <solipsis@pitrou.net> wrote:
Le mardi 27 juillet 2010 à 07:15 -0700, Guido van Rossum a écrit :
Well like it or not Tarek is not going to do it. So who will? You, or a new volunteer?
Well, we don't even know if Éric actually volunteers for maintaining distutils.
I'm kind of guessing that Tarek checked with Éric first (as is customary in such cases).
Otherwise the module will just rot as Tarek said, until distutils2 replaces it.
Well, rotting has been the distutils status quo for years, hasn't it? In fact, I thought that once significant changes were made, things got worse for a while due to (insanely subtle) backwards incompatibilities.
This is certainly a less than optimal transition, but if distutils2 matures quickly enough it will not be as painful as it seems. (much less painful anyway than the state of distutils before Tarek started maintenance on it)
Let's not forget that Tarek is also a volunteer. If he has to choose between maintaining distutils or spending more time getting distutils2 in shape, the choice is his, but ISTM that the choice he stated (work on distutils2) is the better one anyways.
-- --Guido van Rossum (python.org/~guido)
On Tue, Jul 27, 2010 at 4:24 PM, Antoine Pitrou <solipsis@pitrou.net> wrote:
Le mardi 27 juillet 2010 à 07:15 -0700, Guido van Rossum a écrit :
Well like it or not Tarek is not going to do it. So who will? You, or a new volunteer?
Well, we don't even know if Éric actually volunteers for maintaining distutils.
He does as long as I help him.
Note that he is a student so he will have less free time as soon as he's back too school of course, so he cannot guarantee, foresee, the amount of free time per week he will have next year.
Otherwise the module will just rot as Tarek said, until distutils2 replaces it. This is certainly a less than optimal transition, but if distutils2 matures quickly enough it will not be as painful as it seems. (much less painful anyway than the state of distutils before Tarek started maintenance on it)
python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
-- Tarek Ziadé | http://ziade.org
participants (14)
-
Alexander Belopolsky -
Antoine Pitrou -
Barry Warsaw -
Brett Cannon -
Fred Drake -
Guido van Rossum -
Jesse Noller -
M.-A. Lemburg -
Michael Foord -
Nick Coghlan -
Ronald Oussoren -
Senthil Kumaran -
Steve Holden -
Tarek Ziadé