On 8/27/24 11:49, Brian Rosen wrote:
Can you suggest some part of our current process that should not be subject to community consensus, but can be decided by some other group (IESG, RSAB, RSWG, Secretariat, RPC Editor, Tools-team, ...)? We don’t have a mechanism to determine consensus on a web page, and I don’t think we want to create one.
Why would there be any part of our current process that shouldn't be vetted by community consensus? And even if one were identified, it seems like it should require community consensus to change it.
Keith