The Yellowbrick project is an open source Python library for machine learning and visual analysis and diagnostics. The library combines scikit-learn and matplotlib to produce visualizations for machine learning workflow. The Yellowbrick project is also referred to as 'scikit-yellobrick' or 'scikit-yb'. With thousands of users, collaborators, and affiliated organizations, the Yellowbrick project continues to expand significantly, necessitating a need for constant maintenance. The purpose of this project's governance is to provide a structure that clearly defines how Yellowbrick members will administer, organize, and maintain the project.
The Project Roles
All Yellowbrick project contributors are users. Active contributors are defined in a very specific and time-limited manner as such, contributors must be individuals who represent themselves and not companies.
The different project roles are listed and briefly explained in the list below:
Advisors - they are contributors who take on the responsibility of setting the vision and direction for the development of the project; the primary decision making body.
Maintainers - actively manage Yellowbrick development and are primarily responsible for building and deploying the next release
Core-contributors - work with the maintainers to ensure the library is at the highest quality.
Coordinators - specialize in the project management aspects of a version release and also direct traffic to the actively participating group.
Mentor contributors - guide a new contributor in understanding the community, roles, ethos, expectations, systems, and processes in participating and contributing to the Yellowbrick project.
The Decision Making Process
The advisors conduct at least three meetings a year to make decisions. The chair must confirm the availability of all advisors before scheduling these meetings and make sure to include as many advisors as possible, putting into consideration both remote and in-person advisors.
Before voting, members are allowed a minimum of five minutes to speak in favor of or against the proposal. After receiving a vote proposal from one of the advisors, the chair decides whether a vote may be held or seconded by another advisor to hold a vote on the issue.
Votes may take place in two ways; by secret ballot or counting of individual votes.If the majority of advisors vote 'yea', the proposal is passed; if they vote "nay," it is rejected.
The proposal can only be approved if it is agreed by the founders who have the final say in all decision making. Minutes should be prepared by the secretary and made public to the rest of the Yellowbrick community.
Ease / Difficulty to Find and Understand the Governance Model
The governance model was easy to locate on their documentation page. Understanding the model however, took me a while as I am new to it. I was able to put up this contribution together through research, the documentation and the guidelines clearly stated out.
Name: Khairat Ayinde Project Assigned: Yellowbrick Link to Yellowbrick Governance Model: https://www.scikit-yb.org/en/latest/governance/index.html
Yellowbrick Governance Model
The Yellowbrick project is an open source Python library for machine learning and visual analysis and diagnostics. The library combines scikit-learn and matplotlib to produce visualizations for machine learning workflow. The Yellowbrick project is also referred to as 'scikit-yellobrick' or 'scikit-yb'. With thousands of users, collaborators, and affiliated organizations, the Yellowbrick project continues to expand significantly, necessitating a need for constant maintenance. The purpose of this project's governance is to provide a structure that clearly defines how Yellowbrick members will administer, organize, and maintain the project.
The Project Roles
All Yellowbrick project contributors are users. Active contributors are defined in a very specific and time-limited manner as such, contributors must be individuals who represent themselves and not companies. The different project roles are listed and briefly explained in the list below:
The Decision Making Process
The advisors conduct at least three meetings a year to make decisions. The chair must confirm the availability of all advisors before scheduling these meetings and make sure to include as many advisors as possible, putting into consideration both remote and in-person advisors. Before voting, members are allowed a minimum of five minutes to speak in favor of or against the proposal. After receiving a vote proposal from one of the advisors, the chair decides whether a vote may be held or seconded by another advisor to hold a vote on the issue. Votes may take place in two ways; by secret ballot or counting of individual votes.If the majority of advisors vote 'yea', the proposal is passed; if they vote "nay," it is rejected. The proposal can only be approved if it is agreed by the founders who have the final say in all decision making. Minutes should be prepared by the secretary and made public to the rest of the Yellowbrick community.
Ease / Difficulty to Find and Understand the Governance Model
The governance model was easy to locate on their documentation page. Understanding the model however, took me a while as I am new to it. I was able to put up this contribution together through research, the documentation and the guidelines clearly stated out.