Governance in the React Native Community

[rnc-archive]

Governance in the React Native Community

[brentvatne]

An update on this front: representatives from React Native partner organizations and Facebook have voted unanimously in favour of a majority voting model for making decisions that "meaningfully change the react-native-community organization". The topic we're moving on to discussing now will be "What packages belong in react-native-community?" (react-native-community/discussions-and-proposals#176). You can expect to see some updates on that shortly.

[mikehardy]

I think the key to organizational support is aligning interests between the community and the organizations. Perhaps a voting system with tiered recurring donations? I.e if company x donates y $ they can vote on prioritizing bugs.

In my house we call that "implementor's choice". It's connected to effort not money. Connected with the idea that a "good enough" solution may proceed (sometimes, and with sensitivity), then if you're doing the work - carry on. There is a sub-text there also which is that generally the bike-shedding of non-implementors that were obstructing the progress of the implementor are actually sort of Dunning-Kruger, i.e. if they were implementing they'd usually work through most of the same issues and be right to the plan they were nit-picking earlier.

The TL;DR: if you're putting in a lot effort (as an org or a contributor) you get to make some tough (possibly non-majority) calls. But explicitness and transparency and ability to gather that clout (and have it dissipate) is important if you go down that path, so that it's open

And in general having voting windows and polls isn't awful. If you're interested participate and we'll make a decision, if you can't be bothered ... plurality vs majority