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.
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.
Not to cause a fight, I just wanted to point out some say all Debian is
worried about is RC bugs. "Debian worships RC bugs". With
co-maintainers you could do a better job "worshiping RC Bugs" While
doing additional work to innovate how that package will work in
Debian. Plus more QA support when more then one work on the
package.
- Re: package ownership in Debian (was: Why does Ubuntu have... Katrina Jackson
- Re: package ownership in Debian (was: Why does Ubuntu... Gustavo Franco
- Re: package ownership in Debian (was: Why does Ubuntu... Mark Brown
- Re: package ownership in Debian (was: Why does Ubuntu... George Danchev