I find Slack to be very easy for conversation - and even easier for more serious conversations such as ones regarding SPIP etc. as the context is much clearer and it's easier to follow different threads. As for keeping historic records - as I stated, I really don't mind creating a bot that will copy each of the messages and will post them for historic records in the mailing list or whatever ASF wants... Also - Discourse (that has a Slack integration by the way) or other platforms can be used and all will be much easier to use and will encourage more people to join the community.
On Wed, Aug 14, 2024 at 4:41 PM Jungtaek Lim <kabhwan.opensou...@gmail.com> wrote: > My 2 cents here: the service is not appropriate to replace user@ or dev@ > entirely (even putting aside of ASF policy) if any of the functionality is > not fulfilled > > 1. Infinite retention. > > See below. This is what the ASF mail archive serves now. You get the > history from the incubator. > https://lists.apache.org/list?dev@spark.apache.org:2013-06 > > 2. External Search > > ASF mail archive supports search but I don't think it's powerful. But, > everything in user@ and dev@ is exposed to the public (via mail archive) > and "indexed" to search engines. Have you tried "site:lists.apache.org > SPIP" in Google? > > Any tool can be used to accelerate the faster communication, but serious > discussions impacting the project direction (e.g. SPIP, core features, > breaking changes, etc) and their VOTE threads, must be guarded by infinite > retention and be exposed to public (and easier to find in anytime, even for > future community member). > > > On Mon, Aug 12, 2024 at 7:46 PM 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 >> >
