-
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
Use inclusive words in Apache Airflow project #15994
Comments
CC @leahecole |
Love it. A couple of clarifying questions
|
That's one reason. The other one is that #12982 is still opened. Also I some words cannot be removed because are used by 3rd party tools
Both, when we remove the word we should add it to existing rule or create new one similar to this: airflow/.pre-commit-config.yaml Lines 333 to 341 in 476d0f6
|
I would love to take this up @turbaszek |
@Patil2099 I assigned you to this ticket 👏 |
I am not an expert with regular expression. Can you help me with the regular expression? @turbaszek |
Sure, what we would like to check? What words? |
Sorry for the late reply, I have to edit the regex in pre-commit to solve this issue right? @turbaszek. I have to exclude all the words right? mentioned in #15994 (comment). I need a little help in that. |
Thanks for taking on this! Is there any chance that |
@Patil2099 yes, we should add similar hook to pre-commit-config as this one: airflow/.pre-commit-config.yaml Lines 333 to 341 in 476d0f6
The regexp should be like (?i)(\bmaster\b|\bhe\b|\bshe\b|\bhis\b|\bher\b) so we match exact word not substrings like HElp .Also we will need to adjust all occurrences of non-inclusive words.
@ktmud that's interesting suggestion. This would be a breaking change but I think it's worth trying. Any suggestions for a new name? CC @leahecole @kaxil @potiuk |
Yeah. We should likely change DummyOperator but we should deprecate it not remove (and remove it in 3.0). The 'NoOpOperator' or similar could be a good name. |
How about EmptyOperator or TasklessOperator (not sure if this may cause confusion as with Tasks)? |
I like |
Hmmm.. If more people think that
|
Yeah. Dummy is not only non-inclusive but also well a bit dummy :). I like EmptyOperator |
In my AIP-39 implementation I called a time table that never schedules ( |
+1 for |
+1 works for me
…On Tue, Jun 8, 2021 at 10:36 AM Tomek Urbaszek ***@***.***> wrote:
+1 for NullOperator
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15994 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAERMIZ76PYYKTBX4XIU3P3TRXJCPANCNFSM45JVCF6A>
.
--
+48 660 796 129
|
NullOperator works for me - I have also seen "Placeholder" as a substitution for dummy in our docs if you prefer that |
As for dummy other than airflow/airflow/utils/trigger_rule.py Line 33 in 5cd0bf7
|
+1 for NullOperator |
What, not "Noperator"? 😉 +1 for NullOperator. |
Opened PR #17144 to handle the Dummy trigger rule deprecation. A question was raised in the PR review if we want NULL trigger rule or something else. |
PR for renaming The only task left on this issue is the task that this issue was created for :) |
@eladkal I would love to take this issue |
I don't think the hook scans the file it's defined in because then you won't be able to place the words you want to scan for...? We have language-matters hook that checks for white/black (though I don't know why we exclude the files listed in it): airflow/.pre-commit-config.yaml Lines 407 to 423 in 1007828
|
This regex
The correct could be this: (?ix) i = Use case-insensitive matching. For more information, (edited) I will try! |
**@eladkal I am not sure why we are excluding these files. Some of them exist and some don't. Some are from "provider/docs", so I am assuming that they are being excluded because we are using third-party documentation that we cannot change after validation.
|
It is working, should I work to change these words in CHANGELOG: master, dummy..etc?
|
We can't reword that one - it's a notice to the users that the class has changed name. The others were correct at the time the were written (master branch) so it doesn't make sense to change them, but we could do of we want |
@ashb agree with this, then I'm going to add this file CHANGELOG to exclusions. |
@edithturn thanks for taking this on! +1 to Ash's suggestion to exclude the CHANGELOG. Rewriting history may cause more confusion than it does good - as much as I'm always in favor of upgrading language, it might make it harder to tell in the changelog when this change actually occurred. |
Hello! I have a doubt regarding this: I am excluding these files:
And the pre-commit is showing an error in these other files: PR: #23090 I'm not sure how to deal with them, should I exclude them or fix them to change the terms? |
We should fix what we can |
I had no idea "sanity check" is a problem. TIL |
Related: apache#15994 apache#23090 This PR addresses a few items related to inclusive language use and the CI check: - There are several occurrences of "dummy" throughout documentation; however the current CI check for preventing non-inclusive language doesn't inspect `docs/` files. Ideally, the docs also include inclusive language. - Even when removing `docs/` from the exclusion list, non-inclusive language was still escaping pygrep. Upon inspection, the `(?x)` inline modifier was missing from the regex (although intended in apache#23090). Adding this modifier revealed these "dummy" instances and others related non-inclusive occurrences which were previously uncaught. - The exclusion list seemed too broad in places. There are still instances in which directories are excluded as a whole, but the list now is more tailored to non-inclusive occurrences that are beyond the purview of Airflow, history, dev/test files, etc.
* Fix and augment `check-for-inclusive-language` CI check Related: #15994 #23090 This PR addresses a few items related to inclusive language use and the CI check: - There are several occurrences of "dummy" throughout documentation; however the current CI check for preventing non-inclusive language doesn't inspect `docs/` files. Ideally, the docs also include inclusive language. - Even when removing `docs/` from the exclusion list, non-inclusive language was still escaping pygrep. Upon inspection, the `(?x)` inline modifier was missing from the regex (although intended in #23090). Adding this modifier revealed these "dummy" instances and others related non-inclusive occurrences which were previously uncaught. - The exclusion list seemed too broad in places. There are still instances in which directories are excluded as a whole, but the list now is more tailored to non-inclusive occurrences that are beyond the purview of Airflow, history, dev/test files, etc. * Update links in get_pandas_df() of BigQueryHook * dummy-command -> placeholder-command in _KubernetesDecoratedOperator
Description
Apache Software Foundation is discussing how we can improve inclusiveness of projects and raise awareness of conscious language. Related thread on diversity@a.o:
https://lists.apache.org/thread.html/r2d8845d9c37ac581046997d980464e8a7b6bffa6400efb0e41013171%40%3Cdiversity.apache.org%3E
Use case / motivation
We already have pre-commit check that checks for some word. However, on CLC (Conscious Language Checker) Apache Airflow seems to have problems with the following words:
Are you willing to submit a PR?
Related Issues
#12982 #9175
The text was updated successfully, but these errors were encountered: