potiuk commented on issue #42998:
URL: https://github.com/apache/airflow/issues/42998#issuecomment-2412667368

   Andd just to comment  - any kind of revenue sharing/etc. opportunities are 
not possible. This is a vendor-neutral PMC of the Apache Software Foundation 
and since ASF is a registerd 501 c3 charity in Delaware 
(https://apache.org/foundation/) that has the motto of "Releasing Software for 
Public Good", the Airflow PMC cannot endorse or promote any vendors on the 
software the ASF releases. This is why Ecosystem page has a clear disclaimer 
that those are unverified, public links that are neither endorsed nor 
affiliated with Airflow PMC.
   
   And one - even more important thing - as a PMC member of the Apache Airlfow, 
my responsibility is to notice and follow up on branding issues when Airlfow 
registered trademark is used by 3rd parties.
   
   Your website is violating branding rules and you MUST fix it, otherwise we 
will involve Apache Software Foundation trademarks team to follow up with you - 
you should fix it promptly.
   
   Airflow (R) is a registered trademark of the Apache Software Foundation and 
if you want to refer or use the trademark you need to follow the ASF Branding 
policy. The policy is here https://apache.org/foundation/marks/ and you and 
your lawyers should read it in detail and you should follow all the detailed 
guidelines if you want to use "Airflow" trademark.
   
   Example things that are wrong here https://elest.io/open-source/airflow 
   
   * The wording suggest that Airlfow is "by Elastio" this is huge misuse, 
Airlfow is an Apache project and suggesting that other entity owns it "which 
this statement does" is strictly forbidden and ASF trademark team is very 
strict about following and enforcing it (And the fact that Airflow is a 
registered trademark in US makes it very, very enforceable). You should refer 
to "Apache Airflow" in the first prominent place as "Apache Airlfow (R)" and 
name of your offering should be a "nominative use" - for example Manager 
Workflows for Apache Airlfow" (MWAA) is a good name from Amazon because "for 
Apache Airflow" is a nominative use. "Airlfow by Elastio" is definitely not.
   
   * There are a number of other branding rules (again link here 
https://apache.org/foundation/marks/) - and you (and your lawyers) have to read 
it in detail and you have to apply all the rules explained there to your 
website.
   
   Also you have other ASF projects in your managed application list (I did not 
check all but for example I saw Superset) - and you have exactly the same 
issues - so you should implement the changes for all ASF projects you manage. 
   
   Please do it promptly and let us know when done, to avoid unnecessary 
escalation and lawyer involvement. I will let the trademark team in the ASF 
know that we noticed the issue and get you some time to react but I want you to 
know that the ASF treats such violation of their trademarks very, very 
seriously, so my advice is to quickly comply with those requirements.
   
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to