Adding Elestio as deployment option Elestio

[kaiwalyakoparkar]

Description

Hey team,
I am Kaiwalya, Developer Advocate at Elestio. Elestio has been providing options of fully deploying and managing Airflow application as shown here. I think it would be a great idea if we can add it to official readme/documentation here.
🔔 In addition to this, if you are interested we provide partnership opportunities with tools we support by revenue share upon addition of this method in docs. If you would like to collaborate, just shoot me an email at kaiwalya@elest.io :)

Use case/motivation

Example of one-click deploy button:

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[raphaelauv]

you could PR on the doc , https://airflow.apache.org/ecosystem/

[potiuk]

And 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 Elestio" - 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. 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 "Managed Workflows for Apache Airlfow" (MWAA) is a good name from Amazon because "for Apache Airflow" is a nominative use. "Airlfow by Elestio" 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.

[potiuk]

@kaiwalyakoparkar - I renamed the issue to "Elestio is violating ASF trademarks" and assigned you to it.

[kaiwalyakoparkar]

Hey @potiuk, I appreciate your comment. I have forwarded your suggestions to the appropriate teams internally and we will resolve it at the soonest and get back to you here. Thanks :)

[potiuk]

Let us know please, this is pretty important topic that the ASF treats with all seriousness.

[jbenguira]

• s statement does) is strictly forbidden and ASF trademark team is very strict about following and enforcing it. 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 "Managed Workflows for Apache Airlfow" (MWAA) is a good name from Amazon because "for Apache Airflow" is a nominative use. "Airlfow by Elestio" is definitely not.

Hey @potiuk, I've double checked and I'm not seeing ANY places where Elestio claims it's "The wording suggest that Airlfow is "by Elestio".

It's interesting how you built your argument by truncating "fully managed by elestio" to just "by elestio"
Your whole argument now seems to be done in BAD FAITH! And I also noticed you (Jarek Potiuk) trying to make some damage to our brand by renaming this incident to "Elestio is violating" without even discussing first with us or even consulting your legal team.

ON THE CONTRARY it's very clearly indicated everywhere: "Airflow, fully managed by Elestio" which seems ok based on the allowed example you provided "Managed Workflows for Apache Airlfow" and we are linking directly to the official repo on the same page.

Please forward this case to your legal team so we can ensure our implementation is OK and not infringing anything. Our goal is to comply. In the meantime please stay professional instead of going to conclusions, you are not a lawyer nor a judge. So don't say we are not compliant when you are not in a position to decide that.