Second Contribution by Devansh Raizada

[DevanshRaizada]

Name: Devansh Raizada Projects analyzed: HoloViz | FluxML Governance Model Links: Project 1 HoloViz Project 2 FluxML HoloViz Governance Model Overview- HoloViz governance has two levels - the HoloViz Organization and the individual HoloViz Projects. Some of the key attributes in the model are credibility, inclusion, and joint responsibility. It divides the roles in the following manner:

1. Contributors
2. Maintainers
3. Lead Maintainer
4. Project Coordinator

FluxML Governance Model Overview- FluxML has a governance model based on meritocracy and is run by its community. Some of the key attributes in the model are inclusivity, diversity, and simplicity. It divides the roles in the following manner:

1. Project Contributors
2. Steering Council
3. Advisory Committee
4. Community

Analysis of the two Models- Both HoloViz and FluxML both have a different governance model structure serving their unique purposes but still, have the following similarities. Similarities:

• Both models are open-source, community-based, and inclusive of people from all backgrounds.
• Both models strictly follow the NumFocus code of conduct
• Both are developed keeping development machine learning in mind.
• Both models provide a clear & detailed explanation of the roles and responsibilities of each member.
• Both models provide complete documentation ad supportive groups.

There are some differences in the decision-making process of both organizations. Differences:

• Project Roles: HoloViz has maintainers, a lead maintainer, and a project director in addition to the contributors. Whereas FluxML has an Advisory Committee and a council in addition to the contributors.
• Decision-making: HoloViz governance model can be amended with a 2/3 majority whereas FluxML just requires a simple majority.
• Privileges: In HoloViz only the project director gets the privilege of veto whereas in FluxML the Steering Council has extra decision-making power.
• Special Guidelines/Roles: In HoloViz any names, trademarks, logos, or goodwill developed by and associated with the Project (the "Marks") are controlled by the Organization. Fiscal decisions are taken by the Committee in the FluxML model. There is also a special guideline for when a Conflict of Interest arises.

My Take- Both HoloViz and FluxML have great governance models with different purposes, providing extensive tools for Jupyter Notebook which helps in learning python and low-level control over the training process for academics and developers. Both models have their own pluses & minus. Which model is better ultimately boils down to the requirements, goals, and mission of the project.

[DevanshRaizada]

Hi @arliss-NF this is my second contribution kindly review, Thanks!!