royale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com.INVALID>
Subject Re: [DISCUSS] Discuss Release Apache Royale 0.9.0 RC1
Date Wed, 17 Jan 2018 17:39:53 GMT


On 1/16/18, 9:16 PM, "Justin Mclean" <justin@classsoftware.com> wrote:

>Hi,
>
>> Royale is not going to operate like Flex.  We want to be more responsive
>> to our users.  So instead of conducting detailed searches for IP issues
>>at
>> release time, they should be done at commit time or at other times.
>
>The issue has been brought up before so is a known issue. (See that
>discussion thread). Given that discussion I would of assumed that
>committers wouldn't check in plain text CC-BY-SA licensed content. But I
>guess people forget about it, I had even forgotten about that thread. If
>you where watching the commits it would be very easy to miss the file(s)
>in question as they also incorrectly had an ASF headers on them. But any
>PMC member or committer could of noticed this, the fact that no one did
>until now probably indicates how difficult it was to find. Perhaps it
>would be better to deal with licensing issues when they are raised or
>soon after - especially when a 3rd party doesn’t respond in a timely way?
>
>BTW the legal JIRA about CC-SA content is here [1] not sure if you
>managed to find that when looking at the issue.

Are you now claiming this content is under CC-BY-SA instead of just CC-BY?
 I did not see that.  Where did you get that? Share-Alike (SA) has more
restrictions than just CC-BY, AIUI.

-Alex

>

Mime
View raw message