Thanks for breaking this out Sergio! What is the current process for maintaining/moderating existing channels? How would that change with this infrastructure change?
*Teresa Martyny* pronouns: she, her, hers Software Engineer | Data Team Lead | Omada Health <https://www.omadahealth.com/> 500 Sansome St #200, SF, CA 94111 *What is Omada?* <https://vimeo.com/203386025> On Fri, May 24, 2019 at 3:17 PM Sergio Kef <[email protected]> wrote: > Slack is a channel that could support a lot more our community. > I've noticed that as a developer I get a bit overwhelmed by the amount of > messages there, every time I join. This is a "good" problem, shows engaging > community. What we miss though is the opportunity to catch up quickly > what's going on, if we missed some days/weeks or even if it's our first > time there. > > So I propose a small restructure of the channels to make it easier follow > and catch up. > * announcements (as is) > - new releases > - community announcements > * general > - events (meetings, webinars, conferences, etc) > - material (tutorials, blog posts, etc) > * contribute > - contributors' questions (getting started, ci, testing, etc) > - future ideas & more (eg some premature AIPs) > - call for help on bugs/fixes/PRs > * how-to (similar to current troubleshooting) > - user issues > - guidance on ETLs > > Of course the list is open for suggestions. > Let me know what you think. > > Sergio. > -- This email may contain material that is confidential and/or privileged for the sole use of the intended recipient. Any review, reliance, or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Also note that email is not an appropriate way to send protected health information to Omada Health employees. Please use your discretion when responding to this email.
