Differences between revisions 56 and 269 (spanning 213 versions)
⇤ ← Revision 56 as of 2006-04-18 04:58:00 →
Size: 1907
Editor: c-24-6-150-200
Comment:
← Revision 269 as of 2008-11-15 14:00:01 → ⇥
Size: 5197
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
These are the [http://code.google.com/soc/ Google "Summer of Code"] projects involving Python. ## page was renamed from SummerOfCode
This page coordinates the [[http://code.google.com/soc/|Google "Summer of Code"]] projects involving Python and mentored by the Python Software Foundation (PSF).
Line 3: Line 4:
For information on the accepted projects for 2005, see ["SummerOfCode/2005"]. Based on previous years, we are expecting a lot of competition so when making your application it is important to note that the PSF is looking for projects that:
Line 5: Line 6:
= How to apply as a mentor =  * enhance an existing Python project rather than start something complete from scratch;
 * contribute to the Python community rather than are merely written in Python.
 
Line 7: Line 10:
Apply through Google's online form. (Not up yet.) The 2007 PSF SoC coordinator is JamesTauber (jtauber at jtauber dot com). Contact him if you have any questions.
Line 9: Line 12:
 * [http://code.google.com/soc/mentorfaq.html Mentor FAQ] = Students: How to submit a proposal =
Line 11: Line 14:
= How to submit a proposal = Student applications are now open.
Line 13: Line 16:
 * [http://code.google.com/soc/studentfaq.html Student FAQ] [[http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents|Google's Advice for Students]]
Line 15: Line 18:
= Proposal ideas = Looking at the list of PSF [[SummerOfCode/Mentors]] can help you craft your proposal to match their interests.
Line 17: Line 20:
The following ideas are just suggestions. You're free to invent your own ideas, or to use their suggestions as starting points. = Tips on participating =
Line 19: Line 22:
 * Some ideas to help get you started: look at the SimpleTodo and CodingProjectIdeas pages.
 * 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.
 * Work on [http://www.djangoproject.com Django] -- a "high-level Python Web framework that encourages rapid development and clean, pragmatic design" ''(actually, Django will likely be its own Summer of Code sponsor; stay tuned -- JKM)''.
 * 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.
 * Improve Buildbot for python use and/or in general.		    1. Do not overbook yourself. Working on your project should be your main activity for the entire summer.
Line 31: Line 24:
= Accepted proposals =    2. You must provide weekly status reports.
Line 33: Line 26:
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.    1. Participate in the developer community by joining python-dev, jython-dev, or whatever mailing list is appropriate.
Line 35: Line 28:
 * None yet.    1. If you get stuck, ask for help instead of silently struggling. You can ask your mentor for help, or post a question to the development mailing list.

   3. You will be expected to learn how to use SVN.
 
= Mentors: How to apply =

The mentor's responsibility is to ensure the student makes progress. This could entail coaching them, providing motivation, making sure they aren't stuck, answering technical questions, or pointing the student to the proper resources.

Mentors should expect to get a weekly status report from their students, and should badger students who are not communicating. The weekly status should be reported to the PSF SoC coordinator.

However, the mentor is not expected to do work for the student.

Mentoring duties are expected to take a couple of hours per week.

See [[http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors|Google's Advice for Mentors]]

If you are interested in becoming a mentor:

 * Add your name to the mentor list at [[SummerOfCode/Mentors]].
 * join the [[http://mail.python.org/mailman/listinfo/soc2007-mentors|soc2007-mentors mailing list]]


== Project ideas ==

For 2007, the PSF would like to concentrate on proposals that
advance PSF projects (CPython and its documentation,
Jython and its documentation, the Python web site). That said, projects relating to other Python libraries, applications or implementations (PyPy) that are relevant to the promotion of the Python programming language are also encouraged.

The following pages list some ideas:

 * [[CodingProjectIdeas/PythonCore]] -- ideas for the CPython interpreter.
 * [[CodingProjectIdeas/StandardLibrary]]
 * https://www.drproject.org/DrProject/wiki/DrProjectSoC2007 -- DrProject ideas
 * http://wiki.python.org/jython/SummerOfCode -- Jython projects.
 * http://codespeak.net/pypy/dist/pypy/doc/project-ideas.html -- Some ideas for PyPy
 * http://code.google.com/p/sympy/wiki/SummerOfCode -- Ideas for SymPy
 * http://code.google.com/p/pyjamas/wiki/SummerOfCode -- Idea for Pyjamas
 * [[http://docutils.sourceforge.net/docs/dev/todo.html|The Docutils to-do list]] contains a wealth of ideas. Important projects are prioritized. Subscribe to the [[https://lists.sourceforge.net/lists/listinfo/docutils-develop|docutils-develop]] list and ask for advice.
 * http://webpy.infogami.com/ideas -- ideas for web.py
 * http://pyblosxom.sourceforge.net/blog/static/soc2007.html -- ideas for PyBlosxom
 * http://code.google.com/p/crunchy/wiki/SummerOfCodeIdeas -- ideas for Crunchy (educational software).
 * http://www.pysoy.org/wiki/SoC2007 -- ideas for PySoy (3d engine)
See also [[SummerOfCode/Mentors]] where potential mentors have mentioned projects they are willing to mentor.

== Other Organizations using Python ==

If you can't find a well-suited PSF project, but you still want to do something with Python for SOC 2007, you can also consider the projects offered by:

 * Bazaar (http://code.google.com/soc/bzr/about.html)
 * Django (http://code.google.com/soc/django/about.html)
 * Kamaelia, BBC Research (http://code.google.com/soc/bbc/about.html and http://kamaelia.sourceforge.net/SummerOfCode2007)
 * MoinMoin (see MoinMoin:GoogleSoc2007 )
 * Open Source Applications Foundation (http://code.google.com/soc/osaf/about.html)
 * Plone Foundation (http://code.google.com/soc/plone/about.html)
 * SCons (http://code.google.com/soc/scons/about.html and http://www.scons.org/wiki/GSoC2007)
 * Subversion (http://code.google.com/soc/svn/about.html)
 * The Space Telescope Science Institute (http://code.google.com/soc/stsci/about.html)
 * wxPython (http://code.google.com/soc/wxpython/about.html)
 * Zope Foundation (http://code.google.com/soc/zope/about.html)

All the mentoring organizations are listed here: http://code.google.com/soc/

== Previous years ==

 * [[SummerOfCode/2005]]
 * [[SummerOfCode/2006]]

This page coordinates the Google "Summer of Code" projects involving Python and mentored by the Python Software Foundation (PSF).

Based on previous years, we are expecting a lot of competition so when making your application it is important to note that the PSF is looking for projects that:

  • enhance an existing Python project rather than start something complete from scratch;
  • contribute to the Python community rather than are merely written in Python.

The 2007 PSF SoC coordinator is JamesTauber (jtauber at jtauber dot com). Contact him if you have any questions.

Students: How to submit a proposal

Student applications are now open.

Google's Advice for Students

Looking at the list of PSF SummerOfCode/Mentors can help you craft your proposal to match their interests.

Tips on participating

  1. Do not overbook yourself. Working on your project should be your main activity for the entire summer.
  2. You must provide weekly status reports.
  3. Participate in the developer community by joining python-dev, jython-dev, or whatever mailing list is appropriate.
  4. If you get stuck, ask for help instead of silently struggling. You can ask your mentor for help, or post a question to the development mailing list.
  5. You will be expected to learn how to use SVN.

Mentors: How to apply

The mentor's responsibility is to ensure the student makes progress. This could entail coaching them, providing motivation, making sure they aren't stuck, answering technical questions, or pointing the student to the proper resources.

Mentors should expect to get a weekly status report from their students, and should badger students who are not communicating. The weekly status should be reported to the PSF SoC coordinator.

However, the mentor is not expected to do work for the student.

Mentoring duties are expected to take a couple of hours per week.

See Google's Advice for Mentors

If you are interested in becoming a mentor:

Project ideas

For 2007, the PSF would like to concentrate on proposals that advance PSF projects (CPython and its documentation, Jython and its documentation, the Python web site). That said, projects relating to other Python libraries, applications or implementations (PyPy) that are relevant to the promotion of the Python programming language are also encouraged.

The following pages list some ideas:

See also SummerOfCode/Mentors where potential mentors have mentioned projects they are willing to mentor.

Other Organizations using Python

If you can't find a well-suited PSF project, but you still want to do something with Python for SOC 2007, you can also consider the projects offered by:

All the mentoring organizations are listed here: http://code.google.com/soc/

Previous years

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

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