Version 5 (modified by Itamar Turner-Trauring, 8 years ago) (diff)


Google Summer of Code 2012

Project Ideas

These are just ideas, we're open to other ideas as well.

For people who like variety

  • 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.

For people who want to focus on a single programming task

  • IPv6: We are still missing SSL, UDP, and client TCP IPv6 support. Add IPv6 support for these transports with a full API and test coverage for these additions. Add relevant examples and documentation.
  • Debugging user interface for the networking layer - implement a web-based replacement for gladereactor. The idea is to have a debugging user interface for running a Twisted process that shows existing listening ports and open connections, and allows you to view bytes flowing over the transports. gladereactor is a gtk-based half-finished implementation of this.
  • Python 3: Begin working towards Python 3 support. For a start, fix all bugs in Python 3 milestone: and run with no -3 warnings. Then, see how far you can get with actual port.
  • PyPy: Have PyPy be a fully supported platform, with all tests passing.

For people who want to work on documentation

  • Finish half-done documentation: Merge existing documentation from elsewhere, e.g. Conch in 60 seconds, or half-finished documentation that is in the tracker (there's the start of an IMAP howto, for example.)
  • lore2sphinx: finish converting our documentation from a custom format (Lore) to the community standard - RestructuredText as used by Sphinx. In particular, resolve all tickets in the lore2sphinx milestone: and then help transition the release process and to Sphinx by participating in a release.
  • For a particular subproject, review and improve existing examples and howtos and add missing documentation.Every example needs a description, e.g. has descriptions but doesn't. Every example should document its purpose, how it is run, and what it should do. Examples should use current coding and documentation standards and shouldn't use deprecated code. Documentation should use current coding and documentation standards in code snippets, and should use the preferred APIs. Some subprojects have very little documentation or examples and simply need more. Audit and update relevant man pages.

For the detailed-oriented person

  • Coverage: For a particular subproject, go for 100% API documentation and unit test code coverage.
  • Test suite cleanup: overall test suite cleanup, remove deprecations, fix deprecation warnings, get to the bottom of and fix our various recurring Windows errors, fix Windows compiler warnings, fix non-deterministic tests.