Stream: rfc-notifications

Topic: rfcs / Issue #1 RFC process proposal

view this post on Zulip RFC notifications bot (Dec 01 2020 at 14:02):

tschneidereit edited a comment on Issue #1:

Motion to finalize with a disposition to merge

I'd like to propose that we accept this RFC by merging this PR. I'm labeling the PR with the motion-to-finalize and disposition-merge labels. As described in the RFC, I'm tagging stakeholders of affected projects, which right now are the core collaborative projects Cranelift and Wasmtime. Given the fundamental nature of this RFC, I'll go even more broad in whom I'm tagging for sign-off, by including regular contributors (very arbitrarily defined as having contributed 5+ commits with 100+ lines changed in the last 3 months), regardless of whether they're committers or not, in addition to contributors to this particular RFC, and representatives of the BA members.

Stakeholders sign-off

Red Hat

Mozilla

Intel

IBM

Fastly

DFINITY

AssemblyScript

Arm

Unaffiliated

Next steps

With this comment, the RFC enters the motion-to-finalize phase. As soon as a member of any second group signs off, it'll enter the final-comment-period of up to 10 days.

If during that time a member of a key stakeholder group raises a blocking concern, the FCP will be paused until the concern has been resolved. Note that for the sake of that part of the process, only committers and member representatives can raise blocking concerns as a formal matter, but we'd aim to resolve any concerns, regardless of who raises them, as best as possible.

Once the FCP has ended, or at least one member of each stakeholder group has signed off — whichever comes first — this PR can be merged and the FCP accepted.

view this post on Zulip RFC notifications bot (Dec 01 2020 at 14:02):

tschneidereit edited a comment on Issue #1:

Motion to finalize with a disposition to merge

I'd like to propose that we accept this RFC by merging this PR. I'm labeling the PR with the motion-to-finalize and disposition-merge labels. As described in the RFC, I'm tagging stakeholders of affected projects, which right now are the core collaborative projects Cranelift and Wasmtime. Given the fundamental nature of this RFC, I'll go even more broad in whom I'm tagging for sign-off, by including regular contributors (very arbitrarily defined as having contributed 5+ commits with 100+ lines changed in the last 3 months), regardless of whether they're committers or not, in addition to contributors to this particular RFC, and representatives of the BA members.

Stakeholders sign-off

Red Hat

Mozilla

Intel

IBM

Fastly

DFINITY

AssemblyScript

Arm

Unaffiliated

Next steps

With this comment, the RFC enters the motion-to-finalize phase. As soon as a member of any second group signs off, it'll enter the final-comment-period of up to 10 days.

If during that time a member of a key stakeholder group raises a blocking concern, the FCP will be paused until the concern has been resolved. Note that for the sake of that part of the process, only committers and member representatives can raise blocking concerns as a formal matter, but we'd aim to resolve any concerns, regardless of who raises them, as best as possible.

Once the FCP has ended, or at least one member of each stakeholder group has signed off — whichever comes first — this PR can be merged and the FCP accepted.

view this post on Zulip RFC notifications bot (Dec 01 2020 at 14:03):

yurydelendik edited a comment on Issue #1:

Motion to finalize with a disposition to merge

I'd like to propose that we accept this RFC by merging this PR. I'm labeling the PR with the motion-to-finalize and disposition-merge labels. As described in the RFC, I'm tagging stakeholders of affected projects, which right now are the core collaborative projects Cranelift and Wasmtime. Given the fundamental nature of this RFC, I'll go even more broad in whom I'm tagging for sign-off, by including regular contributors (very arbitrarily defined as having contributed 5+ commits with 100+ lines changed in the last 3 months), regardless of whether they're committers or not, in addition to contributors to this particular RFC, and representatives of the BA members.

Stakeholders sign-off

Red Hat

Mozilla

Intel

IBM

Fastly

DFINITY

AssemblyScript

Arm

Unaffiliated

Next steps

With this comment, the RFC enters the motion-to-finalize phase. As soon as a member of any second group signs off, it'll enter the final-comment-period of up to 10 days.

If during that time a member of a key stakeholder group raises a blocking concern, the FCP will be paused until the concern has been resolved. Note that for the sake of that part of the process, only committers and member representatives can raise blocking concerns as a formal matter, but we'd aim to resolve any concerns, regardless of who raises them, as best as possible.

