On Fri, Aug 24, 2012 at 4:00 PM, Rob Weir <robw...@apache.org> wrote: >... > Or if someone who cared sufficiently about this policy area took > ownership and proposed a wording of the policy, either as a Board > resolution, or on legal-discuss, and had that policy approved and > recorded via the ordinary means.
That's why people keep saying: go to legal-discuss. Stop worrying about it here. And to be clear: we're talked about authenticated/blessed binaries. Not convenience artifacts. I think you're well aware of this, yet you keep conflating the two. I don't know why, except maybe to aggravate people. It certainly isn't engendering good will. > Right now is is unfair to say that I, or anyone else in the podling, > is "rebellious" or opposes ASF Policy in this area, since no one seems > to be able to say what the policy actually is, in specific and > actionable terms, and why they think AOO podling is or is not in > compliance. It is totally fair when everybody keeps telling you: no blessed binaries, and you refuse to listen. > I can give the IPMC a hand here, if my point is too obscure. A policy > might look like this: > > Resolved: An Apache project's release consists of a canonical source > artifact, voted on and approved by the PMC. A PMC can also distribute > additional, non-source artifacts, including documentation, binaries, > samples, etc., that are provided for the convenience of the user. > These non-source artifacts must must be buildable from the canonical > source artifact. Additional 3rd party libraries may be included > solely in compliance with license policies defined by Apache Legal > Affairs. Additionally the non-source artifacts (or the PMC) must > ____________ and must not _________________. That's existing policy. As people keep saying (most recently, Joe, in no uncertain terms). -g --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
