So @Eric Huss was raising with me the question of how best to maintain the reference. I definitely think that we should be taking a more active maintaince role here -- I'm curious @T-lang to hear any thoughts about this. In my ideal world, we'd be doing more work to actively complete the reference as well as maintain it.
One thing I could see doing, for example, is making it part of the duty of membership in t-lang to review PRs
e.g., we could setup high-five
I certainly don't ind reviewing reference PRs.
Seems like there are two separate issues as well: who will handle the current gaps between the reference and the Rust language, and who will take responsibility for adding new things to the reference when we change the language.
Yea, there are various degrees of things that would be helpful:
I'd also like to talk about the permissions on the repo itself. Right now I can't merge my own changes, so I'm reluctant to even work on formatting fixes if nobody can approve them. Some options here:
@Eric Huss so I think we ought to create a wg-reference or something to manage the permissions, and give that group write access, and create a highfive. We can make a stream, too. The biggest thing to think about is who will "lead" the group, and how much active work we want to put into that.
There's already a
reference team at https://github.com/rust-lang/team/blob/master/teams/reference.toml, and is a "subteam" of lang. I'm uncertain how this is currently connected to github permissions (I'm under the impression it is not connected). I'm also unsure what "subteam" actually means (like does it automatically give lang members r+ rights if we had bors set up?).
@Eric Huss yes, that does not appear to be sync'd with github, we should fix that. The general procedure these days is to try and avoid giving access rights to individuals, only to teams. I suspect we want to give write access to both lang + this group
I'm cc'ing @James Munns and @Florian Gilcher into this conversation, as it's relevant to Sealed Rust
when it comes to MIR semantics and unsafe code concerns, I could also help with reference maintenance