Come up with some sort of distinction between "policy" and "consensus"

[m]

We've had quite a few pieces of policy put forth that don't specify any punishment for not following them and are a bit unclear about actual procedures they lay out.

I've also pushed back on a lot of policy because they haven't been something that need to go into "law", they're just people trying to gauge whether this is popular and this is a thing we want to do "as a space".

examples for things that might follow under a "consensus" kind of vote:

• do we think a forum is a good idea?
• do we want to reorganize the focus foundry to re-open the door between it and the lounge
• do we want general bridged to telegram
• do we want general to feel like a necessary thing to be a part of to be a part of devhack

Things that still need to be policy are things that define how the board acts, how the teams put in place under the board need to act, the board's relationship with the membership, the membership's relationship with the board and the space, and how that looks with clearly defined procedure.

I'm not even sure I want "official infra teams" specified via policy under the board or just very strong social habits within the space with strong teams that feel enabled to exert control due to social strength.

[m]

Milestone renamed

[m]

Ticket retargeted after milestone closed