Once the FCP has ended, or at least one member of each stakeholder group has signed off — whichever comes first — this PR can be merged and the FCP accepted.

view this post on Zulip RFC notifications bot (Dec 01 2020 at 14:20):

tschneidereit commented on Issue #1:

I do think there's value in defining at least the skeleton of further process for stakeholder disagreement now, rather than the first time we need it (when tensions and stakes may be higher); evidence from other communities (such as Rust) suggests we will eventually need it.

Thank you for raising this, @joshtriplett. I agree that we'll need this, but there's a tradeoff between trying to get all related processes in place and getting this core process formally instated. We should certainly not put it off indefinitely :) I filed #6 to track this.

view this post on Zulip RFC notifications bot (Dec 01 2020 at 14:31):

tschneidereit commented on Issue #1:

Entering Final Call Period

Since we have sign-off by members of multiple stakeholder groups and no blocking concerns have been raised, I'm moving this RFC to Final Call. That means it'll be merged in 10 days from now, or once the remaining stakeholder groups have signed off on it, provided no blocking concerns are raised in the meantime.

view this post on Zulip RFC notifications bot (Dec 02 2020 at 14:31):

tschneidereit edited a comment on Issue #1:

Motion to finalize with a disposition to merge

I'd like to propose that we accept this RFC by merging this PR. I'm labeling the PR with the motion-to-finalize and disposition-merge labels. As described in the RFC, I'm tagging stakeholders of affected projects, which right now are the core collaborative projects Cranelift and Wasmtime. Given the fundamental nature of this RFC, I'll go even more broad in whom I'm tagging for sign-off, by including regular contributors (very arbitrarily defined as having contributed 5+ commits with 100+ lines changed in the last 3 months), regardless of whether they're committers or not, in addition to contributors to this particular RFC, and representatives of the BA members.

Stakeholders sign-off

Red Hat

Mozilla

Intel

IBM

Fastly

DFINITY

AssemblyScript

Arm

Unaffiliated

Next steps

With this comment, the RFC enters the motion-to-finalize phase. As soon as a member of any second group signs off, it'll enter the final-comment-period of up to 10 days.

If during that time a member of a key stakeholder group raises a blocking concern, the FCP will be paused until the concern has been resolved. Note that for the sake of that part of the process, only committers and member representatives can raise blocking concerns as a formal matter, but we'd aim to resolve any concerns, regardless of who raises them, as best as possible.

Once the FCP has ended, or at least one member of each stakeholder group has signed off — whichever comes first — this PR can be merged and the FCP accepted.

view this post on Zulip RFC notifications bot (Dec 11 2020 at 22:19):

tschneidereit edited a comment on Issue #1:

Motion to finalize with a disposition to merge

I'd like to propose that we accept this RFC by merging this PR. I'm labeling the PR with the motion-to-finalize and disposition-merge labels. As described in the RFC, I'm tagging stakeholders of affected projects, which right now are the core collaborative projects Cranelift and Wasmtime. Given the fundamental nature of this RFC, I'll go even more broad in whom I'm tagging for sign-off, by including regular contributors (very arbitrarily defined as having contributed 5+ commits with 100+ lines changed in the last 3 months), regardless of whether they're committers or not, in addition to contributors to this particular RFC, and representatives of the BA members.

Stakeholders sign-off

Red Hat

Mozilla

Intel

IBM

Fastly

DFINITY

AssemblyScript

Arm

Unaffiliated

Next steps

With this comment, the RFC enters the motion-to-finalize phase. As soon as a member of any second group signs off, it'll enter the final-comment-period of up to 10 days.

If during that time a member of a key stakeholder group raises a blocking concern, the FCP will be paused until the concern has been resolved. Note that for the sake of that part of the process, only committers and member representatives can raise blocking concerns as a formal matter, but we'd aim to resolve any concerns, regardless of who raises them, as best as possible.

Once the FCP has ended, or at least one member of each stakeholder group has signed off — whichever comes first — this PR can be merged and the FCP accepted.

view this post on Zulip RFC notifications bot (Dec 11 2020 at 22:21):

tschneidereit commented on Issue #1:

I received a sign-off from the last missing stakeholder group in private message, so we have full approval, in addition to the 1-day FCP having lapsed :) With that, I'll merge this PR, at which point the RFC process is formally instated.

Last updated: Dec 23 2024 at 12:05 UTC