Differences between revisions 24 and 25
Revision 24 as of 2006-04-18 13:29:21
Size: 2664
Editor: AnthonyTowns
Comment:
Revision 25 as of 2006-04-18 15:46:09
Size: 2944
Comment:
Deletions are marked like this. Additions are marked like this.
Line 33: Line 33:
 * Improved '''debian/watch system''': ''to check upstream versions, possibly in a central db''
Line 36: Line 35:
 * Support for '''subversion in alioth'''
 * '''apt-listbugs''' enhancements/fixes: ''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.''
 * '''apt-listbugs''' enhancements/fixes: ''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).
 * 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)
 * Finish the CollaborativeMaintenance project (RaphaelHertzog)
Improved '''debian/watch system''': ''to check upstream versions, possibly in a central db''

This is a draft, and need a lot of work before it leave the draft state.

This wiki page is created to make it easier to plan and coordinate Debian's involvement in the Google Summer of Code 2006.

[http://google-code-updates.blogspot.com/2006/04/summer-of-code-2006.html Request for mentoring organizations] has gone out, and Debian need to move quickly to make it before the May 1st deadline. Mentoring organisations should read the [http://code.google.com/soc/mentorfaq.html mentor FAQ].

TODO

  • Announce our interest to Google and the rest of the world
  • Formulate projects
  • Organise mentors

Contact info

To be decided

Possible Projects (in () possible mentors)

(also see [http://www.us.debian.org/devel/todo/ the general TODO list])

  • ?DebTags: central database rewrite, review functionality, tag adoption and such

  • reportbug enhancements: graphical and/or webbased, so its easier for user to report

  • 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

  • Britney improvements (aba)

  • Adding IPv6 vserver support (aba)

  • Nicer support of pinning in apt [better docs, graphical interface (?), allow matching in Packages] (aba)

  • Unify apt, dpkg, etc (aba)

  • Improvements/unification in QA websites: packages.qa.d.o, qa.d.o/developer, dehs, etc

  • Real perl shlibs (aba)

  • Improve shlibs: to caclulate the used shlibs, rather than the theorically required ones (aba)

  • A user-friendly security-update notifier/installer

  • Improved system to handle WNPP: including expiry of ITPs, checking that orphaned packages have correct maintainer fields, etc. (DavidMorenoGarza, willing to work on this even if it gets into SoC or not)

  • 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]. (pere)

  • apt-listbugs enhancements/fixes: 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).

  • 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)

  • Finish the CollaborativeMaintenance project (RaphaelHertzog)

Improved debian/watch system: to check upstream versions, possibly in a central db

  • (?AigarsMahinovs - I am a DD and was a participant in SOC 2005, I can mentor students willing to do Debian projects)