Clarify oversight of this project after the 2018 edition ships

[anp]

saving this from a discord conversation:

[10:15 AM] Havvy: @anp I have no idea w.r.t #244 (comment) Only thing I can think of is to make FCP a link.
[10:22 AM] anp: @Havvy lemme think more about it? this kinda starts to relate to some of the things i've been wondering about re: rfcbot's relationship to the rfc process -- these messages are an official part of many/most rust team decisions now but rfcbot and its behavior aren't under the purview of any team and i'm feeling pretty hesitant to change language that describes the "core contract" (if you will) between rfcbot and team members (cc @aturon)
[10:23 AM] anp: also there is an #rfcbot channel now btw woo
[10:23 AM] aturon: @anp yes it'd be great to get the oversight firmed up
[10:24 AM] Havvy: Seems like it'd be a part of the infra team to me.
[10:24 AM] aturon: @Havvy in terms of implementation/ops, i agree, but in terms of design/messaging, as @anp says it fits into the whole project RFC structure
[10:26 AM] anp: i think this grey area is probably a big part of why it's been convenient to just...not have a team in charge of it 😛
[10:27 AM] Havvy: But anything that doesn't fall upon a specific team seems to either get pulled into the core team or get neglected...
[10:27 AM] anp: an incisive observation!
[10:28 AM] anp: i'll open an issue to clarify this, and set a reminder to ping appropriate people after the edition ships

[anp]

related:

#181

https://github.com/rust-ops/requests/issues/1

I should also say that I'm very happy for whatever to happen that's best for the Rust community. @Centril has been doing the bulk of the work for a while. I've mostly been keeping the lights on and trying to be an appropriately conservative steward to reflect the fact that this project exerts outsized influence on the Rust project in an absence of much official oversight. I'd be very happy to be able to share that burden more!

Additionally, I believe that the folks at the Matrix.org teams (cc @erikjohnston) have been using a fork of rfcbot, and it would be great if the project could be made flexible enough that they and other organizations could continue to use the tool without having to be fully locked into Rust's governance decisions. Maybe that looks like extracting and publishing a couple of configurable crates? I'm waxing a bit poetic after some coffee, but I love the idea of the Rust community sharing code with the world that helps other projects organize their community decisions while benefiting from Rust's learnings. As the story always goes, I don't think I have the time and space to do this myself, but it's a future worth advocating for.

[erikjohnston]

Additionally, I believe that the folks at the Matrix.org teams (cc @erikjohnston) have been using a fork of rfcbot, and it would be great if the project could be made flexible enough that they and other organizations could continue to use the tool without having to be fully locked into Rust's governance decisions. Maybe that looks like extracting and publishing a couple of configurable crates? I'm waxing a bit poetic after some coffee, but I love the idea of the Rust community sharing code with the world that helps other projects organize their community decisions while benefiting from Rust's learnings. As the story always goes, I don't think I have the time and space to do this myself, but it's a future worth advocating for.

We are using it and loving it! There is absolutely the plan to PR our changes back ftr (they're mostly just making some of the constants configurable rather than any deeper changes), though we are also severely suffering from a lack of time.