ROOST and the community communicate and interact across multiple platforms. These are the officially-recognized platforms and spaces that we currently use, as well as how they're used.
ROOST open source projects are hosted on the @roostorg organization on GitHub. Each GitHub repository is where you'll find the project's source code, issue tracking and project management, pull requests and code review, and related discussions. If the project contains documentation, it can be found directly in the code repo and hosted on the web at the repo's listed website.
ROOST-wide discussions can also be found on the ROOST org itself.
We consider GitHub to be the public record of ROOST projects; while conversations can occur and decisions may be made elsewhere, outcomes must always be documented on the relevant GitHub repository's issue tracker, discussions, or pull request thread. If it's not on GitHub, it didn't happen.
We mirror read-only copies of our repositories on the following code forges:
- @roostorg on Codeberg
- @roostorg on GitLab
- @roost.tools on Tangled
These mirrors do not contain copies of issues, pull/merge requests, or discussions, but do have a copy of all git branches and their commits.
We operate the ROOST Discord server for real-time communication and collaboration with ROOST staff and the community. When joining, you can select your specific areas of interest to tailor your experience. You can also directly join these project-specific channels for collaboration with contributors and adopters:
Be sure to introduce yourself in #welcome and ask questions or chat about anything related to ROOST or online safety in #general!
We treat Discord as our virtual office; while important things may be discussed in passing, chat is not a replacement for publicly-accessible documentation. As such, any decisions or important outcomes must be publicly documented on GitHub to ensure they're discoverable and able to be referenced in the future. Also keep in mind that not everyone invested in a project may be online on Discord at any given time due to timezones and outside commitments; when in doubt, feel free to chat through something with whoever is online, but then file an issue or provide a summary comment on GitHub as a record of the conversation.
We maintain a social media presence on these platforms:
- @roost.tools on Bluesky/atproto
- @roost@hachyderm.io on Mastodon/the fediverse
- company/roost-tools on LinkedIn
- @roostorg on YouTube
Follow us there, boost our posts, and share with your friends!