Differences between revisions 4 and 5
Revision 4 as of 2006-05-23 14:12:18
Size: 1414
Comment:
Revision 5 as of 2008-11-15 14:00:17
Size: 1426
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * Automate postings to the [http://python.org/community/jobs/ Python Job Board].  * Automate postings to the [[http://python.org/community/jobs/|Python Job Board]].
Line 11: Line 11:
 * There are a lot of potential [http://docutils.sourceforge.net/ Docutils] and [http://docutils.sourceforge.net/rst.html reStructuredText] projects in the [http://docutils.sourceforge.net/docs/dev/todo.html To Do List]. Some examples (listed in the "Minimum Requirements..." section): Nested inline markup; Python Source Reader; Suitability for Python module documentation.
 * Create a source code analysis tool similar to that used to produce reports in [http://maven.apache.org/ Maven]. Perhaps integrate it with [http://projects.edgewall.com/trac Trac].
 * There are a lot of potential [[http://docutils.sourceforge.net/|Docutils]] and [[http://docutils.sourceforge.net/rst.html|reStructuredText]] projects in the [[http://docutils.sourceforge.net/docs/dev/todo.html|To Do List]]. Some examples (listed in the "Minimum Requirements..." section): Nested inline markup; Python Source Reader; Suitability for Python module documentation.
 * Create a source code analysis tool similar to that used to produce reports in [[http://maven.apache.org/|Maven]]. Perhaps integrate it with [[http://projects.edgewall.com/trac|Trac]].

python.org website, docs, tools

  • Automate postings to the Python Job Board.

  • Help improve the www.python.org web site production system (pyramid) and write documentation to prepare it for open source release.
  • Help move www.python.org towards dynamic content generation techniques. (Note that Fredrik Lundh has already written an application that's a front-end for content stored in a wiki.)
  • Improve Buildbot for python use and/or in general.
    • Add a SQL backend to store build results
    • Implement per-test-case "Problem Tracking"
    • write more status display plugins, both web and IM
  • Several DocumentationTools exist for Python. Choose one and improve it. Choose two and combine their features. Choose four or more and take over the world. The Python documentation world, at least.

  • There are a lot of potential Docutils and reStructuredText projects in the To Do List. Some examples (listed in the "Minimum Requirements..." section): Nested inline markup; Python Source Reader; Suitability for Python module documentation.

  • Create a source code analysis tool similar to that used to produce reports in Maven. Perhaps integrate it with Trac.

SummerOfCode/PythonWebSite (last edited 2008-11-15 14:00:17 by localhost)

Unable to edit the page? See the FrontPage for instructions.