On Wed, 5 Mar 2008, Anant Narayanan <[EMAIL PROTECTED]> wrote: > > If it's not too late for this month's meeting, I'd like to discuss > the possibility of including a new "post" in our developer base - > the package maintainer. >
The idea is interesting. We have been thinking about something similar in the sci team. We are already maintaining some packages we don't know how to test. We also don't particularly like the idea of getting scientific results based on untested software. The overlays are not a solution. Packages in the overlays do not go through keywording or stabilisation processes, do not get all the publicity, and don't have bug support as advanced as the ones in the main tree. In all the sci* herds, we have more than 180 requests for new packages only in bugzilla. Our active team is small and overloaded with already more than 430 packages to maintain. Many other teams are facing the same issue. We have contacted some talented ebuild submitters who neither want to spend the time nor feel the responsibility of a full dev. A formal proxy-maintainer could really help in our sometimes blind maintaining duties. -- Sébastien
signature.asc
Description: PGP signature
