Oroboros Core Architecture

Slack is our primary means of communicating, and by far has the most activity. There are a number of channels related to this project that you may find useful if you want to reach out to us.

• Open in Slack oroboros-core is our primary channel for this project. Bleeding edge commits, discussion about ongoing approach, resolution of tasks from our Trello board, and results from CI testing all push to this channel. If you want to see the live, up to date development process, this is the place to be.
• Open in Slack general is our channel dedicated to important updates about all Oroboros projects. All major updates to all projects will be seen in this channel, and it is also an appropriate place to post any uncategorized discussion or questions that are not better answered in another channel.
• Open in Slack rtfm is the place to get information about documentation, api docs, tutorials, or suggest edits for clarity to any of these.
• Open in Slack random is the place for general banter that is not explicitly related to project development.
• Open in Slack halp is the place to post when you have looked all over for your answer and are still hitting a wall. You should definitely check the docs first, and also post in rtfm if you need something that just isn't in there.
• Open in Slack social is where our clapbacks, mentions, tags, and public mentions from social media go. This channel only provides a record of public interaction across social media channels, but if you want to see it in one spot, this is the place.

Abuse and inflammatory activity in our Slack channel will be banned without notice. Keep it professional in public channels.

Our Bitbucket repo stores the unbuilt source for all of the code for this project.

It is not currently open to public comment, but members of the development team can message freely there. Our bug tracker will also be hosted there when it opens to the public after the 0.5.0 beta release.

After the public beta launch, there will be much more interaction available here for members outside the core development team.

Our Facebook page will provide most important updates directly in your news feed, and field general purpose discussion with the community.

Our Facebook feed will cover our important updates, related articles and posts of note, and any ongoing relevant happenings in the broader scope of the internet we believe should be made note of. Our Facebook feed is not a place for political commentary unless it is directly relevant to software and internet. Trolling of any sort will not be tolerated.

Most important updates will also be posted to Facebook.

Our Twitter page will provide concise important updates directly.

Our Twitter account will post concise updates about ongoing releases, and communicate openly with other technical professionals interested in interacting with us. Twitter will not be used for lengthy threads or commentary outside of the realm of software and related technology, and most updates will provide a link to a more verbose statement on the topic on another platform.

Most important updates will also be posted to Twitter.

You may contact us via our email for any other correspondance not covered by one of the prior channels.

Our email should be used for verbose communications or inquiries by members of the press or development community about our projects. Email is preferred for any communication that requires a lengthy context and is not time sensitive. This channel will also usually warrant the slowest response.

No business solicitations will be responded to unless we initially opened the channel with you first, and pre-empting our effort to do so will put you out of the running as a potential vendor in the event that we do need your services later.

All inquiries not covered above should be sent via email.