For opensource standards the instructions look pretty okay? Looks similar to instructions for projects like Mattermost, OTRS, etc.
concerns stemmed from the various mentions of everything being in /root which just seems like plain bad security practice.
however a cursory review of the codebase indicates that most of the services run as the zulip user and authentication uses certificates rather than passwords.
Re:Zulip Server 1.6 released
by aero31aero on Saturday June 10, 2017 @01:36PM
(#14528252)
It might not have been obvious, but for installation, you should use a dedicated machine or virtual machine.
That would mean your concerns regarding /root would be solved automatically.
What business priorities? Dropbox owned the IP and opensourced it. No one is selling it now. If you know Django, the instructions are pretty simple.
If you intend to deploy this for your organisation, who is going to deploy and maintain the service for you? Does your company / organisation emphasise the same level of support for internal tools as you do for external services for (paying) customers?
It's not a supported, paid, commercial product...if you want to use it, you can set it up yourself. If you want to have someone set it up and support it, you can hire someone, or use your own staff. It's no different than 99% of open source software out there.
It's not slack--they don't host it for you.
I don't understand your second question.
I suspect that this is common with corporate tools and services since business priorities usually dictate that resources are focused on revenue generating systems / services. Comes with it's own risks...
FTR: will see if I have some cycles to contribute improved release process documentation in the coming months.