Open sgrif opened 5 years ago
@rust-lang/crates-io @rust-lang/cargo We've been discussing having our own RFC process for a while now, I've taken a swing at laying out what that looks like.
I'm unsure about this. I definitely agree that some large features could do with some more discussion and it would be good to have a place to do that which is not the main RFC repo (but which is a shared space between the Cargo and crates.io teams). However, I see some drawbacks:
That's a pretty negative list, sorry. I do think there is a problem that needs solving here and I'm glad you're looking at addressing it!
cc @skade, does the governance team have any thoughts on this aside from wanting to know how it goes if we do this?
Btw; You may want to integrate https://github.com/rust-lang/rfcs/pull/2333 and https://github.com/rust-lang/rfcs/pull/2561 into your templates :)
While we have the main RFC repo, team meetings, and issues/PRs, there's a big gap in how the existing tools serve these teams. We tend to have a lot of internal changes which impact the other team, or lower profile changes which would benefit from going through the RFC process, but would act as noise on the main RFC repo.
This RFC proposes a process for changes which impact both teams, or for user facing changes that don't justify landing on the main RFCs repo