Differences between revisions 144 and 269 (spanning 125 versions)
Revision 144 as of 2006-05-03 17:27:54
Size: 4051
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:
This page is for students and mentors for the [http://code.google.com/soc/ Google "Summer of Code"] projects involving Python and mentored by the Python Software Foundation (PSF). ## 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:
Discussion about any Python-related SoC topic should take place on
[http://mail.python.org/mailman/listinfo/soc2006 the soc2006 mailing list].
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 6: Line 6:
For information on last year's accepted projects, see ["SummerOfCode/2005"].  * 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.
Line 10: Line 14:
[http://code.google.com/soc/student_signup.html Apply through Google's online form.] Student applications are now open.
Line 12: Line 16:
[http://code.google.com/soc/student_step1.html Submit an application.] [[http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents|Google's Advice for Students]]
Line 14: Line 18:
The Drupal folks have some good information for students on how you should write your application: Looking at the list of PSF [[SummerOfCode/Mentors]] can help you craft your proposal to match their interests.
Line 16: Line 20:
 * [http://drupal.org/node/59963 Student requirements]
 * [http://drupal.org/node/59037 HOWTO write an application]
= Tips on participating =
Line 19: Line 22:
Here is Google's [http://code.google.com/soc/studentfaq.html Student FAQ]    1. Do not overbook yourself. Working on your project should be your main activity for the entire summer.
Line 21: Line 24:
   2. You must provide weekly status reports.

   1. Participate in the developer community by joining python-dev, jython-dev, or whatever mailing list is appropriate.

   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.
 
Line 23: Line 34:
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. However, the mentor is not expected to do work for the student. In order to accomplish this, the mentor is expected to dedicate a couple of hours per week. 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.
Line 25: Line 36:
[http://code.google.com/soc/mentor_step1.html Apply through Google's online form.] 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.
Line 27: Line 38:
 * [http://mail.python.org/pipermail/python-dev/2006-April/063965.html Announcement made to Python-Dev]
 * [http://code.google.com/soc/mentorfaq.html Mentor FAQ]
 * Contact [mailto:nnorwitz@gmail.com Neal Norwitz]
  * If neither Neal nor Guido know you personally, please provide personal references of some sort.
However, the mentor is not expected to do work for the student.
Line 32: Line 40:
= Proposal ideas = Mentoring duties are expected to take a couple of hours per week.
Line 34: Line 42:
The ideas on the following pages are just suggestions. You're free to invent your own ideas, and don't have to use these suggestions as starting points. See [[http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors|Google's Advice for Mentors]]
Line 36: Line 44:
 * ["SummerOfCode/PythonCore"]
 * ["SummerOfCode/PythonLibraries"]
 * ["SummerOfCode/Applications"]
 * ["SummerOfCode/PythonWebSite"]
If you are interested in becoming a mentor:
Line 41: Line 46:
= Related sponsors =  * Add your name to the mentor list at [[SummerOfCode/Mentors]].
 * join the [[http://mail.python.org/mailman/listinfo/soc2007-mentors|soc2007-mentors mailing list]]
Line 43: Line 49:
While not sponsors themselves, the PyPy and Jython projects have many SoC sized tasks available. For PyPy, see [http://codespeak.net/pypy/dist/pypy/doc/independent-project-ideas.html] for some concrete suggestions.
Line 45: Line 50:
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]. == Project ideas ==
Line 47: Line 52:
MoinMoin is also participating as their own organization, see [http://moinmoin.wikiwikiweb.de/GoogleSoc2006] for 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.
Line 49: Line 56:
[http://www.bbc.co.uk/rd/ BBC Research] is also a mentor organisation for python projects using the [http://kamaelia.sourceforge.net/Introduction.html Kamaelia] project for audio/video & multimedia/networking related projects, also for graphical construction of systems. Please see our [http://kamaelia.sourceforge.net/SummerOfCode2006.html Summer of Code] page for more details. (There's some discussion on edu-sig which coincides with some of aims BTW, so if you're interested in python for schools, talk to us, we can't guarantee anything but you'll understand why we're interested if you chat to us!) The current list of ideas there that we're looking to mentor includes the following:
 * "Trusted Communications" (trusted by the user)
 * "Component bindings to AV codecs"
 * "Modifications of Visual Graphline editors, Reapplication to Graphline Video Editting"
 * "CSS-esque Styling and XML (?) Layout Definition of Pygame Applications"
 * "Collaborative Sketching Server - A P2P Events Backplane Application"
 * "Creation of an integrated bit torrent component"
 * "OpenGL widget framework"
 * "Hierarchical topology visualiser"
 * "Hierarchical Introspector"
 * "Distributed physics"
 * "Primitives for graphical composition"
The following pages list some ideas:
Line 62: Line 58:
= Accepted proposals =  * [[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.
Line 64: Line 72:
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. == Other Organizations using Python ==
Line 66: Line 74:
 * None yet. 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.