Editing pass for the governance documents, prior to them voted as bei…

…ng official.

code_of_conduct.md

@@ -31,8 +31,7 @@ work, there is urgency or risk to someone, nobody is intervening publicly and
 you don't feel comfortable speaking in public, etc.  For these or other
 reasons, structured follow-up may be necessary and here we provide the means
 for that: we welcome reports by emailing
-[*EMAIL*]() or by filling out [this
-form](GOOGLE FORM).
+[[email protected]](mailto:[email protected]).
 
 This code applies equally to founders, developers, mentors and new community
 members, in all spaces managed by Bqplot. This
@@ -45,8 +44,8 @@ participate within them.
 
 By embracing the following principles, guidelines and actions to follow or
 avoid, you will help us make Bqplot a welcoming and productive community. Feel
-free to contact the Steering Committee at
-[*EMAIL*](EMAIL) with any questions.
+free to contact the Steering Council at
+[[email protected]](mailto:[email protected]) with any questions.
 
 1. **Be friendly and patient**.
 
@@ -120,7 +119,7 @@ or other local personnel that are present.
 
 In situations where an individual community member acts unilaterally,
 they must inform the Code of Conduct committee as soon as possible,
-by emailing [EMAIL](EMAIL) within 24 hours.
+by emailing [[email protected]](mailto:[email protected]) within 24 hours.
 
 
 ## Reporting
@@ -129,14 +128,10 @@ If you believe someone is violating the code of conduct, please report this in
 a timely manner. Code of conduct violations reduce the value of the community
 for everyone and we take them seriously.
 
-You can file a report by emailing [EMAIL](EMAIL) or by filling out [this form](GOOGLE FORM).
+You can file a report by emailing [[email protected]](mailto:[email protected]).
 For more details or information on reporting in-person at an event, please see our
 Reporting Guidelines.
 
-The online form gives you the option to keep your report anonymous or request
-that we follow up with you directly. While we cannot follow up on an anonymous
-report, we will take appropriate action.
-
 
 ## Enforcement
 

code_of_conduct_actions.md

@@ -1,12 +1,10 @@
 # Bqplot Code of Conduct - Enforcement Manual
 
-This is the enforcement manual followed by Bqplot's Steering Committee, 
-
-It is used when we respond to an incident to make sure we are consistent and fair.
+This is the enforcement manual followed by Bqplot. It is used when we respond to an incident to make sure we are consistent and fair.
 
 ## The Code of Conduct Committee
 
-All responses to reports of conduct violations will be managed by the Bqplot Steering Committee ("the committee").
+All responses to reports of conduct violations will be managed by the Bqplot Steering Council, which serves as the Bqplot Code of Conduct Committee ("the Committee").
 
 If a Code of Conduct report involves a member of the Steering Council, that member will not participate in the investigation or any decisions related to that report.
 
@@ -56,11 +54,11 @@ The Code of Conduct Committee will keep the following values and guidelines in m
 
 We value the health of the community over individual contributions.
 
-## How the committee will respond to incidents
+## How the Committee will respond to incidents
 
-When the committee is made aware of an incident, they will promptly reply to the reporter to confirm receipt.
+When the Committee is made aware of an incident, they will promptly reply to the reporter to confirm receipt.
 
-The committee will then review the incident and determine, to the best of their ability:
+The Committee will then review the incident and determine, to the best of their ability:
 
 * What happened.
 * Whether this event constitutes a Code of Conduct violation.
@@ -73,34 +71,34 @@ group's deliberations will be recorded and retained (e.g. email discussions, mee
 
 ## Resolutions
 
-The Committee will strive to achieve a quick resolution of reported issues. The committee must agree on a resolution by consensus. Possible responses may include:
+The Committee will strive to achieve a quick resolution of reported issues. The Committee must agree on a resolution by consensus. Possible responses may include:
 
 * Taking no further action
   - if we determine no violations have occurred.
-  - if the matter has been resolved publicly while the committee was
+  - if the matter has been resolved publicly while the Committee was
     considering responses.
 * Remind publicly, and point out that some behavior/actions/language have been
   judged inappropriate and why in the current context, or can be hurtful to
   some people, requesting the community to self-adjust.
-* A private reprimand from the committee to the individual(s) involved. In this
+* A private reprimand from the Committee to the individual(s) involved. In this
   case, the group chair will deliver that reprimand to the individual(s) over
   email, cc'ing the group.
-* A public reprimand. In this case, the committee chair will deliver that
+* A public reprimand. In this case, the Committee chair will deliver that
   reprimand in the same venue that the violation occurred, within the limits of
   practicality. E.g., the original mailing list for an email violation, but
   for a chat room discussion where the person/context may be gone, they can be
   reached by other means. The group may choose to publish this message
   elsewhere for documentation purposes.
