Changes between Version 7 and Version 8 of GoogleSOC


Ignore:
Timestamp:
02/28/2012 10:39:08 AM (8 years ago)
Author:
Thijs Triemstra
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GoogleSOC

    v7 v8  
    1515  * [wiki: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.
    1616  * 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.
    17   * Python 3: Begin working towards Python 3 support. For a start, fix all bugs in Python 3 milestone: http://twistedmatrix.com/trac/milestone/Python-3.x and run with no -3 warnings. Then, see how far you can get with actual port.
    18   * PyPy: Have PyPy be a fully supported platform, with all tests passing.
     17  * Python 3: Begin working towards Python 3 support. For a start, fix all the bugs in the [milestone:Python-3.x] milestone and run with no `-3` warnings. Then, see how far you can get with actual port.
     18  * PyPy: Have [http://pypy.org PyPy] be a fully supported platform, with all tests passing.
    1919
    2020=== For people who want to work on documentation ===
    2121
    22   * 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.)
    23   * 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: http://twistedmatrix.com/trac/milestone/Lore%20to%20Sphinx and then help transition the release process and twistedmatrix.com to Sphinx by participating in a release.
    24   * For a particular subproject, review and improve existing examples and howtos and add missing documentation.Every example needs a description, e.g. http://twistedmatrix.com/documents/current/web/examples/index.html has descriptions but http://twistedmatrix.com/documents/current/names/examples/index.html 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.
     22  * Finish half-done documentation: Merge existing documentation from elsewhere, e.g. [ticket:5474 Conch in 60 seconds], or half-finished documentation that is in the tracker (there's the start of an IMAP howto, for example.)
     23  * 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 [milestone:"Lore to Sphinx"] milestone and then help transition the release process and twistedmatrix.com to Sphinx by participating in a release.
     24  * For a particular subproject, review and improve existing examples and howtos and add missing documentation. Every example needs a description, e.g. http://twistedmatrix.com/documents/current/web/examples/index.html has descriptions but http://twistedmatrix.com/documents/current/names/examples/index.html 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.
    2525
    2626=== For the detailed-oriented person ===
    2727
    2828  * Coverage: For a particular subproject, go for 100% API documentation and unit test code coverage.
    29   * 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.
     29  * 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.
    3030
    3131=== For people who like helping the world at large ===
    3232
    33   * Fix Twisted in non-US locales. As a first step you'd want to create a custom locale for Linux that was malicious about everything (e.g. lowercasing returns random unexpected bytes, dates are funky, etc.). This would be used to find places where Twisted is making US-centric assumptions, but would actually be a useful project for the Linux community in general. Then, fix resulting bugs in Twisted. Some relevant background material: http://www.moserware.com/2008/02/does-your-code-pass-turkey-test.html
     33  * Fix Twisted in non-US locales. As a first step you'd want to create a custom locale for Linux that was malicious about everything (e.g. lower-casing returns random unexpected bytes, dates are funky, etc.). This would be used to find places where Twisted is making US-centric assumptions, but would actually be a useful project for the Linux community in general. Then, fix resulting bugs in Twisted. Some relevant background material: http://www.moserware.com/2008/02/does-your-code-pass-turkey-test.html