Both models have clearly defined roles and ways for contributions to be made and regulated.
They also have a group of decision-makers for the projects, and they were both easy to understand. When proposals are made, they are first discussed with the community, before being put to a vote. Voting is done publicly, where community members can see what is happening.
Differences
The Yellowbrick’s model is very user focused, it requires coordinators, and maintainers to welcome new users, and actively engage with users in the community. It was easier to find.
It also has a mentor-contributor role which makes sure new contributors are carried along with the rest of the community and they do not feel lost.
Django's model does not explicitly make provisions for beginners, but it does encourage everyone to participate in the discussions in their public forum, assist each other, and be active contributors, it also has an honorary role that serves as a reward system for active contributors who meet a certain criteria.
Conclusion
While I appreciate the beginner-friendly focused approach of Yellowbrick’s model, I will say I prefer Django’s model for the following reasons;
They clearly define everything included in their model, including the decision making process, leaving little to no room for ambiguity and confusion.
Any community member with an idea is allowed to put forth a proposal, as opposed to only advisors being able to put forth proposals at Yellowbrick.
When proposals are made at Django, it is discussed then put to a vote. With the Yellowbrick’s model, the chair still single-handedly gets to decide if at all it gets to be put to a vote at all.
If there is a tie, the process is to vote again at Django, but at Yellow-brick the chair gets the final say with the tie-breaking vote.
Overall, the Django has a more open process, that strongly encourages community participation, which is more on theme with being open-source, as opposed to Yellowbrick’s model where the chair single-handedly decides some things
Name: Imaobong Njokko
The 2 governance models I will be analysing for this issue are;
Project 1- Django Open Source Project Project 2- Yellowbrick Project
Similarities
Both models have clearly defined roles and ways for contributions to be made and regulated. They also have a group of decision-makers for the projects, and they were both easy to understand. When proposals are made, they are first discussed with the community, before being put to a vote. Voting is done publicly, where community members can see what is happening.
Differences
The Yellowbrick’s model is very user focused, it requires coordinators, and maintainers to welcome new users, and actively engage with users in the community. It was easier to find. It also has a mentor-contributor role which makes sure new contributors are carried along with the rest of the community and they do not feel lost.
Django's model does not explicitly make provisions for beginners, but it does encourage everyone to participate in the discussions in their public forum, assist each other, and be active contributors, it also has an honorary role that serves as a reward system for active contributors who meet a certain criteria.
Conclusion
While I appreciate the beginner-friendly focused approach of Yellowbrick’s model, I will say I prefer Django’s model for the following reasons;
Overall, the Django has a more open process, that strongly encourages community participation, which is more on theme with being open-source, as opposed to Yellowbrick’s model where the chair single-handedly decides some things