As already explained earlier, some packages are still looking for a maintainer. The maintainers situation has improved a lot, thanks to some fresh blood in the GNOME team, but some packages still don't have a primary maintainer, someone who will do more than just answering bug reports and uploading new versions, reworking the package if necessary and improving its integration with the rest of GNOME. * dasher: is there someone around using it? * gnome-media: Gustavo Franco wanted to give a hand, but he's still not listed as maintainer. Gustavo, are you still interested? It also looks like Marco Cabizza could be interested in this package. * eel2 and nautilus: this is the big one. These two packages should preferably handled by the same maintainer, and someone with time. * libbonobo(ui): these libraries have few bugs, don't require much work, and are being deprecated. They can stay as is if no one steps up. * gtkhtml3.8: this one looks maintained by the evolution maintainers, especially Heikki Henriksen. Would you like to become the primary maintainer? * control-center: looking at the SVN, Marco Cabizza looks interested in it. How about making it official? The following packages, regardless of a maintainer, need a *lot* of help regarding bug triaging: nautilus, control-center, gnome-panel, gnome-applets, evince, epiphany-browser (bugs need to be checked with the latest xulrunner and reassigned if necessary), gnome-cups-manager, gnome-system-tools, gnome-terminal, gtk+2.0, meta-gnome2 (mostly reports against gnome that need to be reassigned), rhythmbox, totem. List readers, if you care about the shape of GNOME in Debian, please help with these bugs. Some of you are already contributing and when we see the bug reports being dealt with, it is much appreciated. If several people spend a few hours a week dealing with these bugs, the GNOME BTS could be in a reasonable state in about two months! -- .''`. Josselin Mouette /\./\ : :' : josselin.mouette@ens-lyon.org `. `' joss@debian.org `- Debian GNU/Linux -- The power of freedom
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=