This was I think in relation to our discussion around "what is the procedure to add a new flag to the compiler"
I think the goal of the MCP process was more around "big changes to the code" than "all decisions"
But we did also discuss the idea of using it for command-line flags
I don't actually think that submitting a PR has worked that well in the past -- it works ok for folks "in the know", but I think that for folks coming from outside, it's not very clear what the expectations are (e.g., I get pings about this from time to time)
Plus I think we don't always have guidance for writing reports and the like
I guess this fits into the question of "so you want to do X" in the compiler, trying to collect that information
so here is one possible workflow--
but the other possibility is just to say "don't use MCP for outward facing changes"
@pnkfelix I'm curious to get your opinion
one obvious thing: it'd be nice to move all this workflow to one bot, e.g., rfcbot could have a "second" command
that is the same as
rfcbot fcp merge except it doesn't require all the boxes to be explicitly checked
(I remember @pnkfelix you were advocating for "one process")
ok well I edited the RFC and kind of just leftit a bit vague, saying that the second process isn't enough to approve outward facing changes
but I think we should come back to this