All third party proprietary systems not owned by the Apache Project come with risks, Github and Jira included. However Slack strikes me as particularly bad.
1. It breaks the web architecture with unstable URLs. 2. The privacy practices are unclear, unstable, and user hostile. Using Slack requires not just agreeing to the Apache Project's terms (which are quite reasonable) but an extensive legal agreement which Slack claims to be able to unilaterally and retroactively change at their whim. 3. Slack is just ugly and hard to use compared to email or Jira. OK, #3 is IMHO but #1 is bad and and #2 is awful. It's also painful to have to check multiple locations to figure out what's going on. I've used Slack when I'm paid to, but otherwise I avoid it these days, including in open source development. It's just too painful and it's been getting worse over time. I'd like to propose that we simply stop using Slack for project wide communications. Discussion about Maven related things can take place in the mailing list or the issue tracker. Between that, communication is well covered. Thoughts? https://slack.com/trust/privacy/privacy-policy https://arstechnica.com/tech-policy/2024/05/slack-defends-default-opt-in-for-ai-training-on-chats-amid-user-outrage/ -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
