If you’re proposing that Slack replace this dev list, then chat is not an appropriate substitute for emails. Conversations fly by on a conveyor belt, context is easily fractured across multiple threads and short messages, information is poorly indexed by search engines, and the lower bar of entry means there will be more noise.
And these problems are separate from the potentially additional issues of Slack being a closed system, Apache policies about communication, etc. The Python community successfully migrated <https://discuss.python.org/> from mailing lists to a modern forum <https://discourse.org/>. If we are considering migrating off these lists (assuming that’s even possible), then that’s what I would suggest. > On Aug 12, 2024, at 3:06 AM, Nimrod Ofek <ofek.nim...@gmail.com> wrote: > > Hi all, > > Many other oss projects (some of which include some of the participants of > this mailing list I'm sure) are using Slack as a more modern communication > channel. > > I find Slack to be more appropriate these days, easier to navigate through > groups, easier to see context of different threads and also has a built in > mechanism for votes. > > I think that the only issue is that the free plan includes only 90 days > message retention- but I'm sure that one of the managers (Matei maybe?) can > negotiate different retention, we don't really need other features but the > retention is important- and I'm sure it's important for other Databricks > projects that are using Slack like Unity Catalog and Delta. > > What do you think? > > > Thanks, > Nimrod
