Closed fisherxu closed 2 months ago
/assign @kubeedge/maintainers @kubeedge/tsc
/hold
/lgtm
/lgtm
/lgtm Thanks
/lgtm
/lgtm
/lgtm
lgtm from maintainer perspective, thanks
lgtm from maintainer perspective, thanks for clarification. 😄
We've get 6/7 pass from TSC members and @fisherxu as athor, and +1 from @fujitatomoya @WillardHu and @Shelley-BaoYue as SIG leadership and maintainers. This PR is ready to merge.
/hold cancel /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: kevin-wangzefeng
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Looks like you've eliminated "Core maintainers" as a role, and it's now just Maintainers?
Yes :) After discussions with the community, some responsibilities of the previous KubeEdge Maintainers have changed. Community governance related duties have shifted to the TSC, and development-related responsibilities have moved to SIGs, Approvers, etc.
The responsible for coordinating with CNCF on tasks such as voting, surveys, etc is retained, so we will still retain the Maintainer role and Maintainer file as descripted.
Nice! Believe me, you'll be glad in a few months that you cleaned that up.
Definitely! The responsibilities of the roles are clearer. This is a huge step forward in community governance. Thank you for your guidance and help! @jberkus
As discussed, the governance of the KubeEdge community has now shifted towards roles TSC, SIG chair/tech lead, Approver, Reviewer, etc. However, the community still wants to retain the role of Maintainer and Maintainer file. The mentioned roles of TSC, SIG chair/tech lead, Approver, Reviewer can all apply to be Maintainers in the community.
Maintainers will be listed in the official CNCF maintainer list and mailing list, responsible for coordinating with CNCF on tasks such as voting, surveys, etc.
ref: https://github.com/kubeedge/community/issues/203