Hi Jacques,
On Thu, Nov 16, 2017 at 6:54 AM, <[hidden email]> wrote: > Author: jleroux > Date: Thu Nov 16 05:54:23 2017 > New Revision: 1815412 > > URL: http://svn.apache.org/viewvc?rev=1815412&view=rev > Log: > No functional change. > > With this fix, about the Quicksand Google font licensed under the > SIL OPEN FONT LICENSE Version 1.1, we are now clear from all licensing > issues > Though we are still waiting for INFRA-15466 to check the RAT Buildbot > result... > > BTW I referred to https://nifi.apache.org/licensing-guide.html about how > to > handle this case. Only a change in NOTICE was needed, not in LICENSE. Nice > TLP > document, that I'll check again later... > > Modified: > ofbiz/ofbiz-framework/trunk/NOTICE > ofbiz/ofbiz-framework/trunk/themes/rainbowstone/README.md > ofbiz/tools/rat-excludes.txt > > Modified: ofbiz/ofbiz-framework/trunk/NOTICE > URL: http://svn.apache.org/viewvc/ofbiz/ofbiz-framework/trunk/ > NOTICE?rev=1815412&r1=1815411&r2=1815412&view=diff > ============================================================ > ================== > --- ofbiz/ofbiz-framework/trunk/NOTICE (original) > +++ ofbiz/ofbiz-framework/trunk/NOTICE Thu Nov 16 05:54:23 2017 > @@ -3,3 +3,8 @@ Copyright 2001-2017 The Apache Software > > This product includes software developed by > The Apache Software Foundation (http://www.apache.org/). > +========================================================================= > + > +This product bundles the "Quicksand Google font", which is available > +under the "SIL OFL License 1.1" license. > +For details, see themes/rainbowstone/webapp/rainbowstone/fonts/quicksand > I believe that the above should be in the LICENSE file, not in the NOTICE file, according to [1]. Unless there are specific reasons for which you added it to the NOTICE file, I will move it there. Regards, Jacopo [1] https://www.apache.org/legal/src-headers.html |
Administrator
|
Hi Jacopo,
Le 04/04/2018 à 12:12, Jacopo Cappellato a écrit : > Hi Jacques, > > > On Thu, Nov 16, 2017 at 6:54 AM, <[hidden email]> wrote: > >> Author: jleroux >> Date: Thu Nov 16 05:54:23 2017 >> New Revision: 1815412 >> >> URL: http://svn.apache.org/viewvc?rev=1815412&view=rev >> Log: >> No functional change. >> >> With this fix, about the Quicksand Google font licensed under the >> SIL OPEN FONT LICENSE Version 1.1, we are now clear from all licensing >> issues >> Though we are still waiting for INFRA-15466 to check the RAT Buildbot >> result... >> >> BTW I referred to https://nifi.apache.org/licensing-guide.html about how >> to >> handle this case. Only a change in NOTICE was needed, not in LICENSE. Nice >> TLP >> document, that I'll check again later... >> >> Modified: >> ofbiz/ofbiz-framework/trunk/NOTICE >> ofbiz/ofbiz-framework/trunk/themes/rainbowstone/README.md >> ofbiz/tools/rat-excludes.txt >> >> Modified: ofbiz/ofbiz-framework/trunk/NOTICE >> URL: http://svn.apache.org/viewvc/ofbiz/ofbiz-framework/trunk/ >> NOTICE?rev=1815412&r1=1815411&r2=1815412&view=diff >> ============================================================ >> ================== >> --- ofbiz/ofbiz-framework/trunk/NOTICE (original) >> +++ ofbiz/ofbiz-framework/trunk/NOTICE Thu Nov 16 05:54:23 2017 >> @@ -3,3 +3,8 @@ Copyright 2001-2017 The Apache Software >> >> This product includes software developed by >> The Apache Software Foundation (http://www.apache.org/). >> +========================================================================= >> + >> +This product bundles the "Quicksand Google font", which is available >> +under the "SIL OFL License 1.1" license. >> +For details, see themes/rainbowstone/webapp/rainbowstone/fonts/quicksand >> > I believe that the above should be in the LICENSE file, not in the NOTICE > file, according to [1]. > Unless there are specific reasons for which you added it to the NOTICE > file, I will move it there. > > Regards, > > Jacopo > > [1] https://www.apache.org/legal/src-headers.html Looking at it again, I don't remember what decided me to refer to Nifi licensing guide. I said "I'll check again later..." and I just did. I think you are right. It's a kind of Category-A licenses. Hence should not need a NOTICE but a LICENSE change. Ah wait, I think what decided me to put it in NOTICE is because it's a free license but not a MIT/BSD type. I read at http://www.apache.org/dev/licensing-howto.html#mod-notice: Copyright notifications which have been relocated <http://www.apache.org/legal/src-headers.html#headers> from source files (rather than removed) must be preserved in |NOTICE|. However, elements such as the copyright notifications embedded within BSD and MIT licenses need <https://issues.apache.org/jira/browse/LEGAL-59> not <https://issues.apache.org/jira/browse/LEGAL-62> be duplicated in |NOTICE| -- it suffices to leave those notices in their original locations. Then I did not refer-to/read the relocated link and I understand now that relocated means that the licensed product has been donated to the ASF. I tough think that it would be good to ask legal. Not because I doubt but it will help future possible users to find this license in the Category-A licenses list at http://www.apache.org/legal/resolved.html. What do you think? Jacques |
To summarize:
1) we will move the text from NOTICE to LICENSE, because it is currently misplaced 2) you will ask legal if the "SIL OPEN FONT" LICENSE Version 1.1 can be considered a category-A license Jacopo On Thu, Apr 5, 2018 at 8:24 AM, Jacques Le Roux < [hidden email]> wrote: > Hi Jacopo, > > > Le 04/04/2018 à 12:12, Jacopo Cappellato a écrit : > >> Hi Jacques, >> >> >> On Thu, Nov 16, 2017 at 6:54 AM, <[hidden email]> wrote: >> >> Author: jleroux >>> Date: Thu Nov 16 05:54:23 2017 >>> New Revision: 1815412 >>> >>> URL: http://svn.apache.org/viewvc?rev=1815412&view=rev >>> Log: >>> No functional change. >>> >>> With this fix, about the Quicksand Google font licensed under the >>> SIL OPEN FONT LICENSE Version 1.1, we are now clear from all licensing >>> issues >>> Though we are still waiting for INFRA-15466 to check the RAT Buildbot >>> result... >>> >>> BTW I referred to https://nifi.apache.org/licensing-guide.html about how >>> to >>> handle this case. Only a change in NOTICE was needed, not in LICENSE. >>> Nice >>> TLP >>> document, that I'll check again later... >>> >>> Modified: >>> ofbiz/ofbiz-framework/trunk/NOTICE >>> ofbiz/ofbiz-framework/trunk/themes/rainbowstone/README.md >>> ofbiz/tools/rat-excludes.txt >>> >>> Modified: ofbiz/ofbiz-framework/trunk/NOTICE >>> URL: http://svn.apache.org/viewvc/ofbiz/ofbiz-framework/trunk/ >>> NOTICE?rev=1815412&r1=1815411&r2=1815412&view=diff >>> ============================================================ >>> ================== >>> --- ofbiz/ofbiz-framework/trunk/NOTICE (original) >>> +++ ofbiz/ofbiz-framework/trunk/NOTICE Thu Nov 16 05:54:23 2017 >>> @@ -3,3 +3,8 @@ Copyright 2001-2017 The Apache Software >>> >>> This product includes software developed by >>> The Apache Software Foundation (http://www.apache.org/). >>> +=========================================================== >>> ============== >>> + >>> +This product bundles the "Quicksand Google font", which is available >>> +under the "SIL OFL License 1.1" license. >>> +For details, see themes/rainbowstone/webapp/rai >>> nbowstone/fonts/quicksand >>> >>> I believe that the above should be in the LICENSE file, not in the NOTICE >> file, according to [1]. >> Unless there are specific reasons for which you added it to the NOTICE >> file, I will move it there. >> >> Regards, >> >> Jacopo >> >> [1] https://www.apache.org/legal/src-headers.html >> > > Looking at it again, I don't remember what decided me to refer to Nifi > licensing guide. I said "I'll check again later..." and I just did. > > I think you are right. It's a kind of Category-A licenses. Hence should > not need a NOTICE but a LICENSE change. > > Ah wait, I think what decided me to put it in NOTICE is because it's a > free license but not a MIT/BSD type. I read at > http://www.apache.org/dev/licensing-howto.html#mod-notice: > > Copyright notifications which have been relocated < > http://www.apache.org/legal/src-headers.html#headers> from source files > (rather than removed) must be preserved in |NOTICE|. > However, elements such as the copyright notifications embedded within > BSD and MIT licenses need <https://issues.apache.org/jira/browse/LEGAL-59> > not <https://issues.apache.org/jira/browse/LEGAL-62> be duplicated in > |NOTICE| -- it suffices to leave those notices in their original locations. > > Then I did not refer-to/read the relocated link and I understand now that > relocated means that the licensed product has been donated to the ASF. > > I tough think that it would be good to ask legal. Not because I doubt but > it will help future possible users to find this license in the Category-A > licenses list at http://www.apache.org/legal/resolved.html. > > What do you think? > > Jacques > > |
Administrator
|
Yes, will you do the move?
Jacques Le 05/04/2018 à 08:52, Jacopo Cappellato a écrit : > To summarize: > > 1) we will move the text from NOTICE to LICENSE, because it is currently > misplaced > 2) you will ask legal if the "SIL OPEN FONT" LICENSE Version 1.1 can be > considered a category-A license > > Jacopo > > On Thu, Apr 5, 2018 at 8:24 AM, Jacques Le Roux < > [hidden email]> wrote: > >> Hi Jacopo, >> >> >> Le 04/04/2018 à 12:12, Jacopo Cappellato a écrit : >> >>> Hi Jacques, >>> >>> >>> On Thu, Nov 16, 2017 at 6:54 AM, <[hidden email]> wrote: >>> >>> Author: jleroux >>>> Date: Thu Nov 16 05:54:23 2017 >>>> New Revision: 1815412 >>>> >>>> URL: http://svn.apache.org/viewvc?rev=1815412&view=rev >>>> Log: >>>> No functional change. >>>> >>>> With this fix, about the Quicksand Google font licensed under the >>>> SIL OPEN FONT LICENSE Version 1.1, we are now clear from all licensing >>>> issues >>>> Though we are still waiting for INFRA-15466 to check the RAT Buildbot >>>> result... >>>> >>>> BTW I referred to https://nifi.apache.org/licensing-guide.html about how >>>> to >>>> handle this case. Only a change in NOTICE was needed, not in LICENSE. >>>> Nice >>>> TLP >>>> document, that I'll check again later... >>>> >>>> Modified: >>>> ofbiz/ofbiz-framework/trunk/NOTICE >>>> ofbiz/ofbiz-framework/trunk/themes/rainbowstone/README.md >>>> ofbiz/tools/rat-excludes.txt >>>> >>>> Modified: ofbiz/ofbiz-framework/trunk/NOTICE >>>> URL: http://svn.apache.org/viewvc/ofbiz/ofbiz-framework/trunk/ >>>> NOTICE?rev=1815412&r1=1815411&r2=1815412&view=diff >>>> ============================================================ >>>> ================== >>>> --- ofbiz/ofbiz-framework/trunk/NOTICE (original) >>>> +++ ofbiz/ofbiz-framework/trunk/NOTICE Thu Nov 16 05:54:23 2017 >>>> @@ -3,3 +3,8 @@ Copyright 2001-2017 The Apache Software >>>> >>>> This product includes software developed by >>>> The Apache Software Foundation (http://www.apache.org/). >>>> +=========================================================== >>>> ============== >>>> + >>>> +This product bundles the "Quicksand Google font", which is available >>>> +under the "SIL OFL License 1.1" license. >>>> +For details, see themes/rainbowstone/webapp/rai >>>> nbowstone/fonts/quicksand >>>> >>>> I believe that the above should be in the LICENSE file, not in the NOTICE >>> file, according to [1]. >>> Unless there are specific reasons for which you added it to the NOTICE >>> file, I will move it there. >>> >>> Regards, >>> >>> Jacopo >>> >>> [1] https://www.apache.org/legal/src-headers.html >>> >> Looking at it again, I don't remember what decided me to refer to Nifi >> licensing guide. I said "I'll check again later..." and I just did. >> >> I think you are right. It's a kind of Category-A licenses. Hence should >> not need a NOTICE but a LICENSE change. >> >> Ah wait, I think what decided me to put it in NOTICE is because it's a >> free license but not a MIT/BSD type. I read at >> http://www.apache.org/dev/licensing-howto.html#mod-notice: >> >> Copyright notifications which have been relocated < >> http://www.apache.org/legal/src-headers.html#headers> from source files >> (rather than removed) must be preserved in |NOTICE|. >> However, elements such as the copyright notifications embedded within >> BSD and MIT licenses need <https://issues.apache.org/jira/browse/LEGAL-59> >> not <https://issues.apache.org/jira/browse/LEGAL-62> be duplicated in >> |NOTICE| -- it suffices to leave those notices in their original locations. >> >> Then I did not refer-to/read the relocated link and I understand now that >> relocated means that the licensed product has been donated to the ASF. >> >> I tough think that it would be good to ask legal. Not because I doubt but >> it will help future possible users to find this license in the Category-A >> licenses list at http://www.apache.org/legal/resolved.html. >> >> What do you think? >> >> Jacques >> >> |
On Thu, Apr 5, 2018 at 9:42 AM, Jacques Le Roux <
[hidden email]> wrote: > Yes, will you do the move? Yes, I will take care of it Jacopo |
Administrator
|
https://issues.apache.org/jira/browse/LEGAL-380
Jacques Le 05/04/2018 à 10:16, Jacopo Cappellato a écrit : > On Thu, Apr 5, 2018 at 9:42 AM, Jacques Le Roux < > [hidden email]> wrote: > >> Yes, will you do the move? > > Yes, I will take care of it > > Jacopo > |
Administrator
|
It's actually a category b (how did we miss it? :-o).
I have closed LEGAL-380 as duplicate of LEGAL-112 Following advice at http://www.apache.org/legal/resolved.html#category-b <<By attaching an appropriate and prominent label to the distribution, and requiring an explicit action by the user to get the reciprocally-licensed source, users are less likely to be unaware of restrictions significantly different from those of the Apache License. Please include the URL to the product's homepage in the prominent label. An appropriate and prominent label is a label the user will read while learning about the distribution - for example in a README. Please also ensure to comply with any attribution/notice requirements in the specific license in question.>> Since we don't use any source file, only the font binaries, it seems to me that simply adding something like for the "Crypto notice" in the readme.adoc file should be enough Opinions? Jacques Le 05/04/2018 à 20:51, Jacques Le Roux a écrit : > https://issues.apache.org/jira/browse/LEGAL-380 > > Jacques > > > Le 05/04/2018 à 10:16, Jacopo Cappellato a écrit : >> On Thu, Apr 5, 2018 at 9:42 AM, Jacques Le Roux < >> [hidden email]> wrote: >> >>> Yes, will you do the move? >> >> Yes, I will take care of it >> >> Jacopo >> > > |
Administrator
|
Another option could be to replace this font by another one from Category A, like Google "Noto Sans" or what not
But I don't know why Julien picked this font. There might be reasons to use it... Jacques Le 06/04/2018 à 08:03, Jacques Le Roux a écrit : > It's actually a category b (how did we miss it? :-o). > > I have closed LEGAL-380 as duplicate of LEGAL-112 > > Following advice at http://www.apache.org/legal/resolved.html#category-b > > <<By attaching an appropriate and prominent label to the distribution, and requiring an explicit action by the user to get the reciprocally-licensed > source, users are less likely to be unaware of restrictions significantly different from those of the Apache License. Please include the URL to the > product's homepage in the prominent label. An appropriate and prominent label is a label the user will read while learning about the distribution - > for example in a README. Please also ensure to comply with any attribution/notice requirements in the specific license in question.>> > > Since we don't use any source file, only the font binaries, it seems to me that simply adding something like for the "Crypto notice" in the > readme.adoc file should be enough > > Opinions? > > Jacques > > > Le 05/04/2018 à 20:51, Jacques Le Roux a écrit : >> https://issues.apache.org/jira/browse/LEGAL-380 >> >> Jacques >> >> >> Le 05/04/2018 à 10:16, Jacopo Cappellato a écrit : >>> On Thu, Apr 5, 2018 at 9:42 AM, Jacques Le Roux < >>> [hidden email]> wrote: >>> >>>> Yes, will you do the move? >>> >>> Yes, I will take care of it >>> >>> Jacopo >>> >> >> > > |
On Fri, Apr 6, 2018 at 8:18 AM, Jacques Le Roux <
[hidden email]> wrote: > Another option could be to replace this font by another one from Category > A, like Google "Noto Sans" or what not > This is my preference: I prefer to avoid to make our product license trickier just to include a font family. Jacopo |
Yup, agreed, plenty of compatible fonts out there
On Fri, Apr 6, 2018, 11:02 AM Jacopo Cappellato < [hidden email]> wrote: > On Fri, Apr 6, 2018 at 8:18 AM, Jacques Le Roux < > [hidden email]> wrote: > > > Another option could be to replace this font by another one from Category > > A, like Google "Noto Sans" or what not > > > > This is my preference: I prefer to avoid to make our product license > trickier just to include a font family. > > Jacopo > |
Free forum by Nabble | Edit this page |