I think it would be great to get someone to take a lead and define what we should do here. From what I see (and slack discussion here https://apache-airflow.slack.com/archives/C06K9Q5G2UA/p1746587477484579), I think what we need now is to make a concrete proposal on
* which examples should stay * should we include the standard ones * should we enable other example dags as option (and how) I don't feel competent on defining those, - as I mostly work on the CI /DEV to support whatever is needed by those who need example dags for something - but if someone who actually uses example dags in different scenarios could comment and come with proposals how we can treat them, i am happy to support and even implement whatever - including the discovery of example DAGs from providers, J, On Thu, May 1, 2025 at 9:34 AM Jarek Potiuk <ja...@potiuk.com> wrote: > > Yes, probably too many example dags. Probably this is a consequence of > using them as test dags. > > Just comment on that - I think it's more a consequence of not having a way > to separate those. The idea of using test dags for examples and code > snippets is an extremely sound one because it has this nice property that > the examples are not going out-of-sync (which happens very quickly) - but > yeah, what we are really discussing here is how to show such dags > selectively by-default n the UI without changing the dual-purpose of them. > And likely have a way to be able to show more or less of them if you > are the "dev" tester. > > J. > > On Thu, May 1, 2025 at 6:55 AM Daniel Standish > <daniel.stand...@astronomer.io.invalid> 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. >> >
