-
Notifications
You must be signed in to change notification settings - Fork 13.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ™ to Airflow in prominent places #31977
Add ™ to Airflow in prominent places #31977
Conversation
We've started the process of registering the trademark of Airflow and we need to add ™ marks in prominent places of our website.
@@ -18,7 +18,7 @@ | |||
Core Concepts | |||
============================= | |||
|
|||
Here you can find detailed documentation about each one of Airflow's core concepts and how to use them, as well as a high-level :doc:`architectural overview <overview>`. | |||
Here you can find detailed documentation about each one of the core concepts of Apache Airflow™ and how to use them, as well as a high-level :doc:`architectural overview <overview>`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we registering the trademarks for Apache Airflow
or just Airflow
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just aiirflow. But you should read it as Apache (Airflow™)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally speaking it's a bit of dualism:
- ASF expects us to use
Apache Airflow
in prominent places where it is mentioned for the first time on page /paragraph or chapter. - The trademark people (us patent office) will expect to see installation page and there specifically should be "Airlfow™" without Apache.
The 1) is "Brand" , the 2) is "Trademark" and those two are slightly different and serve slightly different purpose.
We will never get it right or clearly defined IMHO - the Trademark/Brand does not really compile
in a consistent way I am afraid - my attempt is to make "best effort" to pass the Trademark registration and keep ASF branding guidelines fulfilled.
Not water + fire, but close.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay, understood, thank you!
Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
I'm wondering if we need to update/add something in the pre-commits to force using Airflow™
instead of Airflow
I don't think we need to use ™ everywhere, I actually asked the trademarks @ asf to finf out answers to some of the questions I have there. I am quite sure there willl be many places where "Airflow" is still good - and the answer "where to use ™" is not one that will be easy to put in automated script to decide, I am afraid. |
* Add ™ to Airflow in prominent places We've started the process of registering the trademark of Airflow and we need to add ™ marks in prominent places of our website. * Update docs/apache-airflow/index.rst Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com> --------- Co-authored-by: Pankaj Koti <pankajkoti699@gmail.com> (cherry picked from commit 10aa704)
We've started the process of registering the trademark of Airflow and we need to add ™ marks in prominent places of our website.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.