Personally, I already use slack every day, so it’s easier for me to see and respond to messages as they come in. I’d be more amenable to Zulip if I used it for anything else, but I don’t, so for me, Slack is a clear winner.
Mike On Fri, Jan 31, 2025 at 11:31 AM Dmitri Bourlatchkov <di...@apache.org> wrote: > Good points from JB about compliance with community guidelines! > > Re: Zulip in general. I've had a lot of user conversations in Nessie via > Zulip lately, and I can say that Zulip is better organised in that regard. > Its topics are more like email threads, which IMHO maps better to `dev` ML > discussions (Apache Way) than Slack's channels. > > One odd thing is that users do seem to be a bit disoriented in Zulip > initially and post comments slack-style. This requires some effort from > people with admin access to sort out discussions into proper threads. > Nonetheless, more mature users benefit from the threaded discussion model > after the initial learning hump, I think. > > That said, if slack were to allow only PMC members to create channels, user > discussions will all pile in "general" and while slack supports threads, > those tend to be impossible to find after they age and scroll out of the > "latest" messages view. In effect the "general" channel becomes a tool for > "right now" conversations without any reusable history. > > To summarize, IMHO, supporting users in Zulip is easier for both users and > developers (committers). > > Cheers, > Dmitri. > > On Fri, Jan 31, 2025 at 3:41 AM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > > > Hi, > > > > It's something I wanted to bring here, so thanks for doing that :) > > > > I agree that we should use one chat service, I would propose Slack. > > It means updating: > > - removing zulip in README.md > > (https://github.com/apache/polaris/blob/main/README.md?plain=1#L35) > > - removing zulip from website > > ( > > > https://github.com/apache/polaris/blob/main/site/content/_index.adoc?plain=1#L32 > > ) > > > > However, I think that Slack is not fully compliant with the Chat > > Bylaws decided by the PPMC when Zulip has been set up > > (https://polaris.apache.org/community/chat-bylaws/), and I propose to > > improve Slack in this regard before removing Zulip. > > Let me chat with Yufei about Slack. > > > > Thanks ! > > Regards > > JB > > > > > > On Fri, Jan 31, 2025 at 9:18 AM Omar Al-Safi <o...@oalsafi.com> wrote: > > > > > > Hi Jack, > > > > > > +1 to depreciating one of the environments. > > > > > > Personally I have been using Apache Polaris Slack space more often than > > > Zulip, hence my personal preference for us to keep using Slack instead > of > > > Zulip, alone not having to use multiple chat clients and just one chat > > > clients for work and other projects is a big plus. > > > > > > Regards, > > > Omar > > > > > > > > > On Thu, 30 Jan 2025, 20:46 Jack Ye, <yezhao...@gmail.com> wrote: > > > > > > > Hi everyone, > > > > > > > > I heard feedback from some of my customers that are trying to use > > > > Polaris that it is a bit confusing to have 2 discussion platforms, > > Zulip > > > > and Slack, both existing for Polaris. They were not sure which one to > > join > > > > to get more attention for questions and discussions, or if they > always > > have > > > > to join and talk on both platforms. > > > > > > > > Do we plan to continue maintaining both platforms, or should we > > deprecate > > > > one and move to just one single platform? > > > > > > > > Best, > > > > Jack Ye > > > > > > >
