+1 Option B (binding) (I'd really prefer D but it seems that has no chance to pass, and anything but DAG 😁)
On Tue, Oct 21, 2025 at 11:05 AM Pavankumar Gopidesu < [email protected]> wrote: > Option c +1 > > Pavan > > On Tue, 21 Oct 2025 at 15:47, Collin McNulty <[email protected]> > wrote: > > > Option D +1 > > Option B +0.5 > > > > (Non-binding) > > > > > On Oct 20, 2025, at 2:02 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] > > > > >
