users@ list has virtually no traffic/subscribers - most of the discussions are on slack (but it's both devel and users). I am also in favour of moving to Github Discussions. The only potential "problem" is that users might not be on Github - but I think it's a small barrier.
On Thu, Aug 27, 2020 at 3:35 PM Ry Walker <[email protected]> wrote: > Why not users@ mailing list: > > * I personally don't currently subscribe to users@ because of email > overload > * I didn't subscribe to users@ for very long as a new users, because I > felt > that I could get better support elsewhere than from others on that list. > > Why not Slack: > > * I do visit Slack to try and help people out, because I can do it on my > own time vs. getting content sent to my bloated inbox > * Sending links to slack discussions is unwieldy (when asking others to > join in) > * It's not a great UX for user questions, as they may get scrolled off / > easily ignored > * Answers aren't indexed by Google > * Answers eventually get deleted by 10k message limit (this would go away > if Slack request goes through positively) > > So for these reasons, I'm in favor of closing users@ mailing list in favor > of Github Discussions. > > > On Thu, Aug 27, 2020 at 7:02 AM Kaxil Naik <[email protected]> wrote: > > > *ASF Infra *has said the following: > > > > Note that github discussion are NOT to be used for anything other than > user > > help. As is the policy of the Foundation, all code-related discussions > and > > project management activities MUST be reflected to an ASF mailing list. > > > > What do you'll think now? I saw we keep slack as it is and accept that > this > > will replace [email protected] list. > > > > If we have some interest I can start a VOTE. > > > > On Mon, Aug 24, 2020 at 9:27 PM Kaxil Naik <[email protected]> wrote: > > > > > I mean I wouldn't want to drop Slack, it is so convenient for quick > > > conversations, especially between committers too. I think Slack can > > > co-exist with Github Discussions (GD), GD just replaces > > > [email protected] > > > > > > On Mon, Aug 24, 2020, 21:14 Jarek Potiuk <[email protected]> > > wrote: > > > > > >> I am all for moving especially looking at the roadmap: > > >> https://github.com/github/roadmap/issues/104 (Q4 2020). > > >> > > >> The question is whether it will serve all the purposes that slack > serves > > >> now and whether we can just abandon slack in one go? > > >> > > >> J, > > >> > > >> > > >> On Mon, Aug 24, 2020 at 7:30 PM Tomasz Urbaszek <[email protected] > > > > >> wrote: > > >> > > >> > We had a small chat about this on slack: > > >> > > https://apache-airflow.slack.com/archives/CCPRP7943/p1598111138037700 > > >> > > > >> > I personally think that if our request for paid Slack is not > accepted > > >> > we should consider moving to Github Discussion. Even if we got paid > > >> > plan, I would be in favor of migrating as we don't know how long it > > >> > will be avaliabe for us. > > >> > > > >> > I saw a few projects using it already and I like keeping discussion > > >> > close to code (all this features of linking and nice code > snippets!). > > >> > If we decide on migration then I would also suggest to consider > using > > >> > StackOverflow for handling troubleshooting. > > >> > > > >> > My only concern is that it's even more Github-locking. But I do not > > >> > expect Github to request open-source projects to pay for anything. > > >> > > > >> > Tomek > > >> > > > >> > > > >> > On Mon, Aug 24, 2020 at 7:18 PM Kaxil Naik <[email protected]> > > wrote: > > >> > > > > >> > > I agree and I share the same concern. But I see it as a drop-in > > >> > replacement > > >> > > for the [email protected] list and is mostly similar to a > > >> forum > > >> > > which will be indexed by Search engine unlike Slack. > > >> > > > > >> > > Also as we are on a free plan with Slack, we can't see history :( > -- > > >> We > > >> > > have asked Slack if they can upgrade us since they are also > Airflow > > >> > Users, > > >> > > we will see what happens with that. > > >> > > > > >> > > Regards, > > >> > > Kaxil > > >> > > > > >> > > On Mon, Aug 24, 2020 at 6:14 PM Deng Xiaodong < > [email protected]> > > >> > wrote: > > >> > > > > >> > > > The only concern I can think of is it seems serving identical > > >> purpose > > >> > of > > >> > > > what Slack is serving at this moment (correct me if I’m wrong > > >> please). > > >> > > > > > >> > > > Then attentions (especially from folks who nicely volunteer to > > >> answer > > >> > > > questions in community) would be distributed unnecessarily. > > >> > > > > > >> > > > > > >> > > > XD > > >> > > > > > >> > > > > On 24 Aug 2020, at 7:06 PM, Kaxil Naik <[email protected]> > > >> wrote: > > >> > > > > > > >> > > > > Hi all, > > >> > > > > > > >> > > > > I know most of us might have already heard or read about > Github > > >> > > > Discussions > > >> > > > > < > > >> > > > > > >> > > > >> > > > https://github.blog/2020-05-06-new-from-satellite-2020-github-codespaces-github-discussions-securing-code-in-private-repositories-and-more/ > > >> > > > > > > >> > > > > . > > >> > > > > > > >> > > > > I noticed Apache Couchdb has been already using it: > > >> > > > > https://github.com/apache/couchdb/discussions > > >> > > > > > > >> > > > > Thought we could also it for the Airflow community. > > >> > > > > > > >> > > > > What do you all think? If most of us agree I will raise an > Issue > > >> with > > >> > > > > Apache INFRA team to enable it for us. > > >> > > > > > > >> > > > > > > >> > > > > Regards, > > >> > > > > Kaxil > > >> > > > > > >> > > > > > >> > > > >> > > >> > > >> -- > > >> > > >> Jarek Potiuk > > >> Polidea <https://www.polidea.com/> | Principal Software Engineer > > >> > > >> M: +48 660 796 129 <+48660796129> > > >> [image: Polidea] <https://www.polidea.com/> > > >> > > > > > > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
