On Fri, 2006-03-24 at 12:46 +0100, Andres Loeh wrote: > > If the overlay's changelog is included on o.g.o's front-page, and the > > wiki / GuideXML site is publically readable, but we just disallow > > anonymous access to the overlay itself (only if requested, this > > wouldn't be the default setup) ... how would that work for you? > > It would work, of course, and it would help prevent certain complaints, > but it's not absolutely necessary. If "on request" is chosen, it's also > important that read access can be given by us without any delay, i.e., > without going through any formal process.
See, I have no problem with this. The operation of the overlay *should* lie completely with the overlay owners. You *should* be able to add *anyone* that you feel is worth adding to read *or* write access, with no further process. As I've said, my only request is a single policy that before an overlay can become publicly readable on overlays.gentoo.org (which is Gentoo infrastructure) that it does not break packages in the main tree that are not in the overlay. If this single policy were in place, then I would fully support overlays.gentoo.org being created. My main point is I don't want one of my tree packages to break because some ricer told some n00b to use some crazy ebuild from some random overlay that isn't really fit for the general masses. If we take at least *some* measures to prevent this, then I'm OK with it. Allowing a free-for-all in the overlays is not acceptable. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
