at least nothing that I've seen tagged on the tsc-agenda. Perhaps there's something in the nodejs/inclusivity repo I've missed?
-
-
Replying to @jasnell
probably not. most people including me have left because of feeling thwarted, unwanted, and harassed.
1 reply 1 retweet 4 likes -
Replying to @ag_dubs
well, all I can say then is that it is difficult to make progress without concrete ideas and proposals on the table.
2 replies 0 retweets 0 likes -
std::mem::transmute_copy(steve, lol) Retweeted ashley williams
i'm seeing lots of concrete ideas and proposals. https://twitter.com/ag_dubs/status/760193009614856192 … and https://twitter.com/ag_dubs/status/760193201621782528 … for example?
std::mem::transmute_copy(steve, lol) added,
2 replies 0 retweets 2 likes -
Replying to @steveklabnik
The process in Node.js core is PR/Issue driven and Consensus-Seeking. Concrete PRs/Issues are more than welcome.
@ag_dubs7 replies 0 retweets 3 likes -
Replying to @jasnell @steveklabnik
consensus-seeking strategies in overwhelmingly homogenous communities are actively not inclusive.
2 replies 2 retweets 21 likes -
consensus requires that there are shared values. consensus as a strategy is unable to change those values
1 reply 0 retweets 4 likes -
i believe
@nodejs needs to modify its shared values. it needs new strategies. consensus will not work by definition1 reply 0 retweets 4 likes -
pluralistic styles (we disagree but how can we find something we can live with) > pure consensus
1 reply 1 retweet 3 likes -
I fear leaning on BDFL to achieve goals is too fickle.
1 reply 0 retweets 0 likes
getting everyone on the same page about the goals of inclusivity needs both vision and buyin.
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.