General, maybe-hypothetical question about RFCs. What does the team do when a non core team member objects to a proposal and seemingly can’t be swayed? Respectfully agree to disagree and move forward anyway? Does that even happen?
-
-
-
The projects I work on use a "steady state" rule. The core team can make a call once the conversation has reached a steady state. The important thing is that the core team makes decisions purely on the basis of rationale already debated.
-
Notably, this is an area where the core team has discretion, but the core teams in projects I work on are very hesitant to approve RFCs when there is significant community disagreement, even in the presence of a steady state. We use it as a signal to scale back or fine tune.
-
Very interesting. Thanks!
End of conversation
New conversation -
-
-
oh man, this is great. Seeing people like
@tomdale cogently explain the reasoning behind a feature really demystified Ember and its direction for me and others.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Is the specifics of the process outlined anywhere? So happy to see more communities adopt this norm
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.