You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The WasmEdge is a lightweight, high-performance, and extensible WebAssembly runtime for the cloud native workloads. See the documentation here and README.md here.
Maintainer List (with employer information)
The maintainer, committer, and reviewer list can be found here.
How your project is making decisions
The maintainers will use voting to make a decision on specific actions or changes. See the section here.
For the feature implementation, the maintainers will update it quarterly with the community. See the section here.
How and when contributors are moving through the contributor ladder (e.g. becoming a maintainer)
The current maintainers will propose the new maintainer first and then get the final result. See the section here.
Maintainer life cycle with information about how and when maintainers are demoted
Voting is a required process for onboarding a new maintainer. See the section here. For demoting the maintainer, the basic rule is volunteer demotion by the maintainer itself. See the section here.
Code of Conduct
The WasmEdge community follows the CNCF Code of Conduct. See the documentation here.
Contributor Guide
The WasmEdge community adopts the CNCF contributor guide. See the details here.
How your community conduct communication and meetings
The WasmEdge community can communicate in the #WasmEdge CNCF slack channel and also a separate Discord server.
The community meeting occurs on the first Tuesday of each month. We also have public issues and Google Docs to discuss and record the community meeting.
How your community handles security reporting and response
Overall, the WasmEdge community adopts the CNCF Security template.
May I ask the process for expediting the governance review? Is there someone officially assigned to oversee this review for the project? The governance review is a crucial step, as it is required by the ToC for our sandbox project to move to incubation. Your assistance is greatly appreciated. Thanks.
Hey, unfortunately, due to limited volunteers in TAG-CS, we're running behind on govenance reviews. As such, we've been taking instructions from the TOC on what order to review them in based on how close those applications are to completing. Yours will get done before it can result in a delay.
While we're chatting though, can you clarify something? You say above:
However, there are three different templates, and none of them are the Helm governance, which is what you say elsewhere you evolved from. What do you specifically mean by the above?
I'm sorry; it's my mistake. The first version of WasmEdge Governance is borrowed from the Helm project. We have made some updates in the last few months, but I forgot to remove this sentence. PR #3841 has solved the problem. Thanks.
Project Name
WasmEdge
Project Website
https://wasmedge.org/
Contact Details 1
@juntao
Contact Details 2
@alabulei1
Links to communication channels
#WasmEdge in the CNCF slack channel and WasmEdge Discord Server
Reason for governance review request
CNCF Incubation acceptance application
Are there any sub-projects, plugins, and related?
No. https://github.com/WasmEdge/ is the main project, including the plugins.
Governance model
WasmEdge adopts CNCF governance template as the governance model.
Governance documents
Governance Execution Examples
Governance Evolution
At the beginning of the project, we adopted the governance from a mature CNCF project called Helm.
As the community grows bigger, we improved our code of conduct for contributors to incorporate other open-source projects. See the PR here.
Meanwhile, as the CNCF’s governance template evolves, the governance of WasmEdge also improves. See the latest update here.
Any specific aspects of your governance structure are you seeking feedback on?
No response
Do you have any concerns or specific areas where you feel your governance could be improved?
No response
Additional notes and resources
No response
The text was updated successfully, but these errors were encountered: