We're trying to structure the discussions and progress tracking of the Allmaps project in a way we hope is open, clear and light-weight. While many of us keep lists with ideas and todo's, and communication is spread across email, chat and live discussions, the important stuff comes together here.

Here's how we use the Github tools:

• GitHub Projects contains one project with the medium term planning of large chunks of (commissioned) work. Work is listed as drafts or issues.
• GitHub Issues is a place where people can flag bug reports, and where (commissioned) work is tracked.
• GitHub Discussions is where we welcome feature requests and ideas for further development of Allmaps. Big, open questions are discuss for desirability and implementation. Small feature requests are reviewed and integrated in a pinned discussions that gather ideas for future development. This way we have an overview of matured ideas that could be taken up in the future. When work starts on a bunch of such ideas (e.g. because as part of a contract) an issue is created to track that work (linking back to the relevant discussions).
• GitHub Pull Requests represent the code development for specific issues.

Some things live outside of GitHub:

• As discussions (e.g. in Q&A) may crystallize to better onboarding, which lives on docs.allmaps.org

We'll try out this approach for now. It'll take some time to move over the main points from our own ideas and notes. And let's evaluate this in the future.