Dear Airflow community,
I am Fortytwoo, a native Chinese (zh-CN) speaker, and I would like to
contribute to the Airflow project by adding Simplified Chinese translations to
the Airflow UI. This is my first major open-source contribution, and I am eager
to learn and follow the community's guidel
I don't think we concluded whether we should use "Dag" or "dag" - but I
think the important goal of why we decided on dropping the "DAG" as acronym
was that we want to really start "owning" the "Dag" term - "Dag" really
meaning "Airflow Workflow".
I think using capitalized form "Dag" fulfills that
Hi all,
As many of you know, airflowctl is on the way for its 1.0.0 release step by
step and has already been stated as a dependency in AIP-94. Building on
that, I have drafted a new Airflow Improvement Proposal: Decouple Remote
Commands from airflow CLI (to airflowctl).
Today, many airflow CLI c
Response thread there. Can’t remember the full outcome from the top of my
head but “Dag, dag, dags” seems fine, preferably for doc, new code, user
facing, but not worth the trouble going through the whole codebase for
refactoring.
https://lists.apache.org/thread/8k338stlkkp07ko3no70p2nng757kd1w
I think our previous consensus was “dag" or “dags", but recent PRs, including
mine, have changed them to "Dag". I’m fine with "Dag" or “dag” (like “dag” a
bit more) as long as it’s not “DAG”.
I believe we should better document the decision this time. I can create that
PR once we finalize it ag
Saw this PR https://github.com/apache/airflow/pull/55097
I thought we discussed this at some point that using just "dag" or "dags"
is perfectly fine. De-emphasizing the mathy origin of the "DAG" concept.
Personally I believe we should leave instances of "dag" or "dags" in the
docs alone.
Is the
