Slack has a search capability, which I've used to find "old' issues. I did loose track of whether airflow's slack maintains history persistently. If it doesn't do I remember that the ASFs overall does (which airflow could benefit from/opt-into, if desired)?
On Sat, May 25, 2019 at 3:16 AM Jarek Potiuk <jarek.pot...@polidea.com> wrote: > I'd go even further and remove troubleshooting altogether and leave it for > announcements, personal discussions, user groups, asking for PRs to be > reviewed - anything that has no "persistent" value. > > See the separate discussion about the user@ devlist: > > https://lists.apache.org/thread.html/9cf5a633cac0eb0652eef88dee82f567d57c39b302a8e9f02b016d85@%3Cdev.airflow.apache.org%3E > > > I think we should discourage users to ask questions in slack and encourage > to move to the userlist, but to do it on the userlist instead. Main reason > is simply because the information in userlist is publicly searchable and > you can find answers to the questions you want much easier if it has > already been answered. Questions/answers in slack are lost very quickly. > > J. > > On Sat, May 25, 2019 at 1:34 AM Teresa Martyny < > teresa.mart...@omadahealth.com> wrote: > > > 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 <sergio...@gmail.com> 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. > > > > > -- > > Jarek Potiuk > Polidea <https://www.polidea.com/> | Principal Software Engineer > > M: +48 660 796 129 <+48660796129> > E: jarek.pot...@polidea.com >
