Hi,

Le mer. 16 févr. 2022 à 13:50, Roman Shaposhnik <r...@apache.org> a écrit :
> ...while the classical ASF communication culture is pretty squarely
> centered around mailing lists it has become apparent in recent
> years that some of our communities (especially younger ones)
> prefer using alternative channels of communication....

I agree, and the risk with sticking with "if it didn't happen on the
mailing list it didn't happen" is that some projects route around
that, just play lip service to it but use other channels for their
actual work. I think that is happening today, to various degrees.

One way to avoid that would be to replace that dogma with more
realistic criteria that can be met with other tools, similar to what
Mark Thomas mentions in this thread, letting each project select the
tools that work best for them within those boundaries.

Things like:
-Project channels must be public, async, archived on ASF-owned
services and searchable
-Project channels must be usable with open source clients (hmmm..Slack?)
-All decisions and votes must be documented on the project's mailing
list, with links to the original discussion.

I think such a list of criteria (to be refined) would give our
projects more leeway while respecting our actual goals in terms of
open communications.

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Reply via email to