Our community uses several conventions to communicate with one another. Below you will find a list of those conventions and how they are used.
Our website is external facing and meant to communicate with potential community members, whether donors, partners, implementers, or individuals. Our website includes a blog where news or general announcements about the community happen as well as the latests specification release.
Our wiki is where we store our content:
Discourse is where our community engages and collaborates across time zones. Using a forum like this as an open mailing list helps to eliminate isolated conversations and share experiences with the larger community. Posts on Discourse are ideally;
Gitbook is best suited for content presented as a guide or a manual that can be downloaded as a PDF and made available in printed form. A Gitbook can be downloaded and printed out as a book. Content on Gitbook is highly stable. Examples include our architecture specification and getting started guide.
We generally do not release software as a community product. This is a work area. See: https://wiki.ohie.org/display/documents/OpenHIE+Contribution+Policy