Skip to content

Information flow

Mick McGrath edited this page Jul 20, 2022 · 3 revisions

Conversation and information follows streams in order to make them accessible and understandable with minimal effort to the end user. This documents purpose is to clearly explain how information flows within Bitovi and out to our community.

Slack

Internal Slack

Internal Bitovi Slack only for Bitovi client based BitOps discussions.

Community Slack

The Bitovi Community Slack is for our day to day activities, such as;

  • PR reviews
  • questions about implementation, errors, etc
  • random thoughts
  • general help

Github

Discussions

Github discussions are for ideas that the community are interested in and want to pursue

Considerations when creating a discussion

  • create a discussion and then provide the link in the community slack to ask for feedback
  • possibly cross-link the post in community slack to the internal slack to help with awareness
  • when we finalize and idea, the results will be turned into one or more of the following

Wiki

The Github wiki should be tailored to provide development information / standards / patterns to developers, and should provide usage for standard users.

Confluence

Bitovi's Confluence will be used for internal tracking and discussions, however, consider that with confluence; "use less over time in favor of public discussion and awareness"

Clone this wiki locally