Skip to content

Commit

Permalink
docs(charter): Declare new Intentional Artifacts as 'small' changes
Browse files Browse the repository at this point in the history
That means these will only need an FCP to take ownership, including
updating the charter, rather than an RFC.
  • Loading branch information
epage committed Sep 26, 2024
1 parent 2fd7321 commit 7ab0916
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions src/doc/contrib/src/team.md
Original file line number Diff line number Diff line change
Expand Up @@ -135,6 +135,7 @@ The degree of process is correlated with the degree of change being proposed:
These decisions are usually processed via private channels by the entirety of the team.
- A change that is a "one-way door".
That is, something that is difficult to reverse without breaking backwards compatibility.
- New or transferred "Intentional Artifact" crates to the team, see also [Rust crate ownership policy](https://forge.rust-lang.org/policies/crate-ownership.html)

- Larger features should usually go through the [RFC process].
This usually involves first soliciting feedback from the Cargo team and the rest of the community, often via the [Rust Internals] discussion board, [Cargo's issue tracker], and the [Zulip] channel.
Expand Down

0 comments on commit 7ab0916

Please sign in to comment.