> busy
The article mentions that you as the rfc creator ultimately takes the decision how to go forward, and should not seek consensus.
from the post:
> The process seeks a consent-based environment, not a
> consensus-based one. If some people care about a topic a
> lot and come up with a written document that explains many
> things in detail, everyone can (and should) trust them.
> The authors shouldn't wait for everyone's confirmation of
> their proposal. When they get enough feedback, they should
> be able to continue further with or abandon the idea. It's
> their decision. Since they prepared the doc and collected
> many comments on it, they can have a better judgment.
> busy
The article mentions that you as the rfc creator ultimately takes the decision how to go forward, and should not seek consensus.
from the post:
> The process seeks a consent-based environment, not a
> consensus-based one. If some people care about a topic a
> lot and come up with a written document that explains many
> things in detail, everyone can (and should) trust them.
> The authors shouldn't wait for everyone's confirmation of
> their proposal. When they get enough feedback, they should
> be able to continue further with or abandon the idea. It's
> their decision. Since they prepared the doc and collected
> many comments on it, they can have a better judgment.