Hi,
Daniel Holth's currently working on PEP 425 and 426 (the drafts for a cross-platform binary distribution format and for package metadata 1.3). I'd like to get myself out of the publication loop by getting him direct access to push to the PEP repo, and trust him to stick to just updating those two PEPs (at least for now - that may change once the packaging module makes it back into the default branch for 3.4).
Guido originally gave me commit access just to work on updating PEP 343, so I'd like to do something similar here.
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
Zitat von Nick Coghlan <ncoghlan@gmail.com>:
Daniel Holth's currently working on PEP 425 and 426 (the drafts for a cross-platform binary distribution format and for package metadata 1.3). I'd like to get myself out of the publication loop by getting him direct access to push to the PEP repo, and trust him to stick to just updating those two PEPs (at least for now - that may change once the packaging module makes it back into the default branch for 3.4).
Guido originally gave me commit access just to work on updating PEP 343, so I'd like to do something similar here.
There is no access control; he should just stick to committing where he is supposed to (just as everybody else). Key managers are currently Georg Brandl, Antoine Pitrou, and Brett Cannon. I keep forgetting whether there is an email alias for them.
Regards, Martin
Le samedi 08 septembre 2012 à 19:00 +0200, martin@v.loewis.de a écrit :
Zitat von Nick Coghlan <ncoghlan@gmail.com>:
Daniel Holth's currently working on PEP 425 and 426 (the drafts for a cross-platform binary distribution format and for package metadata 1.3). I'd like to get myself out of the publication loop by getting him direct access to push to the PEP repo, and trust him to stick to just updating those two PEPs (at least for now - that may change once the packaging module makes it back into the default branch for 3.4).
Guido originally gave me commit access just to work on updating PEP 343, so I'd like to do something similar here.
There is no access control; he should just stick to committing where he is supposed to (just as everybody else). Key managers are currently Georg Brandl, Antoine Pitrou, and Brett Cannon. I keep forgetting whether there is an email alias for them.
hgaccounts <hgaccounts@python.org> :-)
Best regards
Antoine.
-- Software development and contracting: http://pro.pitrou.net
participants (3)
-
Antoine Pitrou -
martin＠v.loewis.de -
Nick Coghlan