Skip to content
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

Jump to bottom

New Org for Tekton Verified Catalogs #889

Closed
QuanZhang-William opened this issue Nov 30, 2022 · 11 comments
Closed

New Org for Tekton Verified Catalogs #889

QuanZhang-William opened this issue Nov 30, 2022 · 11 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@QuanZhang-William
Copy link
Member

QuanZhang-William commented Nov 30, 2022 •
edited
Loading

Proposal

Today, we use a centralized repo to host all the Tekton catalogs.

In TEP-0115, we proposed to decentralize the current Tekton catalog repo to separate catalogs. Each catalog is a new repository and can be hosted in the owner's own GitHub organization.

In TEP-0079, we proposed support tiers for the catalogs and selected 5 resources to be supported at the Verified tier, where the 5 resources are owned and maintained by the @tektoncd/catalog-maintainers. We also have reserved the tektoncd-catalog Github Org to host the Verified catalogs.

We should set up the repositories in the tektoncd-catalog Github Org following the tektoncd project requirements.

Specifically:

  1. Set up CI for the repos using Tekton/Prow (this is to be designed in Automated Testing & Dogfooding)
  2. Set up Peribolos for org administration
  3. Migrate the selected resources to the new catalogs as designed in TEP-0115 and TEP-0079
  4. Update the documentation in the centralized catalog repo
  5. Archive the centralized catalog repo after 9 months

Tracking Issues:

The CI setup for the new organization may require @tektoncd/governing-board member's help
(Please also suggest other work items that I missed in the migration 😄 )
@QuanZhang-William QuanZhang-William added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 30, 2022
@dibyom
Copy link
Member

dibyom commented Nov 30, 2022

Do Prow/Peribolos support multiple GH organizations from the same installation? If so, that might simplify the setup quite a bit

@vdemeester
Copy link
Member

Do Prow/Peribolos support multiple GH organizations from the same installation? If so, that might simplify the setup quite a bit

cc @abayer as I don't remember 🙃

@afrittoli
Copy link
Member

The yaml structure seems to suggest it does:

community/org/org.yaml

Line 1 in 97998b9

orgs:

but of course we would need to use a token who has access to both orgs - which shouldn't be an issue.

@dibyom
Copy link
Member

dibyom commented Dec 1, 2022

Does anyone know how to update the token (is this for tekton-robot as well?) for both orgs?
@QuanZhang-William or I can open a PR to update Prow!

QuanZhang-William added a commit to QuanZhang-William/community that referenced this issue Dec 14, 2022
@QuanZhang-William
[TEP-0115] Mark TEP-0115 as implemented
2ab88fd 
This commit updates TEP-0115 to `Implemented` status.

The Tekton Hub -> Artifact Hub Migration is tracked in: tektoncd/hub#667
The Verified Catalogs Migration is scoped in [TEP-0079][tep-0079] and is tracked in: tektoncd#889

