Hi guys, It's been some time since I gathered the courage to finally speak my mind in this discussion. I'd like to share some thoughts from a non-programmer's perspective and what I wish I knew before joining Apache Airflow community.
TL;DR; Non-technical people would love to build this community as well. We just don't know how ;-) 1. It is amazing that there's an info on the Apache website about the devlist. However, I totally don't know how to use it except for knowing how to join. For someone not familiar with it it's hard to even start his/her discussion because I believe (please correct me if I'm wrong) there are no rules on how to e.g. create a subject in the form of a [DISCUSSION] / [AIP-XY] etc. 2. There's no info about what is devlist / Slack better for but I've seen the latest PR https://github.com/apache/airflow/pull/7204 about it, so I won't talk too much now. 3. I'd be happy to know what I myself, as a non-technical person, can do to make this community better. We have an info about documentation and the need of enhancing it on the website but if I were a student and would like to know more about the nature of OSS projects and even things like how to use JIRA / Github in such project, it would help. Let's say someone would like to gain experience to become a Project Manager in the future and build great teams based on Apache good practices even though open source projects have no actual structures. 4. Meetups / Apache Local Community - I think it's something non-technical people can do. In fact, I was happy to make the 1st Warsaw Apache Airflow meetup happen and cooperate with Aizhamal, Jarek, Tomek and Kamil to think of and make the best experience for people who wanted to know more about Apache Airflow project in general. I'm not sure if I would be honoured to take part in such an experience without the people I mentioned. I simply didn't know that as a Project Manager of cloud / big data project in a usual company I can still have small impact on building a better and more mature community. It's only because I did receive tons of mentorship, constant encouragement from my colleagues. Without them I wouldn't even know that it's possible to contribute as a non-programmer. 5. I was amazed by the results of the survey that Tomek has recently made. I started to look around for more general info about welcoming open source communities and what makes people join such communities. I bumped into a great study made by Digital Ocean which you can find under the following link: https://www.digitalocean.com/currents/december-2019/#anchor-the-community-of-open-source It describes things like inclusivity, men vs. women perception of open source projects / welcoming and friendly communities / rules etc. It's long but worth reading :-) Side story: I once took part in a mentorship program for young Project Managers wannabes and after spending 3 months with a brave and bright young lady I didn't think of open source community as a fresh start for her to gain experience. I'm glad that now I know that it's possible. Karolina Rosół Polidea | Project Manager M: +48 606 630 236 E: karolina.ro...@polidea.com Check out our projects! Karolina Rosół Polidea | Project Manager M: +48 606 630 236 E: karolina.ro...@polidea.com Check out our projects! On Mon, Jan 27, 2020 at 10:23 AM Kaxil Naik <kaxiln...@gmail.com> wrote: > > That is a good find. We can do something similar. > > 2 things I have in mind: > > 1) A separate list sl...@airflow.apache.org where we forward all Slack > communication > > 2) A selective forward (filter certain channels to different list). Some of > them can go to dev@ but some belong to users@ list > > > I see (1) being more relevant. I will create a separate thread to discuss > the specifics of Slack as that can be independent of this thread. > > Regards, > Kaxil > > On Mon, Jan 27, 2020, 14:09 Jarek Potiuk <jarek.pot...@polidea.com> wrote: > > > This is very interesting. I think we should try it. Simple #devlist channel > > with bi-directional connection to devlist seems like it ! > > > > J. > > > > pon., 27 sty 2020, 09:34 użytkownik Tomasz Urbaszek <turbas...@apache.org> > > napisał: > > > > > Hi all, > > > > > > There's an interesting discussion on the devcomm list regarding > > > bidirectional integration between Slack and mailing list: > > > "We have set up Mahout's slack space to forward directly to > > > d...@mahout.apache.org. We will now be able to plan publicly on slack. > > This > > > a bi-directional connection, all messages to d...@mahout.apache.org will > > > show up in Slack. No one will be left out of planning." > > > > > > > > https://lists.apache.org/thread.html/rbc1c1c2a289accb40e7e3967f7c08213f13fea46013f73cf881c74c0%40%3Cdev.community.apache.org%3E > > > > > > I think this can be an interesting approach. WDYT? > > > > > > T. > > > > > > > > > On Sat, Jan 18, 2020 at 2:36 PM Jarek Potiuk <jarek.pot...@polidea.com> > > > wrote: > > > > > > > Based on this and a few other discussions we had in Slack and various > > > PRs I > > > > created another PR proposal: > > > > > > > > [AIRFLOW-XXXX] - add communication chapter to contributing > > > > <https://github.com/apache/airflow/pull/7204> - I tried to capture at > > > > least > > > > my understanding on how Airflow Community works and how communication > > > > happens. A lot of people do not understand how our community works and > > > how > > > > it is made of individuals and how the communication works - including > > how > > > > you should handle emotions during the discussions. I'd love to hear > > > opinion > > > > of all community members on my proposal - and possibly perfect/update > > (or > > > > discard if you think it is far from what we - as a community care > > about. > > > I > > > > think it would be great to have a chapter explaining it - this might > > > help > > > > to point out new people and make it easier to understand how they can > > > > communicate and what to expect. > > > > > > > > Looking forward to your comments. > > > > > > > > J. > > > > > > > > On Sat, Jan 18, 2020 at 12:11 PM Jarek Potiuk < > > jarek.pot...@polidea.com> > > > > wrote: > > > > > > > > > I have just opened two PRs: > > > > > > > > > > - [AIRFLOW-XXXX] Add mentoring information to contributing docs > > > > > <https://github.com/apache/airflow/pull/7202> - this explains > > to > > > > new > > > > > contributors that they can ask to get mentors and that there is an > > > > official > > > > > mentoring programme > > > > > - [AIRFLOW-XXXX] Add rebase info to contributing > > > > > <https://github.com/apache/airflow/pull/7201> - I noticed > > recently > > > > > that a lot of people do not know about rebase workflow and are not > > > > > comfortable with it. I have added a short step-by-step guide on > > how > > > to > > > > > rebase PR in an easy way > > > > > > > > > > Other committers - please take a look and comments on those PRs as I > > > > > think this is a vital part of our communication to the new > > > contributors. > > > > I > > > > > think providing mentoring is a good step in direction of being > > > welcoming, > > > > > especially if we all act as mentors to some capacity and help others > > to > > > > > understand how our community works. > > > > > > > > > > J. > > > > > > > > > > > > > > > On Sat, Jan 18, 2020 at 11:41 AM Jarek Potiuk < > > > jarek.pot...@polidea.com> > > > > > wrote: > > > > > > > > > >> Thanks Kamil! That's super helpful! I did not know such a programme > > > > >> exist! I will add information about it to CONTRIBUTORS.rst > > > > >> > > > > >> On Sat, Jan 18, 2020 at 2:32 AM Kamil Breguła < > > > > kamil.breg...@polidea.com> > > > > >> wrote: > > > > >> > > > > >>> Hello, > > > > >>> > > > > >>> Many projects in the ASF are able to provide mentors for newcomers. > > > In > > > > >>> fact, most projects are happy to assist newcomers to their projects > > > as > > > > >>> part of their normal operations. However, some people are looking > > for > > > > >>> more structure. The Mentor Programme of the The Apache Software > > > > >>> Foundation provides additional support and structure for people > > > > >>> looking to make an initial contribution to an ASF project. > > > > >>> > > > > >>> More information: > > > > >>> http://community.apache.org/mentoringprogramme.html > > > > >>> > > > > >>> Best regards, > > > > >>> Kamil Breguła > > > > >>> > > > > >>> On Fri, Jan 17, 2020 at 10:53 AM Jarek Potiuk < > > > > jarek.pot...@polidea.com> > > > > >>> wrote: > > > > >>> > > > > > >>> > I have some thoughts about the "mentoring" and being more > > > welcoming. > > > > >>> There > > > > >>> > were quite a few discussions about that on slack/github/twitter. > > > > >>> > > > > > >>> > I think there are people with different experiences and some > > people > > > > >>> need a > > > > >>> > bit more mentorship or guidance in some areas of Airflow > > (testing, > > > > >>> > documentation etc). So maybe a proposal (I started doing it > > > already): > > > > >>> > > > > > >>> > *When we (i.e. committers) make some comments and ask the > > > > contributors > > > > >>> to > > > > >>> > do something, we add something like "I am happy to provide more > > > > >>> guidance if > > > > >>> > needed" or "Happy to help if you need" etc. * > > > > >>> > > > > > >>> > I think that might make some people feel more comfortable with > > > their > > > > >>> first > > > > >>> > time contributions. It's really small thing but it might make a > > > > >>> profound > > > > >>> > impact on how we are perceived as community by people who > > consider > > > > >>> joining > > > > >>> > our community. > > > > >>> > > > > > >>> > J > > > > >>> > > > > > >>> > > > > > >>> > On Thu, Jan 16, 2020 at 3:19 PM Jarek Potiuk < > > > > jarek.pot...@polidea.com > > > > >>> > > > > > >>> > wrote: > > > > >>> > > > > > >>> > > So we have the > > > https://issues.apache.org/jira/browse/AIRFLOW-6556 > > > > >>> issue > > > > >>> > > right now. > > > > >>> > > Please comment :) If anyone would like to contribute their time > > > and > > > > >>> > > knowledge (ideally someone with tech-writing experience but > > this > > > is > > > > >>> not > > > > >>> > > necessary). > > > > >>> > > I am happy to mentor such people and help them in setting it > > up > > > > and > > > > >>> > > contributing, reviewing, involving other committers. > > > > >>> > > Let me know if you would like to do something here and we can > > > > >>> separate out > > > > >>> > > some sub-tasks from the main one. > > > > >>> > > > > > > >>> > > J. > > > > >>> > > > > > > >>> > > On Tue, Jan 14, 2020 at 2:00 PM Jarek Potiuk < > > > > >>> jarek.pot...@polidea.com> > > > > >>> > > wrote: > > > > >>> > > > > > > >>> > >> @Jarek, I'm happy to have a think and make a list of the areas > > > of > > > > >>> the > > > > >>> > >>> documentation I find most lacking. Would you like me to post > > > that > > > > >>> here, > > > > >>> > >>> or > > > > >>> > >>> if we open a Jira ticket would it be better to have it > > > commented > > > > >>> there? > > > > >>> > >>> > > > > >>> > >> > > > > >>> > >> It would be great if you can create a JIRA issue and assign > > me. > > > > >>> Thanks! > > > > >>> > >> > > > > >>> > >>> > > > > >>> > >> > > > > >>> > > > > > > >>> > > > > > > >>> > > -- > > > > >>> > > > > > > >>> > > Jarek Potiuk > > > > >>> > > Polidea <https://www.polidea.com/> | Principal Software > > Engineer > > > > >>> > > > > > > >>> > > M: +48 660 796 129 <+48660796129> > > > > >>> > > [image: Polidea] <https://www.polidea.com/> > > > > >>> > > > > > > >>> > > > > > > >>> > > > > > >>> > -- > > > > >>> > > > > > >>> > Jarek Potiuk > > > > >>> > Polidea <https://www.polidea.com/> | Principal Software Engineer > > > > >>> > > > > > >>> > M: +48 660 796 129 <+48660796129> > > > > >>> > [image: Polidea] <https://www.polidea.com/> > > > > >>> > > > > >> > > > > >> > > > > >> -- > > > > >> > > > > >> Jarek Potiuk > > > > >> Polidea <https://www.polidea.com/> | Principal Software Engineer > > > > >> > > > > >> M: +48 660 796 129 <+48660796129> > > > > >> [image: Polidea] <https://www.polidea.com/> > > > > >> > > > > >> > > > > > > > > > > -- > > > > > > > > > > Jarek Potiuk > > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer > > > > > > > > > > M: +48 660 796 129 <+48660796129> > > > > > [image: Polidea] <https://www.polidea.com/> > > > > > > > > > > > > > > > > > > -- > > > > > > > > Jarek Potiuk > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer > > > > > > > > M: +48 660 796 129 <+48660796129> > > > > [image: Polidea] <https://www.polidea.com/> > > > > > > > > >
