potiuk edited a comment on issue #19848: URL: https://github.com/apache/airflow/issues/19848#issuecomment-980463952
First of all - this is my personal opinion, so don't take it as "granted". I hope other PMC members will chime in, but if they don't - please reach out to the Apache Software Foundation Trademark team (as suggested below) if you are unsure. I personally think that such customization options are totally out of scope of our project. Technically (and licence wise) you can modify the code in any way you want (as long as you keep attribution as specified in the licence) but adding a "customization" options where Trademarked Apache Project Logo and Trademarked log would be "customizable" might go against branding rules of the ASF. Since we are not lawyers and can't make decisions for you, it should be up to the users do such modifications and verification if they are "legal". The licence allows you to use the software in whatever way you want and modify it, so you are free to change it, but the names and logo of Apache projects are tradmarked and if you want to use them, you either use it as "Apache N" project or you follow "Powered by N" but you cannot connect your brand with Apache Airflow brand freely (if that's you are after). One thing is adjusting colors of navbar (for example) but totally different is to change/adapt logos and trademarked names - and especially to use them in conjunction with other brands. I think if you are customizing the name and logos you use for Apache Project, first of all you should should make sure that your customisation with brand and logos are following the Apache Software Foundation rules. Names and logos of the ASF projects are trademarked and here are Apache Trademark FAQs that you should verify - http://www.apache.org/foundation/marks/faq/. It's pretty much on your company and lawyers to judge and verify if what you do is fine with those or not. As a project we cannot make that decision for you, so giving a customisation option for that IMHO is not really something we should do (again we are not lawyers, and cannot make suggestions for you). By reading the guildeliens I believe (but I am not a lawyer, so don't take my word for it) it's ok if you remove branding reference to Apache Airflow brand and logo and replace it with your own (keeping the attribution) - but you are not supposed to associate your brand with "Apache Airflow", you might refer to the logo and branding via "Powered by" scheme: http://www.apache.org/foundation/marks/faq/#poweredby but I am not sure if that's what you are after. But regardless of what you can/can't do, I don't think we should make such decisions for our users and provide the customization options for name and logos. -- 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]
