- Added a driver statement
- Increased review date
- Made the reference to S3 at the beginning easier to read
- Allowed to skip or lump together parts of the process
Mild concerns left:
-
I feel like we’re changing too much right now, and not on the basis of objections. The others will have to read through all the changes for the final consent decision, so every change has its cost. Maybe we shouldn’t start at the wiki when reviewing? Maybe we should require each change in the wiki phase to also provide an objection that motivates it?
-
Now that I’ve added the driver we originally had for this (See Consent processes for meetings vs forum or other asynchronous), I think parts of the process are a bit wasteful towards this driver. We might want to delete some bits, or split them into their own documents.
I think the best use of time would be to involve the others now, by pinging/inviting and/or starting a consent decision. (Even if it makes sense to still change the proposal, it would be best to focus on what are the most important problems.) @wolftune do you want to do that? I feel less ownership since you changed quite a bit.