-* A "mutually agreed upon hiatus" where the committee asks the individual to
+* A "mutually agreed upon hiatus" where the Committee asks the individual to
   temporarily refrain from community participation. If the individual chooses
-  not to take a temporary break voluntarily, the committee may issue a
+  not to take a temporary break voluntarily, the Committee may issue a
   "mandatory cooling off period".
 * A permanent or temporary ban from some or all bqplot spaces (mailing lists,
   chat channels, etc.).
 
-The committee has the option to publish official public statements if judged necessary, but generally will pursue resolutions confidentially.
+The Committee has the option to publish official public statements if judged necessary, but generally will pursue resolutions confidentially.
 
 ## Conflicts of Interest
 
-In the event of a conflict of interest, a committee member must immediately
+In the event of a conflict of interest, a Committee member must immediately
 notify the other members, and recuse themselves if necessary.

governance.md

@@ -1,7 +1,9 @@
 
-# DRAFT Main Governance Document
+# BQplot Main Governance Document
 
-Note that this document is a work-in-progress draft, and has not been adopted by the bqplot project yet. 
+The official version of this document, along with a list of individuals and institutions in the roles defined in the sections below, is contained in The Project Governance Repository at:
+
+https://github.com/bqplot/governance
 
 ## The Project
 
@@ -34,65 +36,61 @@ The Project leadership consists of a Steering Council.
 ### Steering Council
 
 
-The Project will have a Steering Council that consists of Project Contributors who have produced contributions that are substantial in quality and quantity, and sustained over at least one year. The overall role of the Council is to ensure, through working taking input from the Community, the long-term well-being of the project, both technically and as a community.
+The Project will have a Steering Council that consists of Project Contributors who have produced contributions that are substantial in quality and quantity, and sustained over at least one year. The overall role of the Council is to ensure, through working and taking input from the Community, the long-term well-being of the project, both technically and as a community.
 
-During the everyday project activities, council members participate in discussions, code review and other project activities as peers with all other Contributors and the Community. In these everyday activities, Council Members do not have any special power or privilege through their membership on the Council. Most day-to-day activities do not block on the steering council. However, it is expected that because of the quality and quantity of their contributions and their expert knowledge, Council Members will provide useful guidance, both technical and in terms of project direction, to potentially less experienced contributors.
+During the day-to-day Project activities, Council Members participate in discussions, code review and other Project activities as peers with all other Contributors and the Community. In these day-to-day activities, Council Members do not have any special power or privilege through their membership on the Council. Most day-to-day activities do not block on the Steering Council. However, it is expected that because of the quality and quantity of their contributions and their expert knowledge, Council Members will provide useful guidance, both technical and in terms of Project direction, to potentially less experienced contributors.
 
 The Steering Council and its Members play a special role in certain situations. In particular, the Council may:
 
 - Make decisions about the overall scope, vision and direction of the project.
 - Make decisions about strategic collaborations with other organizations or individuals.
 - Develop funding sources and spending money.
-
 - Make decisions when regular community discussion does not produce consensus on an issue in a reasonable time frame.
 - Mediate significant conflict between community participants regarding the direction of the project
 - Resolve code of conduct issues
-- Grant or revoke privileges (e.g., releasing, committing, triaging) to Project contributors.
-- Mentor Project contributors
-
-- Make decision on major architectural or backward-incompatible changes, as well as major releases of the project.
+- Grant or revoke privileges (e.g., releasing, committing, triaging) to Project Contributors.
+- Mentor Project Contributors
+- Make decisions on major architectural or backward-incompatible changes, as well as major releases of The Project.
 
-The Steering Committee may delegate some of the above responsibilities to other Project contributors or committees.
+The Steering Council may delegate some of the above responsibilities to other Project Contributors or committees.
 
 ### Council membership
 
 #### Eligibility
 
-To become eligible for being a Steering Council Member an individual must be a Project Contributor who has produced contributions that are substantial in quality and quantity, and sustained over at least one year. Potential Council Members are nominated by existing Council members and voted upon by the existing Council. Based on a successful vote, the newly elected Member is invited to serve in that capacity. The Council is initially selected from the set of existing Core Developers who, as of 2020, have been significantly active over the last year.
+To become eligible for being a Steering Council Member, an individual must be a Project Contributor who has produced contributions that are substantial in quality and quantity, and sustained over at least one year. Potential Council Members are nominated by existing Council Members and voted upon by the existing Council. Based on a successful vote, the newly elected Member is invited to serve in that capacity. The Council is initially selected from the set of existing Core Developers who, as of 2020, have been significantly active over the last year.
 
