Differences between revisions 70 and 71
Revision 70 as of 2006-04-20 15:17:24
Size: 3652
Editor: acgn226
Comment:
Revision 71 as of 2006-04-20 17:21:06
Size: 4522
Editor: IanBicking
Comment: added several items
Deletions are marked like this. Additions are marked like this.
Line 42: Line 42:
 * Create a Python web app server, synthesized from the many options already available, with an eye towards the total developer experience.
 * A web-based IDE, offering through-the-web editing (with version control), execution, and testing of code.
 * Integrate a Javascript interpreter with Python. [http://webcleaner.sourceforge.net/ WebCleaner] has some initial work; so extracting, documenting, and refining that code would be in order.
 * [http://pyxides.stani.be/ PyxIDE] has several potential projects related to IDEs in Python. Real-time code analysis would be a good project (which could in turn be used to build auto-completion and other tools).
 * 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.

These are the [http://code.google.com/soc/ Google "Summer of Code"] projects involving Python and mentored by the Python Software Foundation.

For information on the accepted projects for 2005, see ["SummerOfCode/2005"].

How to apply as a mentor

[http://code.google.com/soc/mentor_step1.html "Apply through Google's online form."]

How to submit a proposal

Proposal ideas

The following ideas are just suggestions. You're free to invent your own ideas, or to use their suggestions as starting points.

  • Some ideas to help get you started: look at the SimpleTodo and CodingProjectIdeas pages. [http://www.python.org/dev/peps/pep-0042/ PEP 42] also lists feature ideas.

  • Revive restricted Python -- inspired by a recent thread on the py3k list.
  • Create a bunch of modules like what Squeak has for 3D modeling, events etc. (the exact list may be somewhat different, I haven't researched this in any depth). This is inspired by a recommendation from Alan Kay made at the Shuttleworth workshop.
  • Add a web-based admin interface and/or user-oriented views to [http://www.third-bit.com/drproject DrProject], a lightweight project management portal intended for use in software engineering courses.

  • Help improve the www.python.org web site production system (pyramid) and write documentation to prepare it for open source release.
  • There are a number of potential TurboGears projects that may be interesting related to Kid, SQLAlchemy and TurboGears itself (like the FastData package).

  • Help move www.python.org towards dynamic content generation techniques.
  • Improve Buildbot for python use and/or in general.
  • Add regular code-coverage (both C and Python) to the build system (maybe even to Buildbot?)
  • The PyPy project has lots of SoC sized tasks. Ask on the pypy-dev mailing list.

  • Improve Jython
  • Write a new and useful application in Python.
  • Improve an existing Python application (e.g. Mailman, BitTorrent, Zope). Some Python-based projects are SoC mentoring organizations in their own right, so you might end up being mentored by them, not the PSF.

  • Write an IPC or RPC package to allow for concurrent Python execution.
  • Work on unit test suite. This includes not only developing support code (such as decorators to flag tests that are implementation-specific, known to fail, etc.), but also to have more code coverage in the unit tests.
  • Implement ctypes support for GCC ARM platforms. The underlying issue is lack of closure API support for ARM in libffi. A patch available at http://handhelds.org/~pb/arm-libffi.dpatch, that should be hopefully a good starting point. ctypes CVS has a libffi_arm_wince directory, which also seems to support closure API.

  • Improve Python Debugger(PDB).Some of general ideas are here: ["PdbImprovments"].If you have any sugesstions related to pdb add them there.

  • Create a Python web app server, synthesized from the many options already available, with an eye towards the total developer experience.
  • A web-based IDE, offering through-the-web editing (with version control), execution, and testing of code.
  • Integrate a Javascript interpreter with Python. [http://webcleaner.sourceforge.net/ WebCleaner] has some initial work; so extracting, documenting, and refining that code would be in order.

  • [http://pyxides.stani.be/ PyxIDE] has several potential projects related to IDEs in Python. Real-time code analysis would be a good project (which could in turn be used to build auto-completion and other tools).

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

Related sponsors

Those interested in working in [http://www.djangoproject.com Django] may do so [http://code.djangoproject.com/wiki/SummerOfCode2006 under the auspices of the Django group].

Accepted proposals

Note: if a project is listed as having two mentors, the first mentor listed is the primary mentor, and the second one is the back-up mentor.

  • None yet.

SummerOfCode/2007 (last edited 2008-11-15 14:00:01 by localhost)

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