> > > I'm not trying to argue about others's people preference; any tool > can be used. It's just that I don't think that "it's newer/graphical" is > a reason for change. >
It's not. I think main reason is it is more accessible, allows to edit your answers and correct typos, works in the browser without having an apache account. Two years ago, we used Slack for synchronous GSoC meetings > (which had its merits). > Slack 2 years ago and. now (especially with their thread support) is much more async-friendly. Do check it out. 2 years is a long time. > So, in addition to dropping the MLs, is the plan to force everyone > to subscribe to GitHub? > No. I was pretty clear about it - let every PMC choose what's best for them. There is no need for everyone to join. Just the community, > There are ASF subscription requirements associated with various > roles (committers, PMC, etc.). > The problem is that this is actually very egalitarian. We have almost 2000 contributors in Airflow and < 50 committers. 1950 of our community members on GitHub (not even including the 10,000 of attendees who participated in Airflow Summit last year) do not have ASF accounts. Do you think it is wise to exclude them? I certainly don't. I think our community is FAR bigger than those who subscribe to devlist. And excluding them by default is well, stupid. > GitHub/Slack/etc. are not yet among them so it seems weird that > those channels could bypass the official ones. Surely. If you want to limit to 50 people out of 2000 contributors, then yeah . Sticking to official ones makes sense. But I want to include more people. Yes. [I asked for clarification about this, earlier in the thread. Did > INFRA > eNover advertised that it would work?] I hope. > Next time I wish to intervene in GH discussion, I'll try it. ;-) > Feel free , As I mentioned many times - I think it differs by community. I am the last one to impose "one solution to rule them all" on all communities. Sounds too, well "Sauronish" ? I think embracing diversity is a thing. And enabling each PMC to be able to choose sounds like Apache Way (as long as the expectations are met). > > Do you mean that those people don't have an email address, or cannot > click on a subscription link in a browser? > Or maybe they feel intimidated by it ? I think technical capabilities are less of a problem, but empathy and human emotions, habits are more important. Just recognising that different people have different needs, expectations, fears and many other emotions is important, I think. People are not robots.
