[launching-pad] Find a home for the Docker Team

[jamesmunns]

This is a tracking issue for finding a long-term home for the Docker team.

Leads (there are no leads currently) Members:

• @sfackler
• @Muscraft

Hey there @sfackler and @Muscraft, I'm James, the Leadership Council member for the Launching Pad Team, and as part of #118, I'm starting the triage process of trying to find permanent homes for teams currently under the launching pad.

In this first pass, I'm making tracking issues for each of the teams, starting the discussion on whether y'all think there is a reasonable team you think would make sense to move under, and in general checking whether the members of these teams are still actively working on things related to these teams.

I'm not familiar with the responsibilities/activities of the Docker team - would you mind letting me know:

• Is this team still active?
• If yes: should we mark one or both of you as "team leads"?
• If yes: Is there a repo or location for more information about this team?

Thank you!

[jamesmunns]

Answering some of my own questions:

• This team maintains https://github.com/rust-lang/docker-rust
• This team is definitely still active!

Still open to feedback or comments on the other items, but I have you marked as "still active" now, so I'll plan to check back after I've finished checking for teams that are currently inactive.

[sfackler]

I think it'd make sense to make @Muscraft the lead - he's much more involved than I am at this point. docker-rust is the only repo we deal with at this point now that the nightly image has been merged in.

[Muscraft]

should we mark one or both of you as "team leads"?

I don't have an opinion on who should be the lead or co-leads, but if @sfackler thinks I should be the lead, I am happy to accept.

[traviscross]

It seems likely to me that this should go under T-release.

[jamesmunns]

Hi @Mark-Simulacrum - as lead of T-Release, do you have any objections to adding the docker team as a subteam of T-Release, with @Muscraft as the lead of the subteam, and @sfackler as a member? If so, we can get a PR opened to shift the docker team out from under the Launching Pad. No worries if this requires discussion with other members of the team.

[jamesmunns]

(also maybe CC @shepmaster and @jdno, as leads of T-Infra, where T-Release is a subteam of)

[Mark-Simulacrum]

Docker (and more generally, at least looking ahead) other "third party" distributions don't really have an amazing home IMO - release itself doesn't really own the distribution (e.g., static.rlo, promote-release) though the line is blurry since Pietro and I are both in infra and release and do most of that work. In that sense, infra could be better, at least my sense is that the docker team is mostly just re-publishing artifacts produced elsewhere, right? There's no custom release notes?

Overall I have no strong opinions.

We also (I think) have no other platforms we vend to officially other than docker hub, which is also a little interesting; I don't think that has any major influence here though.

Cc @rust-lang/release, @rust-lang/infra will also aim to bring this up in our next meeting in a few weeks.

[traviscross]

Given that T-release is a subteam of T-infra, we could just decide to reparent this to T-infra, and then T-infra, in its discretion, could decide whether or not it wants to further reparent this to T-release or just keep it for itself.

[jdno]

I'd be fine making this a sub-team of T-Infra. Feels more natural to me than putting it under T-Release, which is already a sub-team.