janus-idp / .github Goto Github PK

Write down governance rules for this community. Cover following topics:

This is a brain dump, feel free to extend.

• How to become a member:
  • Create and commit to maintaining a plugin - becomes code owner of that plugin
  • Asks for it and it's approved by project area maintainer to join a wider project area group
  • Is nominated by a maintainer
• Who is a maintainer
• Define project areas
• Contributor roles are managed through github groups
• Repositories have github groups serving as code owners per area
• Access is reviewed annually
• Member who is not active will lose merge/review permissions and will be recognized as a honorable/emerit member of the team (remove from group but left in org and added to a running doc of recognized members/authors)

What needs to be done?

Add generic github issue templates to the .github repository to serve as default templates for the organization.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update docker/build-push-action digest to 5cd11c3
• chore(deps): update docker/setup-buildx-action digest to 988b5a0
• chore(deps): update docker/setup-qemu-action digest to 49b3bc8
• chore(deps): update redhat-actions/podman-login digest to 4934294
• chore(deps): update actions/create-github-app-token action to v1.10.3
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

What needs to be done

Disable blank issues in favor of a blank issue template to help ensure all new issues have the status/triage label

To make planning easier, we want to ensure every issue is in the "janus-idp planning" project.

Right now, I can see two options for how this can be done.

1. create a GitHub action (in .github repo) that will be triggered periodically (nightly should be ok) that scans through all issues in all repos in this org that are not in the project (or that were created since the last run) and adds them to the project
2. github action that will be triggered on issue creation on each repo

benefit of 2) is that it will be quicker, but downside is that will be a separate action for each repo (workflows can be reused, so this will be defined in one place

benefit of 1) is that everything will be in one place but a bit slower (nightly)

Acceptance criteria:

• every new issue created in any repo in this org is automatically added to "janus-idp planning"

Governance #20 is merged now, so we should go and apply the changes in order to make us compliant.

Can you please help me fill in the teams with appropriate members? https://github.com/orgs/janus-idp/teams

Please remember: Maintainer teams have write access to their assigned repositories. If we need somebody to just triage/look through issues we don't need them to be maintainers.

Teams starting with [DEPRECATED] are the teams we had before, and should eventually go away. So we should make sure everybody who should own/maintain anything is captured by the "new" teams. I'll be also creating a bunch of Draft PRs creating/updating the CODEOWNERS to match the governance model. These should go in once we're sure the teams are staffed properly.

• New github teams populated and reviewed
• Old teams removed
• CODEOWNERS created in individual repositories.