[tep-0079][https://github.com/tektoncd/community/blob/main/teps/0079-tekton-catalog-support-tiers.md]
QuanZhang-William added a commit to QuanZhang-William/community that referenced this issue Dec 14, 2022
@QuanZhang-William
[TEP-0115] Mark TEP-0115 as implemented
248ec11 
This commit updates TEP-0115 to `Implemented` status.

The Tekton Hub -> Artifact Hub Migration is tracked in: tektoncd/hub#667
The Verified Catalogs Migration is scoped in [TEP-0079][tep-0079] and is tracked in: tektoncd#889

[tep-0079]: https://github.com/tektoncd/community/blob/main/teps/0079-tekton-catalog-support-tiers.md
@QuanZhang-William QuanZhang-William mentioned this issue Dec 14, 2022
Merged
QuanZhang-William added a commit to QuanZhang-William/community that referenced this issue Dec 14, 2022
@QuanZhang-William
[TEP-0115] Mark TEP-0115 as implemented
0d6a1a9 
This commit updates TEP-0115 to `Implemented` status.

The Tekton Hub -> Artifact Hub Migration is tracked in: tektoncd/hub#667
The Verified Catalogs Migration is scoped in [TEP-0079][tep-0079] and is tracked in: tektoncd#889

[tep-0079]: https://github.com/tektoncd/community/blob/main/teps/0079-tekton-catalog-support-tiers.md
tekton-robot pushed a commit that referenced this issue Dec 15, 2022
@QuanZhang-William @tekton-robot
[TEP-0115] Mark TEP-0115 as implemented
1bb4f01 
This commit updates TEP-0115 to `Implemented` status.

The Tekton Hub -> Artifact Hub Migration is tracked in: tektoncd/hub#667
The Verified Catalogs Migration is scoped in [TEP-0079][tep-0079] and is tracked in: #889

[tep-0079]: https://github.com/tektoncd/community/blob/main/teps/0079-tekton-catalog-support-tiers.md
@QuanZhang-William QuanZhang-William mentioned this issue Jan 10, 2023
Open
10 tasks
QuanZhang-William added a commit to QuanZhang-William/community that referenced this issue Jan 13, 2023
@QuanZhang-William
Add tektoncd-catalog org to org.yaml
03a0e77 
Part of [tektoncd#889][tektoncd#889]. This commit add the `tektoncd-catalog` to the `org.yaml` file so that the org, org member, team and team members can be automatically managed by Peribolos (which lets `tektoncd-catalog` org reaches the same level of automation as `tektoncd`).

The role assignment can be only done for the members that have already joined the new org. The role is assigned to each individual based on his/her current role in `tektoncd/catalog` repo.

This commit only adds teams for the [golang][golang] repo as the migration of the repo is under going. More teams will be added in later PRs once we start the migration for other Verified Catalogs.

[golang]: https://github.com/tektoncd-catalog/golang
[tektoncd#889]: tektoncd#889
QuanZhang-William added a commit to QuanZhang-William/community that referenced this issue Jan 13, 2023
@QuanZhang-William
Add tektoncd-catalog org to org.yaml
d4be1a2 
Part of [tektoncd#889][tektoncd#889]. This commit add the `tektoncd-catalog` to the `org.yaml` file so that the org, org member, team and team members can be automatically managed by Peribolos (which lets `tektoncd-catalog` org reaches the same level of automation as `tektoncd`).

The role assignment can be only done for the members that have already joined the new org. The role is assigned to each individual based on his/her current role in `tektoncd/catalog` repo.

This commit only adds teams for the [golang][golang] repo as the migration of the repo is under going. More teams will be added in later PRs once we start the migration for other Verified Catalogs.

[golang]: https://github.com/tektoncd-catalog/golang
[tektoncd#889]: tektoncd#889
@QuanZhang-William QuanZhang-William mentioned this issue Jan 16, 2023
Closed
5 tasks
QuanZhang-William added a commit to QuanZhang-William/community that referenced this issue Jan 19, 2023
@QuanZhang-William
Add tektoncd-catalog org to org.yaml
e633d66 
Part of [tektoncd#889][tektoncd#889]. This commit add the `tektoncd-catalog` to the `org.yaml` file so that the org, org member, team and team members can be automatically managed by Peribolos (which lets `tektoncd-catalog` org reaches the same level of automation as `tektoncd`).

The role assignment can be only done for the members that have already joined the new org. The role is assigned to each individual based on his/her current role in `tektoncd/catalog` repo.

This commit only adds teams for the [golang][golang] repo as the migration of the repo is under going. More teams will be added in later PRs once we start the migration for other Verified Catalogs.

[golang]: https://github.com/tektoncd-catalog/golang
[tektoncd#889]: tektoncd#889
QuanZhang-William added a commit to QuanZhang-William/community that referenced this issue Jan 19, 2023
@QuanZhang-William
Add tektoncd-catalog org to org.yaml
1d9bcae 
Part of [tektoncd#889][tektoncd#889]. This commit add the `tektoncd-catalog` to the `org.yaml` file so that the org, org member, team and team members can be automatically managed by Peribolos (which lets `tektoncd-catalog` org reaches the same level of automation as `tektoncd`).

The role assignment can be only done for the members that have already joined the new org. The role is assigned to each individual based on his/her current role in `tektoncd/catalog` repo.

This commit only adds teams for the [golang][golang] repo as the migration of the repo is under going. More teams will be added in later PRs once we start the migration for other Verified Catalogs.

[golang]: https://github.com/tektoncd-catalog/golang
[tektoncd#889]: tektoncd#889
QuanZhang-William added a commit to QuanZhang-William/community that referenced this issue Jan 19, 2023
@QuanZhang-William
Add tektoncd-catalog org to org.yaml
459fbc8 
Part of [tektoncd#889][tektoncd#889]. This commit add the `tektoncd-catalog` to the `org.yaml` file so that the org, org member, team and team members can be automatically managed by Peribolos (which lets `tektoncd-catalog` org reaches the same level of automation as `tektoncd`).

The role assignment can be only done for the members that have already joined the new org. The role is assigned to each individual based on his/her current role in `tektoncd/catalog` repo.

This commit only adds teams for the [golang][golang] repo as the migration of the repo is under going. More teams will be added in later PRs once we start the migration for other Verified Catalogs.

[golang]: https://github.com/tektoncd-catalog/golang
[tektoncd#889]: tektoncd#889
tekton-robot pushed a commit that referenced this issue Jan 20, 2023
@QuanZhang-William @tekton-robot
Add tektoncd-catalog org to org.yaml
63c1f72 
Part of [#889][#889]. This commit add the `tektoncd-catalog` to the `org.yaml` file so that the org, org member, team and team members can be automatically managed by Peribolos (which lets `tektoncd-catalog` org reaches the same level of automation as `tektoncd`).

The role assignment can be only done for the members that have already joined the new org. The role is assigned to each individual based on his/her current role in `tektoncd/catalog` repo.

This commit only adds teams for the [golang][golang] repo as the migration of the repo is under going. More teams will be added in later PRs once we start the migration for other Verified Catalogs.

[golang]: https://github.com/tektoncd-catalog/golang
[#889]: #889
@tekton-robot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 1, 2023
@ywluogg
Copy link
Contributor

ywluogg commented Mar 2, 2023

/remove-lifecycle stale

@tekton-robot tekton-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 2, 2023
@tekton-robot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 31, 2023
@tekton-robot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 30, 2023
@ywluogg
Copy link
Contributor

ywluogg commented Jul 4, 2023

/remove-lifecycle stale

@tekton-robot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Contributor

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@github-project-automation github-project-automation bot moved this from Todo to Done in Tekton Community Roadmap Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
Tekton Community Roadmap
Status: Done
Milestone
No milestone
Development

No branches or pull requests
6 participants
@vdemeester @afrittoli @dibyom @QuanZhang-William @tekton-robot @ywluogg