Knowledge management naturally emerges from good use of the tool. The core reason for this is that using Zulip in a way that feels natural creates an organized repository of knowledge as a side effect. Here’s what it looks like:Ĭoupled with a culture of using Zulip in an organized way, it’s difficult to overstate the impact it has on knowledge management. In combination with a great search feature, it makes knowledge and communication management so much easier. Zulip is great for privacy/security reasons, but it has also got a two-level conversation hierarchy, and that hierarchy is core to the UX. This is why Zulip is the most important tool at Monadical: People naturally want to communicate with one another verbally, and verbal communication is ephemeral. Company wikis get out of date fast people don’t update them unless they’re told to. In my experience, lots of companies have a problem with knowledge management (communication history included). You might want to read what's the main reason why it's the most important tool in our organization: We're all working remotely since 2016, so communication is key to our success. It's far better tool than Slack or any other competitors, and the most important tool we use in our 16 person (at the time of writing this post) software development agency. I only realized after writing this that the thread was from 2 months ago - I suppose I might as well post anyway even though I imagine only you will see it. for open bugs, and compare the "Closed" tab to get a feel for it. While one can always do better, I feel pretty good about the extent to which Zulip's issue tracker and bugs are managed, as we invest time into reliability and fixing bugs over new features, and certainly we rarely hear complaints from users that Zulip's server/webapp is "buggy". those stale bots that auto-close issues after 1 week of idleness). What you don't want to see in a popular project is large numbers of bugs that are reported and have gotten no attention from the maintainers.įundamentally, the only way a popular project with the scope of a team chat tool has a small number of open issues is if they're not accepting feature requests via the issue tracker or aggressively closing reported issues (E.g. I think having those issues in our tracker helps keep the project healthy, as they make it easy for our large contributor community to find adjacent work to do when working on something. Most of our open issues are feature requests/ideas, code cleanup ideas, bugs in our developer tooling, etc. Thanks for the kind words! I lead the Zulip project, and I think it's important to point out that every popular, healthy project has a large number of open issues in its issue tracker. > Zulip looks really cool! Seems to have a nice community, it's also got loads of open issues though. I didn't look heavily into RocketChat after we found Zulip seemed to fit the bill for us and we've all be overall happy with it. ![]() Mattermost did not impress us a few years ago but we did not re-review it when we switched to Zulip recently (last 4-5 months or so). I recommend trying it out as it's not too difficult to setup. It's not as polished as Slack but it is very functional. If anything the push notifications are perhaps too aggressive (you receive a push notification for a message you may have just read on the desktop app), but we prefer this over possibly missing important messages. Basically, if you want to maintain your privacy, you can use them for push notifications but opt-out of sending them the content of the messages.Īre the push messages reliable? YES! In our experience, more so than Slack. Do read their "Why this is necessary" and "Security and privacy" sections on that page for a thorough understanding of how it works and what you give up. It is very simple and straightforward to tie into their push servers. My small (<20 employees) company recently switched from free Slack to Zulip (self-hosted of course) and we absolutely love it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |