potiuk commented on PR #911: URL: https://github.com/apache/airflow-site/pull/911#issuecomment-1862454072
I am not sure if we want to put Slack as first and foremost in the community. While devlist is much harder to join and less popular, this is the only official and "authoritative" place where things get discussed and agreed to - and (so far) this is the only place that the ASF projects are supposed to make decisions and where important things and announcements happen "If it did not happen on the devlist, it did not happen" Slack is much more casual of course and where things are happening as well, but I would even say GitHub discussions, issues and PRs is where much more "community" things happen. It's much more akin to the "devlist" - where smaller decisions are made in PRs and where issues and discussions about potential future features or current problems happen. The problem with Slack is that it is ephemeral and with much more "synchronous" expectations and pressures (i.e. discussions basicaly disappear when not answered synchronously - no-one will generall look back at the past discussions and questions after they move out behind the edge of your screen). Both devlist and github are mostly asynchronous in nature - and asynchronous communication is very important in ASF communities. I am not sure putting Slack as first thing there is a good idea because of that. I am not sure if I have a very constructive approach how to do it differently. Maybe an idea we should split this tab into two - signalling that we have things which is mostly for users seeking for help and troubleshooting (with slack first and foremost followed by github issues and discussions and ending at [email protected]) and another tab where we have a different set of links for "creators" - i.e. devlist, github PRs, github issues, github discussions. There is significant overlap of both of course, but maybe we should recognise the fact that "users" should have a different "hierarchy of needs" here than "creators" ? Even the ASF standard "dev@" vs. "users@" follows that pattern. Speaking of which @merobi-hub -> I think this one is a perfect candidate to start a devlist discussion about. I think, if you want this PR to proceed and get the right approach, the idea of changing navigation on our website is definitely not a decision any single or even few maintainers should take in a PR, this should be a discussion on devlist and I think you should start one and explain the motivations behind the change and what you think we are going to get by that. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
