51–60 of 134 posts
Aside from that, I think it's biggest potential killer feature is tight issue thread integration: https://github.com/zulip/zulip/issues/12340
Very exciting project
I am looking for something to replace XMPP with our team; I wonder if Zulip could be the one. I do like the thread idea. Does anyone know if there is a CLI client, and if E2E encryption is possible with Zulip? It does not seem like these are built-in, but maybe someone built these as add-ons somewhere. I love XMPP, and OMEMO, but Profanity, and Conversations have some weird quirks when used together that we would rat…
https://element.io/ ? Like XMPP it supports federation, but Matrix is JSON instead of XML.
(Element, formerly Riot, is the client by the company founded by the founders of Matrix.)
I am looking for something to replace XMPP with our team; I wonder if Zulip could be the one. I do like the thread idea. Does anyone know if there is a CLI client, and if E2E encryption is possible with Zulip? It does not seem like these are built-in, but maybe someone built these as add-ons somewhere. I love XMPP, and OMEMO, but Profanity, and Conversations have some weird quirks when used together that we would rat…
https://element.io/ ? Like XMPP it supports federation, but Matrix is JSON instead of XML.
Altough, it seems there is a plugin for WeeChat with E2E encryption[1]. Gotta take a look.
https://monadical.com/posts/how-to-make-remote-work-part-two...
Apart from a user, I am also a contributor to the Zulip project, for the last ~7 months. The community is very helpful and for getting started with open source development, I can't recommend a better place. You get really high quality code reviews, get to participate in meaningful discussions on features and the development goals of the project, and developers constantly share lots of knowledge in streams like #learn…
One of our goals as a project is to have a "teaching-quality" codebase, so this is no surprise. I think this is incredibly important and something every community open source project should strive for.
An analogy I like to use is to think about the experience of contributing to your open source project as a product, so you should:
* Do usability studies where you help a group of people try to get started with your product (I used to do this all the time at events like Python conference sprints pre-pandemic). The first few we did were eye-opening as nobody got anywhere without a lot of handholding, and I suspect that's common.
* Make the development environment tooling Just Work and have a good support experience.
* Write good documentation that thoughtfully explains the ideas one needs to understand to participate on your project. My strategy for this was to avoid explaining how things work to a contributor, and instead meet the need by spending a couple hours writing something like https://zulip.readthedocs.io/en/latest/subsystems/sending-me... and send it to them. That way, even if that contributor bounces (as the vast majority of new people who show up to any volunteer organization do), I still used my time well.
I'm planning a series of blog posts on building a successful open source community, since we've spent a lot of time thinking about how to make contributing to Zulip a great experience, and some ideas are subtle (E.g. the secret to being able to give high quality code reviews is equipping new contributors with the tooling and documentation to help them avoid problems before a reviewer even looks at it!), and I regret not having spent more time sharing that thinking.
I love the idea of this, but I’m trying to move my team away from synchronous communication. That tends to put us back in email, though that has its own problems. What is the asynchronous version of zulip? Forums?
The asynchronous version of Zulip is Zulip. :-) A thing I really like about how Zulip works is that a conversation can happen asynchronously just like email, as well as synchronously. And the same conversation can shift smoothly from one to the other and back. I work on Zulip, and we basically don't use email at all - it's all either in Zulip or on a GitHub thread. (And the interesting discussions, I increasingly try…
Zulip is great for async communication because it surfaces unread messages in an easy to skim and non-overwhelming way.
After a day of not checking Zulip, the user can then open the chat and (before seeing any actual messages) see:
1) which streams have had activity.
2) which threads/topics within those streams have had activity.
then choose which topics to read in a "relevant to me, not relevant to me" quick skim.
Having the topics within streams also allows those topic discussions to persist over time without being lost in the deluge of other messages.
There might be thousands of other chat messages between when I ask a question in #frontend > supercool.js but a teammate will skim later, see
#frontend > supercool.js [1]
and think "hey I know about supercool.js, what's up?" then respond.
I can also search to see if there's already a supercool.js topic thread and catch up on what we've discussed in the past.
I would love to use this, but I don't manage any communities that aren't already married to either Discord or Slack.
Part of the reason is that Zulip's topics make it a lot easier for a part-time participant to use their limited time well (E.g. skimming or reading the conversations in most relevant to them in batch a few times a week). The Slack/Discord/IRC/etc. data model limits how effectively one can participate and benefit from a high-traffic organization without constantly watching it (and being in the organization's dominant time zone!).
More on the inclusivity issues with synchronous chat here:
I absolutely love Zulip but I’m afraid the design keeps folks from joining.
There was a recommendation for it to update their design to be more like Discord new light theme [1] or Twist [2].
Twist is the more fair comparable since they are both Thread based (like email subject line) it’s just that Twist isn’t open source.
[1] https://miro.medium.com/max/4050/1*iwfLW4rnn6U-mlUQpmBAfg.pn...
[2] https://get.twist.help/hc/article_attachments/115005750965/i...
Apart from a user, I am also a contributor to the Zulip project, for the last ~7 months. The community is very helpful and for getting started with open source development, I can't recommend a better place. You get really high quality code reviews, get to participate in meaningful discussions on features and the development goals of the project, and developers constantly share lots of knowledge in streams like #learn…
That probably explains the healthy number of active developers for this project:
Based on my simple analytics that looks at the time between a contributors first and last commit, I'm getting 50 active contributors, which matches up with many of the other popular open source projects I've indexed.
Threads are one major reason I like Zulip over Slack, but speed is another. I usually have two different instances open on my browser with no problems, and one of them has dozens of conversations going on at once. Zulip is also one of the only apps I put on my iPhone, and it's straightforward and unobtrusive. For some reason when I use Slack, the keys feel mushy. I think they're doing so much stuff in the background…
You may not even need the app. Zulip on Android Firefox is a better experience for me than the app, personally. (Tho the web version was, oddly, severely laggy in mobile Chrome the one time I tried it, some time ago...)
