Our model to gather feedback on an idea is to discuss it at a design summit... I realize those only occur every 6 months so it's not applicable for things that _need_ to land quickly, but for all others, that's the way to go (faster consensus than MLs)
The second best model (for things that need to land quickly) is to use the ML... Adding one more review to the review queue to get feedback on a proof-of-concept sounds a bit counter-productive at that point in the cycle, and more people read the MLs than the merge proposal queue.
For this idea in particular, that sounds like a good discussion to have at a summit in Santa Clara, if you'll be there.
Our model to gather feedback on an idea is to discuss it at a design summit... I realize those only occur every 6 months so it's not applicable for things that _need_ to land quickly, but for all others, that's the way to go (faster consensus than MLs)
The second best model (for things that need to land quickly) is to use the ML... Adding one more review to the review queue to get feedback on a proof-of-concept sounds a bit counter-productive at that point in the cycle, and more people read the MLs than the merge proposal queue.
For this idea in particular, that sounds like a good discussion to have at a summit in Santa Clara, if you'll be there.