Hello here, As you might have seen - we had discussed in the Airflow PMC a series of "formalisations" that are needed in the way the PMC works, also to make sure that we are 100% compliant with what the Apache Software Foundation expects from the PMCs.
A bit of education on the Apache Software Foundation follows :) One last thing is to clarify a bit what is "expected" to be communicated at the devlist and how messaging that is not "PMC" originated (i.e. from individuals and companies) should be clearly separated from the "PMC" communication (for example monthly newsletter that is sent by Briana and mostly driven by Astronomer. It is cool and great that Astronomer want to make such summaries and communication, it's just the ASF has clear rules about making clear to not make the impression (even accidentally) that such messages are PMC-driven. For example PR of the month, Monthly TownHall, DevCalle are clearly PMC driven/controlled/involved - we are involved and there are clear rules: "no decision making", PMC members explain what's going on in the project and Briana is wonderfully orchestrating (pun intended !) the PR of the month and TownHall and Vikram orchestrates the Dev Calls. But the newsletter is much more Briana/Astronomer driven - I love to read them, but PMC is not really involved in subscription mechanisms, content, format etc. And if you follow the devlist, you might not realise there is a difference and we wanted to discuss it. I planned to do it on Monday and discuss the proposal in PR before we merge it, but Shahar (AKA "eager beaver" :D) merged it already, so we can discuss it "after merge" and see if there are any comments from the community about it. This chapter has been modified: https://github.com/apache/airflow/blob/main/contributing-docs/02_how_to_communicate.rst#devlist-details I copy the content added below - and if you have any comments or questions, we can discuss it here and if need be, adjust it. This has been earlier discussed in the PMC and we **almost** reached a lazy consensus on this proposal ... (if not the "eager beaver" ;) ). (actually, I pulled Shahar's leg a bit - but the fault is entirely mine - I should have marked it as Draft - but I did not :D). Feel free to comment on it in this thread. --- Apart of regular discussions on development of the project, the community also appreciates if various stakeholders, community members and participants share their experiences, case studies, best practices as well as updates on what's going on in their organizations related to Apache Airflow. There are certain rules for this kind of communication, it cannot be commercial in nature, it should not promote specific products or services, and it should not suggest that the PMC or the ASF endorse any specific products or services. The subject of such messages should refer to Airflow in "Nominative fair use" way as described in Apache Trademark Policy. Such messages can contain summary and digest of what happens in the community - as long as it is unbiased and not commercial in nature. This kind of communication should be shared on devlist and whoever sends such messages should be open to include information from other community members who ask them to include their case studies, experiences or information. Like all the communication in our project - such messages should follow the ASF Code of Conduct. If you are in doubt whether your message is appropriate for the devlist - ask the community on devlist. ---- Jarek - on behalf of the PMC
