Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More informative team descriptions #334

Open
RalfJung opened this issue May 12, 2020 · 6 comments
Open

More informative team descriptions #334

RalfJung opened this issue May 12, 2020 · 6 comments

Comments

@RalfJung
Copy link
Member

Many teams on @rust-lang have a description (the extra text shown when I type @rust-lang/) that just says "managed by the team repository". That's not very useful when I want to figure out which is the right team to ping. Would be better to instead show a brief description of what the team is doing. :)

@RalfJung
Copy link
Member Author

FWIW, as more and more teams are converted to be managed by this repo, we are losing even the useful descriptions that we used to have.

@Mark-Simulacrum
Copy link
Member

We don't currently have description metadata outside of the website section in the toml configs here, and I'd rather not silently use that in other places.

Other than that problem, https://github.com/rust-lang/sync-team/blob/master/src/github/mod.rs#L69 is the place to edit to put more descriptive descriptions in place.

@rylev
Copy link
Member

rylev commented May 20, 2022

We can add a description section to the toml configuration for the GitHub team, and sync that if available.

@RalfJung
Copy link
Member Author

We don't currently have description metadata outside of the website section in the toml configs here, and I'd rather not silently use that in other places.

Hm, that description seems fine for me (looking at the lang team, at least) -- why would one not want to also use that in other places?

@rylev
Copy link
Member

rylev commented May 20, 2022

I think the issue is that that description is explicitly inside the metadata for the website, and this can become confusing if it actually gets used elsewhere.

@Mark-Simulacrum
Copy link
Member

Yeah, I think having a generic description we (also) use for the website is ok, but using the website description implicitly seems likely to confuse us later down the line (e.g., removing a website section causes GitHub description to disappear).

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

No branches or pull requests

3 participants