InnerSource Contributions labeler
- 主要言語
- 言語のデータがありません
- スター
- 749
- フォーク
- 72
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
### New Action request
## Description
It would be helpful to be able to [label contributions to a project](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels) that come from outside the owning team. This is beneficial for being able to recognize InnerSource practices and measure statistics related to that. This action could be combined with the issue-metrics action to get those statistics for issues/and PRs labeled as InnerSource. InnerSource in this case would be defined as contributions from a non-owner team within an organization. ie. When a feature team contributes to the observability tools on which they depend but do not own as an area of responsibility.
Additionally it may be helpful to "label" the repository with a [Repository Topic](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics) so that it can be identified as a repository that practices InnerSource.
One complication that would need to be overcome here is the method by which a contribution is determined to be from a "non-owner" team. The tool could rely on several places to get ownership information:
- Interface with [Backstage API](https://backstage.io/docs/features/software-catalog/software-catalog-api/) assuming that there is a Backstage instance that has a complete catalog of repos with ownership information
- Codeowners file (If someone or a group they belong to is in the codeowners file then they could be considered an owner)
- An org chart interface (API) (such as workday, etc.)
- Other ideas? Open to thoughts here...
コントリビューションガイド
調査の方向性
まず GitHub ラベルとリポジトリトピックのドキュメントを確認し、その後、提案されている ownership の情報源である Backstage API、CODEOWNERS、Workday のような組織図 API を比較します。完了したコントリビューションでは、owner 以外によるコントリビューションをどのように特定するか、どの項目に InnerSource ラベルを付けるか、リポジトリトピックを含めるかどうかを定義する必要があります。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- github
- 領域
- tooling
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 25/100