[launching-pad] Find a home for the Secure Code WG

[jamesmunns]

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

Lead:

• @Shnatsel
• @tarcieri

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-Secure Code 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.

It seems that the Zulip Stream is still active. Have there been any discussions on teams that the Secure Code team might fit with?

Thanks!

[tarcieri]

Hi @jamesmunns,

In the past we have discussed (particularly with @pietroalbini) trying to form a single overall Security Team where the Secure Code team could be a subteam. Really at this point we could probably be rebranded the "RustSec Team" as the main thing we do is maintain and write tooling for the RustSec Advisory DB.

[traviscross]

With that rebranding, this seems most appropriate as a T-infra subteam to me.

cc @Mark-Simulacrum @shepmaster @jdno @ehuss

[traviscross]

@jamesmunns and I had a good talk. As a bit of necessary context here, I should mention that the above is just a friendly suggestion of what seems most appropriate to me. That is, I'm just speaking personally, and I'm in particular curious to hear what @jamesmunns, those on T-infra, and those on the Secure Code WG think of the suggestion.

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 this tracking issue, for bringing the various parties together, and for updating the council on all the various progress on this endeavor.

[traviscross]

In the alternate, as discussed in #141 (comment), perhaps this work, given the current top-level structure, could make sense as a subteam of T-devtools.