Stream: t-lang

Topic: maintaining the reference


nikomatsakis (Apr 22 2020 at 19:58, on Zulip):

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.

nikomatsakis (Apr 22 2020 at 19:58, on Zulip):

One thing I could see doing, for example, is making it part of the duty of membership in t-lang to review PRs

nikomatsakis (Apr 22 2020 at 19:58, on Zulip):

e.g., we could setup high-five

Josh Triplett (Apr 22 2020 at 20:01, on Zulip):

I certainly don't ind reviewing reference PRs.

Josh Triplett (Apr 22 2020 at 20:01, on Zulip):

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.

nikomatsakis (Apr 22 2020 at 20:02, on Zulip):

Yes.

Eric Huss (Apr 22 2020 at 22:14, on Zulip):

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:

nikomatsakis (Apr 22 2020 at 22:58, on Zulip):

@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.

Eric Huss (Apr 22 2020 at 23:07, on Zulip):

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?).

nikomatsakis (Apr 27 2020 at 15:25, on Zulip):

@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

nikomatsakis (Apr 28 2020 at 18:43, on Zulip):

I'm cc'ing @James Munns and @Florian Gilcher into this conversation, as it's relevant to Sealed Rust

RalfJ (Apr 30 2020 at 06:51, on Zulip):

when it comes to MIR semantics and unsafe code concerns, I could also help with reference maintenance

Last update: Jun 05 2020 at 23:15UTC