search

bytecodealliance / governance

Apache License 2.0
11 stars 37 forks source link

Define core and hosted projects, along with their requirements #52

Open fitzgen opened 12 months ago

xwang98 commented 12 months ago

We would like to nominate wamr as a core project. Shall it be started after this PR is approved and merged?

fitzgen commented 12 months ago

@xwang98

We would like to nominate wamr as a core project. Shall it be started after this PR is approved and merged?

Once this PR is merged then, yes, projects can begin the process described within and submit an application.

fitzgen commented 8 months ago

I've moved the enumeration of the actual project requirements into github issue templates. Each requirement has an associated TODO to be filled in. This should address the confusion around what needs to be filled in when proposing a new hosted project or the promotion of a core project.

tschneidereit commented 5 months ago

Hey @xwang98, since it's been quite a while, I wanted to follow up here and give you and update on where things stand.

As you can see, this PR still hasn't been merged, because we still have some small things to work through. In the meantime however, what you can do to get things ready in parallel is to look at the criteria for both hosted projects and core projects that this PR introduces, and check how well WAMR satisfies them. As laid out in the PR, that will be the basis for deciding whether a project can gain Core Project status. Part of the process will be to have the project maintainers provide explanations for how the project satisfies the criteria, or what kinds of plans are in place to get to that place in cases where a criteria isn't yet satisfied.

To be clear, there's no need for you to act right now, but if you want to get a head-start on the process, this would be a great way to do so!

xwang98 commented 5 months ago

@tschneidereit Thank you for the reminder. We have checked the criteria list, and WAMR seems in good shape.

fitzgen commented 2 hours ago

I'm pleased to share that the TSC is ready to move forward with these requirements and merge this pull request. I am extremely proud of the high bar we are setting for ourselves and I am confident that by meeting and sustaining this level of rigor we can achieve the Bytecode Alliance's mission.

I want to thank everyone who shared feedback with us both in this PR thread and via private channels. You've definitely helped improve, clarify, and refine these requirements and the documents describing them; the Bytecode Alliance is better off because of it. Thanks!