Skip to content

New repo doc: license and more role info #3

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.

Sign up for GitHub

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

Merged
rposts merged 1 commit into from
Feb 5, 2026
Merged

New repo doc: license and more role info #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 10 additions & 7 deletions adding-a-repository.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,19 +1,22 @@
An administrator will create the repository once the TSC approves it. All
repositories require DCO sign-off, which is enabled organization-wide.

1. Invite the owner of the repository to the linuxonzapps organization, under
1. Create the repository with an Apache 2.0 license.

2. Invite the owner of the repository to the linuxonzapps organization, under
"People"

2. Once they accept the invitation, go to "Collaborators and Teams" to add the
new owner to the repository in the "Maintain" capacity
3. Once they accept the invitation, go to the repository Settings and
"Collaborators and Teams" to add the new owner to the repository in the
"Maintain" or "Write" capacity, as appropriate

3. Optional: CODEOWNERS
4. Optional: CODEOWNERS

- If you wish to have automatic reviewers set up, a CODEOWNERS file needs to be
created in the repository as well, see [CODEOWNERS](CODEOWNERS) for an
example.

- The team or users who are added as automatic reviewers will also need Write
access to the repository, which is documented here: [Managing teams and people
with access to your
- The team or users who are added as automatic reviewers in the CODEOWNERS
will also need Write access to the repository, which is documented here:
[Managing teams and people with access to your
repository](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)