On Fri, 15 Jul 2022 18:06:58 -0400 "Ricardo Signes" <perl.p5p@rjbs.manxome.org> wrote: > You are taking the temperature of the list. If there is a great outcry that this is a bad idea, or has been tried before, or was explicitly rejected before, you should probably stop. If everyone says, "Sounds great, flesh it out!" then you should write a formal RFC. Based on that feedback, either stop and go back to the drawing board, *or* write up a formal RFC. This is way too ambiguous. There are many more possible results than just "everyone hates it" and "everyone loves it". A proposal might be controversial, or perhaps the reactions will be lukewarm, or maybe it will be completely ignored. This ambiguity creates very bad incentives. It will incentivize some people to push with their RFC regardless of feedback *and* discourage others from pursuing their RFC after receiving minor, unimportant criticsm. I really think that part of the process should be more formal. The most obvious way is to have PSC decide whether a given proposal should be made into an RFC or not. Another option would be some kind of voting. But that sounds complicated. Or maybe a specified minimum number of +1 replies? I don't know.Thread Previous | Thread Next