We've added a new donated site (Yola) in South Africa where sprints can be held - go check out the donated sites page to see if there's a place near you!

I'm pleased to announce another sponsorship we have lined up - this time the Sprints team will be helping to sponsor the AFPY Computer Camp Sprint, lead by Tarek Ziade (see his blog post here). This sprint will be focused on packaging and testing topics and will be happening in Turcey - Burgundy, France

You can see pictures from the last camp Tarek lead here, the PSF Sponsorship money will go to helping pay for the travel for some of the contributors Tarek has lined up to attend.

If you're interested in attending, add your name here - note that space is limited!

The PSF Sprints team is happy to announce we'll be helping to sponsor yet another sprints! The announcement follows:

On the weekend of September 4th, the Cape Town Python Users Group will be sprinting to port Genshi to Python 3. Genshi is the templating engine used by Trac, so porting Genshi is one of the many prerequisites for porting Trac itself.

The local Capetonians will be meeting at the Yola offices in central Cape Town around 10am (8am GMT), but we'll also be hanging out on our IRC channel if those from further afield would like to join in the fun. Anyone with experience in porting C extensions to Python 3 would be particularly welcome.

More details available on the sprint planning page.

This year, PyOhio (July 31 - August 3, Columbus, OH) includes two evenings and two full days of sprints, including a Python Core sprint. The core sprint is part of an integrated program (http://www.pyohio.org/Contribute) to recruit new core contributors at the conference, train them, and get them started working in a mentored environment... all in one four-day event.

PyOhio is a free annual conference on all aspects of Python development. We hope to see you there!

I've just added the "Locations" page to the upper nav bar - this page includes people and/or companies whom have offered up space for sprints. This is a great way to "help the cause" if you or your company/organization have space which could be used by potential sprinters.

Contact sprints@python.org if you have space you wouldn't mind sprinters asking to use if they need it!

From Michael Foord: This year EuroPython had an amazing turnout for the sprints. On the first day we had 83 sprinters and more than half of them stayed through for the second day. People were sprinting on PyPy, Plone, csp (a form of concurrency and a hot topic during the conference) and a whole host of topics - but of particular interest here is the core Python sprint.

There were around twenty five people in the core-sprint room, here's a photo from the first day:

Core developers present included me (Michael Foord), Ezio Melotti, Georg Brandl, Martin von Loewis, Mark Dickinson, Ronald Ousseron, Richard Jones, Steve Holden, Steven Bethard, and Brett Cannon. My apologies to anyone I have missed out, but there were a lot of people there! Other Python luminaries like Dr Ali Afshar, Armin Ronacher, and Nicholas Tollervey joined us as well.

During the conference Ezio Melotti gave a talk on contributing to Python development. Several of the folk who turned up were new to Python development and had been inspired by Ezio's talk. Here's a quote from one of the sprinters:

"Ezio Melotti followed after the break with a useful overview of the Python development process, which inspired me to join the Python Core sprint on Friday. I’ve already contributed my first couple of patches to Python 3.2 – the first of which has been committed to trunk already. "
(from https://metaljoe.wordpress.com/2010/07/24/europython-2010/)

Dr Brett Cannon gave an introductory talk and collected contributor agreements from the sprinters. Ezio and Brett worked together with the new sprinters on improving test coverage. There were quite a few patches committed during the sprint towards this end. Dmitry of Jetbrains looked at testing the nntplib for Python 3, only to discover that it wasn't correctly handling bytes / strings. He produced a patch to fix this.

Other sprinters worked on a range of different topics. I started a prototype of a plugin system for unittest which is nearly ready to be announced and discussed to iron the wrinkles out of it. Mark Dickinson spent his time learning about the Mercurial API and hooks mechanisms in order to start developing the commit hooks that Python will need when it transitions to Mercurial.

Richard Jones worked on tests for the smtpd module which had no direct tests. He also added various new features to the PyPI web interface, including a new JSON rpc interface.

Martin von Loewis summarised his work during the sprints:

"I worked on PyPI (the Cheese Shop). I added support for running it locally with sqlite, and added some demo data. I also started on implementing a mirror on AppEngine. I then also resolved a few bug reports and support requests. "

The changes Martin and Richard Jones made to PyPI were summarized on the catalog-sig:

• There is now a way to request release information in JSON (see http://tinyurl.com/38lefsp)
• It's possible to run the code base locally using sqlite (see the README)
• There is now demodata available (see README); people won't need a full database dump anymore to develop on the code.
• In addition, pypi.appspot.com is likely to become mirror E (perhaps B instead, so that E can have an A record).

Ezio Melotti did a lot of work on improving the Python bug tracker, a continuation of what he has been doing for google summer of code. He fixed and/or worked on:

• http://psf.upfronthosting.co.za/roundup/meta/issue285
• http://psf.upfronthosting.co.za/roundup/meta/issue280
• http://psf.upfronthosting.co.za/roundup/meta/issue279
• http://psf.upfronthosting.co.za/roundup/meta/issue284

Georg Brandl worked on Sphinx and also with Martin. He provided this summary of what he did:

• Prepared and finished Sphinx 1.0 release, switched Python trunk to use it.
• Got PyPI running locally, fixed 3-4 minor tracker items and the broken setup.py register.
• Worked on pdb issues (none committed yet though).

Ronald Ousseron worked on a host of minor issues, mainly but not exclusively Mac OS X related issues. Steven Bethard was only around for the first day and spent most of it transferring issues from the old argparse issue tracker onto the Python issue tracker. He is notable as being the only sprinter who actively increased the number of open issues rather than reducing them.

Łukasz Langa was another sprinter new to Python development who had his first patches to Python accepted during the sprint. Since the sprint he has continued to work on Python, in particular fixing bugs and adding new functionality to the configparser module.

This sprint was particularly successful as not only did many issues get closed and patches committed, but several new contributors were inspired to work on core-Python.

Just a reminder - we've got a call for applications going on right now! Actually, consider this a standing one for as long as this project has funding. If you have a sprint you're considering holding in the next few months, and want/need some sponsorship, please - drop us an application!

We've already funded one sprint - and we have another one coming this week. We want to hear from everyone, even if you're just asking the question "Should I hold a sprint?". 

We will be putting up pages on how/where/what to donate, as well as a page containing information on organizations or companies which have generously offered sprint spaces. 

So - drop us a line! We look forward to hearing from you.

On behalf of the sprints team, I'd like to announce our second sponsored sprint - this time at EuroPython in Birmingham UK July 22nd through the 24th. Michael Foord (fuzzyman) sent us the application - they had already planned on having a "Python Core" sprint, with the rooms supplied by EuroPython. Our sponsorship will go towards other things such as refreshments and food for the participants.

A sampling of those who will be in attendance - Michael Foord, Ronald Ousseron, Georg Brandl, Brett Cannon, Ezio Melotti, Mark Dickinson, Tim Golden and more.

The primary focus of the sprint - beyond general core "things" according to Michael is the migration of Python-Core to mercurial - something long on the to do and wish list of python core. Here's the quote from Michael's application:

We would like to make the mercurial transition the focus of the sprint. At the very least coming out of the sprint with a clear idea (specific list) of what needs to be done.

During the conference both Brett Cannon and Martin von Loewis will be present, so we have a good opportunity to discuss this during the language summit and come away from that with some clear "todos". Ezio Melotti will also be working on roundup -> mercurial integration.

If we have a lot of "beginner" (non-core) sprinters then we will make "how to fix a Python bug", including the whole process from bug tracker to fix, the focus for these people.

This sounds like an awesome place to get introduced to everything you could possibly want to know about core - I know that personally my first Python-Core sprint at Pycon in the US sticks in my mind to this day as a major highlight.

So, if you're going to be at EuroPython - and you're staying for the sprints - drop on in! If you hadn't planned on staying for the sprints - please do! They're an awesome time, and help everyone learn and grow and get awesome things done.

You can also see, on the right hand side bar - we've added a Google Calendar with entries for this sprint, and we hope to be adding more. If you have an upcoming sprint or hackfest, and you want us to write a post to help advertise or add it to the calendar - even if we're not sponsoring it - drop us an email.

Yannick has posted a wrap-up of the latest packaging sprint they held (our trial sponsorship one) over here complete with pictures! It feels great to have helped in some small part - and we hope to help them and other sprint groups (new and experienced) out!

To quote Yannick:

"We have to thank the Python Software Foundation for supporting the sprint by covering the cost of food and drinks. Fuel (food and drinks), is not a requirement for a sprint since dedicated hackers will show up whether they have to bring their own booze of not, but it’s nice to be able reward sprinters with a savory meal. They deserve it. The sprint sponsorship program is a great thing, not because there is a financial bottleneck to organizing sprint, but because having a common coordinator for Python sprint will help to share the excitement and the knowledge of what works for sprints and what doesn’t. Hopefully, other user groups will join us and make sprints a core element of their schedule.

We agree completely - but remember the funds can be put to use for paying for any other expenses as well (food, networking, renting the place you need). Why don't you drop us an application today?

I'm happy to announce on behalf of everyone involved in this effort that we are issuing the first public call for applications for Sponsored Sprints!

We're very happy to have already sponsored one sprint as a trial run, and your sprint could be next!

Please see the applications page for more information on what, how and when. We are accepting applications now for sprints occurring within the next 30 days. 

Organizing these sprints, like all things with Python and the PSF, is a volunteer effort, and there are a lot of ways for you to help. In addition to working on this site and it's content, we are also working on collateral and manuals outlined in the original proposal. For example, Brian Curtin and others have been working on our guide to contributing to Python Core and he's also working on the Python 3 porting guide.

So, even if you're not going to be running a sprint, there are other opportunities for you to get involved. Email jnoller at python.org if you want to help out. If you want to solely focus on the documentation, the mercurial repository with the skeletons is located here. 

Finally, I apologize for the ramp up to this taking as long as it has, and our lack of the detailed manuals and materials. 

Thanks to everyone involved to this point, and to all you future sprint coaches and sprinters. Let's all make Python and the community even greater, together.

Call for Applications

The PSF is happy to open our first call for applications for sprint funding!

Have you ever had a group of people together to hack towards a common goal? You've hosted a sprint!

Have you ever wanted to get a group of like minded Pythonistas together to hack for a day? You're going to want to hold a sprint!

Whether you call them Sprints, Hackfests, Hack-a-thons, or any other name, they're a great way to hang out with like-minded developers and work on common code. Sprints are an unbeatable way to build friendships and contacts that will last for years to come, and they're a great way to learn about something new if you're just starting out.

The Python Software Foundation has set aside funds to be distributed to world-wide sprint efforts. We're anticipating 2-3 events per month focused on covering topics to help the entire community:

• Python Core bug triage and patch submission (on-boarding new contributors)
• Python Core documentation (including process documentation) improvements
• Porting libraries/applications to Python 3
• Python website/wiki content improvements
• PyPI packaging hosting site improvements
• Contribution to other "core" projects, such as packaging related issues.

If you are interested in holding a sprint on any of the topics above and you're looking for some money to help out with sprint costs, we can help (up to a max of $250 USD). Prepare an application including the following information:

• Date and Location: Where will the event be? What day and time?
• Organizers: Who are the event organizers and sprint coach? Is the sprint being run by a Python user group?
• Attendees: How many participants do you expect?
• Goal: What is the focus and goal of the sprint?
• Budget: How much funding you are requesting, and what will you use it for?

Applications should be sent to: sprints@python.org with the subject "Sprint Funding Application - <location>"

We encourage anyone - even those who have never held, or been to a sprint - to consider holding one. We will help you as much as we can with welcome packets, advertising, and hooking you up with required resources - anything to make it possible.

As part of being approved, you will need to agree to deliver a report (hopefully, with pictures!) of the sprint to the Sprint Committee, so we can post it on the sprint blog and site:

http://www.pythonsprints.com

If you have any questions or need more information, contact us by email at sprints@python.org.

Obviously, our site is still undergoing fleshing out - we're planning on issuing the first public Call For Applications later in the week of July 5th. For now, you can view the initial version of the CFA, and check out the details about the project.

Comments, suggestions, etc are all welcome - if you'd like to contribute, you can send an email directly to jnoller@python.org

Additionally, the initial versions of the manuals / handouts defined in the proposal on the about page will be coming online (thanks to sphinx!) in the next few weeks.

As you've probably read - we're happy to announce our pilot sponsored sprint! The Montréal-Python group is putting together the 5th of their python-packaging related sprints (details here), tomorrow July 5th.

Packaging is a critical component of the Python ecosystem and the changes happening now will change the face of the ecosystem for some time to come. We're very excited and happy to help enable (in a small way) this and the Montréal Python group.

As this is the pilot - it will be good to learn all of the specifics of how we will handle the financial transactions moving forward, and we hope to gain a lot of insight and knowledge from the Montréal group in regards to what they feel helps and doesn't help with good sprints, etc. 

If you're in the area - I'm sure the sprinters could always welcome some more company, and we're looking forward to being able to post our first sprint-story (we hope with pictures!) once the sprint is done. 

So, once again - thanks to the Montréal group and the PSF for providing the funds. 

Again - more details can be had on the Montréal-Python wiki.