Core devs: Decision making process

We've been growing our team and managing 10 individuals' thoughts and opinions is significantly more complicated than only 3 or 4. Our team's general decision making process has been to propose changes, discuss, and then if no one vetoes, go forward.

The core team has never been divided to the point of stalling out using this method, but with a growing team, I'm not convinced we should rely on that in the future. How does the other core devs and contributors feel about switching to a more formal voting process like PHP has for RFCs: https://wiki.php.net/rfc/automatic_property_initialization

This would also publicize the discussion around our decisions.

Feedback and Planning

Feedback and Planning

Discussions about the past, present, and future of Elgg and this community site.