So as we’ve all acknowledged and agreed to change on numerous occasions now, we’re still making occasional decisions without properly reviewing them.
It feels like a good opportunity to leverage the module system, and implement formal policy that must be followed. Unless we do this, I feel things are unlikely to change. There should also be a standard way of implementing this policy across the group, so that things aren’t likely to be confused between modules.
I’ve drafted what such a policy might look like at https://communityit.etherpad.mozilla.org/18
Some thoughts on the draft, if we need such a policy and other alternatives to this, would be highly appreciated. Would be great if we can get plenty of feedback before our next meeting, so we can discuss if it should be approved, since meetings are where we make group-wide decisions.
This also plays a major part into the entrance strategy for new contributors. A common question I get when we’ve tried involving new people a couple of times in the past is “can I do x so that y will work better?” and I’ve never really known how to answer. There’s nothing saying I can’t approve that, but nothing saying I can. Therefore, those questions have tended to be left to mrz or just whoever set something up, and not following our module system.