From abfb69338634069422d16c3cf33ed070b8f658aa Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Fri, 13 Oct 2023 11:41:42 -0400 Subject: [PATCH 01/19] Initial governance proposal --- GOVERNANCE.md | 75 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 75 insertions(+) create mode 100644 GOVERNANCE.md diff --git a/GOVERNANCE.md b/GOVERNANCE.md new file mode 100644 index 0000000..975c307 --- /dev/null +++ b/GOVERNANCE.md @@ -0,0 +1,75 @@ +# Vega Project Governance + +## Scope and Goals + +This governance document describes the governance model for [Vega](https://github.com/vega/vega), [Vega-Lite](https://github.com/vega/vega-lite), [Vega-Altair](https://github.com/altair-viz/altair), [Vega-Embed](https://github.com/vega/vega-embed), [Vega-Datsets](https://github.com/vega/vega-datasets), [Vega-Themes](https://github.com/vega/vega-themes), and [Vega-Tooltips](https://github.com/vega/vega-tooltip). These projects are collectively referred to as the "Vega projects" in this document. The Vega projects are spread across the [vega](https://github.com/vega) and [altair-viz](https://github.com/altair-viz) GitHub organizations. + +Our goal is to encourage a diverse community of contributors and users to participate in the development of the Vega projects. + +## People + +We define three levels of people in the Vega projects: contributors, maintainers, and admins. We expect everyone to adhere to our [Code of Conduct](CODE_OF_CONDUCT.md). + +### Contributors + +Contributors are anyone who makes a contribution to a Vega project via GitHub. This includes filing issues, sending pull requests, and participating in discussions. There are no requirements to participate and we encourage everyone to contribute. You do not have to be a maintainer to send a pull request. + +### Maintainers + +Maintainers belong to all or some subset of Vega projects. Maintainers have write access and can push directly to branches on GitHub. They are expected to follow development guidelines, review pull requests, and participate in discussions. Maintainers also have access to specific developer channels on Slack. + +To become a maintainer, a contributor must be nominated by an existing maintainer and approved by a majority of maintainers via Slack reactions within 7 days (simple majority of responses). A new maintainer should be added to 1) the GitHub team, 2) the Slack channel, and 3) the appropriate list below. We want more people to become maintainers and lower the barrier the enter. If you are interested in becoming a maintainer, please reach out to an existing maintainer. + +Maintainers who are inactive for more than six months may be removed from the maintainer list. + +[Admins](#admins) are also maintainers. + +#### [Vega](https://github.com/vega) GitHub Organization Maintainers + +* @fandu-db +* @joelostblom +* @jonmmease +* @keckelt +* @lsh +* @mattijn +* @yhoonkim + +#### [Altair-Viz](https://github.com/altair-viz) GitHub Organization Maintainers + +* @jonmmease + +### Admins + +Admins are maintainers who can also make releases. Admins are [owners of the GitHub organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners). + +To become an admin, a maintainer must be nominated and approved by the existing admins using the same process as for maintainers. + +Admins who are inactive for a year may be removed from the admin list. + +The current admins are: + +#### [Vega](https://github.com/vega) GitHub Organization Admins + +* @arvind +* @domoritz +* @jheer +* @kanitw + +#### [Altair-Viz](https://github.com/altair-viz) GitHub Organization Admins + +* @binste +* @ChristopherDavisUCI +* @jakevdp +* @joelostblom +* @mattijn +* @stsievert + +## Project-specific development guidelines + +Each Vega project may have its own development guidelines in a `CONTRIBUTING.md` file. For example, [Vega-Lite's contributing guide](https://github.com/vega/vega-lite/blob/main/CONTRIBUTING.md) describes design and development principles. + +## Decision-making process + +Major technical decisions should be made in public using GitHub discussions or GitHub issues. While we use [Slack](https://bit.ly/join-vega-slack-2022) for more direct discussions, any results should be documented on GitHub where they are accessible to everyone. Note that we don't pay for Slack and so any discussions disappear after 90 days. + + From 3d806f05521f0a944ea4f6f676927dbbc9d523e8 Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Fri, 13 Oct 2023 13:56:16 -0400 Subject: [PATCH 02/19] Make lukas admin --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 975c307..9648c6b 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -30,7 +30,6 @@ Maintainers who are inactive for more than six months may be removed from the ma * @joelostblom * @jonmmease * @keckelt -* @lsh * @mattijn * @yhoonkim @@ -54,6 +53,7 @@ The current admins are: * @domoritz * @jheer * @kanitw +* @lsh #### [Altair-Viz](https://github.com/altair-viz) GitHub Organization Admins From a43e082a4a3588ad6e01163d3386fd5fe2650723 Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Sat, 14 Oct 2023 10:40:52 -0400 Subject: [PATCH 03/19] Move people to new files, remove Altair for now. --- ADMINS.md | 9 ++++++++ GOVERNANCE.md | 56 ++++++++++---------------------------------------- MAINTAINERS.md | 17 +++++++++++++++ 3 files changed, 37 insertions(+), 45 deletions(-) create mode 100644 ADMINS.md create mode 100644 MAINTAINERS.md diff --git a/ADMINS.md b/ADMINS.md new file mode 100644 index 0000000..5a06311 --- /dev/null +++ b/ADMINS.md @@ -0,0 +1,9 @@ +# Admins + +This document lists the Admins of the Project. Admins may be added once approved by the existing Admins as described in the [Governance document](GOVERNANCE.md). By adding your name to this list you are agreeing to abide by the Project governance documents and to abide by all of the Organization's polices, including the [code of conduct](CODE_OF_CONDUCT.md). + +* @arvind +* @domoritz +* @jheer +* @kanitw +* @lsh diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 9648c6b..9062e4b 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -2,67 +2,35 @@ ## Scope and Goals -This governance document describes the governance model for [Vega](https://github.com/vega/vega), [Vega-Lite](https://github.com/vega/vega-lite), [Vega-Altair](https://github.com/altair-viz/altair), [Vega-Embed](https://github.com/vega/vega-embed), [Vega-Datsets](https://github.com/vega/vega-datasets), [Vega-Themes](https://github.com/vega/vega-themes), and [Vega-Tooltips](https://github.com/vega/vega-tooltip). These projects are collectively referred to as the "Vega projects" in this document. The Vega projects are spread across the [vega](https://github.com/vega) and [altair-viz](https://github.com/altair-viz) GitHub organizations. +This governance document describes the governance model for [Vega](https://github.com/vega/vega), [Vega-Lite](https://github.com/vega/vega-lite), [Vega-Embed](https://github.com/vega/vega-embed), [Vega-Datsets](https://github.com/vega/vega-datasets), [Vega-Themes](https://github.com/vega/vega-themes), and [Vega-Tooltips](https://github.com/vega/vega-tooltip). These projects are collectively referred to as the "Vega projects" in this document. The Vega projects are in the [vega](https://github.com/vega) GitHub organizations. + +The [Vega-Altair](https://github.com/altair-viz/altair) project's governance model is documented at [altair-viz/altair/governance](https://github.com/altair-viz/altair/blob/main/governance/project-docs/GOVERNANCE.md). Our goal is to encourage a diverse community of contributors and users to participate in the development of the Vega projects. -## People +## Roles -We define three levels of people in the Vega projects: contributors, maintainers, and admins. We expect everyone to adhere to our [Code of Conduct](CODE_OF_CONDUCT.md). +We define three levels of roles in the Vega projects: Contributors, Maintainers, and Admins. We expect everyone to adhere to our [Code of Conduct](CODE_OF_CONDUCT.md). ### Contributors -Contributors are anyone who makes a contribution to a Vega project via GitHub. This includes filing issues, sending pull requests, and participating in discussions. There are no requirements to participate and we encourage everyone to contribute. You do not have to be a maintainer to send a pull request. +Contributors are anyone who makes a contribution to a Vega project via GitHub. This includes filing issues, sending pull requests, and participating in discussions. There are no requirements to participate and we encourage everyone to contribute. You do not have to be a Maintainer to send a pull request. ### Maintainers -Maintainers belong to all or some subset of Vega projects. Maintainers have write access and can push directly to branches on GitHub. They are expected to follow development guidelines, review pull requests, and participate in discussions. Maintainers also have access to specific developer channels on Slack. +Maintainers belong to all or some subset of Vega projects. Maintainers are responsible for organizing activities around developing, maintaining, and updating the project. Maintainers have write access and can push directly to branches on GitHub. Maintainers also have access to specific developer channels on Slack. -To become a maintainer, a contributor must be nominated by an existing maintainer and approved by a majority of maintainers via Slack reactions within 7 days (simple majority of responses). A new maintainer should be added to 1) the GitHub team, 2) the Slack channel, and 3) the appropriate list below. We want more people to become maintainers and lower the barrier the enter. If you are interested in becoming a maintainer, please reach out to an existing maintainer. +To become a Maintainer, a contributor must be nominated by an existing Maintainer and approved by a majority of Maintainers via Slack reactions within 7 days (simple majority of responses). A new Maintainer should be added to 1) the GitHub team, 2) the Slack channel, and 3) the [maintainers.md file](MAINTAINERS.md). We want more people to become Maintainers and lower the barrier the enter. If you are interested in becoming a Maintainer, please reach out to an existing Maintainer. Maintainers who are inactive for more than six months may be removed from the maintainer list. -[Admins](#admins) are also maintainers. - -#### [Vega](https://github.com/vega) GitHub Organization Maintainers - -* @fandu-db -* @joelostblom -* @jonmmease -* @keckelt -* @mattijn -* @yhoonkim - -#### [Altair-Viz](https://github.com/altair-viz) GitHub Organization Maintainers - -* @jonmmease - ### Admins -Admins are maintainers who can also make releases. Admins are [owners of the GitHub organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners). - -To become an admin, a maintainer must be nominated and approved by the existing admins using the same process as for maintainers. +Admins are maintainers who can make and are responsible for releases. Admins are [owners of the GitHub organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners). -Admins who are inactive for a year may be removed from the admin list. +To become an Admin, a Maintainer must be nominated and approved by the existing Admins using the same process as for Maintainers. Admins are listed in the [admins.md file](ADMINS.md). -The current admins are: - -#### [Vega](https://github.com/vega) GitHub Organization Admins - -* @arvind -* @domoritz -* @jheer -* @kanitw -* @lsh - -#### [Altair-Viz](https://github.com/altair-viz) GitHub Organization Admins - -* @binste -* @ChristopherDavisUCI -* @jakevdp -* @joelostblom -* @mattijn -* @stsievert +Admins who are inactive for a year may be removed from the Admin list. ## Project-specific development guidelines @@ -71,5 +39,3 @@ Each Vega project may have its own development guidelines in a `CONTRIBUTING.md` ## Decision-making process Major technical decisions should be made in public using GitHub discussions or GitHub issues. While we use [Slack](https://bit.ly/join-vega-slack-2022) for more direct discussions, any results should be documented on GitHub where they are accessible to everyone. Note that we don't pay for Slack and so any discussions disappear after 90 days. - - diff --git a/MAINTAINERS.md b/MAINTAINERS.md new file mode 100644 index 0000000..510aea4 --- /dev/null +++ b/MAINTAINERS.md @@ -0,0 +1,17 @@ +# Maintainers + +This document lists the Maintainers of the Project. Maintainers may be added once approved by the existing maintainers as described in the [Governance document](GOVERNANCE.md). By adding your name to this list you are agreeing to abide by the Project governance documents and to abide by all of the Organization's polices, including the [code of conduct](CODE_OF_CONDUCT.md). + +* @arvind +* @domoritz +* @fandu-db +* @jheer +* @joelostblom +* @jonmmease +* @kanitw +* @keckelt +* @lsh +* @mattijn +* @yhoonkim + +The Vega-Altair project also has maintainers which are listed at [altair-viz/altair/governance/project-docs/MAINTAINERS.md](https://github.com/altair-viz/altair/blob/main/governance/project-docs/MAINTAINERS.md). From 5dcdb971622d4aa1da2a265701cbfda0219f391a Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Sun, 15 Oct 2023 09:35:14 -0400 Subject: [PATCH 04/19] Add more projects Thanks @mattijn --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 9062e4b..9ef1072 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -2,7 +2,7 @@ ## Scope and Goals -This governance document describes the governance model for [Vega](https://github.com/vega/vega), [Vega-Lite](https://github.com/vega/vega-lite), [Vega-Embed](https://github.com/vega/vega-embed), [Vega-Datsets](https://github.com/vega/vega-datasets), [Vega-Themes](https://github.com/vega/vega-themes), and [Vega-Tooltips](https://github.com/vega/vega-tooltip). These projects are collectively referred to as the "Vega projects" in this document. The Vega projects are in the [vega](https://github.com/vega) GitHub organizations. +This governance document describes the governance model for [Vega](https://github.com/vega/vega), [Vega-Lite](https://github.com/vega/vega-lite), [Vega-Embed](https://github.com/vega/vega-embed), [Vega-Datsets](https://github.com/vega/vega-datasets), [Vega-Themes](https://github.com/vega/vega-themes), [Vega-Tooltips](https://github.com/vega/vega-tooltip), [Vega-Editor](https://github.com/vega/editor), and [VL-Convert](https://github.com/vega/vl-convert). These projects are collectively referred to as the "Vega projects" in this document. The Vega projects are in the [vega](https://github.com/vega) GitHub organizations. The [Vega-Altair](https://github.com/altair-viz/altair) project's governance model is documented at [altair-viz/altair/governance](https://github.com/altair-viz/altair/blob/main/governance/project-docs/GOVERNANCE.md). From 2c609a7bb1490b24aafe5dc21d72520f8440ad48 Mon Sep 17 00:00:00 2001 From: Kanit Wongsuphasawat Date: Tue, 17 Oct 2023 10:53:13 -0700 Subject: [PATCH 05/19] fix typo --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 9ef1072..1fffd08 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -2,7 +2,7 @@ ## Scope and Goals -This governance document describes the governance model for [Vega](https://github.com/vega/vega), [Vega-Lite](https://github.com/vega/vega-lite), [Vega-Embed](https://github.com/vega/vega-embed), [Vega-Datsets](https://github.com/vega/vega-datasets), [Vega-Themes](https://github.com/vega/vega-themes), [Vega-Tooltips](https://github.com/vega/vega-tooltip), [Vega-Editor](https://github.com/vega/editor), and [VL-Convert](https://github.com/vega/vl-convert). These projects are collectively referred to as the "Vega projects" in this document. The Vega projects are in the [vega](https://github.com/vega) GitHub organizations. +This governance document describes the governance model for [Vega](https://github.com/vega/vega), [Vega-Lite](https://github.com/vega/vega-lite), [Vega-Embed](https://github.com/vega/vega-embed), [Vega-Datasets](https://github.com/vega/vega-datasets), [Vega-Themes](https://github.com/vega/vega-themes), [Vega-Tooltips](https://github.com/vega/vega-tooltip), [Vega-Editor](https://github.com/vega/editor), and [VL-Convert](https://github.com/vega/vl-convert). These projects are collectively referred to as the "Vega projects" in this document. The Vega projects are in the [vega](https://github.com/vega) GitHub organizations. The [Vega-Altair](https://github.com/altair-viz/altair) project's governance model is documented at [altair-viz/altair/governance](https://github.com/altair-viz/altair/blob/main/governance/project-docs/GOVERNANCE.md). From e787556de950f247fbbf20809bfe9e4eec04e97b Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Fri, 3 Nov 2023 14:56:03 +1000 Subject: [PATCH 06/19] Update GOVERNANCE.md Co-authored-by: Arvind Satyanarayan --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index 1fffd08..8c3b381 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -20,7 +20,7 @@ Contributors are anyone who makes a contribution to a Vega project via GitHub. T Maintainers belong to all or some subset of Vega projects. Maintainers are responsible for organizing activities around developing, maintaining, and updating the project. Maintainers have write access and can push directly to branches on GitHub. Maintainers also have access to specific developer channels on Slack. -To become a Maintainer, a contributor must be nominated by an existing Maintainer and approved by a majority of Maintainers via Slack reactions within 7 days (simple majority of responses). A new Maintainer should be added to 1) the GitHub team, 2) the Slack channel, and 3) the [maintainers.md file](MAINTAINERS.md). We want more people to become Maintainers and lower the barrier the enter. If you are interested in becoming a Maintainer, please reach out to an existing Maintainer. +To become a Maintainer, a contributor must be nominated by an existing Maintainer and approved by a majority of Maintainers via Slack reactions within 7 days (simple majority of responses). A new Maintainer should be added to 1) the GitHub team, 2) the Slack channel, and 3) the [MAINTAINERS.md file](MAINTAINERS.md). We want more people to become Maintainers and lower the barrier the entry. If you are interested in becoming a Maintainer, please reach out to an existing Maintainer. Maintainers who are inactive for more than six months may be removed from the maintainer list. From 83510f207414bbd7e2e195a3fc17f69d72106361 Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Tue, 28 Nov 2023 18:04:07 -0500 Subject: [PATCH 07/19] Updates to community docs as discussed with the steering commitee I also moved the relevant pieces from the Altair governance docs here. --- ADMINS.md | 9 ------ CHARTER.md | 63 +++++++++++++++++++++++++++++++++++++ GOVERNANCE.md | 41 ------------------------ MAINTAINERS.md | 17 ---------- README.md | 5 ++- STEERING-COMMITTEE.md | 15 +++++++++ project-docs/ADMINS.md | 27 ++++++++++++++++ project-docs/GOVERNANCE.md | 63 +++++++++++++++++++++++++++++++++++++ project-docs/MAINTAINERS.md | 33 +++++++++++++++++++ 9 files changed, 205 insertions(+), 68 deletions(-) delete mode 100644 ADMINS.md create mode 100644 CHARTER.md delete mode 100644 GOVERNANCE.md delete mode 100644 MAINTAINERS.md create mode 100644 STEERING-COMMITTEE.md create mode 100644 project-docs/ADMINS.md create mode 100644 project-docs/GOVERNANCE.md create mode 100644 project-docs/MAINTAINERS.md diff --git a/ADMINS.md b/ADMINS.md deleted file mode 100644 index 5a06311..0000000 --- a/ADMINS.md +++ /dev/null @@ -1,9 +0,0 @@ -# Admins - -This document lists the Admins of the Project. Admins may be added once approved by the existing Admins as described in the [Governance document](GOVERNANCE.md). By adding your name to this list you are agreeing to abide by the Project governance documents and to abide by all of the Organization's polices, including the [code of conduct](CODE_OF_CONDUCT.md). - -* @arvind -* @domoritz -* @jheer -* @kanitw -* @lsh diff --git a/CHARTER.md b/CHARTER.md new file mode 100644 index 0000000..8875fee --- /dev/null +++ b/CHARTER.md @@ -0,0 +1,63 @@ +# Charter for the Vega Projects + +## Scope and Goals + +This is the organizational charter for [Vega](https://github.com/vega/vega), [Vega-Lite](https://github.com/vega/vega-lite), [Vega-Altair](https://github.com/altair-viz/altair), [Vega-Embed](https://github.com/vega/vega-embed), [Vega-Datasets](https://github.com/vega/vega-datasets), [Vega-Themes](https://github.com/vega/vega-themes), [Vega-Tooltips](https://github.com/vega/vega-tooltip), [Vega-Editor](https://github.com/vega/editor), and [VL-Convert](https://github.com/vega/vl-convert). These projects are collectively referred to as the "Vega projects" in this document. + +The Vega projects are in the [vega](https://github.com/vega) and [altair-viz](https://github.com/altair-viz) GitHub organizations. + +## Mission + +The Vega projects provide an ecosystem of tools for declarative data visualizations. The various components of this ecosystem build on each other providing different levels of abstraction. + +## Steering Committee + +### Purpose + +The Steering Committee will be responsible for all technical oversight, project approval and oversight, policy oversight, and trademark management for the Organization. + +### Composition + +The Steering Committee voting members are listed in the [STEERING-COMMITTEE.md file](STEERING-COMMITTEE.md). +Voting members may be added or removed by no less than 3/4 affirmative vote of the Steering Committee. +The Steering Committee will appoint a Chair responsible for organizing Steering Committee activity. + +## Voting + +### Decision Making + +The Steering Committee will strive for all decisions to be made by consensus. While explicit agreement of the entire Steering Committee is preferred, it is not required for consensus. Rather, the Steering Committee will determine consensus based on their good faith consideration of a number of factors, including the dominant view of the Steering Committee and nature of support and objections. The Steering Committee will document evidence of consensus in accordance with these requirements. If consensus cannot be reached, the Steering Committee will make the decision by a vote. + +### Voting + +The Steering Committee Chair will call a vote with reasonable notice to the Steering Committee, setting out a discussion period and a separate voting period. Any discussion may be conducted in person or electronically by text, voice, or video. All major decisions should be documented publicly. In any vote, each voting representative will have one vote. Decisions by vote require a simple majority vote of all voting members. + +## Termination of Membership + +The membership of a Steering Committee member will terminate if any of the following occur: + +* **Resignation**. Written notice of resignation to the Steering Committee. + +* **Unreachable Member**. If a member is unresponsive at its listed handle for more than three months the Steering Committee may vote to remove the member. + +* **Code of Conduct violation**. If a member violates the Code of Conduct in a way that justifies at least a warning, the Steering Committee may vote to remove the member. + +## No Confidentiality. + +Information disclosed in connection with any of the Organization's activities, including but not limited to meetings, Contributions, and submissions, is not confidential, regardless of any markings or statements to the contrary. + +## Project Criteria + +In order to be eligible to be a Organization project, a project must: + +* Be approved by the Steering Committee. +* Agree to follow the guidance and direction of the Steering Committee. +* Use only the following outbound licenses or agreements unless otherwise approved: + - For code, a license on the Open Source Initiative's list of [Popular Licenses](https://opensource.org/licenses). + - For data, a license on the Open Knowledge Foundation's list of [Recommended Conformant Licenses](http://opendefinition.org/licenses/). + - For specifications, a community developed and maintained specification agreement, such the [Open Web Foundation Agreements](https://www.openwebfoundation.org/the-agreements) or [Community Specification Agreement](https://github.com/CommunitySpecification/1.0). +* Include and adhere to the Organization's policies, including the [code of conduct](./CODE-OF-CONDUCT.md). + +## Amendments + +Amendments to this charter, or the [code of conduct](CODE_OF_CONDUCT.md) may only be made with at least a 3/4 affirmative vote of the Steering Committee. diff --git a/GOVERNANCE.md b/GOVERNANCE.md deleted file mode 100644 index 8c3b381..0000000 --- a/GOVERNANCE.md +++ /dev/null @@ -1,41 +0,0 @@ -# Vega Project Governance - -## Scope and Goals - -This governance document describes the governance model for [Vega](https://github.com/vega/vega), [Vega-Lite](https://github.com/vega/vega-lite), [Vega-Embed](https://github.com/vega/vega-embed), [Vega-Datasets](https://github.com/vega/vega-datasets), [Vega-Themes](https://github.com/vega/vega-themes), [Vega-Tooltips](https://github.com/vega/vega-tooltip), [Vega-Editor](https://github.com/vega/editor), and [VL-Convert](https://github.com/vega/vl-convert). These projects are collectively referred to as the "Vega projects" in this document. The Vega projects are in the [vega](https://github.com/vega) GitHub organizations. - -The [Vega-Altair](https://github.com/altair-viz/altair) project's governance model is documented at [altair-viz/altair/governance](https://github.com/altair-viz/altair/blob/main/governance/project-docs/GOVERNANCE.md). - -Our goal is to encourage a diverse community of contributors and users to participate in the development of the Vega projects. - -## Roles - -We define three levels of roles in the Vega projects: Contributors, Maintainers, and Admins. We expect everyone to adhere to our [Code of Conduct](CODE_OF_CONDUCT.md). - -### Contributors - -Contributors are anyone who makes a contribution to a Vega project via GitHub. This includes filing issues, sending pull requests, and participating in discussions. There are no requirements to participate and we encourage everyone to contribute. You do not have to be a Maintainer to send a pull request. - -### Maintainers - -Maintainers belong to all or some subset of Vega projects. Maintainers are responsible for organizing activities around developing, maintaining, and updating the project. Maintainers have write access and can push directly to branches on GitHub. Maintainers also have access to specific developer channels on Slack. - -To become a Maintainer, a contributor must be nominated by an existing Maintainer and approved by a majority of Maintainers via Slack reactions within 7 days (simple majority of responses). A new Maintainer should be added to 1) the GitHub team, 2) the Slack channel, and 3) the [MAINTAINERS.md file](MAINTAINERS.md). We want more people to become Maintainers and lower the barrier the entry. If you are interested in becoming a Maintainer, please reach out to an existing Maintainer. - -Maintainers who are inactive for more than six months may be removed from the maintainer list. - -### Admins - -Admins are maintainers who can make and are responsible for releases. Admins are [owners of the GitHub organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners). - -To become an Admin, a Maintainer must be nominated and approved by the existing Admins using the same process as for Maintainers. Admins are listed in the [admins.md file](ADMINS.md). - -Admins who are inactive for a year may be removed from the Admin list. - -## Project-specific development guidelines - -Each Vega project may have its own development guidelines in a `CONTRIBUTING.md` file. For example, [Vega-Lite's contributing guide](https://github.com/vega/vega-lite/blob/main/CONTRIBUTING.md) describes design and development principles. - -## Decision-making process - -Major technical decisions should be made in public using GitHub discussions or GitHub issues. While we use [Slack](https://bit.ly/join-vega-slack-2022) for more direct discussions, any results should be documented on GitHub where they are accessible to everyone. Note that we don't pay for Slack and so any discussions disappear after 90 days. diff --git a/MAINTAINERS.md b/MAINTAINERS.md deleted file mode 100644 index 510aea4..0000000 --- a/MAINTAINERS.md +++ /dev/null @@ -1,17 +0,0 @@ -# Maintainers - -This document lists the Maintainers of the Project. Maintainers may be added once approved by the existing maintainers as described in the [Governance document](GOVERNANCE.md). By adding your name to this list you are agreeing to abide by the Project governance documents and to abide by all of the Organization's polices, including the [code of conduct](CODE_OF_CONDUCT.md). - -* @arvind -* @domoritz -* @fandu-db -* @jheer -* @joelostblom -* @jonmmease -* @kanitw -* @keckelt -* @lsh -* @mattijn -* @yhoonkim - -The Vega-Altair project also has maintainers which are listed at [altair-viz/altair/governance/project-docs/MAINTAINERS.md](https://github.com/altair-viz/altair/blob/main/governance/project-docs/MAINTAINERS.md). diff --git a/README.md b/README.md index 3a01630..71bedfa 100644 --- a/README.md +++ b/README.md @@ -1,2 +1,5 @@ # .github -Community health files for the @vega organization + +Community health files for the Vega Projects. + +The overall project charter is in [CHARTER.md](CHARTER.md). The governance documents are in [GOVERNANCE.md](project-docs/GOVERNANCE.md) in the `project-docs` folder. This folder also contains the list of admins and maintainers for the projects in the Vega organization. diff --git a/STEERING-COMMITTEE.md b/STEERING-COMMITTEE.md new file mode 100644 index 0000000..d9cbc2b --- /dev/null +++ b/STEERING-COMMITTEE.md @@ -0,0 +1,15 @@ +# Steering Committee + +This document lists the members of the Organization's Steering Committee. Voting members may be added once approved by the Steering Committee as described in the [charter](CHARTER.md). By adding your name to this list you are agreeing to abide by all Organization polices, including the [charter](CHARTER.md) and the [code of conduct](CODE_OF_CONDUCT.md). If you are serving on the Steering Committee because of your affiliation with another organization (designated below), you represent that you have authority to bind that organization to these policies. + +| **NAME** | **Handle** | **Affiliated Organization** | +| --- | --- | --- | +| Stefan Binder (Chair) | @binste | - | +| Dominik Moritz (Chair) | @domoritz | - | +| Jeffrey Heer | @jheer | - | +| Kanit Wongsuphasawat | @kanitw | - | +| Arvind Satyanarayan | @arvind | - | +| Joel Ostblom | @joelostblom | - | +| Jon Mease | @jonmmease | [Hex Technologies](https://hex.tech/) | +| Mattijn van Hoek | @mattijn | - | +| Christopher Davis | @ChristopherDavisUCI | - | diff --git a/project-docs/ADMINS.md b/project-docs/ADMINS.md new file mode 100644 index 0000000..266fa13 --- /dev/null +++ b/project-docs/ADMINS.md @@ -0,0 +1,27 @@ +# Admins + +This document lists the Admins of the Project. Admins may be added once approved by the existing Admins as described in the [Governance document](GOVERNANCE.md). By adding your name to this list you are agreeing to abide by the Project governance documents and to abide by all of the Organization's polices, including the [code of conduct](CODE_OF_CONDUCT.md). + +## Vega and Vega-Lite Admins + +This includes projects in the [vega](https://github.com/vega/) org. + +| **NAME** | **Handle** | **Affiliated Organization** | +| --- | --- | --- | +| Arvind Satyanarayan | @arvind | - | +| Dominik Moritz | @domoritz | - | +| Jeffrey Heer | @jheer | - | +| Kanit Wongsuphasawat | @kanitw | - | +| Lukas Hermann | @lsh | - | + +## Vega Altair Admins + +This includes projects in the [altair-viz](https://github.com/altair-viz/) org. + +| **NAME** | **Handle** | **Affiliated Organization** | +| --- | --- | --- | +| Christopher Davis | @ChristopherDavisUCI | - | +| Joel Ostblom | @joelostblom | - | +| Jon Mease | @jonmmease | [Hex Technologies](https://hex.tech/) | +| Mattijn van Hoek | @mattijn | - | +| Stefan Binder | @binste | - | diff --git a/project-docs/GOVERNANCE.md b/project-docs/GOVERNANCE.md new file mode 100644 index 0000000..0ece9e4 --- /dev/null +++ b/project-docs/GOVERNANCE.md @@ -0,0 +1,63 @@ +# Vega Project Governance + +This is the default project governance for the Vega Projects. Our goal is to encourage a diverse community of contributors and users to participate in the development of the Vega projects. + +Each project may override the specific roles and development guidelines in a `GOVERNANCE.md` and `CONTRIBUTING.md` file. However, all projects have to adhere to the code of conduct, the general principles outlined in this document, and the charter. + +## Roles + +We define three levels of roles in the Vega projects: Contributors, Maintainers, and Admins. We expect everyone to adhere to our [Code of Conduct](CODE_OF_CONDUCT.md). + +### Contributors + +Contributors are anyone who makes a contribution to a Vega project via GitHub. This includes filing issues, sending pull requests, and participating in discussions. There are no requirements to participate and we encourage everyone to contribute. You do not have to be a Maintainer to send a pull request. + +### Maintainers + +Maintainers belong to all or some subset of Vega projects. Maintainers are responsible for organizing activities around developing, maintaining, and updating the project. Maintainers are also responsible for determining consensus. + +Maintainers have write access and can push directly to branches on GitHub. Maintainers also have access to specific developer channels on Slack. + +To become a Maintainer, a contributor must be nominated by an existing Maintainer and approved by a majority of Maintainers via Slack reactions within 7 days (simple majority of responses). A new Maintainer should be added to 1) the GitHub team, 2) the Slack channel, and 3) the [MAINTAINERS.md file](MAINTAINERS.md). We want more people to become Maintainers and lower the barrier the entry. If you are interested in becoming a Maintainer, please reach out to an existing Maintainer. + +Maintainers who are inactive for more than six months may be removed from the maintainer list. + +### Admins + +Admins are maintainers who can make and are responsible for releases. Admins are [owners of the GitHub organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners). + +To become an Admin, a Maintainer must be nominated and approved by the existing Admins using the same process as for Maintainers. Admins are listed in the [ADMINS.md file](ADMINS.md). + +Admins who are inactive for a year may be removed from the Admin list. + +## Decisions + +Major technical decisions should be made in public using GitHub discussions or GitHub issues. While we use [Slack](https://bit.ly/join-vega-slack-2022) for more direct discussions, any results should be documented on GitHub where they are accessible to everyone. Note that we don't pay for Slack and so any discussions disappear after 90 days. + +### Consensus-Based Decision Making + +Projects make decisions through consensus of the Maintainers. While explicit agreement of all Maintainers is preferred, it is not required for consensus. Rather, the Maintainers will determine consensus based on their good faith consideration of a number of factors, including the dominant view of the Contributors and nature of support and objections. The Maintainers will document evidence of consensus in accordance with these requirements. + +### Appeal Process + +Decisions may be appealed by opening an issue and that appeal will be considered by the Maintainers in good faith, who will respond in writing within a reasonable time. If the Maintainers deny the appeal, the appeal may be brought before the Organization Steering Committee, who will also respond in writing in a reasonable time. + +## Project-Specific Development Guidelines + +Each Vega project may have its own development guidelines in a `CONTRIBUTING.md` file. For example, [Vega-Lite's contributing guide](https://github.com/vega/vega-lite/blob/main/CONTRIBUTING.md) describes design and development principles. + +## How We Work. + +**Openness**. Participation is open to anyone who is directly and materially affected by the activity in question. There shall be no undue financial barriers to participation. + +**Balance**. The development process should balance the interests of Contributors and other stakeholders. Contributors from diverse interest categories shall be sought with the objective of achieving balance. + +**Coordination and Harmonization**. Good faith efforts shall be made to resolve potential conflicts or incompatibility between releases in this Project. + +**Consideration of Views and Objections**. Prompt consideration shall be given to the written views and objections of all Contributors. + +**Written procedures**. This governance document and other materials documenting this project's development process shall be available to any interested person. + +## No Confidentiality. + +Information disclosed in connection with any Project activity, including but not limited to meetings, contributions, and submissions, is not confidential, regardless of any markings or statements to the contrary. diff --git a/project-docs/MAINTAINERS.md b/project-docs/MAINTAINERS.md new file mode 100644 index 0000000..600ce95 --- /dev/null +++ b/project-docs/MAINTAINERS.md @@ -0,0 +1,33 @@ +# Maintainers + +This document lists the Maintainers of the Project. Maintainers may be added once approved by the existing maintainers as described in the [Governance document](GOVERNANCE.md). By adding your name to this list you are agreeing to abide by the Project governance documents and to abide by all of the Organization's polices, including the [code of conduct](CODE_OF_CONDUCT.md). + +## Vega and Vega-Lite Maintainers + +This includes projects in the [vega](https://github.com/vega/) org. + +| **NAME** | **Handle** | **Affiliated Organization** | +| --- | --- | --- | +| Arvind Satyanarayan | @arvind | - | +| Dominik Moritz | @domoritz | - | +| Fan Du | @fandu-db | - | +| Jeffrey Heer | @jheer | - | +| Joel Ostblom | @joelostblom | - | +| Jon Mease | @jonmmease | [Hex Technologies](https://hex.tech/) | +| Kanit Wongsuphasawat | @kanitw | - | +| Klaus Eckelt | @keckelt | - | +| Lukas Hermann | @lsh | - | +| Mattijn van Hoek | @mattijn | - | +| Younghoon Kim | @yhoonkim | - | + +## Vega Altair Maintainers + +This includes projects in the [altair-viz](https://github.com/altair-viz/) org. + +| **NAME** | **Handle** | **Affiliated Organization** | +| --- | --- | --- | +| Christopher Davis | @ChristopherDavisUCI | - | +| Joel Ostblom | @joelostblom | - | +| Jon Mease | @jonmmease | [Hex Technologies](https://hex.tech/) | +| Mattijn van Hoek | @mattijn | - | +| Stefan Binder | @binste | - | From 11ba88b3756b2fca4f673106fb1e08b975e2cb7d Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Tue, 28 Nov 2023 18:36:36 -0500 Subject: [PATCH 08/19] Describe removing, formatting. --- project-docs/GOVERNANCE.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/project-docs/GOVERNANCE.md b/project-docs/GOVERNANCE.md index 0ece9e4..f545033 100644 --- a/project-docs/GOVERNANCE.md +++ b/project-docs/GOVERNANCE.md @@ -18,9 +18,9 @@ Maintainers belong to all or some subset of Vega projects. Maintainers are respo Maintainers have write access and can push directly to branches on GitHub. Maintainers also have access to specific developer channels on Slack. -To become a Maintainer, a contributor must be nominated by an existing Maintainer and approved by a majority of Maintainers via Slack reactions within 7 days (simple majority of responses). A new Maintainer should be added to 1) the GitHub team, 2) the Slack channel, and 3) the [MAINTAINERS.md file](MAINTAINERS.md). We want more people to become Maintainers and lower the barrier the entry. If you are interested in becoming a Maintainer, please reach out to an existing Maintainer. +To become a Maintainer, a contributor must be nominated by an existing Maintainer and approved by a simple majority of Maintainers via Slack reactions within 7 days (simple majority of responses). A new Maintainer should be added to 1) the GitHub team, 2) the Slack channel, and 3) the [MAINTAINERS.md file](MAINTAINERS.md). We want more people to become Maintainers and lower the barrier the entry. If you are interested in becoming a Maintainer, please reach out to an existing Maintainer. -Maintainers who are inactive for more than six months may be removed from the maintainer list. +Maintainers who are inactive for more than six months may be removed from the Maintainer list by 3/4 vote of the existing Maintainers. ### Admins @@ -28,7 +28,7 @@ Admins are maintainers who can make and are responsible for releases. Admins are To become an Admin, a Maintainer must be nominated and approved by the existing Admins using the same process as for Maintainers. Admins are listed in the [ADMINS.md file](ADMINS.md). -Admins who are inactive for a year may be removed from the Admin list. +Admins who are inactive for a year may be removed from the Admin list by 3/4 vote of the existing Admins. ## Decisions @@ -46,7 +46,7 @@ Decisions may be appealed by opening an issue and that appeal will be considered Each Vega project may have its own development guidelines in a `CONTRIBUTING.md` file. For example, [Vega-Lite's contributing guide](https://github.com/vega/vega-lite/blob/main/CONTRIBUTING.md) describes design and development principles. -## How We Work. +## How We Work **Openness**. Participation is open to anyone who is directly and materially affected by the activity in question. There shall be no undue financial barriers to participation. From 4deca8717cbce55fe9faeda07dfd6f33def752d8 Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Tue, 28 Nov 2023 18:36:43 -0500 Subject: [PATCH 09/19] Formatting --- CHARTER.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/CHARTER.md b/CHARTER.md index 8875fee..4de2768 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -18,9 +18,7 @@ The Steering Committee will be responsible for all technical oversight, project ### Composition -The Steering Committee voting members are listed in the [STEERING-COMMITTEE.md file](STEERING-COMMITTEE.md). -Voting members may be added or removed by no less than 3/4 affirmative vote of the Steering Committee. -The Steering Committee will appoint a Chair responsible for organizing Steering Committee activity. +The Steering Committee voting members are listed in the [STEERING-COMMITTEE.md file](STEERING-COMMITTEE.md). Voting members may be added or removed by no less than 3/4 affirmative vote of the Steering Committee. The Steering Committee will appoint a Chair responsible for organizing Steering Committee activity. ## Voting From f42aab86c68ac336115371cbbc8cfb93fcf82422 Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Wed, 29 Nov 2023 10:53:38 -0500 Subject: [PATCH 10/19] vega altair -> vega-altair --- project-docs/ADMINS.md | 2 +- project-docs/MAINTAINERS.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/project-docs/ADMINS.md b/project-docs/ADMINS.md index 266fa13..75fadd5 100644 --- a/project-docs/ADMINS.md +++ b/project-docs/ADMINS.md @@ -14,7 +14,7 @@ This includes projects in the [vega](https://github.com/vega/) org. | Kanit Wongsuphasawat | @kanitw | - | | Lukas Hermann | @lsh | - | -## Vega Altair Admins +## Vega-Altair Admins This includes projects in the [altair-viz](https://github.com/altair-viz/) org. diff --git a/project-docs/MAINTAINERS.md b/project-docs/MAINTAINERS.md index 600ce95..83a5d47 100644 --- a/project-docs/MAINTAINERS.md +++ b/project-docs/MAINTAINERS.md @@ -20,7 +20,7 @@ This includes projects in the [vega](https://github.com/vega/) org. | Mattijn van Hoek | @mattijn | - | | Younghoon Kim | @yhoonkim | - | -## Vega Altair Maintainers +## Vega-Altair Maintainers This includes projects in the [altair-viz](https://github.com/altair-viz/) org. From 3aac0139a711e1134eac120d4eb3cd5349f648a0 Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Wed, 29 Nov 2023 12:50:43 -0500 Subject: [PATCH 11/19] Add more altair projects Co-authored-by: Stefan Binder --- CHARTER.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHARTER.md b/CHARTER.md index 4de2768..00c6ee7 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -2,7 +2,7 @@ ## Scope and Goals -This is the organizational charter for [Vega](https://github.com/vega/vega), [Vega-Lite](https://github.com/vega/vega-lite), [Vega-Altair](https://github.com/altair-viz/altair), [Vega-Embed](https://github.com/vega/vega-embed), [Vega-Datasets](https://github.com/vega/vega-datasets), [Vega-Themes](https://github.com/vega/vega-themes), [Vega-Tooltips](https://github.com/vega/vega-tooltip), [Vega-Editor](https://github.com/vega/editor), and [VL-Convert](https://github.com/vega/vl-convert). These projects are collectively referred to as the "Vega projects" in this document. +This is the organizational charter for [Vega](https://github.com/vega/vega), [Vega-Lite](https://github.com/vega/vega-lite), [Vega-Altair](https://github.com/altair-viz/altair), [Vega-Embed](https://github.com/vega/vega-embed), [Vega-Datasets](https://github.com/vega/vega-datasets), [Vega-Themes](https://github.com/vega/vega-themes), [Vega-Tooltips](https://github.com/vega/vega-tooltip), [Vega-Editor](https://github.com/vega/editor), [VL-Convert](https://github.com/vega/vl-convert), [Altair-Tiles](https://github.com/altair-viz/altair_tiles), and [dash-vega-components](https://github.com/altair-viz/dash-vega-components). These projects are collectively referred to as the "Vega projects" in this document. The Vega projects are in the [vega](https://github.com/vega) and [altair-viz](https://github.com/altair-viz) GitHub organizations. From 7595ad00c68428a354b48772515426295e6b19b1 Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Wed, 29 Nov 2023 12:52:09 -0500 Subject: [PATCH 12/19] Add UW affiliation --- STEERING-COMMITTEE.md | 2 +- project-docs/ADMINS.md | 2 +- project-docs/MAINTAINERS.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/STEERING-COMMITTEE.md b/STEERING-COMMITTEE.md index d9cbc2b..cfedf0f 100644 --- a/STEERING-COMMITTEE.md +++ b/STEERING-COMMITTEE.md @@ -6,7 +6,7 @@ This document lists the members of the Organization's Steering Committee. Voting | --- | --- | --- | | Stefan Binder (Chair) | @binste | - | | Dominik Moritz (Chair) | @domoritz | - | -| Jeffrey Heer | @jheer | - | +| Jeffrey Heer | @jheer | University of Washington | | Kanit Wongsuphasawat | @kanitw | - | | Arvind Satyanarayan | @arvind | - | | Joel Ostblom | @joelostblom | - | diff --git a/project-docs/ADMINS.md b/project-docs/ADMINS.md index 75fadd5..7053984 100644 --- a/project-docs/ADMINS.md +++ b/project-docs/ADMINS.md @@ -10,7 +10,7 @@ This includes projects in the [vega](https://github.com/vega/) org. | --- | --- | --- | | Arvind Satyanarayan | @arvind | - | | Dominik Moritz | @domoritz | - | -| Jeffrey Heer | @jheer | - | +| Jeffrey Heer | @jheer | University of Washington | | Kanit Wongsuphasawat | @kanitw | - | | Lukas Hermann | @lsh | - | diff --git a/project-docs/MAINTAINERS.md b/project-docs/MAINTAINERS.md index 83a5d47..a7f9b0a 100644 --- a/project-docs/MAINTAINERS.md +++ b/project-docs/MAINTAINERS.md @@ -11,7 +11,7 @@ This includes projects in the [vega](https://github.com/vega/) org. | Arvind Satyanarayan | @arvind | - | | Dominik Moritz | @domoritz | - | | Fan Du | @fandu-db | - | -| Jeffrey Heer | @jheer | - | +| Jeffrey Heer | @jheer | University of Washington | | Joel Ostblom | @joelostblom | - | | Jon Mease | @jonmmease | [Hex Technologies](https://hex.tech/) | | Kanit Wongsuphasawat | @kanitw | - | From 1e522430753aea16102a1fef685f62185a783356 Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Wed, 29 Nov 2023 12:52:38 -0500 Subject: [PATCH 13/19] Talk about chairs --- CHARTER.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHARTER.md b/CHARTER.md index 00c6ee7..976fbd9 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -18,7 +18,7 @@ The Steering Committee will be responsible for all technical oversight, project ### Composition -The Steering Committee voting members are listed in the [STEERING-COMMITTEE.md file](STEERING-COMMITTEE.md). Voting members may be added or removed by no less than 3/4 affirmative vote of the Steering Committee. The Steering Committee will appoint a Chair responsible for organizing Steering Committee activity. +The Steering Committee voting members are listed in the [STEERING-COMMITTEE.md file](STEERING-COMMITTEE.md). Voting members may be added or removed by no less than 3/4 affirmative vote of the Steering Committee. The Steering Committee will appoint one or two Chair(s) responsible for organizing Steering Committee activity. ## Voting From 01d15466a2d5df0d665e92594d2599c7cc1072ae Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Wed, 29 Nov 2023 13:41:15 -0500 Subject: [PATCH 14/19] Simplify approval and oversight to approval only --- CHARTER.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHARTER.md b/CHARTER.md index 976fbd9..8702036 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -14,7 +14,7 @@ The Vega projects provide an ecosystem of tools for declarative data visualizati ### Purpose -The Steering Committee will be responsible for all technical oversight, project approval and oversight, policy oversight, and trademark management for the Organization. +The Steering Committee will be responsible for all technical oversight, project approval, policy oversight, and trademark management for the Organization. ### Composition From 91f426a5941384bf7a126bc7c91b3449fe889d3c Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Fri, 1 Dec 2023 16:34:00 -0500 Subject: [PATCH 15/19] Update project-docs/MAINTAINERS.md Co-authored-by: Arvind Satyanarayan --- project-docs/MAINTAINERS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/project-docs/MAINTAINERS.md b/project-docs/MAINTAINERS.md index a7f9b0a..815bc9d 100644 --- a/project-docs/MAINTAINERS.md +++ b/project-docs/MAINTAINERS.md @@ -8,7 +8,7 @@ This includes projects in the [vega](https://github.com/vega/) org. | **NAME** | **Handle** | **Affiliated Organization** | | --- | --- | --- | -| Arvind Satyanarayan | @arvind | - | +| Arvind Satyanarayan | @arvind | MIT CSAIL | | Dominik Moritz | @domoritz | - | | Fan Du | @fandu-db | - | | Jeffrey Heer | @jheer | University of Washington | From 49374683dfe5eb2083ff1af17e632af020c83ffe Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Fri, 1 Dec 2023 16:34:20 -0500 Subject: [PATCH 16/19] Update CHARTER.md Co-authored-by: Arvind Satyanarayan --- CHARTER.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHARTER.md b/CHARTER.md index 8702036..b9b2df1 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -36,7 +36,7 @@ The membership of a Steering Committee member will terminate if any of the follo * **Resignation**. Written notice of resignation to the Steering Committee. -* **Unreachable Member**. If a member is unresponsive at its listed handle for more than three months the Steering Committee may vote to remove the member. +* **Unreachable Member**. If a member is unresponsive at their listed handle for more than three months the Steering Committee may vote to remove the member. * **Code of Conduct violation**. If a member violates the Code of Conduct in a way that justifies at least a warning, the Steering Committee may vote to remove the member. From 1b1c31fcf08aade12d5214f4079fd7ff744250ee Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Fri, 1 Dec 2023 16:34:29 -0500 Subject: [PATCH 17/19] Update STEERING-COMMITTEE.md Co-authored-by: Arvind Satyanarayan --- STEERING-COMMITTEE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/STEERING-COMMITTEE.md b/STEERING-COMMITTEE.md index cfedf0f..64f9b88 100644 --- a/STEERING-COMMITTEE.md +++ b/STEERING-COMMITTEE.md @@ -8,7 +8,7 @@ This document lists the members of the Organization's Steering Committee. Voting | Dominik Moritz (Chair) | @domoritz | - | | Jeffrey Heer | @jheer | University of Washington | | Kanit Wongsuphasawat | @kanitw | - | -| Arvind Satyanarayan | @arvind | - | +| Arvind Satyanarayan | @arvind | MIT CSAIL | | Joel Ostblom | @joelostblom | - | | Jon Mease | @jonmmease | [Hex Technologies](https://hex.tech/) | | Mattijn van Hoek | @mattijn | - | From fe0d28783afde7868d42db33163b699c5ed1b2d3 Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Fri, 1 Dec 2023 16:34:40 -0500 Subject: [PATCH 18/19] Update project-docs/ADMINS.md Co-authored-by: Arvind Satyanarayan --- project-docs/ADMINS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/project-docs/ADMINS.md b/project-docs/ADMINS.md index 7053984..3f6678a 100644 --- a/project-docs/ADMINS.md +++ b/project-docs/ADMINS.md @@ -8,7 +8,7 @@ This includes projects in the [vega](https://github.com/vega/) org. | **NAME** | **Handle** | **Affiliated Organization** | | --- | --- | --- | -| Arvind Satyanarayan | @arvind | - | +| Arvind Satyanarayan | @arvind | MIT CSAIL | | Dominik Moritz | @domoritz | - | | Jeffrey Heer | @jheer | University of Washington | | Kanit Wongsuphasawat | @kanitw | - | From 1a2beb1dd569181fe4836b6e1c45d6c9c58715fe Mon Sep 17 00:00:00 2001 From: Dominik Moritz Date: Fri, 1 Dec 2023 16:59:29 -0500 Subject: [PATCH 19/19] Updates based on comments --- CHARTER.md | 2 ++ project-docs/GOVERNANCE.md | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/CHARTER.md b/CHARTER.md index b9b2df1..d44c1aa 100644 --- a/CHARTER.md +++ b/CHARTER.md @@ -56,6 +56,8 @@ In order to be eligible to be a Organization project, a project must: - For specifications, a community developed and maintained specification agreement, such the [Open Web Foundation Agreements](https://www.openwebfoundation.org/the-agreements) or [Community Specification Agreement](https://github.com/CommunitySpecification/1.0). * Include and adhere to the Organization's policies, including the [code of conduct](./CODE-OF-CONDUCT.md). +After adding a project to the Vega Organization, add it to the list at the top of this document. + ## Amendments Amendments to this charter, or the [code of conduct](CODE_OF_CONDUCT.md) may only be made with at least a 3/4 affirmative vote of the Steering Committee. diff --git a/project-docs/GOVERNANCE.md b/project-docs/GOVERNANCE.md index f545033..ea07072 100644 --- a/project-docs/GOVERNANCE.md +++ b/project-docs/GOVERNANCE.md @@ -18,7 +18,7 @@ Maintainers belong to all or some subset of Vega projects. Maintainers are respo Maintainers have write access and can push directly to branches on GitHub. Maintainers also have access to specific developer channels on Slack. -To become a Maintainer, a contributor must be nominated by an existing Maintainer and approved by a simple majority of Maintainers via Slack reactions within 7 days (simple majority of responses). A new Maintainer should be added to 1) the GitHub team, 2) the Slack channel, and 3) the [MAINTAINERS.md file](MAINTAINERS.md). We want more people to become Maintainers and lower the barrier the entry. If you are interested in becoming a Maintainer, please reach out to an existing Maintainer. +To become a Maintainer, a contributor must be nominated by an existing Maintainer and approved by a simple majority of Maintainers via Slack reactions within 7 days (simple majority of responses). A new Maintainer should be added to 1) the GitHub team, 2) the Slack channel, and 3) the [MAINTAINERS.md file](MAINTAINERS.md). The details of the vote should be deleted before the new maintainer is added to the channel. We want more people to become Maintainers and lower the barrier the entry. If you are interested in becoming a Maintainer, please reach out to an existing Maintainer. Maintainers who are inactive for more than six months may be removed from the Maintainer list by 3/4 vote of the existing Maintainers.