Re: [DISCUSS] - Grouping of concerns

2022-07-13 Thread Vikram Koka
Thank you all for your responses. Dennis, With respect to your concern on the "hard data - numbers" to support the assertion of the audience. I agree that we don't have the hard numbers at this time to support this assertion and I also understand your concern that there is additional burden to an

Re: [DISCUSS] - Grouping of concerns

2022-07-13 Thread Ping Zhang
Hi Vikram, Great thoughts on this. I agree with this: > I am concerned that we are overwhelming our audience segment (1) with the > work and configurations around running Airflow at scale. I would like to see a better separation on 1) how to set up an airflow cluster in production, how to moni

Re: [DISCUSS] - Grouping of concerns

2022-07-04 Thread Ferruzzi, Dennis
une 30, 2022 8:49 PM To: dev@airflow.apache.org Subject: [EXTERNAL] [DISCUSS] - Grouping of concerns 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. Hi everyone, As I have

Re: [DISCUSS] - Grouping of concerns

2022-07-01 Thread Jarek Potiuk
I very much agree that those different groups need different treatment - both documentation and support-wise as well as a bit different messaging, tooling and level of "hand-holding". I do not want to deep dive into technicalities of those differences, this is something we can figure out when/if we

[DISCUSS] - Grouping of concerns

2022-06-30 Thread Vikram Koka
Hi everyone, As I have been looking through the recent AIPs, development features, and mailing list discussions, it struck me that we have effectively three different audiences here for Airflow. 1. Individuals and small teams using Airflow for their purpose, 2. Enterprises managing Airflow for la