Hi Tomek, Same issue as XD. I could get to the Google doc, but not to the form.
On Thu, Jan 14, 2021 at 11:42 AM Deng Xiaodong <[email protected]> wrote: > Hi Tomek, > > I get the message "*Hi! This form is no longer open. If there's anything > you would like to share please use our slack or devlist*" when I try to > open the link you shared below. > > Just check if it's intentionally closed or if anything is wrong? > > Thanks. > > > XD > > On Thu, Jan 14, 2021 at 4:16 PM Daniel Imberman <[email protected]> > wrote: > >> @tomek I just added a few questions/fixed grammar. PTAL :). >> via Newton Mail >> <https://cloudmagic.com/k/d/mailapp?ct=dx&cv=10.0.51&pv=10.15.7&source=email_footer_2> >> >> On Thu, Jan 14, 2021 at 4:44 AM, Kaxil Naik <[email protected]> wrote: >> >> Looks good to me, thanks Tomek. >> >> On Thu, Jan 14, 2021 at 12:11 PM Tomasz Urbaszek <[email protected]> >> wrote: >> >>> Hi folks, >>> >>> I move the questions from doc to the google form: >>> https://forms.gle/EZz8s5pGYDpHL2Ex8 >>> >>> Please let me know if there's something you would like to fix or add. >>> >>> I'm planning to send the survey out on Monday. >>> >>> Cheers, >>> Tomek >>> >>> On Fri, Nov 20, 2020 at 10:47 AM Tomasz Urbaszek <[email protected]> >>> wrote: >>> >>>> Hello all, >>>> >>>> If you would like to add something more to the survey please feel free >>>> to do so! I'm planning to cut a draft of google form next week. >>>> >>>> Cheers, >>>> Tomek >>>> >>>> On Sun, Nov 15, 2020 at 12:42 AM Tomasz Urbaszek <[email protected]> >>>> wrote: >>>> >>>>> Thanks Jarek for the suggestions! I added them to this document: >>>>> >>>>> https://docs.google.com/document/d/1IbDp2-EsZPFVx1anaj86_LW2AoVDKVxCwMlYgEKAoVM/edit?usp=sharing >>>>> >>>>> Everyone - feel free to add your questions and suggest changes in this >>>>> doc. >>>>> >>>>> I would love to publish this survey before we release Airflow 2.0. In >>>>> this way we may learn more about how many people are aware about it and >>>>> its >>>>> features. >>>>> >>>>> Cheers, >>>>> Tomek >>>>> >>>>> On Wed, Nov 11, 2020 at 8:08 PM Jarek Potiuk <[email protected]> >>>>> wrote: >>>>> >>>>>> I think this is a very, very good time to do this. I am all for it. >>>>>> >>>>>> For sure there are those questions I would like to add: >>>>>> >>>>>> Airflow deployment: >>>>>> >>>>>> * which version of Airflow you use in production >>>>>> * which version of Airflow you use in staging/dev >>>>>> * what is the database you are using as the metadata DB of Airflow >>>>>> * which is the Metadata DB version you use >>>>>> * what executor do you use >>>>>> * which is the queue you are using in case you use Celery Executor >>>>>> [rabbitmq/redis/other] >>>>>> * are you using [ on-premise/ cloud (which) / as a service (which)] >>>>>> deployment >>>>>> * what's the deployment strategy you use ([Kubernetes/Bare Metal/ >>>>>> Virtual Machines/Docker Compose/ other] >>>>>> * what is the DAG distribution you use [Git Sync, NFS, EFS/GCS >>>>>> Fuse/Don't know/Other/ ....] >>>>>> >>>>>> Airflow migration: >>>>>> >>>>>> * do you consider migrating to Airflow 2.0 as soon as it is out? If >>>>>> not why >>>>>> * what is your foreseen timeline of migration for Airflow 2.0 after >>>>>> it is is out >>>>>> * what is the biggest obstacle you see for the migration to Airflow >>>>>> 2.0 >>>>>> * which are the features of Airflow 2.0 you are most excited about : >>>>>> [LIST OF FEATURES HERE - multiple choice] >>>>>> * tell us why are you excited about those >>>>>> * are there any features you wanted that did not make it to Airflow >>>>>> 2.0? Tell us why you need them. >>>>>> * what is the size of your company (5-6 buckets here) >>>>>> * how many people in your company use airflow (3-4 buckets here) >>>>>> >>>>>> Community / Contribution: >>>>>> >>>>>> * are you and your team actively participating in Airflow development >>>>>> - contributions >>>>>> * if yes what do you like/don't like about the process >>>>>> * if no - why not? >>>>>> * do you have your own Airflow customizations to Airflow that you >>>>>> would like to contribute? What are those and what stops you from doing >>>>>> so? >>>>>> >>>>>> Airflow Summit/Documentation: >>>>>> >>>>>> * have you attended the Airflow Summit 2020? >>>>>> * what kind of talks you would like to see at the Airflow Summit >>>>>> 2021? [ some areas I can add + some free choice] >>>>>> * what is your source of information about Airflow multiple choice >>>>>> [Airflow Website/Read the docs/Airflow's Github docs/Github >>>>>> Issues/Airflow's slack/Airflow Summit Videos/Awesome Apache Airflow/Stack >>>>>> Overflow/Google/ Other: free form]* >>>>>> >>>>>> Competition: >>>>>> >>>>>> * did you consider/try other workflow engines? Which ones? >>>>>> * did you/do you consider moving to those other workflow engines? If >>>>>> so, what's missing in Airflow that you can get from those other engines? >>>>>> >>>>>> J. >>>>>> >>>>>> >>>>>> On Thu, Nov 5, 2020 at 4:37 PM Tomasz Urbaszek <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hey all, >>>>>>> >>>>>>> Sorry for the enigmatic title but wanted to avoid explicit subject - >>>>>>> *Airflow >>>>>>> Community Survey 2020* (just to avoid confusion in future). >>>>>>> >>>>>>> So, we are close to the end of the year and time of last year's >>>>>>> community survey. Here is summary and questions we used: >>>>>>> https://airflow.apache.org/blog/airflow-survey/ >>>>>>> >>>>>>> Probably many of the questions will stay (profession, executors, >>>>>>> number of tasks etc) but I'm happy to discuss what else we would like to >>>>>>> learn this year? >>>>>>> Definitely it would be good to probe the python versions and if >>>>>>> responders ever contributed to Airflow. >>>>>>> >>>>>>> Also, if anyone knows a better tool for surveys (especially for data >>>>>>> processing) than Google forms then I'm happy to consider it. >>>>>>> >>>>>>> Best, >>>>>>> Tomek >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Jarek Potiuk >>>>>> Polidea <https://www.polidea.com/> | Principal Software Engineer >>>>>> >>>>>> M: +48 660 796 129 <+48660796129> >>>>>> [image: Polidea] <https://www.polidea.com/> >>>>>> >>>>>>
