Differences between revisions 50 and 51
Revision 50 as of 2007-03-12 22:28:10
Size: 5975
Editor: RunaSandvik
Comment:
Revision 51 as of 2007-03-13 01:20:11
Size: 5933
Comment:
Deletions are marked like this. Additions are marked like this.
Line 66: Line 66:
 1. Release Debian before december 2007.

Summer of Code 2007

?TableOfContents(2)

This wiki page is created to make it easier to plan and coordinate Debian's involvement in the [http://code.google.com/soc/ Google Summer of Code 2007].

Current Status (2007/03/09)

  • We've applied with Google to take part in the Summer of Code 2007. Our two current admins are SteveMcIntyre and StefanoZacchiroli. If last year is anything to go by, we'll probably add more admins later once the programme is up and running.

  • Now it's time to create a repository of proposals for the summer of code. To do so:
    1. please add an entry to the list below with a brief summary of the proposal (one-liner ideally)

    2. add to the entry a link pointint to a subpage of this page with a more detailed description of the proposal. For creating the new page you can start from the ?SummerOfCode2007/ProposalTemplate page; look for it in the left column when creating the new page

    A note about last-year proposals. Down in this page you can found the proposal from the last year. If you're still interested in proposing one of them, please move it to the list of 'this' year proposal, better filling the relative subpage. This way we will avoid proposals remaining here just for inertia on which no one is really interested to take part.

Timeline

(see [http://code.google.com/support/bin/answer.py?answer=60325 Google's FAQ])

  • March 5: Mentoring organizations can begin submitting applications to Google

  • March 12: Mentoring organization application deadline

  • March 13: Google program administrators review organization applications

  • March 14: List of accepted mentoring organizations published on code.google.com; student application period opens

  • March 24: Student application deadline

  • Interim Period: Mentoring organizations review and rank student proposals; where necessary, mentoring organizations may request further proposal detail from the student applicant

  • April 9: List of accepted student applications published on code.google.com

  • Interim Period: Students learn more about their project communities

  • May 28: Students begin coding for their GSoC projects; Google begins issuing initial student payments

  • Interim Period: Mentors give students a helping hand and guidance on their projects

  • July 9: Students upload code to code.google.com/hosting; mentors begin mid-term evaluations

  • July 16: Mid-term evaluation deadline; Google begins issuing mid-term student payments

  • August 20: Students upload code to code.google.com/hosting; mentors begin final evaluations; students begin final program evaluations

  • August 31: Final evaluation deadline; Google begins issuing student and mentoring organization payments

Contact info

For information on how to register to be a mentor, contact Steve or Zack. Please note that you should not register as a mentor if you intend to participate as a student.

For students, if you have questions or want to discuss the project you want to do you can mail the admins, discuss it in the debian-project mailing list, or join the #debian-soc channel on irc.debian.org.

If you would like to work on one of the projects below, as a student participating in Google's summer of code, watch this space for details of how to register.

Suggested GSoC Projects

  1. [wiki:/PiupartsImprovements Improvements to piuparts]

  2. [wiki:/SystemUpgradeTesting Testing system upgrades automatically using QEMU]

  3. Create a collaborative repository of meta-informations (["CRMI"]) about sources packages (including upstream URL, URL of upstream VCS, URL of upstream BTS, debian/watch file, etc.) on top of ["Mole"]. [wiki:/MoleAndCRMI More info]
  4. [wiki:/udebSupport Full support of udebs]
  5. [wiki:/ovalagent OVAL agent] to make it possible to control security update status for clusters of Debian systems
  6. [wiki:/commonsecuritychecks Common security checks] tool, to provide host-level security checks for the default Debian systems.
  7. [wiki:/autosecreview Automatic Security Review] lintian-like portal.
  8. [wiki:/AptCheckpoint apt-checkpoint] Revive the apt-checkpoint project [http://sourceforge.net/projects/apt-checkpoint/ sourceforge] for safer/better end-user experience when upgrading to testing

  9. [wiki:/ImplementTheCDDT Implement the Custom Debian Distributions Toolkit (CDDT)]
  10. [wiki:/RCRANBioC] Improvements and extension to the R CRAN / BioC packaging project [http://pkg-bioc.alioth.debian.org]

  11. [wiki:/live-helper Implement a GUI frontend for live-helper for building Debian Live systems]
  12. [wiki:/DebianCdTester Debian CD Tester] A program to sanity-check Debian CD and DVD images, like lintian/linda do for packages.

  13. [wiki:/WebCleanup Website cleanup] Clean up debian.org and integrate the wiki(s).

Mentors for other projects

Some information on what being a good mentor entails can be found here http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html

Infrastructure Provided to Students

As development must happen in the open, students of Debian projects will either receive access to existing source control repositories or setup an Alioth project. Alioth is a ?SourceForge like resource provided by Debian with access to Subversion/Arch/CVS repositories and services like bug tracking and mailing lists. The students are also expected to maintain a webpage or a wiki page to keep everyone up to date on their status.