Okay, then sorry for the noise... cancelling the VOTE and switching to a
LAZY CONSENSUS in a fresh email thread.
On 22.06.25 23:00, Jarek Potiuk wrote:
I think it would be better to call for LAZY CONSENSUS with `[LAZY
CONSENSUS]` title - calling a vote is indeed not needed, but having a vote
in a '[DISCUSS]` thread might be misleadin - one of the reason to have
`[PREFIX]' is to make them aware that there is a vote or consensus going
on, where they might have to take look - where '[DISCUSS]' is not really
binding for decision.
On Sun, Jun 22, 2025 at 10:50 PM Jens Scheffler <j_scheff...@gmx.de.invalid>
wrote:
Hi,
as the DICSUSS emails silcenced and also the number of ideas/comments
flattened I wanted to call for a VOTE for the example dag
cleanup/refurbish.
Together with Arita, Shubham, Desai and Jarek we have consolidated
idea/plans/tasks in
https://cwiki.apache.org/confluence/display/AIRFLOW/Examples+Refurbish
to be the base of implementation.
I believe an "formal/official" vote is not needed, could also be just a
set of PRs being merged but as it is a larger storyline change I'd cast
the vote to align plans. Comments on the docs and small extensions are
still welcome otherwise target would be to implement the consolidation
and storyline as documented.
The vote will run for ~5 days and last till next Friday, June 27th 23:59
CEST.
Everyone is encouraged to vote, although only PMC members and
Committer's votes are considered binding.
consider my +1 (binding)
Jens
On 11.05.25 16:24, Jens Scheffler wrote:
Hi,
following-up on the discussion we had and the verbal discussion in
Airflow 3 Dev call May 22nd (see notes in
https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3+Dev+call%3A+Meeting+Notes#Airflow3Devcall:MeetingNotes-22May2025)
I propose the following next steps:
1) start a separate interactive discussion in Slack in channel
#sig-examples (https://apache-airflow.slack.com/archives/C08RUFEL466)
- Note: If you have the feeling we need to discuss in Devlist, please
also feel free to replay to the thread here. Butmaybe we need to have
a bit more interaction w/o generating too much noise in the devlist)
2) Within the discussion document some targets and tasks as a concept.
I started a skeleton in
https://cwiki.apache.org/confluence/display/AIRFLOW/Examples+Refurbish
- Feel free to extend, comment!
3) Once our discussion in #sig-examples/Slack/Devlist is sttled I
propose a follow-up [VOTE] in the devlist validating agreement
Everybody who likes to join and engage, please feel free to join
#sig-examples in Slack or let me know!
Jens
On 01.05.25 06:54, Daniel Standish wrote:
Yeah, along Jens lines...
Yes, probably too many example dags. Probably this is a consequence of
using them as test dags.
Probably ideally we are more selective in curating example dags and
distinguishing them from test dags.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org
For additional commands, e-mail: dev-h...@airflow.apache.org
