| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Signed-off-by: Doug Davis <dug@microsoft.com>
|
Hi Doug, I am the TOC sponsor for this project. Let's have a meeting to sync up on proceeding with this. Could you let me know whom I should invite to the discussion? |
Sorry, something went wrong.
|
Hi @cathyhongzhang, for now just include me. |
Sorry, something went wrong.
|
I have gone through this DD. It looks good to me. |
Sorry, something went wrong.
|
FYI: I'm still working on the governance review for this. |
Sorry, something went wrong.
|
/vote |
Sorry, something went wrong.
Vote created@amye has called for a vote on CloudEvents Graduation Proposal + DD (#996). The members of the following teams have binding votes:
Non-binding votes are also appreciated as a sign of support! How to voteYou can cast your vote by reacting to this comment. The following reactions are supported:
Please note that voting for multiple options is not allowed and those votes won't be counted. The vote will be open for 5months 29days 19h 12m. It will pass if at least 66% of the users with binding votes vote In favor 👍. Once it's closed, results will be published here as a new comment. |
Sorry, something went wrong.
|
/check-vote |
Sorry, something went wrong.
Vote statusSo far 9.09% of the users with binding vote are in favor (passing threshold: 66%). Summary
Binding votes (1)
Non-binding votes (11)
|
Sorry, something went wrong.
Vote statusSo far 9.09% of the users with binding vote are in favor (passing threshold: 66%). Summary
Binding votes (1)
Non-binding votes (17)
|
Sorry, something went wrong.
|
/check-vote |
Sorry, something went wrong.
Vote statusSo far 9.09% of the users with binding vote are in favor (passing threshold: 66%). Summary
Binding votes (1)
Non-binding votes (18)
|
Sorry, something went wrong.
|
I would like to add, in addition to my vote, a recommendation for the project when they move to Graduation status, as this is not clearly conveyed in the current criteria and recent discussions on the topic of maintainership have revealed two primary purposes for "committers from two organizations" (addressed in the recommendations from the moving levels task force yet to be accepted by the TOC). While the current structure of the project, as a specification with reference implementations, allows for the community to drive the direction of the project (in accordance with their voting rights process) so no single entity may use it as a means to their ends, it places significant trust in the listed administrators to be available to perform those operations and execute the direction of the community. Given these individuals have admin rights, and I believe to be operating in the interests of the project and community, it would be beneficial for the project to rotate new administrators in, establishing a community path to achieve this status, in order to allow the existing admins a reprieve and achievement to emeritus. This model would increase understanding by community members of project on the operations and maintenance needed, as well ensure institutional knowledge is passed on in a consistent manner before an administrator is no longer able to perform their duties (for whatever reason). As stated before, this is not a requirement for graduation at this time, however as we begin seeing more cloud native projects experience maintainer burnout and turnover post-graduation, having such a process in place allows the project to maintain a pipeline of administrators available to step in as needed. |
Sorry, something went wrong.
|
/check-vote |
Sorry, something went wrong.
Vote statusSo far 9.09% of the users with binding vote are in favor (passing threshold: 66%). Summary
Binding votes (1)
Non-binding votes (18)
|
Sorry, something went wrong.
Vote statusSo far 36.36% of the users with binding vote are in favor (passing threshold: 66%). Summary
Binding votes (4)
Non-binding votes (18)
|
Sorry, something went wrong.
Vote statusSo far 36.36% of the users with binding vote are in favor (passing threshold: 66%). Summary
Binding votes (4)
Non-binding votes (18)
|
Sorry, something went wrong.
Vote statusSo far 45.45% of the users with binding vote are in favor (passing threshold: 66%). Summary
Binding votes (5)
Non-binding votes (18)
|
Sorry, something went wrong.
|
/check-vote |
Sorry, something went wrong.
Vote statusSo far 54.55% of the users with binding vote are in favor (passing threshold: 66%). Summary
Binding votes (6)
Non-binding votes (19)
|
Sorry, something went wrong.
|
/check-vote |
Sorry, something went wrong.
Vote statusSo far 63.64% of the users with binding vote are in favor (passing threshold: 66%). Summary
Binding votes (7)
Non-binding votes (19)
|
Sorry, something went wrong.
|
Votes can only be checked once a day. |
Sorry, something went wrong.
Vote statusSo far 72.73% of the users with binding vote are in favor (passing threshold: 66%). Summary
Binding votes (8)
Non-binding votes (19)
|
Sorry, something went wrong.
Vote closedThe vote passed! 🎉 72.73% of the users with binding vote were in favor (passing threshold: 66%). Summary
Binding votes (8)
Non-binding votes (20)
|
Sorry, something went wrong.
|
@amye - is this meaning that CloudEvents graduated? If so please LMK the exact date when it graduated, I want to update DevStats to reflect this. Thanks! |
Sorry, something went wrong.
|
Jan 25th is the official date. |
Sorry, something went wrong.
|
Thank you, will update DevStats. |
Sorry, something went wrong.
|
DevStats updated: https://all.devstats.cncf.io/d/53/projects-health-table?orgId=1, https://cloudevents.devstats.cncf.io/d/8/dashboards?orgId=1&refresh=15m |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Proposal for CloudEvents to move to Graduated status.
I wasn't sure where to put the draft DD doc, so for now I just put it next to the proposal. If there's a better spot for it let me know.