-
Notifications
You must be signed in to change notification settings - Fork 144
Diversity Working Group Meeting Agenda - 2021 #577
Comments
In the Community Working Group Meeting on 2020-12-16 we agreed on updating the CoC criteria for Ansible Collections as follows:
Let's discuss how the D&I team should evaluate the CoCs - responsibilities, procedure, criteria for what should be in a good CoC, a list of approved standard CoCs etc. How to code of conduct - notes from discussions by @abadger @jillr @samccann |
Java, Ansible, Openshift expertise needed. Join the Hack-a-thon to support the Southern Coalition for Social Justice. As part of the MLK Day of Service, the Red Hat Social Innovation Program is looking for 50-100 participants to support a development effort for the Southern Coalition for Social Justice’s Open Data Policing project. (There's a sign up link for hatters but I'm not sure if community members who are interested can participate). |
Meeting 2021-01-07how the D&I team should evaluate the CoC
Review the sensu-go-ansible collection CoCHack-a-thon to support the Southern Coalition for Social Justice.LogsMinutes: https://meetbot.fedoraproject.org/ansible-diversity/2021-01-07/ansible_d&i_wg_agenda:_https:github.comansiblecommunityissues577.2021-01-07-19.01.html |
|
The Contributor Covenent CoC v1.4 has changed over time without being version incremented. We've voted today to approve the latest version of the text, which maps to this commit: https://github.com/ContributorCovenant/contributor_covenant/blob/207d47805029f4029494f404182f67733f509399/content/version/1/4/code-of-conduct.md |
19:59 <@zodbot> Meeting ended Thu Jan 21 19:59:37 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . |
Action Item: everyone to review contributor covenant CoC 2.0 for next time |
|
Screen readersDo we have any guidance for writing wrt screen readers? abadger1999 made the point that we should not use "please click Also I'm working on using the new (limited Alpha) GitHub issue templates, which should not only be easier for people to complete, I hope would be easier for screen readers. |
I stopped using "click" in general even without considering accessibility issue, as I found it to be more of a boilerplate on the web. If the link is correctly produced, it should be visible to the user even without telling user to click it. I am quite curious about the upcoming new issue templates, do they finally add fields? |
I've found this collection of how to design for accessibility quite interesting and useful, including for screenreaders: https://ukhomeoffice.github.io/accessibility-posters/ Here's the repo: https://github.com/UKHomeOffice/posters |
|
|
We agreed that the Ansible Community will sponsor the PyLadies auction at PyCon US 2021 Meeting ended Thu Mar 18 19:59:08 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . |
Meetbot went away at some point, so irc log from today: https://gist.github.com/jillr/d799c14e05c57017af330466bd70f2cb |
|
|
We didn't have zodbot yet (until the last few minutes, hehe) so meeting log from libera.chat: |
|
|
Meeting ended Thu Aug 5 19:17:33 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . |
Meeting ended Thu Sep 2 19:22:17 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . |
|
Please leave a comment regarding any agenda item you wish to discuss. If you don't show up for the meeting, your item will be skipped.
If your IRC nick is different from your Github username, leave that as well.
Meetings are every other Thursday (e.g; 2021/01/07, 2021/01/21) on IRC at 19:00 UTC.
Diversity Working Group: https://github.com/ansible/community/wiki/Diversity
#ansible-diversity on Libera Chat IRC
The text was updated successfully, but these errors were encountered: