On Thu, 2006-03-23 at 19:31 +0100, Stefan Schweizer wrote: > On 3/23/06, Chris Gianelloni <[EMAIL PROTECTED]> wrote: > > Think about it this way, what if we had two competing products in the > > tree that do the same thing, with the same file names? We would add a > > blocker, no? So what mechanism is there to ensure that there's no > > "blocking" issues between an official in-tree project, and these > > external overlays that are not in the tree? With the tree, we have a > > well-defined policy on this. What policy would we use for the overlays? > > > What about if we just skip your "policies" and let the overlays be a > free place where people can handle issues how they think it is right > for the specific case and not how $super_dev said somewhere. That is > what overlays are about, not?
I'm fine with that, so long as we keep them *far* from *any* Gentoo infrastructure. Once it hits *.gentoo.org then it needs to follow some basic policy. Otherwise, it is allowing anyone to completely bypass any policies we have and allows anyone to cause any kind of breakages that they want, with exactly 0 repercussions. I'm sorry, but I am not OK with just standing by and watching us give complete access to do anything with no accountability. If you are, perhaps you really need to rethink your commitment to our users and your fellow developers. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
