Thanks for sharing, Briana. I got a chance to go through the doc and added my comments directly in the document as suggestions.
Summary: * I think we should also have questions around the operators being used by the community * We should ask questions regarding the security aspect too as Jarek pointed out * I feel that we do not have questions around scale and frequency (more so) that DAGs are run, we can add those * We should also discuss "other" options people use, if not airflow and why? Thanks Andrey and Jarek, I agree with both of your points. Thanks & Regards, Amogh Desai On Thu, Oct 26, 2023 at 6:29 AM Peter DeJoy <pdejo...@gmail.com> wrote: > Thanks so much for putting this together, Briana. A few thoughts from my > end: > > • This isn’t particularly actionable, but right now, the survey feels > quite long. I wonder if we can consolidate some of the questions that are > asking for similar pieces of information in an effort to get more folks to > complete it. > • Similarly, I feel the pick lists are quite long. Can we flatten the > bands down for some of the questions? For example, on the question on how > many production deployments a user is running, we could have 1, 2-5, 5-20, > 20-100, 100+ be options. > • I’m not sure about the question “how many people at your company > directly work on data?” I think we’re going to get poor signal there, as > there’s an argument to be made that every stakeholder at our respective > companies work on data! > • I’d like to see backfills added to the pick list for improvements in > Airflow in the “future” section > • Come to think of it, is there overlap in the “what could be > improved” vs “what would you like to see net new” questions? For example, I > see dataset improvement as an option in the net new question but would > think I’d find that in the improvement section. > > I’m sure I’ll have some other thoughts as I dig through- will keep > updating this thread as things come up! > > Thanks again, > Pete > On Oct 25, 2023, 3:32 PM -0400, Jarek Potiuk <ja...@potiuk.com>, wrote: > > Agree with Andrey's suggestions - added a few of mine directly to the > docs > > as comments/suggestions. Summary of my comments: > > > > * mentioning 2.5 providers compatibility and reasoning why people staying > > below 2.5 > > * I thing suggesting list of services/tools Airflow might interact with > to > > choose, will introduce bias and will make it difficult to get "real" > > impression on what is used. I suggest leaving it "freeform". > > * asking questions about importance/ways how they are managing security > of > > their deployment (and whether they follow advisories) > > * I think we should also ask question about "other" orchestration tools > and > > what made people choose airflow/consider others > > > > > > On Wed, Oct 25, 2023 at 6:58 PM Andrey Anshin <andrey.ans...@taragol.is> > > wrote: > > > > > Hey Briana, > > > > > > Thanks for sharing questions. Let me share some idea/improvements, but > it > > > only my thoughts so it could be non-relevant for create clear survey > > > > > > *Which version of Airflow do you currently use* > > > Maybe it's better keep only this one? > > > - 1.10 > > > - <=2.4 > > > - 2.5 > > > - 2.6 > > > - 2.7 > > > > > > 1.10 it is so legacy now > > > 2-2.4 not so legacy, but latest providers can't be install on this > versions > > > 2.5.x it is the highest version which might install latest providers > > > > > > *Which Metadata Database do you use?* > > > > > > My suggestion is to make this question, if it possible, only for > > > self-hosted Airflow installation. I guess for Managed Airflow it would > > > always be Postgres. > > > > > > An split this question by two different > > > > > > First about type of DB > > > > > > - MySQL (not MariaDB) > > > - Postgres > > > - Microsoft SQL Server > > > - Other: ______ > > > > > > Second one about version DB version > > > > > > - Version: ______ > > > - I don't know > > > > > > Every year new version of Postgres released, so if we consider that > some > > > users might still use 1.10.x then it could be a chance 9.4 - 9.5 used > > > I think more interesting in this question is Postgres have critical > total > > > share value (like 80-90 of all respondent) from which we might start > think, > > > is actually we need in the future (Airflow 3.x/4.x) something different > > > rather than Postgres and SQLite (for testing) > > > > > > > > > > > > ---- > > > Best Wishes > > > *Andrey Anshin* > > > > > > > > > > > > On Wed, 25 Oct 2023 at 19:08, Briana Okyere > > > <briana.oky...@astronomer.io.invalid> wrote: > > > > > > > Hey All, > > > > > > > > For the last few years, we've sent out surveys to get a sense of the > > > state > > > > of this Airflow community, and this year I've been tasked with > > > distributing > > > > it. I'd love to get your feedback before it's pushed live. > > > > > > > > I've made some minor tweaks to the 2022 survey and added the > questions to > > > > this google doc: < > > > > > > > > > > > > https://docs.google.com/document/d/1FbluXNGq9cI3N9zw1cH4F4cEQfyIQ6tk7tGLo4ZN4AE/edit?usp=sharing > > > > > > > > > > > > > Is there anything you think should be added or removed? > > > > > > > > Please note- it is useful to compare data from previous years to this > > > year, > > > > so I believe the majority of the questions should remain similar-ish. > > > > However, there is always room for improvement! > > > > > > > > Here are last year's results for reference: > > > > <https://airflow.apache.org/blog/airflow-survey-2022/> > > > > > > > > Also, if anyone is interested in helping with analysis after the > results > > > > are in, please let me know. > > > > > > > > -- > > > > Briana Okyere > > > > Community Manager > > > > Email: briana.oky...@astronomer.io > > > > <john....@astronomer.io>Mobile: +1 415.713.9943 > > > > Time zone: US Pacific UTC > > > > > > > > <https://www.astronomer.io/> > > > > > > > >
