Review ASF feature requirements for future communication platforms

[ShaneCurcuru]

While the ASF's use of mailing lists is well understood - and SLOPI through our list archives - as more projects switch to newer communication tools, we're looking to better define the core requirements for communications.

One unofficial effort at the ASF Community Development project is here, and is shaping up with many of the same features and rationales, obviously! Just an FYI if folks are following up with more clarifications here, or at CHAOSS.

https://cwiki.apache.org/confluence/display/COMDEV/Communication+Tools+Archiving+Requirements

[pdurbin]

@ShaneCurcuru I'm honored that you linked to SLOPI from that page! Thanks!

Are you asking me to review that page and give feedback?

Or are you just letting me know you linked to SLOPI from it, in case they reach out?

Or both? Whatever is fine! Thanks again. 😄

[ShaneCurcuru]

Just an FYI, feel free to close if there aren't plans for updating SLOPI here!
I just found it wicked cool that you've looked at the ASF's (mostly unwritten) model for how we should store project communications, and come up with such a succinct and spot on description for the core features, and was using it for inspiration to drive our own future work.

Sharing deeper best practices - especially with the rationale or "Why" behind it - can be valuable across organized open source kinds of communities, and is something I hope to keep doing more of.