[launching-pad] Find a home for the Async Working Group

[jamesmunns]

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

Leads:

• @nikomatsakis
• @tmandry

Hey there all, as part of #118, I'm starting the triage process of trying to find permanent homes for teams currently under the launching pad. As WG-async is also a working group, #91 is also relevant.

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 see that meetings stopped mid this year (according to this page ), is WG-async still active as a group?

Thanks!

[jamesmunns]

Note that project-async-crashdump-debugging is also in need of a home, but I believe that it will follow wherever WG-async goes.

[nikomatsakis]

This has been a topic of some discussion. @tmandry was working towards a proposal but we never quite got it over the finish line.

[traviscross]

There's now a PR up for this:

• Adopt wg-async as a subteam (WG) of lang team#1639

It just makes wg-async -- as is -- a lang working group. It doesn't seek to resolve the larger questions of how we on lang might want to further refactor this. But that seems fine. We can later do that, as time permits, as could for any of our subteams.

[traviscross]

See rust-lang/team#1639 (comment) for further context.