Stream: general

Topic: RFC process


view this post on Zulip Till Schneidereit (Nov 20 2020 at 13:41):

@all we're aiming to finalize the proposed RFC process for shared projects in the Bytecode Alliance. I just added a comment to the pull request introducing that process (by using the process itself :stuck_out_tongue:). That comment kicks off the steps required to get the RFC merged, and thus instate the RFC process itself for the BA.

Please feel free to chime in on the PR if you have any concerns! To set expectations, I'll note that we might not be able to address any and all concerns people might have, and intend to merge the PR once the requirements as described in the RFC itself are met. But I'd very much expect that if relevant issues are surfaced, key stakeholders would support addressing those, and holding up acceptance of the RFC until that has happened.

(Sincere apologies for the @\all mention! I thought long and hard about whether it's justified quite a bit, and came to the conclusion that yes, this is one of the rare situations where it is!)

RFC process for Bytecode Alliance projects. Contribute to aturon/ba-rfcs development by creating an account on GitHub.
As the Bytecode Alliance grows, we need more formalized ways of communicating about and reaching consensus on major changes to core projects. This document proposes to adapt ideas from Rust’s RFC a...

Last updated: Dec 23 2024 at 12:05 UTC