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 to duplicate the conversation.
> But so would you in HipChat, or IRC, or Slack, or any chat software I've
> ever heard of.
>
> If you are talking about have a single conversation inside a single
> "stream"/"room"/"channel" with multiple topics (like "JPA 2.2, CDI
> integration, and also cache SPIs"), well... create a topic just for that
> ("JPA+CDI+Caches"). Or use the default topic (called "(no topic)").
>
> I don't think the primary reason for topics is archiving and finding older
> conversation. They help doing that, but their main purpose is to enable
> multiple concurrent conversation to run their course *in parallel, in a
> single "stream"/"room"/"channel"*. You can just focus on one topic and
> temporarily ignore all other topics. Which is nice, but not necessarily
> important in our case, since it's quite rare that we have multiple
> conversations going on simultaneously in a given room. Though one could
> argue that it's rare precisely because we don't have topics and
> understanding each other would be very difficult.There are often some parallel discussions on mailing list(s). The thing is that since Infinispan moved to Zulip the -dev list has become more of an announce-list, 95% of discussion moved to Zulip - just because it's faster to discuss it that way. Also if the discussion is not on a mailing list but couple of selected people, it's easier if that's just a topic on private stream and you can notify more people about that, keeping the history. (You can't add people to a strictly private conversation and let them see the history, though). Radim > > Yoann Rodière > Hibernate NoORM Team > yo...@hibernate.org > > > > On Mon, 30 Jul 2018 at 17:45, Steve Ebersole <st...@hibernate.org> 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. >> >> On Mon, Jul 30, 2018 at 9:27 AM Emmanuel Bernard <emman...@hibernate.org> >> wrote: >> >>> 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 topics? >>>> >>>> >>>> On Fri, Jul 27, 2018 at 9:43 AM Emmanuel Bernard < >> emman...@hibernate.org> >>>> wrote: >>>> >>>>> On Fri 18-07-27 14:38, Guillaume Smet wrote: >>>>>> On Fri, Jul 27, 2018 at 2:31 PM Emmanuel Bernard < >>> emman...@hibernate.org> >>>>>> 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 always miss in tools like Slack. >>>>>>> >>>>>>> Granted Zulip topics are a bit offsetting for the first 5 posts. >> And >>> yes >>>>>>> their mobile client is really bad. But the desktop client is really >>>>>>> nice. >>>>>>> >>>>>> I'm not really excited about topics. We might need a topic once a >>> month, >>>>>> maybe less, when we start a big discussion on a subject (and even so, >>>>>> there's usually only one discussion in parallel). >>>>> If you want to accept the Hibernate community in this and it catches >> up, >>>>> then you will have parallel discussions. Join the Infinispan one for >> an >>>>> example. >>>>> >>>>> Also even if one conversation happens at a given time, it is a very >> good >>>>> organiser for someone that is catching up on subject after the actual >>>>> conversation happened. >>>>> >>>>>> The rest of the time, we just share in the channel. >>>>>> >>>>>> If they were optional, that would do but they are not and you always >>> need >>>>> 2 >>>>>> clicks to share (e.g. go to the right stream, then either choose a >>> topic >>>>> or >>>>>> create new topic), whereas you're at most one click away on HipChat. >>> For >>>>>> our usage I find it a bit suboptimal. >>>>>> >>>>>> I use the HipChat mobile client from time to time, not sure how bad >>>>> Zulip's >>>>>> is. Can you at least follow the streams and post messages? >>>>>> >>>>>> Anyway, it's more a -0 than a -1 for Zulip. >>>>>> >>>>>> Never used Slack. >>>>>> >>>>>> -- >>>>>> Guillaume >>>>> _______________________________________________ >>>>> 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 -- Radim Vansa <rva...@redhat.com> JBoss Performance Team _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
