The Roadmap 2023 for community building
ringabout opened this issue · comments
Management
-
Add list of Nim-related infrastructure and responsible folks (nimeventer, nimforum, nimble, matrix-discord-bridge, Ircord, play.nim-lang backend repo - frontend repo, mail.nim-lang, twitter, discord, telegram, nimbot, Nim package directory etc.)
-
Add list of people that make up the community organization
https://forum.nim-lang.org/t/10006 -
Publish Nim moderation policies
Survey
- Nim community survey
Projects
- Maintain a list which contains contribution-friendly issues. Ideally, we should detail solutions of the issue. => https://github.com/orgs/nim-lang/projects/8
Packages
We intend to improve the workflow of packages.
-
Build a better package scanning workflow; implement the new package scanner, which intends to incrementally check newly added packages => nim-lang/packages#2532 drops CI time from 10+ minutes to a few seconds.
-
Put each nimble package in its own file => nim-lang/packages#777 but it needs to be careful with backward compatibility.
-
Post the errors in the form of comments on the PR.
-
Add a cron, which executes a full check for all packages.
-
Remove old, deprecated, unavailable packages (like ones that give 404)
nim-lang/packages#1269
nim-lang/packages#2075
nim-lang/packages#1807
Backporting
- Improve backporting workflow; adds a backporting bot to automatically backport simple commit. Ideally, it should add a "backporting" label to the specific pull request. If there are some merging conflicts, it needs a manual merging. The pull request with a "backporting" label remaining open is implicitly added to the backporting wishlist. The wishlist can use helps from the community.
Benchmark
- Build a benchmark monitoring workflow.
nim-lang/Nim#21566
Specification
-
Build a testable specification workflow => https://github.com/nim-lang/testspec
-
Document all the defines.
How can you help?
You could join us in the matrix space where we discuss how to build a community. We appreciate doable suggestions and helps, such as improving the workflow, implementing the roadmap, suggesting doable tasks, reviewing code from contributors. United we stand. We shall work together to make the community thrive.
The roadmap is subject to changes.
+ - [ ] Remove old, deprecated, unavailable packages (like ones that give 404)nim-lang/packages#1269
nim-lang/packages#2075
nim-lang/packages#1807
@haxscramper Nice catch! Added it to the list.
I have tagged all unavailable packages with "deleted". There are some smaller issues still remaining with documentation links but the major problems are resolved.
Assuming that the most recent issue doesn't count as part of it in your eyes (https://github.com/pietroppeter/community-management/issues/16), then the setting up of an infrastructure list has been finished, at least in an initial version.