The HoloViz project (formally known as PyViz) is managed using a shared governance model, which means that the project is open to contributions from anyone, regardless of background or experience. The governance model for HoloViz is based on transparency, inclusivity, and shared responsibility, with all members of the community having an equal say in the direction of the project. Contributions are evaluated based on their technical merit and alignment with the project's goals. Decisions are made through consensus, with all members of the community having an equal say in the direction of the project. HoloViz’s tools include Panel, HvPlot, HoloViews, GeoViews, DataShader, and more.
The contributing page outlines the steps involved in contributing to HoloViz, including how to set up a development environment, how to submit a contribution, and how to get involved in the community. The governance model for HoloViz is based on transparency, inclusivity, and shared responsibility, with all members of the community having an equal say in the direction of the project. Contribution ranges from as low as making a simple edit in documentation, writing about the project in blog posts, or starting a discussion to forking the repository and writing codes. The benefits go as far as even landing a job. A contributor is encouraged to open new issues and link PRs for contributions unless it is something as easy as a little documentation.
The HoloViz organization consists of two teams. The team that is in charge of contents and those in charge of attending to issues opened on the HoloViz project. They are referred to as HoloViz dev and Triaging team respectively. The data storage buckets are managed by Jean-Luc Steven(@jlstevens) and Philipp Rudiger (@philippjfr) and are both accessible on their GitHub pages using those handles. Phillip is also in charge of the HoloViz Discourse forum. Communication can be done via issues and PRs on GitHub, through PyViz Gitters, or through a meeting held openly and welcome to every contributor. A link to the google calendar can be easily found on the community page.
Finding and understanding the Governance Model was easy for me. It just took reading and digging a little deep. It was easy to find and understand the governance model.
Name: Qudirah Alimi Project Assigned: HoloViz
Links
Community Page: https://holoviz.org/community.html Contribution Page: https://holoviz.org/contributing.html Main Page: https://holoviz.org/ GitHub Page: https://github.com/holoviz/holoviz/issues
HoloViz
The HoloViz project (formally known as PyViz) is managed using a shared governance model, which means that the project is open to contributions from anyone, regardless of background or experience. The governance model for HoloViz is based on transparency, inclusivity, and shared responsibility, with all members of the community having an equal say in the direction of the project. Contributions are evaluated based on their technical merit and alignment with the project's goals. Decisions are made through consensus, with all members of the community having an equal say in the direction of the project. HoloViz’s tools include Panel, HvPlot, HoloViews, GeoViews, DataShader, and more.
The contributing page outlines the steps involved in contributing to HoloViz, including how to set up a development environment, how to submit a contribution, and how to get involved in the community. The governance model for HoloViz is based on transparency, inclusivity, and shared responsibility, with all members of the community having an equal say in the direction of the project. Contribution ranges from as low as making a simple edit in documentation, writing about the project in blog posts, or starting a discussion to forking the repository and writing codes. The benefits go as far as even landing a job. A contributor is encouraged to open new issues and link PRs for contributions unless it is something as easy as a little documentation.
The HoloViz organization consists of two teams. The team that is in charge of contents and those in charge of attending to issues opened on the HoloViz project. They are referred to as HoloViz dev and Triaging team respectively. The data storage buckets are managed by Jean-Luc Steven(@jlstevens) and Philipp Rudiger (@philippjfr) and are both accessible on their GitHub pages using those handles. Phillip is also in charge of the HoloViz Discourse forum. Communication can be done via issues and PRs on GitHub, through PyViz Gitters, or through a meeting held openly and welcome to every contributor. A link to the google calendar can be easily found on the community page.
Finding and understanding the Governance Model was easy for me. It just took reading and digging a little deep. It was easy to find and understand the governance model.