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.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
I agree with community voting (or GitHub), except for security enhancements talks, which shouldn't be public.
I like the community group idea as well.
@Juho - Do you mean "community voting" as in "voting on the Community site?"
@brett Yes, that's what I meant.
- Previous
- 1
- 2
- Next
You must log in to post replies.