Oh, right. As a member; I should have noticed that 
In that case I would personally prefer having design on the community subteam (as opposed to having no official design position whatsoever, or an independent design team). As you mentioned it would be a tiny team otherwise.
Iāve mentioned this elsewhere on this forum ā I think we should make it explicit that community team members need work on everything the team works on. As the team forms the members can communicate with each other (and publicly) what they intend to focus on. Working outside of oneās focus is of course okay too.
Yes. Lots of RfCs and stuff have cross-cutting concerns. Iām not sure if there will be joint projects , since the teams donāt really have āprojectsā per se (rather, rfcs might be drafted by individual members the way stuff happens now). I believe that cross-cutting RfCs were brought up at some point during the original discussion on the governance structure.
I donāt think this needs to be a hard rule. The core team, though it handles nontechnical things not in the purview of the subteams, is a technical team. The original governance model had the mod team āspecialā to avoid conflicts of interest, but I think this specialness can be extended to some or all nontechnical teams. The subteam āleaderā is a post that was pretty clearly designed for technical things. Supporting this could require a tweak to the original RfC, but not one that would warrant much discussion or debate I presume.
Rather, I would expect that the community/design/etc teams would have one or more particular core team members that they keep in communication with.
I donāt think anyone does 
. The responsibilities of subteams were pretty clear for technical stuff. They had to handle a defined technical process in a defined technical way. We didnāt really address how non-technical teams would work because we only had one example (for which we had a concrete design) and while ācommunity teamā had been brought up the idea wasnāt explored much.
