From 1d72a15966272a726e099a9cd5896f1a01ca75c0 Mon Sep 17 00:00:00 2001 From: Kushal Kolar Date: Sat, 17 Feb 2024 01:25:53 -0500 Subject: [PATCH 1/8] Create GOVERNANCE.md --- GOVERNANCE.md | 119 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 119 insertions(+) create mode 100644 GOVERNANCE.md diff --git a/GOVERNANCE.md b/GOVERNANCE.md new file mode 100644 index 000000000..5102707ce --- /dev/null +++ b/GOVERNANCE.md @@ -0,0 +1,119 @@ +# fastplotlib governance + +The governance of fastplotlib applies to all fastplotlib related activities. This includes the fastplotlib github organization, all repositories under the fastplotlib github organization, as well as any events or workshops organized by members of the fastplotlib Leadership Team. + +## Mission + +Leverage new graphics APIs and modern GPU hardware to create fast and interactive scientific visualizations using an expressive and elegant API. + +## Leadership team + +### Maintainers + +The maintainers are the core developers of fastplotlib and together have a complete understanding of the codebase. + +1. [Kushal Kolar](https://github.com/kushalkolar) +1. [Caitlin Lewis](https://github.com/clewis7) + + +### Advisory Committee + +The advisory committee hold a significant stake in fastplotlib as determined by the **Maintainers**. The responsibilities of the **Advisory Committee** are to 1) attend a yearly roadmap meeting, 2) be available for conflict resolution. + +1. Eric Thomson +1. Guillaume Viejo +1. Andrea Giovannucci +1. John Pearson + +### Neutral moderator + +No voting power, has no stake in the fastplotlib project + +* Reagan Bullins + +### Voting power distribution + +Maintainers: 50% + +Advisory Committee: 50% + +Veto: Any vote can be vetoed by a unanimous vote within the maintainers. + +Note that currently the voting power is primarily held by the maintainers - Kushal Kolar & Caitlin Lewis. This is intentional since the library is in an early stage. Knowledge of the codebase and its inner workings are predominantly held by Kushal & Caitlin, and nobody else. + +### Voting Process + +1. For the purpose of conflict resolution the leadership team must be convened by the neutral moderator. In all other situations the leadership team may be convened by one of the maintainers. +1. Once the leadership committee is convened and discussions have occurred, voting must conclude within 1 hour. +1. Voting is performed anonymously and handled solely by the neutral moderator in the case of conflict resolution, or by one of the maintainers. +1. After voting has finished, any maintainer may invoke a veto vote. If the veto succeeds, then the same item may not be voted on for 100 days. + +## Adding members to the Leadership Team + +### Confirming Maintainers + +* Given to individuals on merit basis after they have demonstrated strong expertise of the library through contributions, reviews and discussions. +* Adding a maintainer requires one of: + * a unanimous vote by current maintainers + * 75% vote within the advisory committee +* For continued membership in the maintainer group the individual has to demonstrate strong and continued alignment with the fastplotlib mission. The individual must also actively commit to the repo, respond to issues, and review pull requests. +* The membership is for an individual, not a company or organization. +* There must always be a minimum of 2 maintainers. +* A maintainer may be removed by one of: + * 60% vote within the maintainers + * 75% vote within the advisory committee + +### Confirming an advisory committee member + +* A candidate advisory committee member may only be nominated by a current maintainer or advisory committee member. +* Candidate must have used fastplotlib in their own work or library, or made contributions to fastplotlib. +* Candidate must be committed to the mission and demonstrate, with examples, how their role on the advisory committee would further the mission. +* If the Individual fulfills the above criteria they may be considered. The Leadership Team then requires an overall 80% vote to add the candidate as an advisory member. +* The membership is for an individual, not a company or organization. + * 60% vote within the maintainers + * 75% vote within the advisory committee + +## Invoking a vote from the leadership team + +### Conflict + +Anyone (absolutely anyone, not just the leadership team members) who feels that the code of conduct or governance document has been breached may invoke a vote by contacting the neutral moderator. + +#### Process + +1. Contact the neutral moderator with a description of the conflict, max of 250 words. +2. Neutral moderator must schedule a vote within 15 days. If that is not possible then within the next 45 days. +3. If there is a special case that requires urgency, such as upcoming events, workshops, etc., the neutral moderator may try to schedule a vote ASAP. Exercising this urgency is solely at the discretion of the neutral moderator. +4. The individual who has invoked the conflict vote can choose to present their case, or they may choose to let the neutral moderator represent them. + * Every individual involved in the conflict is given a maximum of 15 minutes to be represented. This time limit may be expanded at the discretion of the neutral moderator if a justifiable reason is provided. +5. The Leadership Team votes on one of the actions from “Enforcement Guidelines”: https://www.contributor-covenant.org/version/2/1/code_of_conduct/. It is advised that the first offense leads to action (1) “Correction” and then go down the list for repeated conflicts from the same individual/organization. Very bad behavior, as determined by the leadership team, can justify a first offense resulting in (3) “Temporary Ban” or (4) “Permanent Ban”. +6. Voting is performed as described in the section **Voting Process**. + +### Adding a member to the leadership team +1. A current maintainer or advisory committee member may nominate a candidate and then contact the neutral moderator with a written summary, of no more than 100 words, with reasons for adding the candidate to the Leadership Team. +1. The nominator should specify whether the candidate should be a maintainer or advisory committee member. +1. The neutral moderator must then schedule a vote within 100 days. +1. The nominator and candidate may then speak for no more than 10 minutes each on why the candidate should be added to the leadership team. +1. Voting is performed as described in the section **Voting Process**. + +## Changes to this governance document + +#### Until February 28, 2025 + +During early stages of fastplotlib development, changes to the governance document may be made directly through unanimous approval by the original maintainers, Kushal Kolar & Caitlin Lewis, without contacting the neutral moderator. + +#### After February 28, 2025 + +Any member of the leadership team can propose changes to the governance document. Approving the changes requires a 75% vote within the maintainers and a 75% vote within the advisory committee. + +## Reasons for invoking a vote + +Things that can be voted on include but aren’t limited to: +1. Nominating a member to the leadership team +1. Adding a nominee to the leadership team +1. Removing a member from the leadership team +1. Banning any person (not just leadership team members) or organization from interacting with the fastplotlib github repository and/or fastplotlib github organization. +1. Appeal to un-ban a previously banned person or organization. + * Can only occur 3 months after the initial ban + * Person must contact the neutral moderator directly to start an appeal + * Maximum of 3 appeal attempts are allowed From 30cc44eb6a9eede3d234e206e8d11cab699b89e2 Mon Sep 17 00:00:00 2001 From: Kushal Kolar Date: Sat, 17 Feb 2024 02:28:10 -0500 Subject: [PATCH 2/8] Update GOVERNANCE.md --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 5102707ce..8c4f9b3cf 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -100,7 +100,7 @@ Anyone (absolutely anyone, not just the leadership team members) who feels that #### Until February 28, 2025 -During early stages of fastplotlib development, changes to the governance document may be made directly through unanimous approval by the original maintainers, Kushal Kolar & Caitlin Lewis, without contacting the neutral moderator. +During early stages of fastplotlib development, changes to the governance document may be made directly through unanimous approval by the original maintainers, Kushal Kolar & Caitlin Lewis, without contacting the neutral moderator or consulting with the advisory committee. They (Kushal & Caitlin) may also add new members to the advisory committee through unanimous approval. #### After February 28, 2025 From 5ac4c9c05e510e8735751d2d643f1b09e9b00119 Mon Sep 17 00:00:00 2001 From: Kushal Kolar Date: Tue, 20 Feb 2024 14:30:04 -0500 Subject: [PATCH 3/8] Apply suggestions from code review Co-authored-by: Caitlin Lewis <69729525+clewis7@users.noreply.github.com> --- GOVERNANCE.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 8c4f9b3cf..1abd48611 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -1,12 +1,12 @@ # fastplotlib governance -The governance of fastplotlib applies to all fastplotlib related activities. This includes the fastplotlib github organization, all repositories under the fastplotlib github organization, as well as any events or workshops organized by members of the fastplotlib Leadership Team. +The governance of fastplotlib applies to all fastplotlib related activities. This includes the fastplotlib GitHub organization, all repositories under the fastplotlib GitHub organization, as well as any events or workshops organized by members of the fastplotlib Leadership Team. ## Mission Leverage new graphics APIs and modern GPU hardware to create fast and interactive scientific visualizations using an expressive and elegant API. -## Leadership team +## Leadership Team ### Maintainers @@ -18,7 +18,7 @@ The maintainers are the core developers of fastplotlib and together have a compl ### Advisory Committee -The advisory committee hold a significant stake in fastplotlib as determined by the **Maintainers**. The responsibilities of the **Advisory Committee** are to 1) attend a yearly roadmap meeting, 2) be available for conflict resolution. +The Advisory Committee hold a significant stake in fastplotlib as determined by the **Maintainers**. The responsibilities of the **Advisory Committee** are to 1) attend a yearly Roadmap meeting, 2) be available for conflict resolution. 1. Eric Thomson 1. Guillaume Viejo @@ -27,7 +27,7 @@ The advisory committee hold a significant stake in fastplotlib as determined by ### Neutral moderator -No voting power, has no stake in the fastplotlib project +No voting power, has no stake in the fastplotlib project. * Reagan Bullins @@ -43,8 +43,8 @@ Note that currently the voting power is primarily held by the maintainers - Kush ### Voting Process -1. For the purpose of conflict resolution the leadership team must be convened by the neutral moderator. In all other situations the leadership team may be convened by one of the maintainers. -1. Once the leadership committee is convened and discussions have occurred, voting must conclude within 1 hour. +1. For the purpose of conflict resolution the Leadership Team must be convened by the neutral moderator. In all other situations the Leadership Team may be convened by one of the maintainers. +1. Once the Leadership Team is convened and discussions have occurred, voting must conclude within 1 hour. 1. Voting is performed anonymously and handled solely by the neutral moderator in the case of conflict resolution, or by one of the maintainers. 1. After voting has finished, any maintainer may invoke a veto vote. If the veto succeeds, then the same item may not be voted on for 100 days. @@ -104,15 +104,15 @@ During early stages of fastplotlib development, changes to the governance docume #### After February 28, 2025 -Any member of the leadership team can propose changes to the governance document. Approving the changes requires a 75% vote within the maintainers and a 75% vote within the advisory committee. +Any member of the Leadership Team can propose changes to the governance document. Approving the changes requires a 75% vote within the maintainers and a 75% vote within the advisory committee. ## Reasons for invoking a vote Things that can be voted on include but aren’t limited to: -1. Nominating a member to the leadership team -1. Adding a nominee to the leadership team -1. Removing a member from the leadership team -1. Banning any person (not just leadership team members) or organization from interacting with the fastplotlib github repository and/or fastplotlib github organization. +1. Nominating a member to the Leadership Team +1. Adding a nominee to the Leadership Team +1. Removing a member from the Leadership Team +1. Banning any person (not just Leadership Team members) or organization from interacting with the fastplotlib GitHub repository and/or fastplotlib GitHub organization. 1. Appeal to un-ban a previously banned person or organization. * Can only occur 3 months after the initial ban * Person must contact the neutral moderator directly to start an appeal From 1b76169570e32e6a4055b9b38df82ac4a31bf5cc Mon Sep 17 00:00:00 2001 From: Kushal Kolar Date: Tue, 20 Feb 2024 23:56:11 -0500 Subject: [PATCH 4/8] Update GOVERNANCE.md --- GOVERNANCE.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 1abd48611..ff7b107b5 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -2,6 +2,8 @@ The governance of fastplotlib applies to all fastplotlib related activities. This includes the fastplotlib GitHub organization, all repositories under the fastplotlib GitHub organization, as well as any events or workshops organized by members of the fastplotlib Leadership Team. +The purpose of this document is to formalize the governance process used by the fastplotlib project, to clarify how decisions are made and how the various elements of our community interact. + ## Mission Leverage new graphics APIs and modern GPU hardware to create fast and interactive scientific visualizations using an expressive and elegant API. From e8876478fc472549bfaef41c86028b3caf9e4228 Mon Sep 17 00:00:00 2001 From: kushalkolar Date: Wed, 10 Apr 2024 19:37:57 -0400 Subject: [PATCH 5/8] update gov --- GOVERNANCE.md | 117 +++++++++++++++++++++++--------------------------- 1 file changed, 54 insertions(+), 63 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index ff7b107b5..3ad450dcb 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -6,116 +6,107 @@ The purpose of this document is to formalize the governance process used by the ## Mission -Leverage new graphics APIs and modern GPU hardware to create fast and interactive scientific visualizations using an expressive and elegant API. +The mission of `fastplotlib` is to leverage new graphics APIs and modern GPU hardware to create fast and interactive scientific visualizations using an expressive and elegant API. ## Leadership Team ### Maintainers -The maintainers are the core developers of fastplotlib and together have a complete understanding of the codebase. +The maintainers are the core developers of fastplotlib and together have a complete understanding of the codebase. They are also known as code-owners. + +The current maintainers are: 1. [Kushal Kolar](https://github.com/kushalkolar) 1. [Caitlin Lewis](https://github.com/clewis7) +Responsibilities: + +* Carry out the `fastplotlib` mission. +* Work towards completion of the roadmap. +* Timely responses to issues and pull requests. +* Code review. +* Attend a yearly Roadmap meeting. +* Be available for conflict resolution. ### Advisory Committee -The Advisory Committee hold a significant stake in fastplotlib as determined by the **Maintainers**. The responsibilities of the **Advisory Committee** are to 1) attend a yearly Roadmap meeting, 2) be available for conflict resolution. +The Advisory Committee holds a significant interest in fastplotlib as determined solely by the **Maintainers**. The responsibilities of the **Advisory Committee** are to 1) attend a yearly Roadmap meeting, 2) be available for conflict resolution. +1. Amol Pasarkar 1. Eric Thomson 1. Guillaume Viejo 1. Andrea Giovannucci 1. John Pearson +Responsibilities: + +* Help carry out the `fastplotlib` mission. +* Provide strategic guidance. +* Attend a yearly Roadmap meeting. +* Be available for conflict resolution. + ### Neutral moderator No voting power, has no stake in the fastplotlib project. * Reagan Bullins -### Voting power distribution +Responsibilities: + +* Facilitate conflict resolution without voting power. + +## Adding a member to the advisory committee +1. Only individuals, not organizations, may be added to the leadership team. A candidate individual must be nominated by a current member of the leadership team. +2. A candidate must: + * Be committed to the fastplotlib mission. + * Have demonstrated contibutions to `fastplotlib` through one of: + * Significant contributions to the codebase. + * Significant application of fastplotlib in a dependent package. + * Significant technical guidance or feedback on the development of `fastplotlib`. -Maintainers: 50% +## Adding a maintainer -Advisory Committee: 50% +Candidate maintainers must have demonstrated prolonged and significant contributions to the codebase over a long period of time. A candidate can be nominated by any current maintainer. The candidate may then be added as a maintainer through a unanimous vote within the current maintainers. -Veto: Any vote can be vetoed by a unanimous vote within the maintainers. +## Decision making -Note that currently the voting power is primarily held by the maintainers - Kushal Kolar & Caitlin Lewis. This is intentional since the library is in an early stage. Knowledge of the codebase and its inner workings are predominantly held by Kushal & Caitlin, and nobody else. +Decisions about the future of the project are made through discussion with all members of the community. All non-sensitive project management discussion takes place on the issue tracker. Occasionally, sensitive discussions may occur on a private core developer medium. -### Voting Process +Decisions should be made in accordance with the mission and code of conduct of the `fastplotlib` project. -1. For the purpose of conflict resolution the Leadership Team must be convened by the neutral moderator. In all other situations the Leadership Team may be convened by one of the maintainers. -1. Once the Leadership Team is convened and discussions have occurred, voting must conclude within 1 hour. -1. Voting is performed anonymously and handled solely by the neutral moderator in the case of conflict resolution, or by one of the maintainers. -1. After voting has finished, any maintainer may invoke a veto vote. If the veto succeeds, then the same item may not be voted on for 100 days. +We use a “consensus seeking” process for making decisions. The Leadership Team tries to find a resolution that has no open objections among Leadership Team members. Leadership Team members are expected to distinguish between fundamental objections to a proposal and minor perceived flaws that they can live with, and not hold up the decision-making process for the latter. If no option can be found without objections, the decision is escalated to the maintainers who have ultimate authority. -## Adding members to the Leadership Team +Decisions are made according to the following rules: -### Confirming Maintainers +Minor documentation changes, such as typo fixes, or addition / correction of a sentence, require approval by a maintainer and no disagreement or requested changes by other maintainers on the issue or pull request page via lazy consensus. Pull-request authors are expected to give “reasonable time” to others to give their opinion on the pull request if they’re not confident others would agree. -* Given to individuals on merit basis after they have demonstrated strong expertise of the library through contributions, reviews and discussions. -* Adding a maintainer requires one of: - * a unanimous vote by current maintainers - * 75% vote within the advisory committee -* For continued membership in the maintainer group the individual has to demonstrate strong and continued alignment with the fastplotlib mission. The individual must also actively commit to the repo, respond to issues, and review pull requests. -* The membership is for an individual, not a company or organization. -* There must always be a minimum of 2 maintainers. -* A maintainer may be removed by one of: - * 60% vote within the maintainers - * 75% vote within the advisory committee +Code changes and major documentation changes require agreement by one maintainer and no disagreement or requested changes by other maintainers on the issue or pull-request page (lazy consensus). For all changes of this type, maintainers are expected to give “reasonable time” after approval and before merging for others to weigh in on the pull request in its final state. -### Confirming an advisory committee member +Changes to the API principles require a dedicated issue on our issue tracker and follow the decision-making process outlined above. -* A candidate advisory committee member may only be nominated by a current maintainer or advisory committee member. -* Candidate must have used fastplotlib in their own work or library, or made contributions to fastplotlib. -* Candidate must be committed to the mission and demonstrate, with examples, how their role on the advisory committee would further the mission. -* If the Individual fulfills the above criteria they may be considered. The Leadership Team then requires an overall 80% vote to add the candidate as an advisory member. -* The membership is for an individual, not a company or organization. - * 60% vote within the maintainers - * 75% vote within the advisory committee +Changes to this governance model or our mission, vision, and values require a dedicated issue on our issue tracker and follow the decision-making process outlined above. -## Invoking a vote from the leadership team +If an objection is raised on a lazy consensus, the proposer can appeal to the Leadership Team and the change can be approved or rejected by escalating to the maintainers. -### Conflict +## Conflict Resolution Anyone (absolutely anyone, not just the leadership team members) who feels that the code of conduct or governance document has been breached may invoke a vote by contacting the neutral moderator. -#### Process +### Process 1. Contact the neutral moderator with a description of the conflict, max of 250 words. 2. Neutral moderator must schedule a vote within 15 days. If that is not possible then within the next 45 days. -3. If there is a special case that requires urgency, such as upcoming events, workshops, etc., the neutral moderator may try to schedule a vote ASAP. Exercising this urgency is solely at the discretion of the neutral moderator. -4. The individual who has invoked the conflict vote can choose to present their case, or they may choose to let the neutral moderator represent them. +3. The individual who has invoked the conflict vote can choose to present their case, or they may choose to let the neutral moderator represent them. * Every individual involved in the conflict is given a maximum of 15 minutes to be represented. This time limit may be expanded at the discretion of the neutral moderator if a justifiable reason is provided. -5. The Leadership Team votes on one of the actions from “Enforcement Guidelines”: https://www.contributor-covenant.org/version/2/1/code_of_conduct/. It is advised that the first offense leads to action (1) “Correction” and then go down the list for repeated conflicts from the same individual/organization. Very bad behavior, as determined by the leadership team, can justify a first offense resulting in (3) “Temporary Ban” or (4) “Permanent Ban”. -6. Voting is performed as described in the section **Voting Process**. +4. The maintainers vote on one of the actions from “Enforcement Guidelines”: https://www.contributor-covenant.org/version/2/1/code_of_conduct/. It is advised that the first offense leads to action (1) “Correction”. Repeated or serious offenses from the same individual/organization may lead to escalating levels of actions. Very bad behavior, as determined by the leadership team, can justify a first offense resulting in (3) “Temporary Ban” or (4) “Permanent Ban”. +5. The advisory committee members may advise on the actions, but the ultimate decision is voted on by the maintainers. -### Adding a member to the leadership team -1. A current maintainer or advisory committee member may nominate a candidate and then contact the neutral moderator with a written summary, of no more than 100 words, with reasons for adding the candidate to the Leadership Team. -1. The nominator should specify whether the candidate should be a maintainer or advisory committee member. -1. The neutral moderator must then schedule a vote within 100 days. -1. The nominator and candidate may then speak for no more than 10 minutes each on why the candidate should be added to the leadership team. -1. Voting is performed as described in the section **Voting Process**. +## Transparency + +Governance decisions, meeting minutes, and voting outcomes are publicly documented and accessible. We aim for transparency to allow the broader community to understand and trust the governance process. ## Changes to this governance document -#### Until February 28, 2025 +### Until February 28, 2025 During early stages of fastplotlib development, changes to the governance document may be made directly through unanimous approval by the original maintainers, Kushal Kolar & Caitlin Lewis, without contacting the neutral moderator or consulting with the advisory committee. They (Kushal & Caitlin) may also add new members to the advisory committee through unanimous approval. - -#### After February 28, 2025 - -Any member of the Leadership Team can propose changes to the governance document. Approving the changes requires a 75% vote within the maintainers and a 75% vote within the advisory committee. - -## Reasons for invoking a vote - -Things that can be voted on include but aren’t limited to: -1. Nominating a member to the Leadership Team -1. Adding a nominee to the Leadership Team -1. Removing a member from the Leadership Team -1. Banning any person (not just Leadership Team members) or organization from interacting with the fastplotlib GitHub repository and/or fastplotlib GitHub organization. -1. Appeal to un-ban a previously banned person or organization. - * Can only occur 3 months after the initial ban - * Person must contact the neutral moderator directly to start an appeal - * Maximum of 3 appeal attempts are allowed From 9d22d624f51231c76c5b5875e62e6b53d6ba4e63 Mon Sep 17 00:00:00 2001 From: Kushal Kolar Date: Sat, 13 Apr 2024 02:15:39 -0400 Subject: [PATCH 6/8] Update GOVERNANCE.md --- GOVERNANCE.md | 1 - 1 file changed, 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 3ad450dcb..f57479816 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -34,7 +34,6 @@ The Advisory Committee holds a significant interest in fastplotlib as determined 1. Amol Pasarkar 1. Eric Thomson -1. Guillaume Viejo 1. Andrea Giovannucci 1. John Pearson From bac18773384e54459cd1f3260eefb6bff33dda22 Mon Sep 17 00:00:00 2001 From: kushalkolar Date: Mon, 15 Apr 2024 18:37:03 -0400 Subject: [PATCH 7/8] update gov --- GOVERNANCE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index f57479816..6c538079e 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -30,7 +30,7 @@ Responsibilities: ### Advisory Committee -The Advisory Committee holds a significant interest in fastplotlib as determined solely by the **Maintainers**. The responsibilities of the **Advisory Committee** are to 1) attend a yearly Roadmap meeting, 2) be available for conflict resolution. +The Advisory Committee holds a significant interest in fastplotlib as determined solely by the **Maintainers**. 1. Amol Pasarkar 1. Eric Thomson @@ -108,4 +108,4 @@ Governance decisions, meeting minutes, and voting outcomes are publicly document ### Until February 28, 2025 -During early stages of fastplotlib development, changes to the governance document may be made directly through unanimous approval by the original maintainers, Kushal Kolar & Caitlin Lewis, without contacting the neutral moderator or consulting with the advisory committee. They (Kushal & Caitlin) may also add new members to the advisory committee through unanimous approval. +During early stages of fastplotlib development, changes to the governance document may be made directly through unanimous approval by the original maintainers, Kushal Kolar & Caitlin Lewis. They (Kushal & Caitlin) may also add new members to the advisory committee through unanimous approval. From 08733b952f292628c502436c2b64ed5064b74af7 Mon Sep 17 00:00:00 2001 From: Caitlin Lewis <69729525+clewis7@users.noreply.github.com> Date: Sun, 21 Apr 2024 12:21:55 -0400 Subject: [PATCH 8/8] modify mission statement --- GOVERNANCE.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 6c538079e..27acb1c45 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -8,11 +8,20 @@ The purpose of this document is to formalize the governance process used by the The mission of `fastplotlib` is to leverage new graphics APIs and modern GPU hardware to create fast and interactive scientific visualizations using an expressive and elegant API. +`fastplotlib` aims to provide a library that allows for the following: +- Rapid prototyping and algorithm development +- Realtime analysis and visualization +- Efficient rendering of thousands of objects +- Compatibility with lazy-loading and lazy-compute objects +- Shipping dependent packages as a distributable (ex: PyInstaller) + +Ultimately, `fastplotlib` is, and will always be, a free and open-source project that belongs to the community. Our end goal is to aid in the advancement of science, and as a result, we will guide the project in a direction that best serves our community in achieving this purpose. + ## Leadership Team ### Maintainers -The maintainers are the core developers of fastplotlib and together have a complete understanding of the codebase. They are also known as code-owners. +The maintainers are the core developers of fastplotlib and together have a complete understanding of the codebase. They are also known as code-owners. At any given time, there must be a minimum of two maintainers. The current maintainers are: pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy