Changes between Version 14 and Version 15 of GoogleSOC

04/01/2012 07:36:24 PM (8 years ago)
Itamar Turner-Trauring



  • GoogleSOC

    v14 v15  
    5555  * Finish half-written code, documentation, bug fixes, etc.: We  have >200 tickets that at some point had code written and received at least one code review, but for various reasons never made it in. This is a great way to learn because  you don't have to start from scratch, and there's a variety of tasks  (from minor fixes to documentation to new features) most of which have code reviews as a starting point. See for a list.
    5656  * PyPy: Have [ PyPy] be a fully supported platform, with all tests passing.
     59== Getting Started with Twisted Development ==
     60Here are some of the tools we use:
     62  1. IRC
     63  2. the Trac issue tracker
     64  3. the svn revision control system
     65  4. the diff and patch utilities
     67If you have not used IRC before, please go through this short tutorial on installing and using an IRC client:
     70Please familiarize yourself with how Twisted uses Trac by exploring the reports from this link:
     73With sufficient exploration you should be able to answer the following questions (you don't have to tell me the answers, just make sure you know how to find them):
     74  1. What is the oldest open Twisted ticket?
     75  2. How many tickets are currently waiting on review? How do we denote tickets waiting on a review (hint: look at the keyword)
     76  3. Using the custom query page at, find out how many open tickets we have that have the "documentation" keyword.
     78If you have not used svn before, please go through the svn training mission at:
     81If you have not used diff and patch before, please go through the diff and patch training mission at:
     84If you have any questions while going through this material, don't hesitate to get in touch. You can email me, and you can also find me as itamar on the Freenode IRC network; jesstess on Freenode can also be of help if I'm not around.
     86Once you've gone through this material, the next steps will be to:
     87  1. Meet up on IRC (stop by the #twisted channel)
     88  2. Check out and explore the Twisted source code
     89  3. Read a few parts of the Twisted core documentation and run some example Twisted scripts
     90  4. Run the Twisted test suite - cd into the checkout folder and run "bin/trial twisted".
     92And then you'll be in great shape to start working on your first Twisted ticket. We'll suggest a first ticket when you get in touch over email; you'd want to fix it in your Twisted svn checkout, run `svn diff`, upload the resulting patch to the ticket and then add the "review" keyword to the ticket. This process is described in detail here: