Development Sprints

Edit page
# Monday, April 14th 2014 – Thursday, April 17th 2014 Development sprints are a key part of PyCon, a chance for the contributors to open-source projects to get together face-to-face for up to four days of intensive learning, development and camaraderie. Newbies sit with gurus, go out for lunch and dinner together, and have a great time while advancing their project. What's a sprint? ------------------- PyCon Development Sprints are four days of intensive learning and development on an open source project of your choice, in a team environment. It's a time to come together with colleagues, old and new, to share what you've learned and apply it to an open source project. In the crucible of a sprint room, teaming with both focus and humor, it's a time to test, fix bugs, add new features, and improve documentation. And it's a time to network, make friends, and build relationships that go beyond the conference. PyCon provides the space and infrastructure (network, power, tables & chairs); you bring your skills, humanity, and brainpower (oh! and don't forget your computer). Come for PyCon, stay for the sprints! Who can participate? -------------------- **You!** All experience levels are welcome; sprints are a great opportunity to get connected with, and start contributing to your favorite Python project. **Participation in the sprints is free!** Who can run a sprint? --------------------------- **You!** If you've never run a sprint before, the [In-Person Event Handbook]( is an excellent guide. What's the schedule? ------------------------- Details TBD, but sprints will start Sunday afternoon, really kick off Monday morning and keep running through Thursday. Will there be food during the sprints? ------------------------------- Yes! Boxed lunches will be provided on Monday and Wednesday, and buffet lunches will be provided on Tuesday and Thursday. Lunch will be available in room 517D at the convention center. Breakfast and dinner are on your own, so grab some newfound friends and check out a [nearby restaurant](/2014/venue/restaurants/)! Where will the sprints be? ------------------------------- Sprints will be in rooms 518A-C, 519A/B, 520A-F and 524A-C on the 5th level of the Convention Center. During the sprint days, lunch will be in 517B on the same level. Which projects are sprinting? ---------------------------------- - [GNU Mailman][1] is sprinting again this year. Here is our [sprint page][2] with details. - OpenHatch is a website (and non-profit) to help people get involved in open source. It's written in Django, and needs HTML, CSS, Python, and Javascript help -- all levels welcome. More info on our [sprint page][21]. - The [Center for Open Science][3] is sprinting on a number of projects to make science more open: improving the [Open Science Framework][4] (OSF), improved OSF file rendering (to HTML), add-ons for the OSF for services such as Dropbox and Wakari (already have Github and S3), torrents for science, etc. Project page coming soon. - Pylons Project / [Pyramid][18] is sprinting as usual. - [SaltStack][5] will be there on Monday to help you jump in and start contributing! Join our [mailing list][6] where we will post updates about the sprint. (Or just come talk to us at our booth for more information) - [Stackless][7] will be sprinting on various things Stackless related. More details soon. - [Mercurial][8] will be sprinting on the bundle2 format and Python 3 support. A good opportunity to meet developers and help out with fixing bugs. - [Fabric][9], [Invoke][10] and [Paramiko][11] will be sprinting on various things including Fabric 2.0! - [Django][12] will be sprinting too. Newcomers and seasoned developers are welcome. Get a head start by going over the [contributing guide][13]. - Port [OpenStack][14] to Python 3: Port OpenStack components and OpenStack dependencies (MySQL-python, python-ldap, websockify, ...) to Python 3: send patches to port as much code as possible. [Python3/SprintPycon2014][15] - [Gittip][16] will be sprinting on Monday. - [Apache Allura]( will be sprinting on various projects & tasks. - [Apache Bloodhound]( developers will be sprinting to backport features into [Trac]( core . - [Warehouse](, aka PyPI version 2, will be sprinting on getting legacy PyPI support completed. - [Twisted]( will be sprinting. - [Open edX]( will be sprinting on Monday. - [Sunlight Foundation]( developers will be continuing the tradition of hosting the annual PyCon Open Government sprint for people interested in working on any kind of open government project, we'll have things for people to contribute to or feel free to bring your own project. - [OpenContracting Data Standard][17] team have a [wide range of projects][19] for everyone from python devs, machine-learning peeps , data geeks, designers, librarians.....there's something for everyone.. - [PyPy]( will be sprinting. - [backy]( - @theuni will be sprinting on a low-level VM-oriented block-device backup utility - [Pyston]( will be working on improving language support. - [scikit-learn]( - Machine Learning in Python. We will work on issues reported on the github tracker and kill as many bugs as possible for the next release. - [Pelican]( will be working on existing issues, reviewing and testing pull requests, and preparing for the imminent 3.4 release. - [pika]( will be working on open issues, pull-requests, and adding additional test coverage to get 0.9.14 released and working on 0.10 to add Python 3 support. - []( will be sprinting. - [IPython]( We will be sprinting, Fernando Pérez will be present on Monday Morning, and Matthias Bussonnier will be present until thursday, come if you have question about IPython, or want to stat contributing. We will also try to port the Turtle module to have a javascript Backend in order to get Turtle into the notebook. - [Bookie]( will be sprinting. We'll be working on Pyramid python code, JS for FF/Chrome browser extensions, and working through GSoC submissions. - [PyDy]([SymPy]( will be sprinting Sunday evening and Monday. We will be working on bug fixes, roadmapping, and restructuring our website with live and executable examples. - [py.test]( - [CPython](, the reference Python implementation - Pygments - ReadTheDocs - Django Simple History - ElasticUtils - PyVideo - Kivy - Pip / virtualenv - Sage - [ResearchCompendia]( - [Software Carpentry][20] - [Scrapy]( will be sprinting on Monday. We will be working on writing spiders for [pycon-speakers]( [1]: [2]: [3]: [4]: [5]: [6]:!forum/salt-users [7]: [8]: [9]: [10]: [11]: [12]: [13]: [14]: [15]: [16]: [17]: [18]: [19]: [20]: [21]: