community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: What is the legal basis for enforcing release policies at ASF?
Date Fri, 21 Aug 2015 15:41:00 GMT

> On Aug 20, 2015, at 8:27 PM, William A Rowe Jr <wrowe@rowe-clan.net> wrote:
> 
> On Aug 20, 2015 08:52, "Jim Jagielski" <jim@jagunet.com> wrote:
>> 
>> Coming in late.
>> 
>> A snapshot is not a release. Licenses "kick in" at distribution/
>> release.
> 
> I want to fix FUD before it infests the rafters and subfloor.  I really
> have never read something so stupid or ill phrased...
> 
> Every contributor committing code to any ASF project, or even contributing
> it to us in public forums (including our mailing lists, our bug trackers,
> etc) is committing that code under the AL or has designated explicitly what
> licence it came in under (commit message: forked from BSD-licensed code
> base at {URL}.)
> 
> 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.
> 
>> There is also a trademark issue as well... only the ASF
>> can declare something as a release.
> 
> There we agree :)

Please reread what was said... We are talking *releases* here.
Making something publicly available is NOT A RELEASE. It may be
under a license, but is IS NOT A RELEASE.

For god's sake Bill, calm down.

Mime
View raw message