Differences between revisions 54 and 118 (spanning 64 versions)
Revision 54 as of 2007-03-15 22:59:13
Size: 6344
Editor: ?SvenLuther
Comment:
Revision 118 as of 2009-02-12 10:20:18
Size: 5650
Comment: pointer to 2008
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
== Current Status (2007/03/15) == == Final summary ==
Line 9: Line 9:
 * We've been accepted to take part in the Summer of Code 2007. Our
 two current admins are SteveMcIntyre and StefanoZacchiroli. We're
 looking for more mentors and ideas, and we need to start signing up
 students for projects (either the Debian ideas or their own).
This year all students finished their projects. All information including what each of them did can be found at:
Line 14: Line 11:
 * If you're a DD and you have a proposal for a project: http://lists.debian.org/debian-devel-announce/2007/10/msg00001.html
Line 16: Line 13:
  1. please add an entry to the list below with a '''brief''' summary of the proposal (one-liner ideally) See also next year's program : SummerOfCode2008
Line 18: Line 15:
  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 == Current Status (2007-04-12) ==

 * We've been accepted to take part in the Summer of Code 2007. Our admins are SteveMcIntyre, StefanoZacchiroli, AnthonyTowns, LukClaes and ErichSchubert.

 * We received over 100 student applications that were reviewed by the
 mentors. We asked google to aprove up to 20 projects for us, but we got only 9: http://code.google.com/soc/debian/about.html

 * The rest of the ideas and comments were stored and might be used in the future for improving Debian. (SummerOfCode2007IdeasList)
