-
Notifications
You must be signed in to change notification settings - Fork 5
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
Proposal for the total number of Notary Project Org maintainers #60
Comments
+1 |
1 similar comment
+1 |
+1 on the number 6 for active org maintainers |
+1 for additional maintainers. The intent was to have fairly equal representation across invested parties, where no one entity may overly control the direction. |
+1 |
+1 as per our meeting discussions. |
+1 to have a total of 6 Org maintainers for Notary Project. I think this number is possible to be changed based on the contributor and diversity growth in the future. |
Based on the voting results, a two-thirds supermajority of governance and organization maintainers have agreed to support a total of |
+1 on the 6 active org maintainers |
As a follow-up to the community meeting held on January 2, 2024, I created this issue to build a consensus on the total number of Org maintainers. According to the statistics, the current Org maintainers (
3
in total) have not been active in the past 3, 6, or 12 months. Therefore, it is necessary to elect more Org maintainers to ensure a sufficient majority for Notary Project governance and to fulfill the Org maintainer’s duty. The proposal is to have a total of6
Org maintainers for Notary Project.Tagging Org and sub-project maintainers for reviewing this issue. Please comment
+1
orLGTM
if you support the proposal. Other proposals are welcome, and we can discuss them in this issue and reach consensus.@NiazFK @justincormack @SteveLasker @cipherboy @OliverShang @FeynmanZhou @HuKeping @JeyJeyGao @duffney @gokarnm @mnm678 @priteshbandi @Two-Hearts @rgnote @iamsamirzon @toddysm @shizhMSFT @vaninrao10 @yizha1
The text was updated successfully, but these errors were encountered: