First Contribution by Devansh Raizada

[DevanshRaizada]

Name: Devansh Raizada Project Assigned: HoloViz

Important links for reference: Community Page Contribution Page Main Page GitHub Page Governance Summary Organization Charter Governance Model

HoloViz The HoloViz project is based on a shared governance model, which means contributions are welcomed by everyone belonging to any background and expertise. HoloViz functions like a community in which everyone has their say and follows attributes like credibility, inclusion, and joint responsibility. The HoloViz project was formerly known as PyViz.

Contributions of any magnitude are welcome ranging from a small grammatical error or writing a piece on the internet to major changes according to the need and your capabilities. The new contributors are encouraged to first set up the correct environment and then start small contributions growing gradually on the way. There are many benefits of contributing ranging from the benefits of HoloViz and your skill growth to you earning major sums. The HoloViz governance has two levels - the HoloViz Organization and the individual HoloViz Projects.

The project member roles in HoloViz are divided into the following fashion. 1)The Project Roles (i)Contributors: These are those people who have at least made one contribution to the project. The definition of a contribution ranges from submitting, reviewing, and discussing GitHub Pull Requests and issues to sharing their opinion in public forums in important discussions.

(ii)Maintainer: These are also contributors with some extra responsibilities and power. Maintainers are responsible for developing, maintaining, and updating the project. They have Github permissions like merge permission. They are added and removed to the list by mutual agreement voting process in a cycle of 3 months.

(iii)Lead Maintainer: A lead maintainer is also a maintainer with additional responsibilities who are elected or removed by a voting process in the maintainers. A lead maintainer is a person who is highly involved in all aspects of the project such as advocacy, planning, support, review, and development.

(iv)Project Director: Director is a person who gives overall direction to the project in addition to the responsibilities of a maintainer. The director is expected to follow the vote of the maintainers but has the power to veto the verdict with a written explanation. The maintainers can override the veto with a 3/4 vote in their favor and can elect or remove a director with 4/5 votes.

2)Decision Making-

(i)Consensus-Based Decision Making: The maintainers are the ones involved in the decision-making process and are expected to have an explicit agreement through consensus. In general, the consensus is defined by the absence of strong objections. If consensus cannot be reached, the Maintainers will decide by vote.

(ii)Voting: A maintainer can call for a vote with reasonable notice and set a deadline(minimum of 3 working days). The maintainers are explained how to vote and have one vote for each which is publically accessible.

(iii)Appeal Process: Decisions may be appealed by opening an issue. Maintainers will judge on the appeal. If still unsatisfied the appeal may be brought before the Organization Steering Committee.

(iv)Quorum: Unless otherwise stated, a quorum for a vote can be met with the participation of at least 50% of Maintainers, and at minimum, 2 participants.

3)How We Work-

(i)Openness: Participation is open to anyone whose affected by the activity. There shall be no undue financial barriers to participation.

(ii)Balance: The development process should balance the interests of Maintainers, Contributors, and other stakeholders.

(iii)Coordination and Harmonization: Good gestures shall be shown to resolve potential conflicts between releases in this project.

(iv)Consideration of Views and Objections: Prompt consideration shall be given views and objections of all maintainers and contributors.

(v)Written procedures: The documentation of any material in this project shall be given to anyone interested.

4)No Confidentiality- Information disclosed in connection with any Project activity is not confidential.

5)Trademarks- Any names, trademarks, logos, or goodwill developed by and associated with the Project (the "Marks") are controlled by the Organization.

6)Amendments- Amendments to this governance policy may be made by an affirmative vote of 2/3 of all Maintainers, with approval by the Organization's Steering Committee.

[DevanshRaizada]

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

[arliss-NF]

Hi @DevanshRaizada - this is good work. HoloViz has a large governance model and you did a great job consolidating the information.

[DevanshRaizada]

@arliss-NF Thank you so much for reviewing my contribution.