On Thursday 24 November 2005 12:31, Diego 'Flameeyes' Pettenò wrote: > What I'm waiting for now are comments if someone has ideas where to put > guides that does not belong directly to an existant project. And if someone > wants to join the effort of documenting maintenance process for his > packages, it would be helpful, too. Trying not to let this idea die, as I still think it might be good in the long run, especially if there's a way to get them collected in a single place. Right now the main problem is that they are spread across projects (at least video/sound projects).
Possible solutions I thought of: 1) have every herd controlled by a project, so that the maintainers' guides can be committed there; it would be difficult to find the maintainer's guide for a package this way; 2) have a single repository for maintainers' guides that does not belong to other projects; 3) have a single repository for *every* maintainers' guide. The problem with 1 and 2 is that the maintainers' guides would be difficult to locate in the mess of projects. The problem of 3 is that we have already complex maintainers' guides such as xine's and the one spyderous wrote for X11 herd, that might be difficult to fit in a single organization.. To solve 1's and 2's problem, the solution could be adding a <maintainerguide> tag to metadata.xml, that carries the URL to the maintainer's guide for the package. It would also make simpler, for example, the case where a single guide is used for more than one package (see always xine's). -- Diego "Flameeyes" Pettenò - http://dev.gentoo.org/~flameeyes/ Gentoo/ALT lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE
pgp9xae7VUadb.pgp
Description: PGP signature
