Adopt wg-async as a subteam (WG) of lang

[traviscross]

We're working to move things out from under the launching-pad team to more appropriate places. It makes the most sense for the async working group to be adopted as a subteam of lang, so let's do that.

Note that there are ongoing discussions of how we on lang might want to further refactor this working group. This PR doesn't seek to resolve those. It just puts the working group in our domain. We can later adjust as we deem proper.

See:

• [launching-pad] Find a home for the Async Working Group leadership-council#137

cc @nikomatsakis @tmandry @eholk @yoshuawuyts @compiler-errors @jamesmunns

[eholk]

This seems like a good way to make this reorganization tractable. We can start by getting it out of the launching pad, but any more substantive changes can happen later.

[traviscross]

@jamesmunns and I had a good talk. He suggested that it would be valuable to add some further context to this PR.

The first bit of context is that I'm making this PR with my lang/lang-ops hat on -- that is, the hat of a member of the adopting team (and of the ops team that supports it in many administrative and policy matters like this) -- and not with my council hat on. This PR should of course be approved by @nikomatsakis and/or @tmandry, who were CCed above, and who are incidentally the leads of both lang and of WG-async, and this can be seen as my suggestion to my fellow team members about the appropriate handling. As mentioned, there have been ongoing discussions within the lang team about how to refactor the async working group, and this PR does not seek to resolve those discussions, but simply to take the step of putting it within our domain, leaving us of course later free to make other adjustments.

On the council side, @jamesmunns is of course the one coordinating this, and is of course in my view doing a great job in that. Thanks to James for opening the tracking issues, such as the one here, for bringing the various parties together, and for updating the council on all the various progress on this endeavor.

---

Putting on my council hat for a moment, I suppose we might consider the question of whether each of (or each specific batch of) these moves requires an FCP from the council. My own feeling is that it's probably not necessary to require such process for moves of a group out from under launching-pad, where both the group and the adopting team agree on the handling (and where no other potentially-adopting team is making a claim), especially given our preexisting consensus that moving such groups out from launching-pad to more appropriate teams is what we'd like to see happen. But I'm curious to hear what @jamesmunns thinks, and if it's at all unclear we should of course raise this topic in our next council meeting on 2025-01-17.

[ehuss]

Just a heads up that this will delete the page https://www.rust-lang.org/governance/wgs/wg-async.

If we don't want to break all the links on the internet, we could add a redirect to https://github.com/rust-lang/www.rust-lang.org/blob/HEAD/src/redirect.rs.

[traviscross]

Draft PR for the redirect up in:

• Add redirect for wg-async adoption by lang www.rust-lang.org#2106