Line 21: Line 25:
(see [http://code.google.com/support/bin/answer.py?answer=60325 Google's FAQ]) see [http://code.google.com/support/bin/answer.py?answer=60325 Timeline in Google's FAQ]
Line 23: Line 27:
 * '''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
== Mailing list ==
Line 38: Line 29:
== Mentors and ideas == Now that we're getting into the process, we're using a mailing list to
organise things. Details are at
http://lists.alioth.debian.org/mailman/listinfo/soc-coordination . All
mentors should already be signed up, and students will be added when
project decisions have been made (if they're not already subscribed by
then).
Line 40: Line 36:
To register as a mentor, follow
[[http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-mentors-and-organization-administrators this process]] on the Google site. Please note that you should not
register as a mentor if you intend to participate as a student.
== This year's projects ==
Line 44: Line 38:
Also add yourself to the page here, either with your project idea(s)
or in the 'other' list at the bottom.
More details coming soon on each one...
Line 47: Line 40:
== Students == === Implementing Mole, infrastructure for managing information ===
Line 49: Line 42:
If you would like to work on one of the projects below, as a student
participating in Google's summer of code, you also need to sign up;
[[http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-student-applicants details]].
 * '''Student:''' [wiki:Jeroen Jeroen van Wolffelaar]
 * '''Mentor:''' Martin Michlmayr
 * '''VCS:'''
 * '''Mailing list:'''
 * '''IRC:'''
 * '''Original idea:'''
 * '''Final mentor summary:'''
Line 53: Line 50:
If you have questions or want to discuss the project you want to do
you can mail the admins, come and find us. Discuss it in the
debian-project mailing list, or join the #debian-soc channel on
irc.debian.org.
=== Automated Upgrade Testing Using QEMU ===
~+(Virtual Live OS Upgrade Testing Suite)+~
Line 58: Line 53:
== Suggested GSoC Projects ==  * '''Student:''' IanHaken
 * '''Mentor:''' LarsWirzenius
 * '''VCS:''' svn://svn.debian.org/vlosuts/
 * '''Mailing list:''' vlosuts-devel@lists.alioth.debian.org
 * '''IRC:''' #debian-vlosuts on irc.oftc.net
 * '''Original idea:''' [http://code.google.com/soc/debian/appinfo.html?csaid=24C7766EC4271F15 GSoc Abstract]
 * '''Final mentor summary:'''
Line 60: Line 61:
 1. [wiki:/PiupartsImprovements Improvements to piuparts]
 1. [wiki:/SystemUpgradeTesting Testing system upgrades automatically using QEMU]
 1. 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]
 1. [wiki:/udebSupport Full support of udebs]
 1. [wiki:/ovalagent OVAL agent] to make it possible to control security update status for clusters of Debian systems
 1. [wiki:/commonsecuritychecks Common security checks] tool, to provide host-level security checks for the default Debian systems.
 1. [wiki:/autosecreview Automatic Security Review] lintian-like portal.
 1. [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
 1. [wiki:/ImplementTheCDDT Implement the Custom Debian Distributions Toolkit (CDDT)]
 1. [wiki:/RCRANBioC] Improvements and extension to the R CRAN / BioC packaging project [http://pkg-bioc.alioth.debian.org]
 1. [wiki:/live-helper Implement a GUI frontend for live-helper for building Debian Live systems]
 1. [wiki:/DebianCdTester Debian CD Tester] A program to sanity-check Debian CD and DVD images, like lintian/linda do for packages.
 1. [wiki:/WebCleanup Website cleanup] Clean up debian.org and integrate the wiki(s).
 1. [:EmbeddedDebian:Embedded Debian] Help emdebianize debian packages and work on tools to make it possible to (cross) build useful mini-debian systems for handhelds and embedded systems.
 1. [wiki:/SummerOfCode2007/KernelConfigProposal Kernel Config] A tool to manage the debian kernel configuration files.
=== Piuparts improvements ===
Line 76: Line 63:
== Mentors for other projects ==  * '''Student:''' [wiki:Ana Ana Beatriz Guerrero López]
 * '''Mentor:''' LukClaes
 * '''VCS:''' svn://svn.debian.org/piuparts/
 * '''Mailing list:''' http://lists.alioth.debian.org/mailman/listinfo/piuparts-devel
 * '''IRC:''' #piuparts
 * '''Original idea:'''
 * '''Final mentor summary:'''
Line 78: Line 71:
 * LukClaes - projects related to QA or release/testing migration
 * Martin Michlmayr (tbm) - projects related to QA
 * [wiki:madduck Martin Krafft] - projects related to [http://wiki.logcheck.org/index.cgi/logfilter logfilter] and ["netconf"].
 * AigarsMahinovs
 * RaphaelHertzog
 * AnthonyTowns
 * Wookey - projects related to Embedded Debian, cross-toolchains/building, slimming down Debian base.
=== Bug Triage and Forward Tool ===

 * '''Student:''' Gustavo Rezende Montesino
 * '''Mentor:''' Loïc Minier
 * '''VCS:''' git://git.debian.org/git/bug-triage/bugtaf.git/
 * '''Mailing list:''' bug-triage-devel@lists.debian.org
 * '''IRC:'''
 * '''Original idea:''' [http://lists.debian.org/debian-project/2007/03/msg00169.html Proposal draft]
 * '''Final mentor summary:'''

=== BitTorrent Proxy for Debian Archive ===

 * '''Student:''' CameronDale
 * '''Mentor:''' AnthonyTowns
 * '''VCS:''' svn://svn.debian.org/debtorrent/debtorrent/trunk
 * '''Mailing list:''' debtorrent-devel@lists.alioth.debian.org
 * '''Website:''' http://debtorrent.alioth.debian.org
 * '''IRC:''' #debtorrent on irc.oftc.net
 * '''Original idea:'''
 * '''Final mentor summary:'''

=== OVAL Agent for Debian ===

 * '''Student:''' PavelVinogradov
 * '''Mentor:''' JavierFernandezSanguino
 * '''VCS:''' svn://svn.debian.org/svn/oval/
 * '''Mailing list:''' oval-devel@lists.alioth.debian.org
 * '''Website:''' http://oval.alioth.debian.org/
 * '''Original idea:''' [http://nixdev.net/projects/oval/debian_oval_proposal.html Submitted proposal]
 * '''Final mentor summary:'''

=== Bug Submission and Manipulation Web-based User Interface for debbugs ===

 * '''Student:''' [wiki:Marga Margarita Manterola Rivero]
 * '''Mentor:''' StefanoZacchiroli
 * '''VCS:''' svn://svn.debian.org/bts-webui/
 * '''Mailing list:''' http://lists.debian.org/debian-debbugs/
 * '''IRC:'''
 * '''Original idea:'''
 * '''Final mentor summary:'''

=== A modular lintian-like CD-image testing tool ===

 * '''Student:''' [wiki:Tincho Martín Hernán Ferrari]
 * '''Mentor:''' SteveMcIntyre
 * '''Wiki page:''' [wiki:DebianCDTester DebianCD Tester]
 * '''VCS:'''
 * '''Mailing list:'''
 * '''IRC:'''
 * '''Original idea:''' SummerOfCode2007/DebianCdTester
 * '''Final mentor summary:'''

=== GUI frontend for live-helper for building live Debian systems ===

 * '''Student:''' [wiki:ChrisLamb Chris Lamb]
 * '''Mentor:''' [wiki:daniel Daniel Baumann]
 * '''VCS:''' svn://svn.debian.org/debian-live/dists/trunk/live-magic/
 * '''Mailing list:''' debian-live-devel@lists.alioth.debian.org
 * '''IRC:''' #debian-live on irc.oftc.net
 * '''Original idea:''' [http://lists.alioth.debian.org/pipermail/debian-live-devel/2007-March/001029.html Submitted proposal]
 * '''Final mentor summary:'''

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

Final summary

This year all students finished their projects. All information including what each of them did can be found at:

http://lists.debian.org/debian-devel-announce/2007/10/msg00001.html

See also next year's program : SummerOfCode2008

Current Status (2007-04-12)

Timeline

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

Mailing list

Now that we're getting into the process, we're using a mailing list to organise things. Details are at http://lists.alioth.debian.org/mailman/listinfo/soc-coordination . All mentors should already be signed up, and students will be added when project decisions have been made (if they're not already subscribed by then).

This year's projects

More details coming soon on each one...

Implementing Mole, infrastructure for managing information

  • Student: [wiki:Jeroen Jeroen van Wolffelaar]

  • Mentor: Martin Michlmayr

  • VCS:

  • Mailing list:

  • IRC:

  • Original idea:

  • Final mentor summary:

Automated Upgrade Testing Using QEMU

(Virtual Live OS Upgrade Testing Suite)

Piuparts improvements

Bug Triage and Forward Tool

BitTorrent Proxy for Debian Archive

OVAL Agent for Debian

Bug Submission and Manipulation Web-based User Interface for debbugs

A modular lintian-like CD-image testing tool

GUI frontend for live-helper for building live Debian systems

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.