On Thu, 2006-03-23 at 15:51 +0000, Stuart Herbert wrote: > On 3/23/06, Chris Gianelloni <[EMAIL PROTECTED]> wrote: > > I see no problem with providing these sorts of overlays to > > bridge the gap between contributing users and developers. I *do* see a > > problem with simply allowing random overlays from any developer for > > anything. > > That's a reasonable point, and it's an experience I've not personally > been on the receiving end of. > > But the flip side is reasonable too. Our governing metastructure is > explicitly clear that: > > a) Projects are not mandatory, and > b) That competing projects are allowed > > I don't see how we can limit overlays to just packages "owned" by the > developers who own the overlay without violating those two policies.
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? -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
