[[PageOutline]]
= Scipy Summer of Code =

Please see the SummerofCodeIdeas.

According to the [http://code.google.com/support/bin/answer.py?answer=60325&topic=10729 Google SoC timeline], coding (and payments) start on May 28th. That should be plenty of time to make sure you have everything you need to succeed, and that all infrastructure issues, both with Scipy and with Google, get resolved.

Before May 28th, you should make sure that you have completed all of the "First Steps" listed below:

== First Steps ==

 1. Get a subversion account for Scipy and [https://projects.scipy.org/scipy/scikits/ Scikits]
 1. Join both the [http://scipy.org/Mailing_Lists Scipy user and developer mailing lists].  You should view these lists as a resource and a place to float ideas coming out of your project work.  Please make active use of these lists: we will be reading them too, and it gives you access to the resources of a larger community.
 1. Refine scope, milestones, and deliverables.
 1. Create a blog for your project.  As per the PSF's request, you should post notes about progress, problems, discoveries, etc.  All the standard blogs provide syndication feeds in at least one XML format.  These XML feeds will be accessed periodically by a script and compiled into a "group blog" (for example, see http://www.planetpython.org/).  If you don't have a preference, you should probably just use blogger.com since it's a Google service.
 1. Install the development version of Scipy from subversion.  Make sure to run all the tests.
 1. Familiarize yourself with the relevant sections of the Scipy code.
 1. Read through the guidelines below including reading the links.

== Guidelines ==

 1. '''Style:'''  Please install [http://www.logilab.org/857 pylint] and run it often as a check on your code quality.
  * [http://www.python.org/dev/peps/pep-0008/ Style Guide for Python Code]
  * [http://projects.scipy.org/scipy/numpy/wiki/CodingStyleGuidelines Numpy Style Guide]
 1. '''Testing:'''  Please note that good documentation strings and unit tests are a crucial part of Scipy code base.  These are absolutely necessary for your code to be usable by others.
  * TestingGuidelines
 1. '''Documentation:'''
  * [http://projects.scipy.org/scipy/numpy/wiki/DocstringStandards Docstring standards]
  * [http://projects.scipy.org/scipy/numpy/browser/trunk/numpy/doc/HOWTO_DOCUMENT.txt How To Document]
 1. '''License:''' All Scipy code should be made available under a revised BSD-style license.

= SoC 2007 =
We have two [http://code.google.com/soc/ Google's Summer of Code 2007] projects through the [http://wiki.python.org/moin/SummerOfCode Python Software Foundation].

== MachineLearning for !SciPy and !SciKits ==
{{{
Student: David Cournapeau
Mentor: Jarrod Millman
Backup mentor: Brian Hawthorne
}}}

== Modeling system for OptimizationProblems for !SciPy and !SciKits ==
{{{
Student: Dmitrey Kroshko
Mentor: Alan Isaac
Backup mentor: Anne Archibald
}}}

= SoC 2006 =

== Neural Nets in !SciPy ==

{{{
Student: Frederic Mailhot
Mentor: Robert Kern
}}}

The goal of this project is to extend !SciPy's functionality by adding modules for the design, training and use of a variety of neural network architectures, including standard feedforward and recurrent networks, among others. As a guide I intend to work from the modules in Matlab's Netlab toolkit, as well as from my own experience implementing recurrent networks.

== Support Vector Machines for !SciPy ==

{{{
Student: Albert Strasheim
Mentor: Dave Kammeyer
}}}

Integrating libsvm (and possibly other SVM libraries) with !SciPy using ctypes and providing various tools for manipulating datasets for use with SVMs.