Re: [gentoo-dev] Official overlay support

[Andres Loeh]

> > > 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.

Ok.

> 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.

I see your point. Then I'd suggest to have o.g.o host two classes of
overlays: (A) publically readable ones that fulfill basic policies and don't
break the main tree, and (B) others where read and write access can be
granted on request by the overlay owners, but isn't available automatically.

Every overlay would belong to class B at first -- in fact, o.g.o could go
online only supporting B. We can take our time and work out goog guidelines
for class A repos, and then gradually change some of the overlays to class
A status.

> 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.

Yes, as I said, I understand that.

Cheers,
  Andres