Add subproject maintainers to GOVERNANCE#156
Conversation
Signed-off-by: jonasrosland <jrosland@vmware.com>
|
love the idea, because it also outlines a path on how to contribute and grow inside the project harbor. |
|
LGTM |
Signed-off-by: Orlix <OrlinVasilev@users.noreply.github.com>
|
@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% |
|
@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. |
|
@yanji09 @wy65701436 please approve! |
|
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:
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. |
|
Before introducing new role, we probably need to clean up the subproject firstly, there are some of them are super inactive. |
|
closing this in favor of #290 |
|
#290 supersedes this one so let's close this one! |
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 jrosland@vmware.com