New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[AIRFLOW-XXXX] - add communication chapter to contributing #7204
[AIRFLOW-XXXX] - add communication chapter to contributing #7204
Conversation
7ea5179
to
2d84295
Compare
Hey @mschickensoup, would you like to take a look? 😺 |
f496cbc
to
367833f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this text! I think it's super important for anyone who'd like to join Apache Airflow community. I've left my comments but I also have a general feedback. First of all, I'd focus on a perspective of a total newbie. I had an impression that not everyone might be familiar with Slack / devlist etc. What is missing (not in the text itself) but within the community are rules / good practices on how to e.g. open subjects on the devlist / how to assign them to a certain category/classification [DISCUSSION] etc. or there are such rules but I didn't find them. Not sure. I think it's also worth mentioning how much fun it brings if you communicate with the others. It's not just distributed teams but you actually can meet other contributors live on various events and speaking to them would not be as scary when you have already communicated with them within community 😄I know the whole text is about "How to communicate" inside the community. However, I'd add something like (it's a thought, not the real sentence I'd use) "we are humans, fun individuals who except for being active on the devlist can be met on various meetups/events/local communities". Plus, there is nothing on how to communicate if you're not a developer but you want to be a part of the community too. If there was no Aizhamal, I wouldn't know that I could communicate/be a part of the team and do some good as well :-) I think it's important to also highlight the work of people who make sure that things are ordered, that there are meetups across the world and who take care of clear/proper communication on a daily basis if others forget about it. I guess I did some huge off-top now but I had to speak my mind. Hope you'll find my comments useful.
367833f
to
f2bd780
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All updated Any more comments? @nuclearpinguin @mik-laj ?
thanks @mschickensoup for comments |
(cherry picked from commit 3f25ff9)
(cherry picked from commit 3f25ff9)
(cherry picked from commit 3f25ff9)
(cherry picked from commit 3f25ff9)
Communication
Issue link:
Document only change, no JIRA issue
Make sure to mark the boxes below before creating PR: [x]
[AIRFLOW-NNNN]
. AIRFLOW-NNNN = JIRA ID** For document-only changes commit message can start with
[AIRFLOW-XXXX]
.In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.