On Fri, Jul 28, 2006 at 01:06:05PM -0600, Katrina Jackson wrote: > Okay here is another honest question: Do you really honestly think not > having co-maintainers for base packages is ever a good idea? What if > someone is busy? You don't really feel safe noticing your base packages > aren't being co-maintained since people are busy. Having co-maintainers is a tradeoff: on the one hand, it increases the number of people who in theory ought to be responsible for looking at a given package. On the other hand, it also makes it much easier for each individual to assume that someone else will deal with things that need to be handled. What works best depends on the situation - the package and the people involved. > Also back to the innovation issue: Don't your think having more > comaitainers there would be more innovation merging a package into Debian. > Is your goal just to make a package compile and not have RC bugs, or is it > to take a package and innovate in a way to make that package experience must > better for a Debian User? With co-maintainers this would be easier to pull > off. Sometimes that can help, sometimes it's not really relevant - for example, with things that need work over a wide range of packages maintainership isn't a big deal. -- "You grabbed my hand and we fell into it, like a daydream - or a fever."
Description: Digital signature