Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Justin Mclean
Hi, > 3. Have an authorized agent of Adobe modify the trademark whitelist >prior to publication. > > That seems OK to me since you are an Adobe employee and you are assuring us > that you have discussed the matter with Adobe legal and obtained permission to > perform that specific mitigation

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Justin Mclean
HI, > I would be surprised if this gives me permission to add other Apache > trademarks to my blog title. You can add any Apache trademark as long as you correctly attribute it, there’s no need to ask for permission. However if it was an Adobe trademark with that extra clause you would need to

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Alex Harui
On 4/26/15, 9:57 PM, "Justin Mclean" wrote: >HI, > >> Are you saying once we let someone use Apache Foo, they can also use >> Apache Bar without asking again? > >As long at as it's correctly attributed and follows Apache trademark >guidelines/policy [1] there’s no need to ask for permission to

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Justin Mclean
HI, > Are you saying once we let someone use Apache Foo, they can also use > Apache Bar without asking again? As long at as it's correctly attributed and follows Apache trademark guidelines/policy [1] there’s no need to ask for permission to use an Apache trademark. You’ll note it states "Anyon

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Marvin Humphrey
On Sun, Apr 26, 2015 at 9:17 PM, Alex Harui wrote: > "If I missed listing a trademark, I’ll add it in > the first commit after this donation lands in the repo, but where the > trademark names are just used in an example to show people how to put a > list of things in a UI widget, I’ll just replac

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Alex Harui
On 4/26/15, 9:27 PM, "Justin Mclean" wrote: >HI, > >> Isn’t this always the case? > >No, it's only the addition of that extra sentence that causes the issue. The Apache preferred attribution is ""Apache, Apache Foo, and Foo are trademarks of The Apache Software Foundation. Used with permission

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Justin Mclean
Hi, > The list of Adobe products in the text at the bottom was created by me > from a template given to me by Adobe lawyers. Apparently, I missed > listing a few products. Are you 100% sure you have permission to modify that list of trademarks, given the wording of the second sentence? Can you

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Justin Mclean
HI, > Isn’t this always the case? No, it's only the addition of that extra sentence that causes the issue. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: gene

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Justin Mclean
Hi, > It seems as those Adobe has denied us the use of "ColdFusion", "Dreamweaver", > and "Illustrator" by not including them in the whitelist, and then using the > "no other license" language. Yep that exactly my concern. > Possible mitigations would be: > > 1. Remove "ColdFusion", "Dreamweav

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Alex Harui
On 4/26/15, 9:10 PM, "Marvin Humphrey" wrote: >On Sun, Apr 26, 2015 at 8:44 PM, Alex Harui wrote: >> Please explain in this thread or in the JIRA issue why this a concern. >> How is this bad for Apache? > >So, if I look on the page `flx_olapdatagrid_ol.html`, I see the following >text >in the

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Alex Harui
On 4/26/15, 9:00 PM, "Justin Mclean" wrote: >Hi, > >Alex I have no idea what you discussed with Adobe legal so it would be >better if you raised it. > >The issue is the "No other license to the Adobe trademarks are granted.” >which probbably means we can only use the trademarks initially listed

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Marvin Humphrey
On Sun, Apr 26, 2015 at 8:44 PM, Alex Harui wrote: > Please explain in this thread or in the JIRA issue why this a concern. > How is this bad for Apache? So, if I look on the page `flx_olapdatagrid_ol.html`, I see the following text in the middle... The product field can have the values: Col

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Justin Mclean
Hi, Alex I have no idea what you discussed with Adobe legal so it would be better if you raised it. The issue is the "No other license to the Adobe trademarks are granted.” which probbably means we can only use the trademarks initially listed by Adobe and I don’t think we can change that list

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Alex Harui
Justin, I’m sorry, but I still don’t understand your concern. I think you’ll have to create the JIRA issue and describe it. Here’s the template again: "Adobe and are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries and are use

Re: [RESULT][IP Clearance] Flex Documentation for Apache Flex

2015-04-26 Thread Justin Mclean
Hi, > Where can I see that non standard attribution? Alex you mind doing the honours given you had the discussion with Adobe legal. I assume it would need to be a LEGAL Jira. JFYI On the weekend I asked an associate at a law firm specialising in IP / trademark law and their (unpaid) informal v

[RESULT] [IP Clearance] Apache Usergrid Code Donation

2015-04-26 Thread John D. Ament
Vote passes with no -1's after 72+ hrs, and +1's from Chris Mattmann, Lewis John Mcgibbney and Dave Johnson. Thanks everyone! John On Tue, Apr 21, 2015 at 10:47 PM John D. Ament wrote: > All, > > Upon entering the incubator, the Apache Usergrid podling filed a CCLA for > contributors. Within