Hi Briana, Thank you for putting this together. It's looking pretty good for the first draft.
I have added quite a few comments and left some suggestions for changes. A few important things to call out here: 1. We should work backwards from what our goals are with this survey and how we want this to inform us, removing any questions that don't help us in forming any opinion. For instance, the question "How many people at your company directly work on data?" probably won’t inform us about anything. Instead, asking "YOE with Airflow" would help us understand new user preferences versus pro user preferences. 2. In the demographics section, it would be beneficial to ascertain whether the respondent only uses Airflow or contributes to it as well. This way, we can completely hide the section about contribution and vice versa. 3. Some of the options are quite descriptive. Let’s aim to reduce the time to finish the survey as much as possible. 4. Can you please indicate which questions should have single-choice answers and which should have multiple-choice answers? Last year, there were some questions that should have been multiple choice, but were formatted as single choice, resulting in mixed responses. Thanks Shubham On 2023-10-25, 12:35 PM, "Jarek Potiuk" <ja...@potiuk.com <mailto:ja...@potiuk.com>> wrote: 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. AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que le contenu ne présente aucun risque. 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 <mailto: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.inva > <mailto:briana.oky...@astronomer.io.inva>lid> 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 > > <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/> > > <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 <mailto:briana.oky...@astronomer.io> > > <john....@astronomer.io <mailto:john....@astronomer.io>>Mobile: +1 > > 415.713.9943 > > Time zone: US Pacific UTC > > > > <https://www.astronomer.io/> <https://www.astronomer.io/>> > > >
