chaoss / wg-dei Goto Github PK
View Code? Open in Web Editor NEWCHAOSS Working Group focused on Diversity, Equity, and Inclusion metrics
License: MIT License
CHAOSS Working Group focused on Diversity, Equity, and Inclusion metrics
License: MIT License
This issue is for coordinating around developing the resource page for Communication Inclusivity: Captioning.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1eIXfiXkpTa6YdiAEbEMOkGLTPYlYYXuWc_O7DaM2EE4/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
@GeorgLink In the focus area template, I want to link to an example/directions/criteria for how to write a good goal-metric. Do you have something like that?
Idea: Write a tutorial on how to measure the diversity in an open source community.
The tutorial might be structured as follows:
Include an example from beginning to end within the tutorial to make it tangible.
Possibly start with one Goal-Question to test the format.
?? How can we include an incentive to share the results with us. This would be helpful for comparisons and benchmarking. Can we add some gamification? Maybe have an anonymous sharing option.
Hello, I was reviewing our metrics on Project Places (https://github.com/chaoss/wg-diversity-inclusion/blob/master/goal_project_places.md) and I think we should include the following additional aspects in the document:
What do you think? Perhaps we can discuss this in our next call?
Sample Objectives:
Sample Strategies:
Sample Metrics:
Thank you @dicortazar for helping me with this issue.
This issue is for coordinating around developing the resource page for Contributions: Contribution Sentiment.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1oLr2kWKKbR8Vx7NrZ2xHXZ12cYN0vaqp1zehmF0IcKc/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
Hey! Akshita and I were working on Code of Conduct metrics, and realized that we could not find a mention of CoC in README or in code, we should add that!
This issue is for coordinating around developing the resource page for Contributions: Contribution-Type.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1FJNsWimNN4KUgtCeq6z3etY_x3KJOrA376gCtOCIkzg/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
I've created a Google Doc where we can collaborate on our CHAOSSCon D&I Panel Submission. It's an updated version of what was submitted for CHAOSSCon NA.
We should also decide whether to also submit this to the FOSDEM Community Devroom?
Hello, would it make sense to have a sandbox where newbies can first raise issues/create pull requests within our group before making it visible to the entire world?
This issue is for coordinating around developing the resource page for Governance - Code of Conduct Enforcement.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1O__IONyNX8KRlkwSgmPIvOuzx8M01WUr2gZy2j3cF7w/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
This issue is for coordinating around developing the resource page for Governance - Path to Influence.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1g3zMQpBgieUzkJN8Zw9QBgyStDmjCiw5NQaaMoM7hF0/edit
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
This issue is for coordinating around developing the resource page for Governance - Board/Council Diversity.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/13toY8vWR5OGwiuLKzI7cmhnjqc7H8L9u-iUyRmE9egg/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
After reviewing some PRs, I've realized that we should have a common way of contributing either using the command line interface or directly using the GitHub interface. Some discussion at [1].
The following is a first set of steps we should consider when preparing a PR:
Then, regarding to how to document a commit, the following are a list of ideas that help to produce an homogeneous way of working:
Others comments are welcome :)
[1] https://github.com/erlang/otp/wiki/writing-good-commit-messages
[2] https://help.github.com/articles/syncing-a-fork/
[3] https://blog.carbonfive.com/2017/08/28/always-squash-and-rebase-your-git-commits/
This issue is for coordinating around developing the resource page for Communication Inclusivity: Listening.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1YHs1r-NHRTv1XoOcC-EnGDoo5tmYl-0WzfGuYmFbpEs/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
This is the only repository that has a different convention from other repositories.
This issue is for coordinating around developing the resource page for Event Diversity - Diversity Access Tickets.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1Gs1xm_-ojc6Y32pYmtdbROnMa81ux_RiK8aeXU43QtE/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
I wanted to understand how this is coming together.
I see influence from our shared work at Mozilla (great to see open demographics project includes) and in fact we are doing pilots right now on qualitative and quantitative community health baselines that with d&i as central. With considerations for privacy, risk, respect ,ethics and legality of measuring d&i.
How might we better align?
This issue is for coordinating around developing the resource page for Governance - Code of Conduct.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1DGiBT3lUaIcNJBsDICsliJPNumOglzFPGJKnWiU3pD0/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
This issue is for coordinating around developing the resource page for Contributions: Collaboration Style.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1yx_EJO5lSnjeFji7__8kAaecDIRqFP95xkZm6GhOgxc/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
This issue is for coordinating around developing the resource page for Event Diversity - Speaker Demographics.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/17Lc7cn2c18OP-nEDB2ioJ2bOIDRy2SEFju-42zJNDeI/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
This issue is for coordinating around developing the resource page for Project Places - Issue Tracker.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1s0R-ira9guSQU6dVQVV3AOgs2o1VWgJ3kpBbi5WCfPI/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
I want to propose these files are organized into folders (vrs using prefix)
We may have other documents per goal-metric, and this helps us isolate and organize a bit better. For example
FROM: project-places-documentation.md
TO:
Project-Places (Folder)
-> documentation.md
-> issue-tracker.md
Contribution (Folder)
-> filename.md
I also propose all goal-metrics documents in root go in a folder named goal-metrics.
We have documentation as a metric, maybe maintainability is also relevant.
Maintainability:
If a stranger can modify your code and fix a bug in less than an hour, it is maintainable.
Test it. Ask someone who is outside of the project to take a look at your code and tell you how clear it is. Not how beautiful your classes and code constructs are—that’s what makes it clean. Instead, ask someone to fix a bug in just 30 minutes and see how they react. You will realize how clear the code is and whether it speaks the language a stranger can understand.
Full reference: https://www.yegor256.com/2018/09/12/clear-code.html
This was shared on Twitter during CLSummit by @_sagesharp_:
Folks at #CLSummit especially @CHAOSSproj should take a look at the inclusivity survey put together by @prdgm. Cc @Sunnydeveloper
I'll do this early in the week, was hoping I could benefit from Nicole's slides. @GeorgLink are you able to send those to me?
This issue is for coordinating around developing the resource page for Governance - Foundation Staff Diversity.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/101e0JlHwxXNXH8dfaiZTEWjgG-YshBESao75PWHJaZA/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
Develop Resource Page: Communication Inclusivity: Technical Jargon
This issue is for coordinating around developing the resource page for Communication Inclusivity: Technical Jargon.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1t2P67jUWcoWUvhz1M2pfA6q7Pe16OWGyJNsTOBSDjcg/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
This issue is for coordinating around developing the resource page for Project Places Documentation.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1OaKDksmuoi6nhaduZ4F96mTwQJvIFnfI8BqLx4MRO38/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
This issue is for coordinating around developing the resource page for Communication Inclusivity: Alternatives.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1e0Y0BhKqEeZeMpcttdFH8Q9NOq-Q6zp78aW-_65hMpc/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
This issue is for coordinating around developing the resource page for Project Places - Communication Channels.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1quMb1e2Hsm6hPf6G4vY6JtS3GUGv9vBZ7JBcuzuCiFs/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
Tobie Langel shared a tweet on the mailing list about adopting the Bechdel Test to Open Source.
I had to look up Bechdel test and include here what I found:
The Bechdel test (/ˈbɛkdəl/ BEK-dəl) is a method for evaluating the portrayal of women in fiction. It asks whether a work features at least two women who talk to each other about something other than a man. (From: https://en.wikipedia.org/wiki/Bechdel_test)
The tweet Tobie referred to states:
The equivalent of the Bechdel test would be that there is a PR for an OSS project which gets reviewed, commented on, and accepted without having a man on the PR history.
I read this to require for a pull request (assuming GitHub):
We could add a Bechdel metric that is the ratio of pull requests that pass the Bechdel test.
This might be a suitable D&I metric.
(without worrying about how to implement the metric for now).
According to @serebrenik, we should discuss the following ideas: "I would also (1) separate sexual and romantic orientation and (2) add religion (or lack thereof) as a dimension."
Initial discussion at #21
This issue is for coordinating around developing the resource page for Event Diversity - Attendees Demographics.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1psK_UH5uLeiVHagpoJbCtm8dF1nIshfCx6qXXJWe4yc/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
This issue is for coordinating around developing the resource page for Event Diversity - Code of Conduct at Event.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1XKrsbVCPA5dqEfOnMVRyRcjqRNS05icKLojdgQawph0/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
Per proposal in chaoss/community#5 :
The README.md of the repository contains a list of who is maintainer. Each CHAOSS repositry brings together different people and they document in the repository specific CONTRIBUTING.md how somone becomes a maintainer on their repository.
TODO:
From today's call:
This issue is for coordinating around developing the resource page for Event Diversity - Kid Friendliness.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1jiylWjkLm04paBcflkNn0-yahvy958ShiUbrKrG20Zs/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
In our meeting we decided the heading was good for questions, but not the zero.
This issue is for coordinating around developing the resource page for Communication Inclusivity: Mode Alternatives.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1z3v374eXIcAd6Fr3Y-J9qflFiunr5KTYoIscdSIPxWg/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
This issue is for coordinating around developing the resource page for Contributions: Perceived Value.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/12UcHlVgP2AA55SbQj1gwWa_8IcQKrIaIJg6Jpy6D0BA/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
This issue is for coordinating around developing the resource page for Communication Inclusivity: Speaking.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1hwtXIUAvZzpd38vFdH-iQDa95RCgFo_2f8a6lGzTzRc/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
At the PR #24, there was an ongoing discussion about having specific bugs suited for novices.
Comment by @aserebrenik on the PR by @emmairwin "Some projects explicitly tag bugs suited for novices to facilitate the onboarding process. This is related to the discussion about the README in the Project places file."
The referenced Goal can be found at https://github.com/chaoss/wg-diversity-inclusion/blob/master/goal_project_places.md
This issue is for coordinating around developing the resource page for Governance - Team/Module Ownership Diversity.
The resource page lives in the following google document for easy editing, commenting, and revision:
https://docs.google.com/document/d/1How8BisNtZs7_coUonDA_99arbcXEZzyaOlxLMrbDBw/edit?usp=sharing
Once the page is in a decent shape, we will put a copy of it in the repository as a markdown file.
To work on this issue, feel free to leave a comment here and start editing the document. For questions, feedback requests, and other coordination tasks, please leave a comment here on the issue.
Please edit the google document directly and add your ideas to it. We can help with cleaning it up later.
As there is an agreement about the current state of the goals, questions and metrics defined by the community, the next step is to write down this in the D&I working group.
This will use the same format as in the 'metrics' repository at [1].
Please consider either cleaning or removing the current README set of metrics.
[1] https://github.com/chaoss/metrics/blob/master/1_Diversity-Inclusion.md
https://docs.google.com/document/d/16-M2hsv4wwnk5GpDSFLc8EQVNAGkfB7k1GagM4aQ6Kw/edit
Who is going and can do the tutorial?
Hi,
I would like to propose one of two things so we are better, and more easily connected.
Mailing list for this WG - so we can send informal discussions without triggering bigger debates.
Gitter chat, which can connect to this repo (have used before and like).
I came across a metric that I consider worth sharing: Share of Voice
Source: https://medium.com/@mbbroberg/community-metrics-share-of-voice-b51d15f38366
This was not on my radar and I don't think we have it on our list of metics (haven't checked though).
I notice that we are naming files one of two ways:
with-dashes.md
with_underscores.md
I would like to propose the standard be for dashes. If there is agreement, then the task is to update all files with underscores to dashes.
Thanks
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.