owned this note
owned this note
Published
Linked with GitHub
# Nov 9th D&I in Open Source Call
* [D&I Shared Calendar]( https://calendar.google.com/calendar?cid=Z3V2dGZyc3A5YTdraGNtdjVpN21nYzN0NDBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ) - Add your events!
**How to ask questions, join, or watch**
[Check the wiki :)](https://wiki.mozilla.org/index.php?title=Diversity_and_Inclusion_for_Communities_and_Contributors/DI_Call_09_04_2018&action=submit)
Air Mozilla:https://t.co/q15U6KA8Uc
If you haave issues with the above,
* https://air.mozilla.org/
* Click on the video banner
* Try again: https://t.co/q15U6KA8Uc
## Roll Call
Please add your name, Twitter/Mastadon handle, project association, and pronouns and where you are from :)
* Emma Irwin, @sunnydeveloper, Mozilla, she/her
* Chris Reynolds @[jazzs3quence](https://twitter.com/jazzs3quence), HumanMade/WordPress, he/him, SLC, UT
* Georg Link, @georglink, CHAOSS, he/him --- Sorry, I cannot figure out how to join the call (Air Mozilla streaming link requires login) or find the livestream (I don't see it on the youtube channel). Streaming on Airmo )(see link above), we will upload to Youtube afterwards (sorry)
* Dan Scott, @[denials](https://twitter.com/denials) / @[dbs@mastodon.social](https://mastodon.social/@dbs), he/him, Laurentian University (Sudbury territory of Atikameksheng Anishnaabek) / McGill University
## Agenda
### TK Labels
http://localcontexts.org/tk-labels/
TK Labels are a tool for Indigenous communities to add existing local protocols for access and use to recorded cultural heritage that is digitally circulating outside community contexts. The TK Labels offer an educative and informational strategy to help non-community users of this cultural heritage understand its importance and significance to the communities from where it derives and continues to have meaning. TK Labeling is designed to identify and clarify which material has community-specific restrictions regarding access and use. This is especially with respect to sacred and/or ceremonial material, material that has gender restrictions, seasonal conditions of use and/or materials specifically designed for outreach purposes. The TK Labels also can be used to add information that might be considered ‘missing’, including the name of the community who remains the creator or cultural custodian of the material, and how to contact the relevant family, clan or community to arrange appropriate permissions.
* Jane Anderson, Associate Professor at New York University
* Kim Christen Director of Digital Initiatives, Washington State
## Question
* Here in British Columbia there are are something like 62 aboriginal languages, many are down to one person who can speak a language, and one who can still write/read. Do you see Tk Labels as a way, or maybe it is for aboriginal cultures to recover language?
* Will you provide links to the webpages you demoed?
* When will tk Label Hub go live?
* I wonder if some institutions have argued that they should be able to propose the default-tk label, where none exists yet. How do you deal with the tension of that meaning well, with what is essentially risk for labels in recollinalization.
* What I hear was Secret/Sacred label (and other labels)ares also a good tool for teaching people, why they shouldn't be seeing that information. In our diversity & inclusion work, we know we can get access to data(including margenlized, underrepresented and vulnernable people) that is publically available, but where the individual(s) may not have understood that public on the internet . What do you think Tk Labels can teach people about personal safety, privacy and consent online? ()
* How do you suggest this project is best shared with Aborginal, First Nations who might learn about how to do this. I don;'t want to say what the value is to them'
* How can people get involved with this work, can they contribute ?
Appreciation for the amount of work, and thought that made this possible, thank you
# September 4th D&I in Open Source Call
* [D&I Shared Calendar]( https://calendar.google.com/calendar?cid=Z3V2dGZyc3A5YTdraGNtdjVpN21nYzN0NDBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ) - Add your events!
**How to ask questions, join, or watch**
[Check the wiki :)](https://wiki.mozilla.org/index.php?title=Diversity_and_Inclusion_for_Communities_and_Contributors/DI_Call_09_04_2018&action=submit)
## Collaboration Zone
*If you are looking for others working on simliar issues, or even for simple things like feedback on a blog post - please do reach out here!*
I need help with....
*
*
If you are interested in lending your skills, time, energy to something specific - please add your name here. (only add if you have actual time available :)*
I can help with...
*
## Roll Call
Please add your name, Twitter/Mastadon handle, project association, and pronouns and where you are from :)
* Emma Irwin - Mozilla, @[sunnydeveloper](https://twitter.com/sunnydeveloper), she/her, Vancouver Island Canada
* Gina Helfrich - NumFOCUS, @[ginahelfrich](https://twitter.com/ginahelfrich) / @[numfocus](https://twitter.com/numfocus), she/her, Ausin, TX, USA
* Karin Lagesen - Code of conduct committee, The Carpentries, she/her, Oslo Norway, @karinlag
* Simon Waldman - Code of conduct committee, The Carpentries, @[tidal_simon](https://twitter.com/tidal_simon). Scotland. he/him
* Kate Mancuso - Mozilla, @[musingvirtual](https://twitter.com/musing_virtual), Oakland CA, they/them
* Marina Zhurakhinskaya @[marinaz](https://twitter.com/marinaz), she/her, Cambridge, MA, USA
* Sage Sharp @[_sagesharp_](https://twitter.com/_sagesharp_), they/them, Portland, OR, USA
* Tara Robertson @[tararobertson](https://twitter.com/tararobertson), she/her/hers, Vancouver, BC, Canada
## Collaboration Zone
*If you are looking for others working on simliar issues, or even for simple things like feedback on a blog post - please do reach out here!*
I need help with....
*
If you are interested in lending your skills, time, energy to something specific - please add your name here. (only add if you have actual time available :)*
I can help with...
*
GDPR/CoC study group
* I will start a study group on this for The Carpentries, if others are interested, contact me on karin.lagesen@gmail.com.
## Links!
Share blog posts, and other articles here!
[Outreachy is hiring for a part-time contractor](https://www.outreachy.org/blog/outreachy-is-hiring/)
I've filed an [inclusivity bug](https://github.com/hackmdio/codimd/issues/934) against hackmd.io - we'll see how they respond to it!
# Agenda
## Jess Mitchell - Thinking Differently - Inclusive Design (40 minutes)
### Questions (add here or in Air Mozilla channel)
* "How can I make this suck for people "
* are there any standards for asking questions like race gender? Because I am aware this sucks for people, yet we are trying to get better at understanding the impact of our actions.
* Where can we find the Inclusive Design Guide?
* Edge cases, and for whom will this fail? What thypes of questions can we ask to find edge cases?
* Is there a link to your Anger Iceburg? (I want to use this! :)
* New moms is a taxonomy (in this culture, in this scenario are attributes you mentioned? How do we arrive at those attributes?)
* How can we better follow your work?
* Do you run workshops?
## GDPR & Code of Conduct - Alicia Gray (15 min)
### Questions
* Are Code of Conduct reports subject to GDPR? And if so, why is this the case?
* If CoC reports are subject to GDPR, how does that mean report information needs to be handled?
* Since things like Google docs and github are GDPR compliant, if we use these tools in reporting, does that mean our reporting procedures are GDPR compliant? What other considerations or best practices would there be?
What happens if a reported person requests that you remove personally identifying information? I'm concerned about bad actors using GDPR to expunge their record or try to get around a ban.
* A question about bad actors misuse (Emma to verbalize)
* The nature of CoC complaints is that enforcement committees sometimes need to hold information on (for example) people's race, sexual orientation, etc. In GDPR terms this is "Special Category Data" (SCD). SCD has a [separate list of allowable reasons for processing](https://gdpr-info.eu/art-9-gdpr/), and I'm not sure (short of blanket prior consent from everybody, which is a barrier to participation, and can probably be withdrawn) that operating a CoC fits with any of them. Help?
* Related to the question above, what about information on people who are being reported on? They are not likely to consent to us keeping data on them.
* Our CoC committee is multinational, including non-EU members. How does this sit with the rules about exporting personal data from the EU?
* Some more legal questions can be found here (from Karin, Carpentries CoC): https://docs.google.com/document/d/1St5U1w6iUe3y1Bpj-Sge-PaZknGnO6CUrUBlyoZWqPo/edit?usp=sharing
---
---
# August D&I in Open Source Call
[Etherpad](https://public.etherpad-mozilla.org/p/open-source-community-call) is going away, but here's the old link.
* [D&I Shared Calendar]( https://calendar.google.com/calendar?cid=Z3V2dGZyc3A5YTdraGNtdjVpN21nYzN0NDBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ) - Add your events!
**How to ask questions**
* You can ask questions right in Zoom! or ......
* Via Telegram Group: https://t.me/joinchat/A8b9ygwClPKToUbFxkhkWA
* On Twitter #opensourcediversity
* [YouTube Stream](https://www.youtube.com/watch?v=BQ4bZPcgY38)
** Etherpad Alternative**
We are testing HackMD this call ([see background](https://github.com/mozilla/diversity/issues/176)), suggest your favourites here:
* Piratepad
## Roll Call
Please add your name, Twitter/Mastadon handle, project association, and pronouns and where you are from :)
* Emma Irwin - Mozilla, @[sunnydeveloper](https://twitter.com/sunnydeveloper), she/her, Vancouver Island Canada
* Becky Faith - Institute of Development Studies, @[Becky_Faith](https://twitter.com/Becky_Faith), she/her, Brighton UK
* Aaron Turon - Mozilla + Rust, @[aaron_turon](https://twitter.com/aaron_turon), he/him, Portland Oregon (USA)
* Jan-Christoph Borchardt – Nextcloud, Open Source Diversity @[jancborchardt](https://twitter.com/jancborchardt), he/him, Berlin Germany
* Camila Ayres – Nextcloud, Open Source Diversity @[camilasan](https://github.com/camilasan/), she/her, Berlin (Germany)
* Georg Link - University of Nebraska at Omaha - CHAOSS project, [@georglink](https://twitter.com/georglink), he/him, Omaha, NE, USA
* Kate Mancuso - Mozilla [@musingvirtual](https://twitter.com/musingvirtual), they/them, Oakland California
* Akshita Gupta - Outreachy Intern, Mozilla @[akshitac8](https://twitter.com/akshitac8), she/her, India
* Sage Sharp - Otter Tech Founder, Outreachy organizer, [sage's twitter](https://twitter.com/_sagesharp_), they/them, Portland, OR, USA
* Alberto Roca - Director, EquitableTech.org, [@MinorityPostdoc](https://twitter.com/minoritypostdoc), he/him, southern California USA
* Marina Zhurakhinskaya - Red Hat, Outreachy organizer, @[marinaz](https://twitter.com/marinaz), she/her, Cambridge, MA, USA
## Collaboration Zone
*If you are looking for others working on simliar issues, or even for simple things like feedback on a blog post - please do reach out here!*
I need help with....
* Kate: I need people to fill out our [code of conduct enforcement survey](https://docs.google.com/forms/d/e/1FAIpQLSd7SONJbO4-4oNfzB_yUcuKsGwkBYE3AKhb_JO7jfzctE5zEg/viewform) - results will be shared in the open.
* Alberto: Any recommendations for general Code of Conduct sites/resources for online message boards? Requesting something similar to event CoC site: http://confcodeofconduct.com
Kate: maybe take the Contributor Covenant and modify it? https://www.contributor-covenant.org/
*
If you are interested in lending your skills, time, energy to something specific - please add your name here. (only add if you have actual time available :)*
I can help with...
*
## Links!
Share blog posts, and other articles here!
* Jaice's article on [Being an impostor](https://medium.com/@jaydumars/i-am-an-impostor-6273106e7e07)
* Aaron's series on Listening and Trust in OSS:
* [Part 1](http://aturon.github.io/2018/05/25/listening-part-1/)
* [Part 2](http://aturon.github.io/2018/06/02/listening-part-2/)
* [Part 3](http://aturon.github.io/2018/06/18/listening-part-3/)
* Mendez et al (2018) Open Source barriers to entry, revisited: A tools perspective. Proceedings of ACM ICSE conference, Sweden, May 2018 (ICSE'2018) [session](https://www.icse2018.org/event/icse-2018-technical-papers-open-source-barriers-to-entry-revisited-a-tools-perspective) & [paper](https://ir.library.oregonstate.edu/concern/technical_reports/p5547w99b) (Note Alberto learned about this paper from recent [POSSE](http://foss2serve.org/index.php/POSSE) workshop for OSS & higher education instructors)
* from OpenSourceBridge.org #OSB18 attendees, diversity & justice channel created in new discussion board community osbridge.zulipchat.com. Conference ending after 10 years but board created to keep in touch especially to bring event back w/new leadership
* [Aaron and Niko's talk on how Rust does OSS](https://www.youtube.com/watch?v=rdmpOktHLmM)
* [The Increasing Rust's Reach program](https://blog.rust-lang.org/2018/04/02/Increasing-Rusts-Reach-2018.html)
# Agenda
## D&I in Open Source Website (8 minutes)
[Open Source Diversity](https://opensourcediversity.org) – hub for diversity & inclusion initiatives in the free & open source space
:)
We are also here for feedback.
### Questions (add here or in Zoom channel)
* How can people propose ideas or get involved?
* Github organization at https://github.com/opensourcediversity
* Twitter account at [@osdiversity](https://twitter.com/osdiversity)
* Meetup in Berlin every month https://www.meetup.com/opensourcediversity/ (also meetups in Tirana and Bangalore)
* Get involved! :) Contribute to the website, suggest projects to add, or start your own local meetup
* Where would the CHAOSS D&I workgroup fit on the opensourcediversity.org page? I think it might fit as a space to network and collaborate rather than a project that supports people - althought it does. *~Georg*
* It’s a perfect project for the site, and the only reason some projects aren’t on the site yet is simply time. ;) It would fit great in the general "Projects" category. If you like, submit a pull request to the index.html in our [website repository](https://github.com/opensourcediversity/opensourcediversity.org) simply creating a new entry. (It’s simple static HTML for now)
* Thank you, I'm happy to create the pull request. *~Georg*
* <3 thank you!
* Jaice mentioned that the toolkit would be made into a "consumable unit" - will the person hired be willing to collaborate with others on the toolkit, or will it be read-only document? (I copied this down to the current agenda item. *~Georg*)
## Inclusive Open Governance
### Panel Questions
1. Diversity and inclusion in FOSS is often an after-thought, with the burden of work by those most impacted. **Do you have any examples of how governance can make inclusive practices more central to project goals and operation?**
2. To the extent that Open Source leaders (module owners, decision-makers, enablers, coordinators) are drawn from the population of contributors with either financial freedom, or organizational support from their employers, **do you think grant systems, internships or similar can help surface more diverse leaders? Have you seen this happen?**
* "chopping wood and carrying water award" <3
* "design opportunities not to require a lot of people's time"
4. Mozilla recently released these [Open Source Archetypes](https://blog.opentechstrategies.com/2018/05/field-guide-to-open-source-project-archetypes/), which identifies different 'types' of projects - from those who are essentially building 'for themselves' (e.g. Rust developers building Rust - most tools in fact) vs those who are building for others (e.g. Linux kernel building an OS to be widely distributed - Sage: I disagree that the Linux kernel was designed to be widely distributed; the community has adapted to it being widely used, but most of the developers still view their part of the kernel as their personal domain). **Do you see a difference in how diversity and inclusion is and/or should be applied in these project 'archetypes'?**
* One of the benefits we get from having a larger community is seeing things from the perspective of people who are using Rust in production. People can get very bent out of shape about specific features - we are trying to shift the focus to the larger user group of Rust. - Aaron
* Sometimes a project is more than just a project - it's a community. It's messy and peopley and it's all about the ways in which people collaborate. Governance shapes and frames those interactions, and I believe archetypes are a way for people to express generalities. There is a base level of inclusion that is table stakes for every project. - Jaice
6. *Making Code of Conduct enforcement real, and trusted* in open projects is a major hurdle. In part, because fear that long-time/established contributors who are core to development might be impacted. **How do you deal with these types of fears (knowing those same people likely result in exclusion of others who might have equal or greater impact on a project).**
* Jaice: this is top of mind for me because I'm involved with the Kubernetes Code of Conduct document. The code of conduct should serve the victim. The Occam's razor that I use to frame it is "does this serve the victim? or "does it revictimize them?" I don't care as much about the academic framing of rights. We started with the Contributor Covenant as a base.
* Aaron: Rust started from day 1 with a code of conduct and the originator cared a lot about these issues. One of the things that our initial code of conduct failed to do was lay out a clear mechanism for how we report issues and what the consequences are for that. We had a formative experience early on with a really technically savvy contributor who was a skilled politician and over time became toxic - and they very quickly started claiming the core team was trying to silence their technical opinions. It was really difficult to deal with this and find the route least damaging to the community. One of the things we did at the top level was introduce an official moderation team of folks who do not have responsibilities on the core team - they are a separate group that has more detachment and can in some cases integrate folks into the community in a better way. There's a way in which these are also symbolic steps that are setting the norms and putting focus on the ways we want to interact. Rust is now struggling with how to ensure everyone's voice is heard (e.g one contributor comments a lot).
* Sage - suggest shifting language from "victim" to "reporter" and "harasser" to "reported person" - this allows for people who don't feel they are "victims" and shifts away from the language of sexual harassment to address microaggressions. Also allows for reports that people may not be sure if their issue is a Code of Conduct violation to be encouraged to report, even if they don't feel like a victim.
### Panel:
* [Jaice Singer Dumars](https://medium.com/@jaydumars/i-am-an-impostor-6273106e7e07#---61-342) - Open Source Software Governance program manager at Google, Kubernetes.
* [Aaron Turon](https://aturon.github.io/) - Rust Core Team
* [Paris Pittman](https://twitter.com/ParisInBmore/) (not confirmed) - Developer Relations, Kubernetes Community
### Your Questions (add here or in Zoom channel)
* Jaice mentioned that the toolkit would be made into a "consumable unit" - will the person hired be willing to collaborate with others on the toolkit, or will it be read-only document?
*
## On Meritocracy
> Sometimes good words and good aspirations get tarnished with history, and need to be set aside. I personally aspire to many aspects of our work being a meritocracy. And the original meaning I took for meritocracy in open source meant empowering individuals, rather than managers, or manager's managers or tenure-based authority. I still long to develop these things.
>
> However, it's now clear that so-called meritocracies have included effective forms of discrimination. This might be hidden bias, where some aspect of identity causes a person's contributions to be routinely devalued. It might be over discrimination or harassment. It might be threats that minimize the contributions even offered. Whatever the cause, open source "meritocracies" suffer from these problems -- open source projects tend to have less diversity than other software organizations.
>
> Fairly or not, the word "meritocracy" has come to signal systems where there is little effective restraint on perpetuating discrimination. It may even become a code-word for organizations that resist the need to build diverse and inclusive organizations.
>
> I personally long for a word that conveys a person's ability to demonstrate competence and expertise and commitment separate from job title, or college degree, or management hierarchy, and to be evaluated fairly by one's peers. I long for a word that makes it clear that each individual who shares our mission is welcome, and valued, and will get a fair deal at mozilla -- that they will be recognized and celebrated for their contributions without regard to other factors.
>
> Sadly, "meritocracy" is not that word. Maybe it once was, or could have been. But not today. The challenge is not to retain a word that has become tainted. The challenge is to build teams and culture and systems that are truly inclusive. This is where we focus.
(Source: Mitchell Baker )
### Your Questions (add here or in Zoom channel)
*
## Next Call - September 5th
[D&I Calendar]( https://calendar.google.com/calendar?cid=Z3V2dGZyc3A5YTdraGNtdjVpN21nYzN0NDBAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ)
### Topics:
* TBD - Propose a topic (eirwin@mozilla.com)
* Code of Conduct Q&A (regular section, for people to help each other)
* GDPR and your Code of Conduct - with Mozilla's trust & privacy manager [Alicia Gray](https://www.linkedin.com/in/alicia-gray-cipp-840777a/)
* invite academic scholars researching OSS communities, e.g. see Mendez 2018 under "Links!" above