addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1linklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Office Hour Sprint (No recruiters, no hiring managers)

  • Feb 26, 2013 · 7:00 PM
  • This location is shown only to members

On a semi-regular basis, office hours will be accompanied by a development sprint.

If you haven't participated in a sprint before, sprints are short periods of time (a few hours) during which a collection of people get together to work on a useful open source project together.

For the first sprint we will be sprinting on Twisted (, a popular networking engine.

In the future, if you have ideas for OSS projects to contribute to, feel free to bring it up after a sprint or here in the Meetup comments.

Sprint details

Twisted is a library for writing event-driven applications (web applications and servers, SSH, mail, IRC, games, you name it). You should get a few things done before you come sprint, especially if you've never contributed to Twisted before:

  • Read the Basic Contributor Guide, which outlines the basic process for contributing code to Twisted

    Make sure to create a Trac account and checkout the source. Also note that Twisted predates PEP8, so it has its own style guide, which happens to in particular use camelCase. Take a quick peek at that just to get a sense of it.

    As mentioned, all patches that you submit need to be reviewed by someone else other than the author of the patch, not necessarily a "committer" (although you can't review a patch from someone else if both of you are not committers, so if you want to do a review, find a ticket written by a committer). So reviewing patches is another task that can and should be done during the sprint by all the sprinters.

  • Take a look at how reviews should be done:

  • Finally, find a ticket or tickets you might want to work on in the issue tracker ( as this will let you get started right when you arrive. If you're looking for "Easy" tickets you can find a link to some tickets marked easy in the contributor's guide linked above.

    If you need help locating something that looks interesting feel free to post in the comments or ask in the IRC channel (either one mentioned below).

If you were able to follow those steps, you're all set. If you weren't or if you're just plain a beginner, you're still welcome to come and you'll get help, but preferential treatment will be given to people who've managed to get themselves set up and ready to go. See you then!

On the day of the sprint, you should make yourself present in the #twisted-dev channel on Freenode so that other developers (at the sprint and otherwise) can interact with you as you work. There will also be a #nycpython-sprint channel if you'd like to banter or want quick help from something that doesn't necessarily bear asking in #twisted-dev. Of course we'll have everyone there in person as well if you can grab someone to give you a hand.

Join or login to comment.

  • mark p.

    forgot the@#$! laptop.. no room for it here, but i have a mathematical proof that to maximize confusion you have to leave 10gen's m101p homework until the day it's due.. i assume there is another way and show a contradiction

    February 26, 2013

  • Andrew B.

    Second Chris's comment. I would love to participate in a sprint, particularly focused on Django on something in the Django ecosystem (tastypie, django-celery, django-storages, etc.)

    February 21, 2013

    • Gloria W

      If you want to sprint on something different but be present, this is fine. You may also want to reach out to http://www.djangonyc....­ where Sean, the organizer, is awesome.

      February 23, 2013

    • Julian B.

      We'll definitely do something Django related at some point too. Feel free to bug me if it doesn't happen sooner or later. And yeah definitely anyone who wants to sprint on whatever is totally cool.

      February 23, 2013

  • Chris R.

    I'm busy for this one but am definitely interested in more of these in the future.

    February 21, 2013

  • Gloria W

    To avoid confusion:

    This event runs in parallel to our Open Office Hours, and will be treated like a separate event at the same time and location.

    There are prerequisites above. Be sure to read and follow the steps Julian mentioned above. You can't just veg on this one, participation is mandatory, otherwise you won't get anything out of it.

    February 20, 2013

  • Evan M.

    python newb just trying to get more hours in.


    February 20, 2013

13 went

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy