Community | Disroot.org


Then, within a period of four weeks, we do our best to accomplish as much as we can. Once the time is up, we close the sprint, move unfinished tasks back on the backlog pile, and post a message via all the channels (Mastodon, blog post) abo...



Onion Details



Page Clicks: 0

First Seen: 04/26/2024

Last Indexed: 10/23/2024

Domain Index Total: 104



Onion Content



Community Transparency plays a big role here in Disroot . We want to be open about our plans, ideas and current progress. We also want to encourage contributions to the project from the Disroot community. Therefore, we've setup a bunch of tools to make it easy for anyone to follow Disroot 's development, and also take an active part in discussing, reporting issues and submitting ideas and fixes. How do we work? We use a project board where we put all the things needed to be done. We've chosen a "agile methodology" as a starting point and we're working in sprints, which are short periods of time. In our case, a sprint takes four weeks. In the beginning of the sprint, we sit together and decide which tasks have priority and should be added to the current task-board. Then, within a period of four weeks, we do our best to accomplish as much as we can. Once the time is up, we close the sprint, move unfinished tasks back on the backlog pile, and post a message via all the channels (Mastodon, blog post) about the recent changes and new developments on the Disroot platform. Additionally once a year we send out our Annual Report which is a summary of what has been done in the past year, what were the costs and incomes for the entire year and our estimated budget and plans for the following year. How can I see what is happening? The best way to see what are we currently busy with, what we've done so far and what we are planning for the future is to follow our git repositories. Disroot Project | Current progress | List of issues How can I help? There are many ways to become active and contribute to the Disroot project. Submit and track bugs It doesn't matter if you've been using Disroot for some time or if you've just joined, reporting bugs is something you can always do. So if you discover something that doesn't look quite right or doesn't function as it should, let us know by making an issue on the Disroot-Project repository . Submit features You can also use the Disroot-Project repository to let us know which new features you would like to see in the future. Disroot-Project Help solve other peoples issues If you're using Disroot for some time now, you're familiar with the platform or had to solve some issues before, then you can be of huge help to others who are struggling to find their way around all the features. It is also a great help for us if more Disrooters help answering questions and solving minor problems for others, meaning that the workload is better spread and replies can appear faster. Start watching our XMPP room to see how you can help if anyone need it. disroot@chat.disroot.org Help us with howto's We have already written and translated quite some guides and tutorials to help users learn how to use the services we provide, but there's still a long way to go to cover all of its aspects, for all possible devices and operating systems. We need more people to get involved in writing and translating howtos if we want to create a universal documentation that can be used by our users and those of other platforms that provide similar services and that are also, as much as possible, in their own languages. Disroot Howto Project howto@chat.disroot.org Donate money And last but not least, financial support is always needed, so don't be afraid throwing a briefcase full with dollars our way. And if that's too much, then remember that every penny counts and if you decide to "buy us coffee" on regular basis, it would be awesome. For more details, check here