-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📣 Calling All Contributors: Let’s form a dedicated maintainer team! #14
Comments
@janhalen Are we talking about the os2forms_docs repo only ? :-) |
The scope for this issue is only the docs repo yes, but the steering or coordination committees can decide that a similar approach should be set in motion for more or even all repos. That would have to be broken down into other issues in the relevant repos... |
Lets start with this one. Repos that are "important" are pinned in the top of the gitbub account. And should be the ones to look at. :-) |
@skifter: Ok understood.. And the rest are due to be archived or consolidated/moved into other repos or organisations then? Or how do you view their state? https://github.com/orgs/OS2Forms/repositories?q=sort%3Aupdated-asc |
Proposal for allocation of ressources for a dedicated team for repository maintenance
This repository seems to be without a clear agreement on who acts as the maintainer team. I have observed stale PRs since 2021 and a pretty low activity rate.
To revitalize the repo, resources should be allocated to participate in and automate standard workflows like PR handling, issue triaging, and docs-as-code flows for documentation.
@Tgjerulff: Could this concern be raised with the steering and coordination committees?
@skifter, @lilosti: Could you please indicate if you are interested in submitting a bid for this task?
By investing up front in automation via GitHub Actions, the ongoing task is not a huge undertaking and the maintenance can be streamlined, enhance quality of docs and automation, thus boosting public community engagement.
TL;DR: The project needs allocated resources for setup and ongoing oversight. Any takers? 😃
The text was updated successfully, but these errors were encountered: