You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Justin Mclean <ju...@classsoftware.com> on 2018/01/08 02:00:35 UTC
Re: [royale-typedefs] branch develop updated: update year to 2018
Hi,
> NOTICE | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/NOTICE b/NOTICE
> index 40c36eb..e5fd060 100644
> --- a/NOTICE
> +++ b/NOTICE
> @@ -1,5 +1,5 @@
> Apache Royale Typedefs
> -Copyright 2012-2017 The Apache Software Foundation
> +Copyright 2018 The Apache Software Foundation
Any reason for this change especially that the Adobe copyright a few line below is still given as a year range and didn’t change? A casual glance at this notice someone may get the incorrect impression that Adobe owned copyright 2003-2012, Apache has copyright in 2018 and someone unknown owned it 2013-2017.
It a trivial thing (and a year range is not required) but the year a work was first created may in some cases be important as changes to copyright terms/length of copyright may depend on the the year a work was created. [1]
Thanks,
Justin
1. https://en.wikipedia.org/wiki/Copyright_Term_Extension_Act
Re: [royale-typedefs] branch develop updated: update year to 2018
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I'm pretty sure it is ok as-is.
Thanks,
-Alex
On 1/7/18, 6:44 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>Hi,
>
>> The first publication of a product called Royale will be in 2018
>
>Sure but the code existed at the ASF before that as part of the Flex
>project from 2012 to 2017. So perhaps just add the date range after
>mention of the Flex project?
>
>I’m sure you didn’t mean this way, but in it’s current form it reads like
>Adobe is a more important contributor than the ASF. I’m not sure the
>project would want to give that impression even unintentionally.
>
>Thanks,
>Justin
Re: [royale-typedefs] branch develop updated: update year to 2018
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> The first publication of a product called Royale will be in 2018
Sure but the code existed at the ASF before that as part of the Flex project from 2012 to 2017. So perhaps just add the date range after mention of the Flex project?
I’m sure you didn’t mean this way, but in it’s current form it reads like Adobe is a more important contributor than the ASF. I’m not sure the project would want to give that impression even unintentionally.
Thanks,
Justin
Re: [royale-typedefs] branch develop updated: update year to 2018
Posted by Alex Harui <ah...@adobe.com.INVALID>.
The first publication of a product called Royale will be in 2018
(hopefully soon).
Thanks,
-Alex
On 1/7/18, 6:00 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>Hi,
>
>> NOTICE | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/NOTICE b/NOTICE
>> index 40c36eb..e5fd060 100644
>> --- a/NOTICE
>> +++ b/NOTICE
>> @@ -1,5 +1,5 @@
>> Apache Royale Typedefs
>> -Copyright 2012-2017 The Apache Software Foundation
>> +Copyright 2018 The Apache Software Foundation
>
>Any reason for this change especially that the Adobe copyright a few line
>below is still given as a year range and didn’t change? A casual glance
>at this notice someone may get the incorrect impression that Adobe owned
>copyright 2003-2012, Apache has copyright in 2018 and someone unknown
>owned it 2013-2017.
>
>It a trivial thing (and a year range is not required) but the year a work
>was first created may in some cases be important as changes to copyright
>terms/length of copyright may depend on the the year a work was created.
>[1]
>
>Thanks,
>Justin
>
>1.
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikipe
>dia.org%2Fwiki%2FCopyright_Term_Extension_Act&data=02%7C01%7Caharui%40adob
>e.com%7Cca06efff6dce43c3ccf008d5563ba775%7Cfa7b1b5a7b34438794aed2c178decee
>1%7C0%7C0%7C636509736579045150&sdata=77Nnvda6j96tqBMF%2BAhUMoH3f8LKgpMK4Bn
>yDvG5L7s%3D&reserved=0