-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Submit DEI Standing Committee Charter #160
Changes from 12 commits
21c5e3f
ee2aac6
0bf91e5
00c953b
237bcdd
be107c2
fcc07f4
03afee8
109a67f
69f499c
824e909
0ed3317
74bab33
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# Diversity Equity and Inclusion Committee Charter | ||
|
||
Project Jupyter welcomes and encourages participation in our community by people of all backgrounds and identities. We are committed to promoting and sustaining a culture that values mutual respect, tolerance, and learning. We work together as a community to help each other live out these values. | ||
|
||
The Diversity Equity & Inclusion (DEI) Committee is a standing committee established under Jupyter’s governance model. The committee reviews its charter annually and may make changes at any time during the year. Substantive changes to the purpose or mission must be submitted to the Executive Council (EC) and the Software Steering Council (SSC) for approval. | ||
|
||
## Purpose | ||
|
||
The purpose of this committee is to lead strategic initiatives designed to improve the diversity, equity, and inclusion of Project Jupyter community leaders, contributors, and end users across the globe. For the long-term sustainability of our community, we champion efforts to build an open source environment where people feel respected, valued, and encouraged to continue participating. The DEI group impacts all Jupyter forums, including but not limited to software, working groups, standing committees, JupyterCon, social media, GitHub, the EC, and the SSC. | ||
|
||
## Mission/Areas of Responsibility | ||
|
||
The DEI standing committee is responsible for: | ||
* Propose, execute, and evaluate the impact of DEI initiatives | ||
marthacryan marked this conversation as resolved.
Show resolved
Hide resolved
marthacryan marked this conversation as resolved.
Show resolved
Hide resolved
|
||
* Research, establish, and collect metrics related to DEI | ||
* Advocate for increased participation of underrepresented groups in the Jupyter community. | ||
* Serve as a point of contact for DEI topics for the global Jupyter community | ||
* Include the topic of DEI in discussions and spaces within Project Jupyter. | ||
* Recommend and promote training, educational, and motivational materials on DEI | ||
* Flag DEI issues or potential issues to the EC or the SSC | ||
|
||
## Meetings | ||
* Frequency - this committee should meet at least once every two weeks. | ||
* The Jupyter Decision-Making Guide will be used to make official decisions. | ||
* To ensure active participation, a member who is unable to join for more than two thirds of regularly scheduled weekly meetings in a 90 day period may be asked to step down from the committee. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does this statement mean that the DEI group requires all of its members to attend meetings synchronously 2 out of every 3 times? If so, will these meetings alternate times to accommodate all timezones and the "2/3" is only counted on meetings that fit your timezone? Or is actively engaging meeting notes asynchronously enough to count here? Ideally, this group becomes a body of people that represents the global community it serves; we should tune our expectations so that a diverse body can comfortably serve from anywhere. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thx @Zsailer for asking about the sync/async as timezone. Sorry to hijack this PR, but would like to mention we had the exact same discussions during the last Software Steering Council (SSC). Should those aspects be defined for all groups, or are they a delegated to the groups? In the latter case the groups would be free to decide and evolve the rules by themselves and those aspects should not be mentioned in the charter IMHO. Thinking loud, I would prefer the governance to define some guidance for all groups to have a basis and common framework to avoid discussion and too much disparity across groups. BTW the timezone question is a perfect topic for the DEI group to ensure enough on-call representation from around the globe :) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The delay linked to vote mentioned in the Decision-Making Guide is a year. Is there a specific reason to have 90 days here?
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @Zsailer Thanks for bringing this up. The "time zone problem", as I'll call it for short, affects our team and many others. On the DEI committee, we have made an effort to set weekly meetings at a time that is convenient for most of our members. We currently have four members on the DEI committee, all of whom are in the Americas, and we are focused on synchronous participation. We are definitely open to holding our meetings at different times if we find someone for whom our current meeting time is not suitable. We use the word "may" in our charter to say that it is not automatic to exclude a person for being unable to attend 2/3 of the meetings. Other committees should set expectations for themselves. Does this address your concern? @fcollonval Our charter describes an expectation (but not a requirement) to attend more than 2/3 of scheduled weekly meetings. The decision-making guide describes a requirement to participate in at least 2/3 of formal votes. Because a scheduled weekly meeting is not as formal, we don't consider our guidance to be in conflict with the decision-making guide. |
||
|
||
## Committee Reports | ||
* Reports will be submitted to the EC half-yearly on or before the 15th of July and January for the preceding calendar half. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Just clarifying, is the intention that these reports are for the Executive Council only? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, that's correct. I do think it's fair to ask this committee to present some form of public communication whether it be in the form of a blog post, a YouTube video, or office hour. I will add this to our next agenda for discussion. Thanks for bringing this up. |
||
* Reports should include the following metrics: | ||
marthacryan marked this conversation as resolved.
Show resolved
Hide resolved
marthacryan marked this conversation as resolved.
Show resolved
Hide resolved
|
||
* Overview of activities and challenges if any | ||
* Budget update including spending for that quarter - if applicable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest instead (it sounds more readable to me, but I'll defer to a native speaker)
The responsibilities of the DEI standing committee are to: