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.

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

Add subproject maintainers to GOVERNANCE #156

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

jonasrosland
Copy link
Contributor

This PR will add a section regarding subproject maintainers in Harbor's governance documentation.
The reason for this is to ensure contributors within the project can receive elevated privileges and ownership of parts of the project.

Would love to see your thoughts on this, so please discuss.

As outlined in the governance doc, this change would require a supermajority agreement by all maintainers.

Signed-off-by: jonasrosland [email protected]

@Vad1mo
Copy link
Member

Vad1mo commented Mar 8, 2021

love the idea, because it also outlines a path on how to contribute and grow inside the project harbor.
Would definitely try to incorporate some harbor related project under the harbor umbrella.

@hainingzhang
Copy link
Contributor

LGTM

@OrlinVasilev OrlinVasilev requested a review from a team as a code owner December 12, 2022 14:14
Copy link
Member

@Vad1mo Vad1mo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Like it

@OrlinVasilev
Copy link
Member

@Vad1mo @wy65701436 @stonezdj can we can get this in it's kinda suuuuper old and with the new active sub-projects we need it 100%

@OrlinVasilev OrlinVasilev requested a review from a team December 14, 2022 07:56
Copy link
Member

@OrlinVasilev OrlinVasilev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@Vad1mo
Copy link
Member

Vad1mo commented May 28, 2024

@goharbor/all-maintainers can we come to an agreement here? IMO it would make much sense to delegate responsibility to subproject maintainers, we have now more subprojects than when this was created. There are also more coming.

@OrlinVasilev
Copy link
Member

@yanji09 @wy65701436 please approve!

@wy65701436
Copy link
Contributor

Regarding the subproject of Harbor, I believe it is not just a matter of defining roles. We should provide a comprehensive definition of a subproject, which should include:

  1. What is a subproject of Harbor? What criteria should be considered whether a project is to be accepted as a subproject? and How?
  2. How do we measure the quality and release standards of a subproject?
  3. What is the withdrawal mechanism for a subproject? For instance, in the case of Harbor Operator, how do we assess the contribution of a maintainer if the subproject is decided to be deprecated?

Introducing a new role could be beneficial for the community, but we need to establish a clear process for managing subprojects, which we currently lack.

@wy65701436
Copy link
Contributor

Before introducing new role, we probably need to clean up the subproject firstly, there are some of them are super inactive.

Copy link
Contributor

@wy65701436 wy65701436 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/hold for discussion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants