Re: [python-committers] Contributor Form
Hi Tim: Thank-you for submitting your contributor agreement form to the PSF. It has been added to the online bug tracker. Pat On Tue, May 29, 2012 at 6:34 AM, Tim Silk wrote: > To whom it may concern, > > Please find attached my completed python contributor form. > > Tim Silk. > -- Pat Campbell PSF Administrator/Secretary pat...@python.org ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Contributor agreement for ssm
Hi Sidney: Yes, I was able to update your contributor agreement form information located on the online bug tracker. Thanks, Pat On Fri, May 25, 2012 at 2:48 PM, Sidney San Martín wrote: > Thanks Pat! > > Is this the page you’re looking for? > > http://bugs.python.org/user15625 > > > On Friday, May 25, 2012 at 2:44 PM, Pat Campbell wrote: > > > Hi Sidney: > > > > > > Thank-you for submitting your contributor agreement form. I would like > to add your > > form to the PSF online bug tracker. > > > > In order for me to add your contributor agreement form to your profile > (on the online bug > > tracker) I will need to access your user number webpage or please > provide the link to your > > > > > > "user# editing" webpage in order for me to mark (Yes) to receiving your > contributor > > agreement form. > > > > Or, you could provide me with your "user name, user number, & real name > (the way it > > > > > > > > appears on the online bug tracker "login" webpage, since I was not able > to access the > > > > > > > > webpage based on the information provided on the form. The login webpage > is "case > > > > > > > > sensitive", therefore, the data used to access a webpage on this site > must be exact. > > > > Thanking you in advance, > > Pat > > > > > > > > On Fri, May 25, 2012 at 10:53 AM, Sidney San Martín > > s...@sidneysm.com)> wrote: > > > Hey, > > > > > > I was just asked to sign a contributor agreement on bug 14835. It’s > attached! > > > > > > Thanks, > > > Sidney > > > > > > > > > > > > > > -- > > Pat Campbell > > PSF Administrator/Secretary > > pat...@python.org (mailto:pat...@python.org) > > > > -- Pat Campbell PSF Administrator/Secretary pat...@python.org ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] signed contributors agreement
Hi Ralf: Thank-you for submitting your contributor agreement form to the PSF. It has been added to the online bug tracker. Pat On Tue, May 29, 2012 at 5:02 AM, Ralf Schlatterbeck wrote: > please find enclosed my contributors agreement > (requested for issue1079) > > Best Regards > Ralf Schlatterbeck > -- > Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 > Open Source Consulting www: http://www.runtux.com > Reichergasse 131, A-3411 Weidling email: off...@runtux.com > osAlliance member email: r...@osalliance.com > -- Pat Campbell PSF Administrator/Secretary pat...@python.org ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
[python-committers] Wording about packaging in the 3.3 announcement
Hi Georg, I would like to clarify something in order to remove a misleading or confusing statement from the release email: * The new "packaging" module, building upon the "distribute" and "distutils2" projects and deprecating "distutils" First, packaging *is* distutils2, modulo a few changesets that I have to port between the codebases. Second, I would remove the mention of distribute: packaging is an implementation of the packaging PEPs which have their origins in setuptools and which have been improved by the community, and it also takes some minor features and ideas from setuptools, but I think that “building upon” is too strong (and mentioning only distribute may hurt the feelings of setuptools authors and users—distutils-sig is a heated place). My suggestion: * The new "packaging" module (also known as distutils2, and released standalone under this name), implementing the new packaging formats and deprecating "distutils". The whatsnew document has the same problem, and also mixes packaging (venv and packaging) with imports (namespace packages), but I did not get a chance to fix it before today, so I probably will after the alpha. Thanks ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
[python-committers] Contributor Agreement - Michael Driscoll
We received an agreement from Michael Driscoll by postal mail. I've forwarded it to our administrator. KBK ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Wording about packaging in the 3.3 announcement
On Wed, May 30, 2012 at 12:20 AM, Éric Araujo wrote: > The whatsnew document has the same problem, and also mixes packaging (venv > and packaging) with imports (namespace packages), but I did not get a chance > to fix it before today, so I probably will after the alpha. Those additions were from me, and were a result of the fact that those are *big* changes that should have a huge positive impact for end users in the long run, but weren't being advertised in the What's New at all. (packaging was at least mentioned in the "new modules" section, but replacing the framework for component distribution deserves a lot more prominence than that - it's far more significant for the future of Python than minor syntactic changes like PEP 380 or 409). The reason they're lumped together like that is because they're all related to code distribution - namespace packages are about being able to easily split up a single Python package across multiple installed components, PEP 405 is about maintaining multiple independent sets of installed components on a single machine, and packaging/pysetup is the new system for building and installing components in general. While it makes sense that Raymond doesn't want to devote too much time to cleaning up What's New until the feature set stabilises in the first beta, we need to remember that alpha users also need some pointers to the shiny new toys we'd like them to tinker with. pysetup and pyvenv in particular are rather hard to test in an automated fashion, so we'd really like people hammering on them manually. In the absence of preliminary entries on those topics, I added the shorthand section so that they were at least mentioned and users would know to go look at them and try them out. Ideally, each of those bullet points will be expanded out to an entire section in their own right. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit privileges for Daniel Urban
On Thu, May 17, 2012 at 2:44 PM, Nick Coghlan wrote: > In the absence of any -1 votes, I'll get Daniel to send his public key > through to the hgaccounts address. I'll still watch his commits and > remind him that getting patches reviewed on the tracker first is still > often the preferred approach, even for committers. On reflection, I decided to instead extend Daniel an offer that he could add me to the nosy list on any issues he was working on and I'd take a look. An explicit offer to review any patches he submits seems like a sensible interim step prior to granting him direct push access. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit privileges for Daniel Urban
On May 29, 2012, at 11:46 PM, Nick Coghlan wrote: > On Thu, May 17, 2012 at 2:44 PM, Nick Coghlan wrote: >> In the absence of any -1 votes, I'll get Daniel to send his public key >> through to the hgaccounts address. I'll still watch his commits and >> remind him that getting patches reviewed on the tracker first is still >> often the preferred approach, even for committers. > > On reflection, I decided to instead extend Daniel an offer that he > could add me to the nosy list on any issues he was working on and I'd > take a look. > > An explicit offer to review any patches he submits seems like a > sensible interim step prior to granting him direct push access. > Probably a bit less scary for him as well, we might hope. I know I am in trepidation of even looking at the codebase when I consider the chops of those who wrote most of it. He's going to make it! regards Steve PS: Will be leaving committers as soon as I find out how, but not for any other reason than bandwisth. I hope you all know where to find me if you need me. Devs-keep-devving. As you were. -- Steve Holden st...@holdenweb.com, Holden Web, LLC http://holdenweb.com/ Python classes (and much more) through the web http://oreillyschool.com/ Conferences and technical event management at http://theopenbastion.com/ Next: Open Django Central Jun 8-9: http://opendjango.com/central/ ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
[python-committers] Threadjack: python-dev input to site redesign [sorry ...]
Is any one person in the dev community anxious to represent that community in the (hopefully forthcoming) "new new python.org" development. Probably a good time to talk about that, as the RFP is open. I think I'd give bonus marks to anyone who offered (as one of the alternative styles) Jost's random multi-logoed blue designs, which I suspect might be a fond choice occasionally for some old-timers such as myself. No reason why history must be forgotten. We aren't the State Department. regards Steve PS: feel free to move to python-dev, where I no longer lurk. On May 29, 2012, at 11:46 PM, Nick Coghlan wrote: > On Thu, May 17, 2012 at 2:44 PM, Nick Coghlan wrote: >> In the absence of any -1 votes, I'll get Daniel to send his public key >> through to the hgaccounts address. I'll still watch his commits and >> remind him that getting patches reviewed on the tracker first is still >> often the preferred approach, even for committers. > > On reflection, I decided to instead extend Daniel an offer that he > could add me to the nosy list on any issues he was working on and I'd > take a look. > > An explicit offer to review any patches he submits seems like a > sensible interim step prior to granting him direct push access. > > Cheers, > Nick. > > -- > Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia > ___ > python-committers mailing list > python-committers@python.org > http://mail.python.org/mailman/listinfo/python-committers -- Steve Holden st...@holdenweb.com, Holden Web, LLC http://holdenweb.com/ Python classes (and much more) through the web http://oreillyschool.com/ Conferences and technical event management at http://theopenbastion.com/ Next: Open Django Central Jun 8-9: http://opendjango.com/central/ ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