-When considering potential Members, the Council will look at candidates with a comprehensive view of their contributions. This will include but is not limited to code, code review, infrastructure work, mailing list and chat participation, community help/building, education and outreach, design work, etc. We are deliberately not setting arbitrary quantitative metrics (like “100 commits in this repo”) to avoid encouraging behavior that plays to the metrics rather than the project’s overall well-being. We want to encourage a diverse array of backgrounds, viewpoints and talents in our team, which is why we explicitly do not define code as the sole metric on which council membership will be evaluated.
+When considering potential Members, the Council will look at candidates with a comprehensive view of their contributions. This will include, but is not limited to, code, code review, infrastructure work, mailing list and chat participation, community help/building, education and outreach, design work, etc. We are deliberately not setting arbitrary quantitative metrics (like “100 commits in this repo”) to avoid encouraging behavior that plays to the metrics rather than The Project’s overall well-being. We want to encourage a diverse array of backgrounds, viewpoints and talents in our team, which is why we explicitly do not define code as the sole metric on which Council membership will be evaluated.
 
 #### Term
 
-Council membership terms last two years. Initial terms will be staggered so that there is a new selection of steering council members every year. Council members can serve multiple consecutive terms.
+Council membership terms last two years. Initial terms will be staggered so that there is a new selection of Steering Council Members every year. Council Members can serve multiple consecutive terms.
 
-When a Steering Council member term ends, or when they leave the SC, a new SC will be nominated.
+When a Steering Council Member term ends, or when they leave the Steering Council, a new Steering Council will be nominated.
 
 #### Expectations
 
-The Steering Council will have regular meetings at least monthly. Council members should participate in 3/4 of the regular meetings, and engage regularly in discussions and offline votes on the Steering Council mailing list.
+The Steering Council will have regular meetings at least monthly. Council Members should participate in 3/4 of the regular meetings, and engage regularly in discussions and offline votes on the Steering Council mailing list.
 
-If a Council member becomes inactive in the project for a long period of time, they may be considered for removal from the Council. Before removal, the inactive Member will be approached by the other members of the Council to see if they plan on returning to active participation. If not they will be removed immediately upon a Council
-vote.
+If a Council member becomes inactive in The Project for a long period of time, they may be considered for removal from the Council. Before removal, the inactive Member will be approached by the other members of the Council to see if they plan on returning to active participation. If not, they will be removed immediately upon a Council vote.
 
-If they plan on returning to active participation soon, they will be given a grace period of one year. If they don’t return to active participation within that time period they will be removed by vote of the Council without further grace period. All former Council members can be considered for membership again at any time in the future, like any other Project Contributor.
+If they plan on returning to active participation soon, they will be given a grace period of one year. If they do not return to active participation within that time period, they will be removed by vote of the Council without further grace period. All former Council Members can be considered for membership again at any time in the future, like any other Project Contributor.
 
-Retired Council members will be listed on the project website, acknowledging the period during which they were active in the Council.
+Retired Council Members will be listed on the project website, acknowledging the period during which they were active in the Council.
 
-The Council reserves the right to eject current Members, if they are deemed to be actively harmful to the project’s well-being, and
-attempts at communication and conflict resolution have failed.
+The Council reserves the right to eject current Members, if they are deemed to be actively harmful to the project’s well-being and attempts at communication and conflict resolution have failed.
 
 #### Conflict of interest
 
-It is expected that the Council Members will be employed at a wide range of companies, universities and non-profit organizations. 
+It is expected that the Council Members will be employed at a wide range of companies, universities and non-profit organizations.
 
 Because of this, it is possible that Members will have a range of interests related to the project, and possibly conflicts of interests. Such conflict of interests include, but are not limited to:
 
 - Financial interests, such as investments, employment, or contracting work, outside of The Project that may influence their work on The Project.
-- Access to proprietary information of their employer that could potentially leak into their work with the Project.
+- Access to proprietary information of their employer that could potentially leak into their work with The Project.
 - An issue where the person privately gains an advantage from The Project resources, but The Project has no gain or suffers a disadvantage.
 
-All members of the Council shall disclose to the rest of the Council any interest they may have as it relates to the project. The council will evaluate whether it constitutes a conflict. Members with a conflict of interest in a particular issue may participate in Council discussions on that issue, but must recuse themselves from voting on the issue.
+All members of the Council shall disclose to the rest of the Council any interest they may have as it relates to the project. The Council will evaluate whether it constitutes a conflict. Members with a conflict of interest in a particular issue may participate in Council discussions on that issue, but must recuse themselves from voting on the issue.
 
 #### Private communications of the Council