On 07/30/2018 06:20 PM, Yoann Rodiere wrote:
> If we must compare Zulip to emails, cross-posting to multiple mailing lists
> would be equivalent to posting to different "streams", which are the
> equivalent of "rooms" in HipChat or "channels" in IRC.
> Short answer is: you can't do that, you have t
If we must compare Zulip to emails, cross-posting to multiple mailing lists
would be equivalent to posting to different "streams", which are the
equivalent of "rooms" in HipChat or "channels" in IRC.
Short answer is: you can't do that, you have to duplicate the conversation.
But so would you in Hip
On Mon, 30 Jul 2018 at 16:39, Steve Ebersole wrote:
>
> I am not asking about a "supart". Think about topics that we cross post to
> hibernate-dev and willdfly-dev or hibernate-dev and infinispan-dev... so
> the discussion *simultaneously* spans multiple topics/audiences.
In zulip what you write
I am not asking about a "supart". Think about topics that we cross post to
hibernate-dev and willdfly-dev or hibernate-dev and infinispan-dev... so
the discussion *simultaneously* spans multiple topics/audiences.
On Mon, Jul 30, 2018 at 9:27 AM Emmanuel Bernard
wrote:
> Same as in an email thre
Same as in an email thread, you change the topic for a subpart of your
conversation. You can opt to fork the topic name at a
given point in time retroactively (which you don't get for emails).
On Mon 18-07-30 9:10, Steve Ebersole wrote:
>In practice, what happens when a discussion spans multiple
In practice, what happens when a discussion spans multiple topics?
On Fri, Jul 27, 2018 at 9:43 AM Emmanuel Bernard
wrote:
> On Fri 18-07-27 14:38, Guillaume Smet wrote:
> >On Fri, Jul 27, 2018 at 2:31 PM Emmanuel Bernard
> >wrote:
> >
> >> I like Zulip a lot. I've been using it extensively an
On Fri 18-07-27 14:38, Guillaume Smet wrote:
>On Fri, Jul 27, 2018 at 2:31 PM Emmanuel Bernard
>wrote:
>
>> I like Zulip a lot. I've been using it extensively and the notion of
>> topic (like a email subjet) is a big +1 for me and for any more casual
>> lurker. Also it reduces the proliferation of
On Fri, Jul 27, 2018 at 2:31 PM Emmanuel Bernard
wrote:
> I like Zulip a lot. I've been using it extensively and the notion of
> topic (like a email subjet) is a big +1 for me and for any more casual
> lurker. Also it reduces the proliferation of one off/single subject
> channel that a lurker alw
I like Zulip a lot. I've been using it extensively and the notion of
topic (like a email subjet) is a big +1 for me and for any more casual
lurker. Also it reduces the proliferation of one off/single subject
channel that a lurker always miss in tools like Slack.
Granted Zulip topics are a bit offs
Slack does require more memory than other solutions, running on 200 MB
here for 3 Organizations, but it is a really nice tool.
So my preference is Slack.
Mit freundlichen Grüßen,
*Christian Beikov*
Am 27.07.2018 um 09:19 s
So, I guess this closes the "Stride" case: we won't use it.
I quite like Zulip, but I must admit it doesn't do much to make life easy
for new users. This choice of theirs to make topics mandatory (or at least
*seemingly* mandatory), in particular, is very likely to confuse new users,
be it Hiberna
+1 to test Zulip, thanks for setting it up Yoann.
Personally having used it quite a bit with other projects: it has
potential but it's not particularly polished yet; in particular the
mobile client has severe issues, and people are quite often failing to
use the "topics" correctly.
In the news to
I encountered yet another problem with HipChat [1], so I created a
Hibernate organization in Zulip. Turns out GitHub and Google authentication
are available even in the free plan.
Anyone cares to join me to test it? It's here:
https://hibernate.zulipchat.com/#
[1]
https://bitbucket.org/hipchat/hi
On Tue, May 22, 2018 at 10:26 AM, Yoann Rodiere wrote:
> ... But I think the one criteria that will make us pick Stride is free
> hosting. Most other platforms either do not have a free plan, or do not
> provide all of their features to free plan users. Zulip apparently removes
> OAuth authentica
I see it much simpler.
We're moving to Stride because that's how HipChat evolved.
On Tue, 22 May 2018, 09:34 Yoann Rodiere, wrote:
> I think the problem here is about how we're choosing to migrate to another
> tool. We are basically moving to Stride because Atlassian is being
> uncooperative w
I think the problem here is about how we're choosing to migrate to another
tool. We are basically moving to Stride because Atlassian is being
uncooperative with updating HipChat, even though Stride is still not fully
functional.
Atlassian made HipChat, and we're not happy with HipChat. Atlassian ma
Hi,
On Fri, May 18, 2018 at 1:37 PM, Steve Ebersole wrote:
> You can't "do your job" without yet another way to get notified of CI job
> status? I'm confused - did Jenkins remove all of its other forms of
> notification? ;) Seriously though, I've never understood this desire to
> have yet an
On 05/18/2018 03:56 PM, Scott Marlow wrote:
> Does Zulip have a Fedora (native) client that can be installed by
> Fedora dnf tool?
No, they don't have RPM, I use the provided AppImage. Yes, nuisance
(updates are not automatic). Issue [1] from 2015 looks stale.
htop tells me that it's consuming
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.zuli
You can't "do your job" without yet another way to get notified of CI job
status? I'm confused - did Jenkins remove all of its other forms of
notification? ;) Seriously though, I've never understood this desire to
have yet another communications "inbox" spammed by automated notifications
- and
Hi,
On Fri, May 18, 2018 at 12:16 AM, Sanne Grinovero
wrote:
> 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 bu
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
On 17 May 2018 at 20:32, Guillaume Smet 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
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.
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?
Well, can we at least wait for the Jenkins integration then?
If as you say "it won't take long", we won't have long to wait.
Frankly, I don't see why we would want to rush into this migration...
especially since Stride is not ready yet. We will be part of the first
users to migrate and I'm not su
On 17 May 2018 at 19:11, Guillaume Smet wrote:
> Hi Steve,
>
> Hum. I see at least 1/ and 3/ as being annoying. I personally like to have
> the JIRA/GitHub/Jenkins notifications on HipChat.
JIRA and GitHub integrations are available already.
I'm confident Jenkins won't take long:
- https://jira
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 instr
Hi Steve,
Hum. I see at least 1/ and 3/ as being annoying. I personally like to have
the JIRA/GitHub/Jenkins notifications on HipChat.
What would be the advantages of migrating so soon?
On Thu, May 17, 2018 at 8:03 PM, Steve Ebersole wrote:
> I got an email from Atlassian this morning about th
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.
29 matches
Mail list logo
