{"id":29419867,"url":"https://github.com/bytecodealliance/rfcs","last_synced_at":"2025-07-12T01:13:12.243Z","repository":{"id":39571450,"uuid":"275248548","full_name":"bytecodealliance/rfcs","owner":"bytecodealliance","description":"RFC process for Bytecode Alliance projects","archived":false,"fork":false,"pushed_at":"2025-05-14T20:50:08.000Z","size":728,"stargazers_count":68,"open_issues_count":10,"forks_count":24,"subscribers_count":41,"default_branch":"main","last_synced_at":"2025-07-12T00:44:55.697Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/bytecodealliance.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2020-06-26T21:11:59.000Z","updated_at":"2025-07-07T07:21:00.000Z","dependencies_parsed_at":"2025-03-31T18:37:36.939Z","dependency_job_id":"ab185dd4-4564-4156-9c32-de689be3eade","html_url":"https://github.com/bytecodealliance/rfcs","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/bytecodealliance/rfcs","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bytecodealliance%2Frfcs","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bytecodealliance%2Frfcs/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bytecodealliance%2Frfcs/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bytecodealliance%2Frfcs/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/bytecodealliance","download_url":"https://codeload.github.com/bytecodealliance/rfcs/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bytecodealliance%2Frfcs/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":264922908,"owners_count":23683705,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-07-12T01:13:11.289Z","updated_at":"2025-07-12T01:13:12.203Z","avatar_url":"https://github.com/bytecodealliance.png","language":null,"readme":"# Bytecode Alliance RFCs\n\nThis respository is the home of the RFC (request for comments) process for Bytecode Alliance projects. RFCs are a tool for getting feedback on design and implementation ideas and for consensus-building among stakeholders.\n\n## What is an RFC?\n\nAn RFC is a markdown file laying out a problem and a proposed solution. To support getting feedback early on, RFCs can come in [draft](template-draft.md) or [full](template-full.md) forms (see the linked templates for details). Draft RFCs should be opened as [draft PRs](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests). In either case, discussion happens by opening a pull request to place the RFC's markdown file into the `accepted` directory.\n\n## When is an RFC needed?\n\nMany changes to Bytecode Alliance projects can and should happen through every-day GitHub processes: issues and pull requests. An RFC is warranted when:\n\n* The work involves changes that will significantly affect stakeholders or project contributors. Each project may provide more specific guidance. Examples include:\n    * Major architectural changes\n    * Major new features\n    * Simple changes that have significant downstream impact\n    * Changes that could affect guarantees or level of support, e.g. removing support for a target platform\n    * Changes that could affect mission alignment, e.g. by changing properties of the security model\n* The work is substantial and you want to get early feedback on your approach.\n\n## Workflow\n\n### Creating and discussing an RFC\n\n* The RFC process begins by submitting a (possibly draft) pull request, using one of the two templates available in the repository root. The pull request should propose to add a single markdown file into the `accepted` subdirectory, following the template format, and with a descriptive name.\n\n* The pull request is tagged with a **project label** designating the Bytecode Alliance project it targets.\n\n* Once an RFC PR is open, stakeholders and project contributors will discuss it together with the author, raising any points of concern, exploring tradeoffs, and honing the design.\n\n### Making a decision: merge or close\n\nTBD, see [the first RFC](https://github.com/bytecodealliance/rfcs/pull/1).","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbytecodealliance%2Frfcs","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fbytecodealliance%2Frfcs","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbytecodealliance%2Frfcs/lists"}