Hi, We already have guidance on communication expectations. [1][2] Mailing lists are the primary space for project decisions, voting, and long-term record keeping. Instant messages in Slack or other platforms can be useful for coordination and faster conversation, but they must support the lists, not replace them. Anything that affects technical direction or governance needs to be summarised back to dev@, so the whole community can participate and audit the outcome. Note, this topic has recently come up on the board list.
I thought we could look at how and indeed if podlings apply this in practice. Questions to explore - Where has chat helped with newcomer support, rapid problem-solving, or community building? - Where has it created transparency risks, exclusion across time zones, or fragmentation of discussion? - What are good patterns for summarising chat back to dev@ so decisions remain public, archived, global, and accessible? - How do podlings ensure tools do not disadvantage people with limited bandwidth, blocked services, or lower English fluency? Kind Regards, Justin 1. https://cwiki.apache.org/confluence/display/INCUBATOR/Communication+in+Apache+Projects 2. https://cwiki.apache.org/confluence/display/INCUBATOR/International+and+Cultural+Awareness --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
