debexpo / mentors.debian.net

Mentor: [mailto:haas@debian.org Christoph Haas]

Summary: [http://mentors.debian.net mentors.debian.net] is currently a very specialized web-based repository that allows everybody to contribute software packages to Debian without the need to be a Debian Developer (or Debian Maintainer). It has successfully helped simplifying the sponsoring process in the last years. However it needs to be refactored and in the process should be turned into a generic piece of software that can be used for other Debian source/binary package repositories, too.

Required skills:

Optional skills:

Description: [http://mentors.debian.net mentors.debian.net] has been around for years. It was started as a hacky Perl/CGI web interface. Two years later it was rewritten completely in Python/CGI making the source code more readable. But our tiny development team lacked serious Python experience so that the result was still far from perfect. After some brainstorming on the Debian mailing lists and on IRC we collected some interesting ideas (see also: DebianMentorsNet) on what the "next" mentors.debian.net could look like.

The idea is not only to "just" refactor the mentors.debian.net web site with the underlying maintenance scripts but to create something more generic. Our working title is "debexpo" (Debian package exposition) and I have created a Trac (wiki + bug tracker) at http://debexpo.workaround.org/trac/ to begin with. debexpo should work similar to Ubuntu's [http://revu.tauware.de/ REVU] tool or the [http://code.google.com/p/debppa/ Personal Package Archives (PPA)]. The debexpo software should be generic enough to provide the basis for mentors.debian.net as well as allow private repositories for anyone. The basic concepts are:

Currently I'm alone on the project. I think I have a good idea of what the resulting debexpo software should look like. "Pylons" (which is similar to Django or Turbogears) is a flexible web framework for such projects and I'm rather active in the Pylons project myself and have created real-life applications with it already. I'm usually very responsive and reachable via Jabber for mentoring. I'm open-minded regarding the general direction of the project. But I will probably insist that it will be done with Pylons because I have to maintain the software in the long run.