community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From William A Rowe Jr <wr...@rowe-clan.net>
Subject Re: What is the legal basis for enforcing release policies at ASF?
Date Fri, 21 Aug 2015 01:19:13 GMT
On Aug 20, 2015 7:39 PM, "Alex Harui" <aharui@adobe.com> wrote:
>
>
>
> On 8/20/15, 5:27 PM, "William A Rowe Jr" <wrowe@rowe-clan.net> wrote:
>
> >It is generally AL code all the time.  I don't know where you invented a
> >'kick-in' concept, but unless the committers are violating their
> >ICLA/CCLA,
> >nothing could be further from the truth.
>
> Committers sometimes make mistakes.  IIRC, Justin recently caught a
> mistake where some files accidentally got their non-AL headers replaced
> with AL headers.
>
> Large codebase contributions, especially initial podling code grants might
> be messy as well until scrubbed and approved for an official ASF release.
> I know from experience.

We don't disagree on this point.  Sometimes, they are caught through the
release process, or by peer review.  Other times, we must retract the claim
we offered.

Nothing changes the fact that code is either offered under the AL 2.0 or
another license, unless the author/licensor changes their license
retroactively.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message