On Thursday 23 March 2006 13:57, Jakub Moc wrote:
> Ciaran McCreesh wrote:
> > On Thu, 23 Mar 2006 19:31:24 +0100 "Stefan Schweizer"
> >
> > <[EMAIL PROTECTED]> wrote:
> > | 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?
> >
> > Sounds like a perfect way to break lots and lots of systems. Those
> > policies are mostly there for good reason.
>
> You want to apply policies on overlays? Well no - sorry, overlays are
> none of QA's or any other policy business. They are overlays, not
> official tree.  If user installs ebuilds from overlay and breaks his
> system, then well - not a Gentoo problem. Why should any policies apply?

That is not what Stuart said, he indicated that overlays would be treated as 
supported systems including the use of our bugzilla system to track defects. 
If that is the case it crosses the line into the land of the "official" in 
which case policys start to be applied. While I agree that it would be very 
useful to have any overlays centrally located I do find the term "Official 
overlay" to be insanely oxymoronic in your use of the term overlay, which I 
gather to be "a set of ebuilds not bound by the QA and/or security 
requirements of the portage tree".

If I understand correctly what you are pushing then is a Official overlay 
respository for Unofficial overlays....

You can't have it both ways, either they are wholey Unofficial and do not get 
tracked in bugzilla at all (something which would have to be made VERY clear 
to our users, e.g. a you use it you get to keep the pieces policy, and the 
developer or team in question is the *only* point of contact for fixing 
things) -or- it is an Official overlay with official support which means it 
needs to abide by the rules...

-- 
Daniel Ostrow
Gentoo Foundation Board of Trustees
Gentoo/{PPC,PPC64,DevRel}
[EMAIL PROTECTED]

Attachment: pgpQyEPKB2Xy4.pgp
Description: PGP signature

Reply via email to