[Chaoss-software] [Oss-health-metrics] [CoC working group] Invite to Code of Conduct working group
Jesus M. Gonzalez-Barahona
jgb at bitergia.com
Wed Nov 15 09:02:42 UTC 2017
On Tue, 2017-11-14 at 21:48 -0800, Raymond Paik wrote:
> Thanks Georg.... Sorry I could not be at the meeting.
>
> A clarifying question on one of the items. When you say "digital", I
> assume that means the CoC not only cover behaviors at in-person
> events/events (in physical spaces), but also behaviors online (e-
> mail, conference calls, etc.)?
Yes. In fact, that "digital behaviour" is more important for us that
"in-place", since the former would be far more frequent.
This comes in part from the fact that, due maybe to historical reasons,
some CoC could seem designed for in-place situations, with only some
mentions or "extensions" for digital situations.
Jesus
> Ray
>
> On Tue, Nov 14, 2017 at 2:46 PM, Georg Link <glink at unomaha.edu>
> wrote:
> > Hi CHAOSS Community,
> >
> > The CoC working group had its first call today.
> > We make our process open to the whole community, share our minutes
> > here with you, and archive them on the mailing lists.
> >
> > IRC Minutes: http://ircbot.wl.linuxfoundation.org/meetings/chaoss-c
> > ommunity/2017/chaoss-community.2017-11-14-21.01.html
> > IRC Log: http://ircbot.wl.linuxfoundation.org/meetings/chaoss-commu
> > nity/2017/chaoss-community.2017-11-14-21.01.log.html
> >
> > ===== On Call =====
> > - Georg Link
> > - Jesus M Gonzales-Barahona
> > - Sean Goggins
> > - Vicky Janicki
> >
> > Absent:
> > - Alexander Serebrenik
> > - Ray Paik
> >
> >
> > ===== Agenda =====
> > - Agree on working group procedure
> > - Agree on why we want a CoC for CHAOSS
> > - Agree on features we want our CoC to have
> > - Agree on criteria for evaluating a CoC. (removed because
> > duplicate with previous)
> > - Determine next steps and next meeting
> >
> >
> > ====== Agree on working group procedure ======
> > We use the first meeting to determine the requirements for a CHAOSS
> > CoC. Then we spend some time individually evaluating existing CoC’s
> > against our requirements. The goal is to find a CoC we are
> > comfortable with and avoid writing our own. In our second call, we
> > discuss the benefits and shortfalls of existing CoC’s and formulate
> > a recommendation to the CHAOSS governance board.
> >
> > The result of the meetings will be posted to the mailing lists.
> >
> >
> > ====== Agree on why we want a CoC for CHAOSS ======
> > The CHAOSS Project has in its charter section 5 for a code of
> > conduct.
> >
> > 5. Code of Conduct
> > 1. The GB may adopt a fair, reasonable, and non-discriminatory
> > Project code-of-conduct, with approval from The Linux Foundation as
> > outlined below.
> > 2. The Project will operate in a transparent, open,
> > collaborative, and ethical manner at all times.
> > 3. The output of all Project discussions, proposals,
> > timelines, decisions, and status will be made open and easily
> > visible to all.
> >
> > This section encapsulates our core values of being an open
> > community. It is a rough guideline for everyone participating in
> > the CHAOSS Project. However, the charter gives the GB the power to
> > implement a more detailed Code of Conduct that is more specific on
> > acceptable behavior and can provide consequences for someone who
> > does not behave according to our values.
> >
> >
> > ====== Agree on features we want our CoC to have ======
> >
> > 1) *Positive.* Some CoC seem more oriented to avoid bad behavior
> > that anything else. We prefer those that are positive, describing
> > how the community is and wants to be diverse, and how we all want
> > to have diversity in mind and how we encourage diversity. For
> > example, We prefer to say "Our community is inclusive, and respects
> > any person, whichever their culture, national origin, gender, age,
> > ..." instead of having a list of "bad behaviors". The former is
> > more welcoming.
> >
> > 2) *Broad.* As broad as possible. To deal with as many different
> > cases of community behavior - instead of enumerating behaviors. -
> > Balance between being specific and generic that focuses on the
> > idea.
> >
> > 3) *Equal.* A conflict of professional/work CoC with our CHAOSS
> > CoC. We will only propose our own Code of Conduct and cannot speak
> > to other communities and accepted behavior there. We can treat
> > everyone as responsible individuals who have to comply with our CoC
> > in the same ways.
> >
> > 4) *Public.* Make all CoC incidences and consequences public. This
> > does not apply to the whole process, but to the final decisions.
> >
> > 5) *Reporting.* Have a private email address for reporting
> > incidences. A team of 3 are elected to watch this address and deal
> > with the incidences and escalate if necessary.
> >
> > 6) *Digital.* Some code of conducts are historically created for
> > physical spaces. We want one that is specified for digital spaces.
> >
> > 7) *Abstract.* Abstract with spirit of CoC at the top and then
> > guidelines specified in detail below.
> >
> > 8) *Consequences.* Outlines a way to deal with misconduct.
> > Specifies consequences for misconduct. - For example excluding
> > someone from the community.
> >
> >
> > ====== Determine next steps and next meeting ======
> >
> > Everyone looks at 1-2 codes of conduct and compares them against
> > our criteria.
> > Only put CoCs that one of us proposes in our table.
> > We have two evaluators/reviewers for each CoC.
> > We have a Google Doc, in which we capture the outcome of our work:
> > https://docs.google.com/document/d/12NVJnFccSapPKK_f5a7HjwgQ4VP2ws9
> > Sn1IG2t8ha4g/edit?usp=sharing
> >
> > We will meet once more to compare notes and make a recommendation.
> >
> >
> > Best,
> > Georg
> >
> > On Sat, Nov 11, 2017 at 11:54 AM, Georg Link <glink at unomaha.edu>
> > wrote:
> > > Hi CHAOSS community,
> > >
> > > I present to you the CoC working group and provide details on our
> > > first meeting.
> > >
> > >
> > > # CoC working group members
> > >
> > > The following CHAOSS CoC working group members self-selected by
> > > answering the Doodle:
> > > - Alexander Serebrenik
> > > - Georg Link
> > > - Jesus M Gonzales-Barahona
> > > - Ray Paik
> > > - Sean Goggins
> > > - Vicky Janicki
> > >
> > >
> > > # Meeting Details
> > >
> > > We will meet Tuesday, November 14, 2017 at 3pm US Central Time
> > > (immediately after the weekly metrics hangout call).
> > >
> > >
> > > # Proposed Meeting Agenda
> > >
> > > - Agree on working group procedure. (following items depend on
> > > this decision).
> > > - Agree on why we want a CoC for CHAOSS.
> > > - Agree on features we want our CoC to have.
> > > - Agree on criteria for evaluating a CoC.
> > > - Determine next steps and next meeting.
> > >
> > >
> > > # Meeting Document
> > >
> > > We have a Google Doc, in which we can capture the outcome of our
> > > work:
> > > https://docs.google.com/document/d/12NVJnFccSapPKK_f5a7HjwgQ4VP2w
> > > s9Sn1IG2t8ha4g/edit?usp=sharing
> > >
> > >
> > > # Meeting Location
> > >
> > > Anyone can join the meeting:
> > > Join from PC, Mac, Linux, iOS or Android: https://unomaha.zoom.us
> > > /j/6440246040
> > > Or iPhone one-tap :
> > > US: +14086380968,,6440246040# or +16468769923,,6440246040#
> > > Or Telephone: Dial(for higher quality, dial a number based on
> > > your current location):
> > > US: +1 408 638 0968 or +1 646 876 9923 or +1 669 900 6833
> > > Australia: +61 (0) 2 8015 2088
> > > Germany: +49 (0) 30 3080 6188
> > > Ireland: +353 (0) 1 691 7488
> > > Netherlands: +31 (0) 20 241 0288
> > > Spain: +34 91 198 0188
> > > Meeting ID: 644 024 6040
> > > International numbers available: https://unomaha.zoom.us/zoomconf
> > > erence?m=YWAlhhdbhslUJ5Cfo9K919HXCUMBC-2T
> > >
> > >
> > > Best,
> > > Georg
> > >
> > > PS: To reduce cross-posting, please respond only on the Oss-healt
> > > h-metrics at lists.linuxfoundation.org list.
> > >
> > >
> > > On Tue, Nov 7, 2017 at 7:35 PM, Georg Link <glink at unomaha.edu>
> > > wrote:
> > > > Hi everyone,
> > > >
> > > > We have had some great discussion about the Code of Conduct
> > > > (CoC) the CHAOSS group should adopt. Thank you to everyone who
> > > > sent an email or commented on the GitHub issue.
> > > >
> > > > To date, we seem to agree:
> > > > - CHAOSS should have one CoC which uniformly applies to both
> > > > committees
> > > > - CHAOSS should look at existing CoC's as a first option
> > > > before writing a new CoC
> > > >
> > > > To move the CoC discussion forward and come to an agreement, I
> > > > invite you to a working group. The working group will make a
> > > > recommendation to the CHAOSS Board which then will vote on the
> > > > proposal.
> > > >
> > > > I hope the working group can accomplish its goal with two calls
> > > > and thus I propose the following process:
> > > > - 1st Call:
> > > > * Decide on requirements we want from a CoC
> > > > - Between calls
> > > > * Review CoC's and check them against our requirements
> > > > - 2nd Call
> > > > * Discuss existing CoC's regarding our requirements
> > > > * Formulate a recommendation to the CHAOSS Board
> > > >
> > > > If you want to participate in the working group, please fill
> > > > out the doodle so that we can find a time that most of us can
> > > > participate in the first call. The call will, of course, be
> > > > announced on both CHAOSS mailing lists and will be open to
> > > > anyone:
> > > > https://doodle.com/poll/3wr7ubyvhvycuq8n
> > > >
> > > > Best,
> > > > Georg
> > > >
> > > > PS: Sorry for cross-posting but this is relevant to both CHAOSS
> > > > committees.
> > > >
> > > > --
> > > > Georg J.P. Link
> > > > PhD Student
> > > > College of Information Science and Technology | PKI 367
> > > > University of Nebraska at Omaha | www.unomaha.edu
> > >
> > >
> > >
> > > --
> > > Georg J.P. Link
> > > PhD Student
> > > College of Information Science and Technology | PKI 367
> > > University of Nebraska at Omaha | www.unomaha.edu
> >
> >
> >
> > _______________________________________________
> > Oss-health-metrics mailing list
> > Oss-health-metrics at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/oss-health-metri
> > cs
--
Bitergia: http://bitergia.com
/me at Twitter: https://twitter.com/jgbarah
More information about the Chaoss-software
mailing list