You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PySAL takes a benevolent dictator model approach to its governance while ESLint uses a consensus board approach which gives every member of the board equal votes and responsibilities as long as the project is concerned.
Another difference between both projects is in their project roles with PySAL having a Benevolent dictator, that possesses the highest power in terms of decision-making for the project, a steering council which makes decisions concerning the vision and direction the project takes, they are also responsible for appointing a new benevolent dictator in the case where the current benevolent dictator fails to choose a successor.
There is also the package maintainers role, which is made of core developers that makes proposals about package release, contents and features to be released to the steering council.
There is the release manager who takes responsibility for proposing the timing and features to be released when there is no consensus.
ESLint package contains roles such as Technical steering committee (TSC), Reviewers, Committers, and Website team members. The TSC has overall authority over the project performing a similar function as the steering council for PySAL but possessing the highest power over the project. The reviewers are community members with the power to merge pull requests from contributors as well as theirs after receiving feedback from a fellow reviewer, committer, or a member of the TSC. The committers are community members that have shown continued support and contribution to the growth of the project. Committers have pushed access to the project’s repository.
The PySAL project is a community driven and the community is fully involved in the decision-making process except a formal vote is declared and the steering committee ensures the project does not veer off its vision. However, for ESLint the TSC have overall control of the project and everything that happens to the project. Decisions are made by the TSC using consensus seeking decision model or simply majority wins, these decisions are then passed on to the community.
I believe the Benevolent Dictator model is best and the reason is that it takes a community-driven approach to decision-making and doesn’t give room for the benevolent dictator and steering committee to exercise too much power over the project. This model promotes inclusivity and a sense of ownership among the community members.
The text was updated successfully, but these errors were encountered:
Name: Benjamin Faruna Adejo
Projects Analyzed: PySAL | ESLint
PySAL governance model: https://github.com/pysal/governance
ESLint governance model: https://eslint.org/docs/latest/contribute/governance#process-for-adding-committers
PySAL takes a benevolent dictator model approach to its governance while ESLint uses a consensus board approach which gives every member of the board equal votes and responsibilities as long as the project is concerned.
Another difference between both projects is in their project roles with PySAL having a Benevolent dictator, that possesses the highest power in terms of decision-making for the project, a steering council which makes decisions concerning the vision and direction the project takes, they are also responsible for appointing a new benevolent dictator in the case where the current benevolent dictator fails to choose a successor.
There is also the package maintainers role, which is made of core developers that makes proposals about package release, contents and features to be released to the steering council.
There is the release manager who takes responsibility for proposing the timing and features to be released when there is no consensus.
ESLint package contains roles such as Technical steering committee (TSC), Reviewers, Committers, and Website team members. The TSC has overall authority over the project performing a similar function as the steering council for PySAL but possessing the highest power over the project. The reviewers are community members with the power to merge pull requests from contributors as well as theirs after receiving feedback from a fellow reviewer, committer, or a member of the TSC. The committers are community members that have shown continued support and contribution to the growth of the project. Committers have pushed access to the project’s repository.
The PySAL project is a community driven and the community is fully involved in the decision-making process except a formal vote is declared and the steering committee ensures the project does not veer off its vision. However, for ESLint the TSC have overall control of the project and everything that happens to the project. Decisions are made by the TSC using consensus seeking decision model or simply majority wins, these decisions are then passed on to the community.
I believe the Benevolent Dictator model is best and the reason is that it takes a community-driven approach to decision-making and doesn’t give room for the benevolent dictator and steering committee to exercise too much power over the project. This model promotes inclusivity and a sense of ownership among the community members.
The text was updated successfully, but these errors were encountered: