On Tuesday 06 September 2005 13:02, Henne Vogelsang wrote:
No need for yet another bugtracking system. We already have a bugzilla up dont we? :)
Yes, but is Novell willing to use this for all the contributer's packages? We will see. For example Ubuntu's bugzilla is only for their supported main packages. Other packages (their universe and multiverse repositories) have a seperate bug-tracking system, they don't allow them in their main bugzilla.
You are showing the classical reflex when it comes to this topic ;) You immediately invent a "inner circle" of people that decide whats good and whats bad. I understand that, that is my first reflex too. But thinking about it, that approach has a lot of disadvantages.
Yes it's the standard way of many projects. If there's an other way were it is still possible to maintain a high quality, well then even better. :-)
Its a bottleneck for
* packages - A large sum of packages to handle by a small sum of people
Yes, this problem can be seen for example on Ubuntu's universe. They have 20 maintainers, and about 8000 packages or so. No wonder they are not able to get universe into good shape for Ubuntu's release. This is a very big bottleneck.
* people - For every inner circle there exists an outer circle. You would need to organize the "transfer" of people from the outer circle to the inner circle. That implys some other inner circle that decides these things.
But I suppose at least one such inner circle will exist at Novell who will have the last word on SUSE Linux.
* changes - If youre in the outer circle you have to rely on the inner circle to "implement" the change you want. Or you need to go trough the "people" bottleneck to get into the inner circle yourself.
You always end at some bottleneck if you want to contribute. Thats not very open i think.
But how is quality management handled if everyone can upload random stuff? Is a staging, unstable, untested, or whatever you'll call it repository enough? Cheers, Andreas