On Wed, 2006-03-22 at 22:03 +0000, Stuart Herbert wrote: > To answer Daniel's other question, about bugs.g.o ... trac on > overlays.g.o will have its bug tracking system disabled. We already > have one bug tracking system - bugs.g.o - and that's sufficient.
Umm... no? If some random developer goes out there and creates his own fork of catalyst in his overlay, I sure don't want to receive a *single* bug on it. Ever. If you're already using Trac, you should keep the bug tracking enabled, so the bugs stay with the overlay. Once something moves into the official tree, then it can use bugs.gentoo.org for its bug tracking. This means developers that don't wish to participate in the overlays are not forced to waste their time troubleshooting problems in these overlays and can focus on our *core* product, the portage tree. I have no problem with someone, for example, making their own fork of catalyst for testing new stuff and then, after extensive testing, submitting it "upstream" to the official repository, but forcing me to waste my time trying to figure out that some random developer out there has made a fork that does something different from the official version when a user has a bug is completely counter-productive. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
