Almost every other "burden" can be taken up by interested folks. If I really really want feature X I can impl it
-
-
But, the rfc is a roadblock to doing so. I cannot impl till an RFC lands, which is not something I can force
1 reply 0 retweets 1 like -
Getting proposed features to the stage where the burden can be picked up by folx who really want is is important
2 replies 0 retweets 2 likes -
Replying to @ManishEarth @whitequark
I agree, but it is a huge amount of work, and important not to get wrong
1 reply 0 retweets 0 likes -
Replying to @nick_r_cameron @whitequark
Right, but the rfc process already lets you talk about that. You can talk about flaws in the rfc.
1 reply 0 retweets 0 likes -
You can propose not-yet-fleshed-out strawman alternatives for folks to discuss.
2 replies 0 retweets 0 likes -
Replying to @ManishEarth @whitequark
both of these things are quite a lot of work. We need to be able to more easily triage which rfcs deserve this
1 reply 0 retweets 1 like -
Replying to @nick_r_cameron @whitequark
This sort of cycles back to the BDFL thing again. The community has no control over this. Only the teams.
3 replies 0 retweets 0 likes -
Replying to @ManishEarth @whitequark
the roadmap is meant to be the North Star that guides the triage, and the community has lots of input into that
2 replies 0 retweets 0 likes -
Despite good intentions, the "lots of input" from community had little practical effect, AFAICT.
1 reply 0 retweets 1 like
In particular, we didn't understand practical consequences of something not being on the roadmap.
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.