Thanks, I indeed was thinking I was taking the task. I see it like this:
- Drafting (of either drivers or proposals) in topics, tagged appropriately
- When those doing the drafting feel something is a candidate for a consent-decision, it gets marked (how?) as such and the team (or maybe circle if it’s in a specific scope) gets pinged
- After some delay (how much?) to give others a chance to participate in further drafting, then a formal consent-decision point is posted
The key is that it can feel awkward if the first reading is also the time to consent. That situation means any update needs either an objection or a later revision process.
Another summary:
- Bad: ping everyone at the beginning (too much distraction, not everyone can take time to help with every draft)
- Mediocre: ping everyone only at decision time (people who might want to discuss the draft feel pushed to already consent, feels extra formal)
- Nice: ping everyone toward the end of drafting but in advance of the formal decision. Gives people a chance to participate while it still feels like open drafting time.
In short: add a delay between announcing a potential final-draft and posting the consent-decision (which may then have some updates). Probably ping everyone at both those times though.
@iko does this seem right by your thoughts on this?