I was trying to dig up the FLOSS 2013 survey data, but it seems like the
domain I was using to find them lapsed.
I tried searching but was having a hard time finding where this data is
now. Does anyone know a current URL for where to find all of this?
Justin W. Flory
= Quick Summary =
(1) Looking at CoC from 3 views: reporter, reported, reviewer
(2) Answering three questions:
- What's helpful for reviewer
- How to protect anonymity of reporter
- What does an "end result" look like
To pick up this discussion both from our FAD and also from today's
meeting, we wanted to start the discussion about one of our oldest
tickets, about guidelines for reporting CoC violations.
To summarize what we're trying to get at, we want to figure out what
kinds of things are important for all three involved groups:
(1) The reporter
(2) The reported
(3) The reviewer
To help get at these things, we came up with three questions at the last
meeting to consider and try answering to help us get at the point of
what we want our guidelines to cover and help solve:
(1) What is helpful for someone writing a report to enable the
reader(s) to solve the problem?
(2) What is important to protect the anonymity of the reporter? How
should reports be considered for privacy?
(3) What kind of end results to a report do we want to consider?
What do you all think is important to consider here or what do you think
we should be covering with this? To help get us started, here's some of
my answers to these questions:
(1) A reviewer needs to understand what the problem is and why it is
causing a problem. If possible, having documented evidence of a dispute
or a concern is needed, like log files or screenshots. The reviewer
needs to be neutral and as much as possible, not be biased towards
either the reporter or the reported.
(2) The reporter's anonymity should always be a first concern and
private options to make reports should be available. This could be a
private ticket or a thread to explain their problem to a small, select
group of people. The reporter's name or specific details about them
should never be shared outside of the initial group reviewing the report
(unless the reporter consents to otherwise). The team reviewing should
be as small as can be justified.
(3) The key part of the end results is making the reporter feel like
their voice is being acknowledged and heard by making the report,
assuming it is valid. Having clear guidelines for actions or steps to
consider for how the report is handled and what possible outcomes of a
report are would be helpful for this, so a regular procedure can be
followed for every report.
What do you all think?
Justin W. Flory
You are kindly invited to the meeting:
Diversity Team IRC Meeting on 2017-04-05 from 07:00:00 to 08:00:00 US/Eastern
The meeting will be about:
Every week, the [Diversity Team](https://fedoraproject.org/wiki/Diversity) meets to discuss items on our [agenda](https://pagure.io/fedora-diversity/issues).
The goal of this diversity initiative is to help promote an inclusive community within Fedora. To do this, we assist the Diversity Advisor with the planning and implementation of diversity efforts such as the enforcement of the code of conduct, creating content highlighting the diverse community in Fedora, and offering workshops and fostering communication between Fedora sub-projects.
Wednesday March 8 is International Women's Day , an annual global event
that aims to forge a more diverse and inclusive working world.
Though women is a underrepresented gender in Fedora community, they make
a substantial impact.
Let's celebrate women's day by appreciating and recognizing women
contribution in Fedora.
I hope we will all make an effort to ensure that Fedora is a diverse and
Thanks & Regards,