Does Zulip have a Fedora (native) client that can be installed by Fedora dnf tool?
I've been using Zulip in a browser [1] (as I do with hipchat) and it seems at least as good as hipchat. Has anyone looked at the Zulip multiple organization (team) support [2]? Scott [1] https://infinispan.zulipchat.com/ [2] https://zulip.readthedocs.io/en/1.7.1/prod-multiple-organizations.html On 05/18/2018 02:57 AM, Radim Vansa wrote: > Just out of curiosity, when choosing a replacement for HipChat, have you > considered Zulip? > > Infinispan uses that for about a month now and besides being too > colourful (similar to HipChat) there's been positive feedback, > especially due to the threading feature. > > Radim [trying to lure everyone to the same client] > > On 05/18/2018 12:16 AM, Sanne Grinovero wrote: >> On 17 May 2018 at 20:32, Guillaume Smet <guillaume.s...@gmail.com> wrote: >>> By the way, you say it’s clear we don’t want to stay on HipChat. >>> >>> When did we decide that? I don’t remember a discussion about it. >> I didn't say it was decided, but I think we're working on that since >> Steve asked about it today. To which I agree *because* it seems clear >> to me that we don't want to stay on it - a notion I inferred from >> multiple previous discussions. >> >> Steve pointed out multiple flaws e.g. the native client packaging >> broken on Fedora, to which Atlassian pretty much replied by letting us >> know they won't invest in HipChat as the future is Stride. We can >> choose when to switch but staying doesn't look sensible to me as it >> certainly won't improve; it's also likely that they'll want everyone >> migrated eventually so to shut the existing service down. >> >> I for one gave up as well installing the native client and have been >> using the web client since setting up my new workstation, as I was >> expecting Stride to arrive soon. >> >> The other day some people tried to join and gave up because of login >> complexity - that's IMO a very bad sign: not welcoming community >> people means it's failing its primary requirements. >> >> And let's not forget all authentication nonsense; especially days that >> I'm working more on the WildFly side of things and need to login to >> multiple instances I really look forward to a better system (hopefully >> it is!?). >> >> Question, since you want a decision: are you only suggesting to delay >> or suggesting that you should rather stay on HipChat? >> >> Personally, I'm fine delaying a bit even though I can live happily >> without Jenkins notifications, but let's hear the others as well. >> >> Thanks, >> Sanne >> >> >>> For sure, we probably won’t have a choice because there’s a good chance >>> Atlassian will close the service but what are the problems that make a >>> migration so urgent? >>> >>>> Le 17 mai 2018 à 20:16, Sanne Grinovero <sa...@hibernate.org> a écrit : >>>> >>>> lol, I was writing about the same to the team list. >>>> >>>> +1 to have people register, it's better for them anyway. I checked >>>> it's easier to self-register. >>>> >>>> +1 to migrate quickly. It's clear we don't want to stay on HipChat, if >>>> this doesn't work out we'll see. >>>> >>>> Refer to my parallel email for Fedora instructions. >>>> >>>> Thanks, >>>> Sanne >>>> >>>> >>>>> On 17 May 2018 at 19:03, Steve Ebersole <st...@hibernate.org> wrote: >>>>> I got an email from Atlassian this morning about the migration from >>>>> HipChat >>>>> to Stride. Basically they have not gotten Stride feature-complete in >>>>> terms >>>>> of HipChat which is the trigger for the mass migration. However, they are >>>>> reaching out to all waiting teams to see if any want to migrate anyway. >>>>> The list of missing features they sent me are: >>>>> >>>>> >>>>> 1. Guest access >>>>> 2. Some admin controls and compliance settings >>>>> 3. Integrations with Atlassian server products (the Jira Server app is >>>>> currently in beta and coming soon) and some other popular >>>>> integrations. See >>>>> all available Stride integrations >>>>> >>>>> <http://click.mailer.atlassian.com/?qs=6712850cb7a4f2d4a207f46e5f190a454855738b8db6340974f28f3c2e1e6aa7c674a6314ad5df11014e5e2ee39bd3d4326606d2826b241a> >>>>> . >>>>> 4. User management via API >>>>> 5. Dark mode >>>>> >>>>> I am not really sure exactly what is missing WRT (2). (3) is >>>>> nice-to-have, >>>>> but not blocker IMO assuming it gets added at some point. >>>>> >>>>> I think (1) is the only one that is concerning. Though TBH for myself >>>>> personally, I do not think registering is a big deal. >>>>> >>>>> Unless I hear otherwise, I plan on asking them to proceed with our >>>>> migration to Stride. >>>>> _______________________________________________ >>>>> hibernate-dev mailing list >>>>> hibernate-dev@lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev >>>> _______________________________________________ >>>> hibernate-dev mailing list >>>> hibernate-dev@lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev > > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
