Skip to content
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

Draft of WASMEdge governance review. #772

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

jberkus
Copy link
Contributor

@jberkus jberkus commented Feb 15, 2025

This is the draft copy of the WASMEdge review, in response to #690 .

This is the first review in the new format. It's somewhat ad-hoc because the review request, and Incubading request, was not in the current checklist format.

attn: @geekygirldawn @edrob999 @xmulligan

assign @TheFoxAtWork @dzolotusky @dims

Copy link
Contributor

@TheFoxAtWork TheFoxAtWork left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great love the format!

@alabulei1
Copy link

Hi @jberkus,
Thank you for your insightful review. Much appreciated.

I'm wondering whether I should address the 'Miscellaneous issues' now or wait until the review is complete. Let me know what do you think. Thanks.


- [mailing list](https://groups.google.com/g/wasmedge/): rarely used
- [Discord](https://discord.com/invite/JHxMj9EQbA): very active
- [community meeting](https://docs.google.com/document/d/1iFlVl7R97Lze4RDykzElJGDjjWYDlkI8Rhf8g4dQ5Rk/edit?tab=t.0: held regularly, videos uploaded
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [community meeting](https://docs.google.com/document/d/1iFlVl7R97Lze4RDykzElJGDjjWYDlkI8Rhf8g4dQ5Rk/edit?tab=t.0: held regularly, videos uploaded
- [community meeting](https://docs.google.com/document/d/1iFlVl7R97Lze4RDykzElJGDjjWYDlkI8Rhf8g4dQ5Rk/edit?tab=t.0:) held regularly, videos uploaded


Status: Mostly Satisfactory

WASMEdge has clearly made progress in all aspects of governance and contributor management since joining the CNCF. They have many miscellaneous issues with governance and contributor documentation, which is normal for a project at this stage. The project needs to use its advancement to Incubating in order to drive more contributor recruitment.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
WASMEdge has clearly made progress in all aspects of governance and contributor management since joining the CNCF. They have many miscellaneous issues with governance and contributor documentation, which is normal for a project at this stage. The project needs to use its advancement to Incubating in order to drive more contributor recruitment.
WASMEdge has clearly made progress in all aspects of governance and contributor management since joining the CNCF. They have many miscellaneous issues with governance and contributor documentation, which is normal for a project at this stage. The project needs to use its advancement to Incubating in order to drive more contributor recruitment.

Do a quick sanity check on the number of maintainers. A very large critical project applying for graduation which has three maintainers is probably at bus-factor risk. In contrast, a narrowly-scoped project with 50 maintainers is probably listing people who are not actually maintainers.
Also check that maintainers on the list are active using Devstats, GitHub and LFX Insights. Query inactive maintainers. --->

Currently WASMEdge has [four Maintainers](https://github.com/WasmEdge/WasmEdge/blob/master/docs/OWNER.md), which seems reasonable for a project this size. They are also the foudning maintainers of WASMEdge, and there has yet to be any maintainer turnover. All are active. The project has promoted many regular contributors to intermediate levels of code ownership (Reviewer and Committer), and seems prepared to eventually advance one or more contributors to maintainer according to the documented requiremens.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Currently WASMEdge has [four Maintainers](https://github.com/WasmEdge/WasmEdge/blob/master/docs/OWNER.md), which seems reasonable for a project this size. They are also the foudning maintainers of WASMEdge, and there has yet to be any maintainer turnover. All are active. The project has promoted many regular contributors to intermediate levels of code ownership (Reviewer and Committer), and seems prepared to eventually advance one or more contributors to maintainer according to the documented requiremens.
Currently WASMEdge has [four Maintainers](https://github.com/WasmEdge/WasmEdge/blob/master/docs/OWNER.md), which seems reasonable for a project this size. They are also the founding maintainers of WASMEdge, and there has yet to be any maintainer turnover. All are active. The project has promoted many regular contributors to intermediate levels of code ownership (Reviewer and Committer), and seems prepared to eventually advance one or more contributors to maintainer according to the documented requirements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

4 participants