Skip to content
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.

Add the style team #523

Merged
merged 1 commit into from
Sep 28, 2016
Merged

Add the style team #523

merged 1 commit into from
Sep 28, 2016

Conversation

nrc
Copy link
Member

@nrc nrc commented Sep 15, 2016

No description provided.

@nrc
Copy link
Member Author

nrc commented Sep 15, 2016

r? @steveklabnik or @brson

@nikomatsakis
Copy link
Contributor

Hmm. I don't have strong objections, but for some reason I had thought that we were going to just keep the standing teams (and not the more temporary strike teams) on the web site. On the other hand, I guess it's nice to have the team membership documented.

@nrc
Copy link
Member Author

nrc commented Sep 21, 2016

It seems to me to be pure win - we advertise the existence of the team and make the team feel more official. I don't think it takes anything away from the more permanent teams, there is no maintenance overhead, and there is no cost to having more data on this page.

@brson
Copy link
Contributor

brson commented Sep 23, 2016

I've gone back to both the style strike team RFC and the unsafe strike team RFC to see if there was a definitive word on whether we are adding strike teams to the web page, and there is not, though both myself and niko suggested we did not expect strike teams to be listed on the web site.

I am starting to come around to the idea that we should be more expansive in how we define teams, but I'm frustrated about how we've gotten here, that we did not sufficiently establish a definition that we all agree on before creating them.

@nrc
Copy link
Member Author

nrc commented Sep 25, 2016

that we did not sufficiently establish a definition that we all agree on before creating them.

Yeah, I guess this is the fundamental problem - I think we all kind of have slightly different ideas of what the strike teams should be like and it is probably worth discussing this somewhere since I expect we'll create more in the future.

My personal mental model has been that strike teams are just like regular teams, but have limited duration and a very specific focus. It seems you and Niko are thinking of something more lightweight from the linked comments.

In practical terms, I think that if we don't reuse the existing procedures and communication channels for teams, then we have to create new ones for strike teams, and that is a lot more effort than the administration of adding and later removing things like this. It is feeling difficult to get the style/formatting process the visibility it needs, and I feel very out of touch with what the unsafe guidelines team are doing.

@aturon
Copy link
Member

aturon commented Sep 27, 2016

@brson @nikomatsakis Are there specific downsides you see with listing strike teams on the web site?

Personally, I'm in favor of listing them, and think we should also highlight them on the eventual roadmap page. That's both to recognize the teams in an official way, and to help direct people toward important work that's under way.

@nikomatsakis
Copy link
Contributor

I'm ok with it; maybe we can link the team name over to some description of its purpose (or even the RFC). I just didn't expect to do it, but I'm not entirely sure why. It seems to make sense now. =)

@brson brson merged commit 6caf7c2 into rust-lang:master Sep 28, 2016
@brson
Copy link
Contributor

brson commented Sep 28, 2016

Merged.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants