backstage / backstage/community-plugins
🔧 Repository: Bitrise, Explore, Fossa, and SonarQube Plugin Ownership
- Dominant language
- TypeScript
- Stars
- 422
- Forks
- 697
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 286
Description
### 📜 Description
The @backstage/sda-se-reviewers group was listed as the owner of the Bitrise, Explore, Fossa, and SonarQube plugin when the Community Plugins repository was first created and underwent the initial plugin migration (see the commit [here](https://github.com/backstage/community-plugins/commit/3f98e0959956e79e296dea106c2ec1f0d0229195)).
This issue seeks to confirm whether or not this group wishes to continue ownership of these plugins. As discussed in today's Community Plugins SIG, the maintainers would be happy to assume ownership of the plugins if the current owners no longer have the capacity to maintain the plugins.
As members of the group, please let us know your thoughts @dschwank @iammnils @petergrau 🙂
### 👀 Have you spent some time to check if this bug has been raised before?
- [x] I checked and didn't find similar issue
### 🏢 Have you read the Code of Conduct?
- [x] I have read the [Code of Conduct](https://github.com/backstage/community-plugins/blob/main/CODE_OF_CONDUCT.md)
### Are you willing to submit PR?
Yes I am willing to submit a PR!
Contributor guide
Research direction
Review the referenced initial plugin migration commit and the current ownership entries for the Bitrise, Explore, Fossa, and SonarQube plugins. Confirm the existing group's decision in the issue discussion, then ensure the repository ownership records reflect the agreed maintainers.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100