Differences between revisions 110 and 111
Revision 110 as of 2006-05-26 14:36:33
Size: 16910
Editor: BaruchEven
Revision 111 as of 2006-05-26 14:49:54
Size: 1676
Editor: BaruchEven
Comment: Remove suggested projects, make it a page for those who follow progress on soc
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
Information on how to register to be a mentor was posted to debian-private, contact baruch (baruch@debian.org) if you need more info. Please note that you should not register as a mentor if you intend to participate as a student. Debian SoC coordinator: Baruch Even baruch@debian.org
Line 22: Line 22:
For students, if you have questions or want to discuss the project you want to do you can mail baruch, discuss it in the debian-project mailing list, or join the #debian-soc channel on OFTC. Students who have any issue with their mentor or a mentor who has an issue with their student should contact the coordinator to help resolve it.
Line 24: Line 24:
If you would like to work on one of the projects below, as a student participating in Google's summer of code, please go submit your application on this webpage:

Mentors should login to the system read, review and comment on the projects at http://code.google.com/soc/debian/open.html

== Possible Projects (in () possible mentors) ==
(also see [http://www.debian.org/devel/todo/ the general TODO list] and the EtchTODOList)

=== General ===
 * Improve the '''boot system''': ''speed up and make it dependency based. See discussions on [http://lists.alioth.debian.org/pipermail/initscripts-ng-devel/ the initscripts-ng list] and [http://wiki.debian.org/LSBInitScripts LSB init script page].'' Some [http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/2006-January/000542.html project ideas] are already written. (pere) -- multiple proposals there, don't propose this also
 * Finish the CollaborativeMaintenance project (RaphaelHertzog)
 * Make Debian more suitable for embedded systems, e.g. by removing Perl from the base system
 * Unload ftp.debian.org, with the RedirectProposal (aba/zobel)
 * FriendsOfDebian website, a debian community site that could also raise money for debian

=== QA related ===
 * Improve/unify the '''QA websites''': ''packages.qa.d.o, qa.d.o/developer, dehs, etc''
 * Create a better environment for regression/unit tests (tbm)
 * Improve the '''system to handle WNPP''': ''including expiry of ITPs, checking that orphaned packages have correct maintainer fields, etc.'' (DavidMorenoGarza)
 * Create a collaborative repository of meta-informations about sources packages (including upstream URL, URL of upstream VCS, URL of upstream BTS, debian/watch file, etc.) (RaphaelHertzog)
 * Help [http://dehs.alioth.debian.org Dehs project] to accept watch submitting and maintaining in an external framework instead of the single deb packages. Improve the Dehs postgres Db structure to optimizing query speed. Create rss feed with useful information from Dehs data. Collaborate with devscript maintainer to specify in a standar way the upstream news/changelog file in watch file and write with devscript package maintainer an official policy about watch file. Optimize, clean and standardize source code. (Stefano Fabri)
 * Add improvements to the BTS LDAP gateway like last-change-dates, last-mail, full-content, etc. (DavidMorenoGarza)
 * A program to sanity-check Debian CD and DVD images, like lintian/linda do for packages. (SteveMcIntyre)
 * BTS interface in kmail: on display of a bts related mail (headers!), add buttons like 'view this bug', 'close/reopen this bug' (would ask for version first), 'edit bug tags', 'set severity', 'retitle', ... to the toolbar (cmot, just a funky idea...)
 * Web frontend for QA applications (linda, lintian, piuparts) and other packaging utilities (like pbuilder) Some work has been done in that topic, and it could be useful for CollaborativeMaintenance too

=== Release/Testing transition related ===
 * Improve '''Britney'''; britney is the name of the scripts used to update Debian's testing distribution: it automates some of the hard problems of Debian release management. See [http://azure.humbug.org.au/~aj/blog/debian/britney AJ's blog] and the [http://www.debian.org/releases/testing/ general info about Testing] (aba)
 * Create a "Migration Tracking System" which can be used to track the various migrations that are happening. It should have a web interface as well as a mail interface. It should transparently make use of debbug's usertags to keep track of the bugs related to a specific transition. (RaphaelHertzog)

=== Package management ===
 * Improve '''DebTags''': ''central database rewrite, review functionality, tag adoption and such'' (ErichSchubert?)
 * '''DebTags''': AI tagger (bayesian etc.) (ErichSchubert?)
 * add powerful tag-based search capabilites [http://debtags.alioth.debian.org/cgi-bin/search.cgi Debtags-Enhanced Search] to aptitude (check out the link!)
 * Unify '''apt, dpkg''', etc (aba) ''but note that wajig is already a rather nice Python-based wrapper around apt, dpkg, apitude, ...''
 * Introduce real '''perl shlibs''' (aba)
 * Improve '''shlibs''': ''to caclulate the used shlibs, rather than the theorically required ones'' (aba)
 * Build a [http://www.r-project.org R] / [http://cran.r-project.org CRAN] package generator system for [http://cran.r-project.org CRAN] to extend the current approx. 50 packages to the full 800 or so. All of these packages actually build automagically thanks to existing '''cdbs''' rules. We need a simple stateful system to keep track of what has been added to [http://cran.r-project.org CRAN], what has been updated etc pp. There is a somewhat dormant [http://alioth.debian.org/projects/pkg-bioc/ Alioth Project] with some info. R knowledge helpful, Perl/Python/Ruby/... to implement. (DirkEddelbuettel)
 * [[Anchor(dh_ocaml)]] Automate computation of [http://caml.inria.fr OCaml] library dependencies (re-)writing `dh_ocaml`. See: [http://lists.debian.org/debian-ocaml-maint/2005/04/msg00046.html idea description], [http://bugs.debian.org/328422 proof of concept implementation (#328422)]. (StefanoZacchiroli)
 * Make RubyGems work nicely together with the Debian packaging system and Debian Ruby modules. (DavidMorenoGarza)
 * Revive the apt-checkpoint project [http://sourceforge.net/projects/apt-checkpoint/ sourceforge] for safer/better end-user experience when upgrading to testing
 * Add support for multiarch. [http://lists.debian.org/debian-devel/2004/01/msg00762.html] [http://wiki.debian.org/IRC/debian-tech/Logs/20050927-multiarch?highlight=%28multiarch%29]

=== Individual packages ===
 * Rewrite [http://packages.qa.debian.org/debian-cd debian-cd], the scripts used to create CD images. The current debian-cd works but has many flaws/limitations. Check out old discussions on the subject:
   * http://lists.debian.org/debian-cd/2004/01/threads.html#00025
   * http://lists.debian.org/debian-cd/2004/01/msg00045.html
   * Many people used modified version of debian-cd (Ubuntu, Debian-Edu, ...) and the new design should suit them all.
 * Add '''IPv6 support to vserver''' (aba)
 * Improve support of '''pinning in apt''' ["real" dependency resolver, better docs, graphical interface (?), allow matching in Packages, etc] (aba)
 * Make '''reportbug''' enhancements: ''graphical and/or web-based, so it's easier for users to report bugs''
 * Improve '''wpasupplicant''': ''Split out the roaming functionality from wpasupplicant and associate based on what is known to the system from /etc/network/interfaces.'' (KyleMcMartin)
 * Fix and enhance '''apt-listbugs''': ''There are quite a few seemingly simple bugs and wishes in the BTS, but it's seen no updates for 10 months. A few small changes would make it much more useful.'' (RaphaelHertzog: probably too limited in scope to be a good project).

=== New applications ===
 * Create a Python/GTK/QT '''app to manage Debian BTS''': ''would queue actions and then send an e-mail to the BTS to commit changes, make it easier to browse bugs, cross-reference, tag/update/close, etc'' -- proposed multiple times (meaning what?)
  * (StefanoZacchiroli: this overlaps with the ''make reportbug enhancements'' point above. What about splitting the above one in two: (1) provide a gui for `reportbug`, (2) provide a web ui for `reportbug`? If, besides interfaces, more features for `reportbug` are requested they should be described separately as well)
  * (PhilippKern: Managing bugs is likely to be separate from reporting bugs, it's rather a superset. It may be however implemented in the same application. But then it should only expose the bug management features to end-users if they want it to. I already volunteered to take this one, ''if it would be a valid project request'', in private to aba, as he's the creator of the bts2ldap gateway. Not reply yet, though.)
 * Create a user-friendly '''security-update notifier/installer'''
 * Package and integrate [http://www.networkmultimedia.org NMM - Network Multimedia-Middleware]. As NMM becomes (one of) the new KDE 4 multimedia backends (see this [http://www.linuxtag.org/2006/de/besucher/programm/freies-vortragsprogramm/samstag.html?talkid=319 presentation at the Linuxtag2006]) this would be initial work to support KDEs new multimedia framework Phonon.(nmm provides already sarge package)
 * Package and integrate of [http://www.nomachine.com NX] and [http://freenx.berlios.de FreeNX]. See also [http://lists.alioth.debian.org/pipermail/pkg-nx-group/2006-April/000135.html this mail].
 * Help implement ["CDDT"] -- Custom Debian Distributions Toolkit. The toolkit is partially functional, but there are a lot of things to do, for the current status look at the following [http://lists.debian.org/debian-custom/2006/02/msg00074.html message].
 * Develop a new, robust (i.e. not shell script based), security checking tool based on the experience derived from [http://packages.debian.org/checksecurity Checksecurity] and [http://packages.debian.org/tiger Tiger] implementing common host-level security checks, providing better alert mechanisms, and, optionally, integrating with OSS information management systems such as [http://www.prelude-ids.org/ Prelude] (through [http://packages.debian.org/libprelude2 libprelude] and [http://www.ossim.net/ Ossim] (JavierFernandezSanguino)
 * Layered Subversion, [http://laysvn.alioth.debian.org/], which can be very useful to maintain the configuration files of an inhomogenous set of servers, needs to be rewritten for efficiency increases (working on single files is very slow with subversion because of locking, so the rewrite needs to plan ahead and then work on whole layers). Maybe this could be intergrated into svk, too, or even some functionality into upstream subversion itself. (ErichSchubert)
 * Implement netboot in Debian Live (already implemented)
 * Implement a script frontend to Debian Live that creates Live netbooting media, ie. CF/USB Flash, Floppy, CD-ROM (for use in networks where no DHCP server can be used). Such media would contain a kernel, initrd and a hard-coded IP address inside the bootloader's config. file.
 * Implement a GUI frontend for Debian Live
 * TCOS: Thin Client Operating System [http://soleup.eup.uva.es/mediawiki/index.php/TCOS/en TCOS wiki] (need mentor)
 * Package and integrate of the German and Frensh user administration tool [:DebianEdu/CipUX:CipUX] for Debian-Edu into Debian (need mentor)
 * Write a replacement for the webmin based user administration frontent [:DebianEdu/CAT:CAT] for Debian-Edu (need mentor)
 * Implement the idea of non-master language documentation and translation system: [http://wiki.skolelinux.de/ChunkCMS ChunkCMS] (need mentor)

=== Security ===
 * Help integrate a coherent SELinux security policy into Etch, see ["SELinuxStatus"]
 * Create various variants of the reference policy for specific audiences (server, single user, desktop)
 * Create policy modules for specific packages, or contribute additions back to reference policy
 * SELinux: Automatically select policy modules for installed Debian packages (with dependency handling!), user UI for customizing this list (ErichSchubert)
 * Develop an [http://oval.mitre.org OVAL] agent for Debian. Define a mechanism to automaticaly generate OVAL queries from DSAs so that admins can set a central monitoring network (through an OVAL server and distribute OVAL agents) that can determine which systems need security updates. Optionally rate the urgency of the update using [http://www.first.org/cvss/ CVSS] (by CVE-linking with the [http://nvd.nist.gov/ National Vulnerability Database]) (JavierFernandezSanguino)
 * Develop a lintian-like system (i.e. both local tools and a lintian.debian.org service) to do automatic security review of packages source code and, through a metric, attempt to spot packages with possible security vulnerabilities that need to be reviewed before being released with the testing/stable release (JavierFernandezSanguino)
 * ''Integrate disk encryption in Debian-Installer. LUKS framework seems to be the way to go (several passwords, changing password allowed, ...)'' Already in d-i

=== Infrastructure ===
 * Develop a central translation coordination system (or enhance existing systems, such as [http://translate.sourceforge.net/ Pootle] or [http://sourceforge.net/projects/wordforge Wordforge] that would be used by translation teams to manage (coordinate), commit and review statistics for '''all''' the different l10n components in Debian, from program message translations to package description translations including the website, documentation, debconf notes, etc. For more information on the current state of affairs read [http://people.debian.org/~jfs/debconf6/html/ Internationalisation and localisation in Debian] (JavierFernandezSanguino)
 * Implement a highly reliable, BGP-based load-balancing DNS system for accessing Debian mirrors (cf [http://www.supersparrow.org/ Super Sparrow]). Requires ability to provide assurance that code is extremely robust (through careful testing and thorough testing), and ability to work with ISP and mirror admins (AnthonyTowns, JamesTroup, RyanMurray)
 * Expand the BitTorrent protocol/application to work effectively with large, constantly updating collections of files such as the Debian archive. Requires a good understanding of P2P protocol design, significant reimplementation of the BitTorrent code, and an ability to think through new protocols. (AnthonyTowns)
 * Create a DistributedAdminTool, as a webmin replacement, usable for whole networks and domains.

=== Porting ===
 * Port debian-installer to hurd-i386
 * Help out with the [http://debian-coldfire.alioth.debian.org/ Debian port to the Coldfire]. Good knowledge of either the kernel, glibc, or the toolchain would be required (WouterVerhelst).

=== Misc/unsorted ===

== Mentors for other projects ==

Check the mails in -private on how to register to be a mentor, to speed things up also email baruch at baruch@debian.org to notify me of your request so I can accept it.

 * AigarsMahinovs - I am a DD and was a participant in SOC 2005, I can mentor students willing to do Debian projects
 * aba (Andi Barth) - projects related to release management, QA, project management
 * Martin Michlmayr (tbm) - projects related to QA, release and project management; possibly also projects related to embedded systems.
 * DirkEddelbuettel - would be glad to mentor and help on R / CRAN related integration
 * StefanoZacchiroli - automated handling of OCaml dependencies (`dh_ocaml`)
 * DavidMorenoGarza - willing to work on the projects I'm offering to mentor even if they don't get into SOC; if so, please contact me.
 * SergioTalensOliag - will be happy to mentor anyone interested in working on the ["CDDT"].
 * JavierFernandezSanguino - willing to mentor security enhancement or security audit related projects.
 * AndreasSchuldei - would help with FriendsOfDebian and/or the DistributedAdminTool
 * A project was opened for the SoC on Alioth at http://alioth.debian.org/projects/soc/
 * Coordination is done on the mailing list [http://lists.alioth.debian.org/pipermail/soc-coordination/ soc-coordination]
Line 133: Line 29:
This still needs to be fleshed out and decided... Students are required to keep their development in the open, it is recommended that you use Alioth for your source control repository, you can use the [http://alioth.debian.org/projects/soc/ soc project] for your repository.
Line 135: Line 31:
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 student is also expected to maintain a webpage or a wiki page to keep everyone updates about his status. Most Debian development happens in the open already, so you will find a wealth of information on mailing lists and IRC, your mentor should be able to direct you to the proper resources.

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


Projects were selected and are starting as of 2006-05-23. On the Google website you can find the [http://code.google.com/soc/debian/about.html list of accepted projects].


  • May 1st - 8th: Student proposals accepted by Google
  • May 6th - 13th: DebCamp in Mexico

  • May 14th - 21st: DebConf in Mexico

  • May 21st: Deadline for Debian to accept proposals
  • May 23rd: Google publishes list of accepted proposals
  • June 30th: Mid-programme student evaluations due from mentors
  • August 21st: Student projects due
  • September 5th: Final mentor and student evaluations due

Contact info

Debian SoC coordinator: Baruch Even baruch@debian.org

Students who have any issue with their mentor or a mentor who has an issue with their student should contact the coordinator to help resolve it.

Infrastructure Provided to Students

Students are required to keep their development in the open, it is recommended that you use Alioth for your source control repository, you can use the [http://alioth.debian.org/projects/soc/ soc project] for your repository.

Most Debian development happens in the open already, so you will find a wealth of information on mailing lists and IRC, your mentor should be able to direct you to the proper resources.