Move all existing teams to working group format

[thibaudcolas]

How about we move existing DSF teams over to the working group format? I’ve heard a few people wondering how the Django Software Foundation’s teams are managed. In particular there are three questions that come up very often, which I don’t think we have a clear answer for:

1. How to contact the team if you need to work with them.
2. How they manage their members (adding and removing members).
3. Where to learn more about the team’s activities.

Those strike me as things that have been solved for working groups.

Benefits and drawbacks

I think those teams would benefit from having:

• A Chair and Co-Chair
• Defined membership criteria and terms
• A charter that can evolve over time (some teams are defined via DEPs, but DEPs require a lot more work than working group changes)
• Defined ways for team internal comms, and reaching out to the team
• Reporting standards, so the rest of the world knows what the team is up to

Two drawbacks I see are:

• There being no need for the DSF Board to delegate powers to those teams. In some sense the teams are doing some things that would otherwise fall to the board, but for most teams it’s very indirect.
• Similarly the need for a board liaison isn’t as strong. It could be useful though.

---

Context: What is the “Technical Team” and the “Technical Advisory Team”?

[nanorepublica]

I'm a plus one for this with the caveat that we get the new Steering Council in place first as I would expect them to be interested in helping on this front (or at least I would if elected 😄)

The other question that comes to mind is hierarchy of teams (if one exists). I don't expect it complex, but more along the lines of does every team just report into the Board directly or do some teams report in the Steering Council, which in turn reports to the Board or is the Steering Council at the same level as the board?

This was also my thinking with issue #24