51–60 of 126 posts
I mistakenly assumed there wasn't a paid offering. So it's becoming clear that the only revenue model going forward is open core model.
Earlier quoted context omitted.
Zulip has a rebase-based development workflow and doesn't use merge commits because in my experience, it produces a much more readable commit history (which is really important for understanding historical changes). We've been very happy with this approach. Some relevant reading on our version control approach for those who might be interested: * https://zulip.readthedocs.io/en/latest/git/overview.html * https://zuli…
Doesn't using rebase generally mean you have to rebase on top of master and thus with your local branch you may need to git push --force ?
For this reason, most major open source projects use that part of the workflow (asking their contributors to rebase their PRs on top of master and never use `git pull --merge`), even if they plan to merge the commits into master via a merge commit.
(The Git documentation is very aggressive in discouraging force-pushing of commits, but that advice is intended for a public repository, like the main zulip.git repository, that others might pull from. Obviously, we don't force-push to zulip.git, but if you're using Git right, you should be force-pushing to your fork when you fix a typo in one of your commits.)
We looked at it briefly, but the number of components make it look more of a tech demo than a product meant to be installed on-prem. Redis, Postgres, Rabbitmq and Memcached just to run a chat?
> more of a tech demo than a product It is neither a tech demo nor a product, it is a mature open source project. In fact, in my mind tech demos tend towards having fewer mature components. > Redis, Postgres, Rabbitmq and Memcached just to run a chat That set of dependencies seems quite normal to me for a mature project. Mastodon (the most popular open-source-twitterish-thing) has a similar set of dependencies, and i…
Whaaat!? I who always thought irc was the on-prem Slack alternative. Its a pretty cool thing that recently got created (around 1988). Try it out! Will blow you mind straight out of the water tbh. There's even some public chat rooms you can hang around in.
I hang out on freenode every day. But I have higher expectations of chat in 2018 when it comes to what I would choose for an actual organization. So does everyone else.
IRC isn't blowing anyone's mind. Especially that first time they try to reply to someone but their message is never received because the other person closed their laptop.
We looked at it briefly, but the number of components make it look more of a tech demo than a product meant to be installed on-prem. Redis, Postgres, Rabbitmq and Memcached just to run a chat?
https://zulip.readthedocs.io/en/latest/production/install.ht...
> just to run a chat
Don't overlook the fact that this is a scalable and stable solution used by many companies with thousands of users for each instance. I would have my doubts about the project if it wouldn't use those components.
We looked at it briefly, but the number of components make it look more of a tech demo than a product meant to be installed on-prem. Redis, Postgres, Rabbitmq and Memcached just to run a chat?
Earlier quoted context omitted.
zulip ends up being a bit like e-mail where you can add people to threads and they immediately have the history. I've used mattermost, not slack, but that basic model fixes a lot of issues I have with mattermost.
A more specific slack channel (and I assume mattermost channel) is a thread that you can add people to any time and they will immediately have history. Or put in the inverse, a Zulip thread that is too general is a channel with information overload and becomes useless. Does the nesting have intrinsic value over simply more top level channels?
The idea is you subscribe to a channel, but then any post to the channel needs to also have some sort of logical subject.
How does it compare to mattermost?
With the addition that Mattermost is open core, not fully open source.
We've been using Zulip for just over a week in xi-editor and related projects, and I'm thrilled. Huge improvement over the pastiche of IRC and Reddit we were using before.
A bunch of other cool open source projects use it, including Python Core, parts of the Rust community, MariaDB, Coala, the Lean Theorem Prover, the HL7 standard, and many more.