+1 Option B (binding). To me if we're stepping away from the meaning the acronym used to have and coining a new Airflow name for our workflows, then we should capitalize it like any other proper noun.
Cheers, Niko ________________________________ From: Vincent Beck <[email protected]> Sent: Monday, October 20, 2025 12:19:53 PM To: [email protected] Subject: RE: [EXT] [VOTE] Finalizing “DAG” terminology for docs and blog ("dag" vs "DAG" vs "Dag") CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que le contenu ne présente aucun risque. +1 Option B (binding) On 2025/10/20 19:07:05 Jarek Potiuk wrote: > +1 Option B (binding) > > On Mon, Oct 20, 2025 at 9:03 PM Constance Martineau via dev < > [email protected]> wrote: > > > Hi everyone, > > > > As discussed in this email thread > > <https://lists.apache.org/thread/h4b0vjfr4dkbyhrkoxpfjo67s38yr0hh>, I am > > formally calling a vote to finalize how we refer to Airflow workflows in > > writing. The vote will run for roughly 72 hours, and last until Thursday > > October 23rd at 7:00 pm UTC (countdown link > > <https://countingdownto.com/?c=6656693>) > > > > The options are: > > > > - Option A: Prefer dag in docs; use DAG only when referring to the > > class/import > > - Option B: Prefer Dag in docs; use DAG only for the class/import > > - Option C: Keep DAG as the standard everywhere (status quo) > > - Option D: Prefer Dag in docs, use Dag for class/import and alias DAG > > (for backcompat reasons) > > > > You can vote any fractional between -1 and +1 for any of the options, and > > the option with the highest sum (even if it's a negative) wins. This is a > > procedural vote, meaning that -1 is not considered a veto. Everyone is > > encouraged to vote, but only PMC members and Committer's votes are > > considered binding. > > > > Please see email thread > > <https://lists.apache.org/thread/h4b0vjfr4dkbyhrkoxpfjo67s38yr0hh> for > > additional context. > > > > Why this matters: We’ve had inconsistent terminology across docs and > > repeated PR debates over capitalization. Standardizing will make our > > writing clearer, strengthen the Airflow brand, and give external > > stakeholders a single reference to follow. > > > > Best, > > Constance > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
