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

Add launching-pad team. #1206

Merged
merged 2 commits into from
Feb 2, 2024
Merged

Add launching-pad team. #1206

merged 2 commits into from
Feb 2, 2024

Conversation

ehuss
Copy link
Contributor

@ehuss ehuss commented Jan 14, 2024

This adds the launching-pad team, and connects all of its subteams into it. This should help with tracking the team membership and their status and connections.

cc @jonathanpallant

@ehuss
Copy link
Contributor Author

ehuss commented Jan 14, 2024

Opening as a draft because this will break the website until rust-lang/www.rust-lang.org#1914 is merged and deployed.

In the future, I would like to make it so that subteam-of will be required, but we aren't quite there yet. One wrinkle is keeping track of the top-level teams in a way that makes sense. If they are subteams of the leadership-council, that will likely also cause problems for the website (and I'm not sure what else).

Comment on lines -188 to -196
if !matches!(team.kind(), TeamKind::Team) && parent.subteam_of().is_some() {
bail!(
"{} `{}` can't be a subteam of a subteam (`{}`)",
team.kind(),
team.name(),
parent.name(),
);
}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't 100% understand why this clause was left in #1046. @fmease Can you say why this is here?

Copy link
Member

@fmease fmease Jan 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I didn't get notified by the ping, maybe because this PR is marked as a draft? I saw this PR just now since I'm subscribed to this repo.

Copy link
Member

@fmease fmease Jan 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I kept this check because it's not clear where to place WGs and PGs that are children of subteams on the website. Today, WGs and PGs are placed at the bottom of the page in distinct sections. It doesn't feel right to place WGs/PGs that aren't actually direct children of the team whose page we are looking at at the same level as other WGs/PGs especially since the user wouldn't necessarily be able to draw a connection between a given group and the respective parent team.

Copy link
Member

@fmease fmease Jan 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For example:

Team A
+-- Team A-A
|   +-- Working Group A-A-A
+-- Team A-B

The webpage of team A would look like:

Team A
--- Subteams
Team A-A
Team A-B
--- WGs
Working Group A-A-A
--- PGs

Now it's unclear if WG A-A-A is a direct child of A, A-A or A-B (without looking at their names of course which might not reflect the hierarchy).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that for subsubteams (and sub^N-teams, N>2), I've made the website semi-preserve the hierarchy by walking the team structure in pre-order. The situation is slightly better since they're contained in the same section on the page.

@rylev
Copy link
Member

rylev commented Jan 16, 2024

@ehuss with rust-lang/www.rust-lang.org#1914 merged, is this ready for review?

@Kobzol Kobzol mentioned this pull request Jan 16, 2024
@ehuss
Copy link
Contributor Author

ehuss commented Jan 16, 2024

Review is fine, but it cannot be merged as the deploy is currently not working, see: https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/www.2Erust-lang.2Eorg.20deploy.20is.20failing/near/412879305

@ehuss ehuss marked this pull request as ready for review January 31, 2024 23:12
@ehuss
Copy link
Contributor Author

ehuss commented Jan 31, 2024

Now that the website has been deployed, this should be ready.

@rylev rylev merged commit 9e97227 into rust-lang:master Feb 2, 2024
1 check passed
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

Successfully merging this pull request may close these issues.

3 participants