On 2018-05-29 12:39, Ed Leafe wrote:
On May 29, 2018, at 11:23 AM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
The Corporate gig has tasked me with looking into a way for several similar organizations to communicate and share with each other things are the related to the success of all of them; a collaborative sharing of ideas, best practices, information, etc. to help the (healthcare) product as a whole.
I have advised against a listserve as I don't feel that's friendly enough for sharing materials/files/stories. I'm believing a forum would be best.
Slack! It's the answer to everything!!
Seriously, though, there are a lot of things to consider. Is the team co-located? Spread across different offices? Different time zones?
Since you mention several organizations, I will assume that they are geographically disperse; in such cases, some form of asynchronous communication is best. Otherwise, people will miss out on things because they are in a different time zone. Email is great for async communication, but hard to use as a reference document. Wikis are accessible, but suffer from bit rot. I prefer to use GitHub, assuming that people have ability to handle the basics of git. You can write docs using ReStructured Text (.rst), and view them on GitHub in their rendered form. For an example, see the style guide for the OpenStack project I work on (Nova): https://github.com/openstack/nova/blob/master/HACKING.rst. After you see that, click the 'Raw' button on the top right to see the original .rst file.
One of the nice things is that it is easy to update the doc using pull requests. These can be reviewed and merged as needed. This allows teams to collaborate easily, and helps ensure that a consistent style is used for all docs. You might also consider GitHub Pages (https://pages.github.com/) for a more website-y look.
-- Ed Leafe
Thanks, Ed. I'll review that. The end-users are NOT tech-savvy folks, most likely, so it'll have to be a super-user-friendly UI.