[Cialug] Code of Conduct?

[Jeff Chapin]

This seems like a topic I probably should not comment on (I have never paid
dues, and am a remote, email-only member), and I will not be offended if my
input is not wanted.

I think that having a code of conduct is a great idea. The world we live in
is increasingly moving towards that being expected of all groups, and it is
a sign of a willingness to be inclusive.

I do not think that it would be possible to come up with an exhaustive list
of prohibited behaviors, nor would we likely keep it maintained -- so I
think that it would be a great idea to leverage what a larger group was
doing. Add in the fact that this community, both locally, and nationally,
that our demographics are highly skewed, this is going to be a difficult
thing to create from the ground up without a base to start with.

There was an 'open source code of conduct' for a while, but they seem to
have closed the project: https://github.com/todogroup/opencodeofconduct. I
really wish that this project was still live, because we could then fork a
code of conduct off that, and vote and rebase it periodically to pull in
core updates for issues our group has not had to deal with.

All of that said, I would be interested in *starting* such a project, if
others are also interested. We could develop the code and store it on
Github, allow other groups to fork/pull requests, and develop a generic
code of conduct.  This is probably overkill for what *WE* need, but it is a
contribution to the larger open source community. Short of starting a
larger project, I would be interested in helping with the Code of Conduct
for our group.

On Mon, May 24, 2021 at 9:13 AM Theron Conrey <theron at conrey.org> wrote:

> If we're going to adapt one, I would prefer that we go broad. If there are
> folks that are looking for community, we want to make sure we're there to
> support them in the most healthy way possible. A Simple "be respectful"
> isn't going to provide the air cover folks are looking for.
>
> I would recommend starting with a couple examples of well defined codes of
> conduct from larger OS projects and maybe a few local meetups. Here are a
> few good ones imho.
>
> https://www.honeycomb.io/honeycomb-user-community-code-of-conduct/
> https://www.meetup.com/pdxpython/pages/12061872/Code_of_Conduct/
>
> addressing CoC violations is a challenge everywhere, but being clear about
> it in our CoC is critical.
>
> https://reshamas.github.io/managing-our-code-of-conduct/#addressing-violations
>
>
> I would be willing to step in and help get this off the ground if needed.
> Either way, I think this is REALLY important that we treat this with the
> seriousness it deserves, and set a high bar at inclusiveness over whatever
> the hell the other option is.
>
> -theron
>
>
> On Mon, May 24, 2021 at 1:30 AM Andrew Denner <linux-list at upeke.com>
> wrote:
>
> > As much as I hate a need to even talk about it, in the "Be prepared"
> > mindset before a problem happens, what are people's opinions on a simple,
> > easy code of conduct for the group?
> >
> > It was suggested by a long time member to have some sort of a blurb on
> our
> > website something along the lines of "CIALUG members are expected to get
> > along with others and be respectful."  I welcome anyone with wordsmithing
> > or administrative powers to improve on that statement.
> >
> > They also recommended that we come up with some sort of council or
> > procedure on how to handle any violations.
> >
> > I welcome others' thoughts and input on this issue.
> > _______________________________________________
> > Cialug mailing list
> > Cialug at cialug.org
> > https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
> >
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> https://www.cialug.org/cgi-bin/mailman/listinfo/cialug
>


-- 
Jeff Chapin
President, CedarLug, retired
President, UNIPC, "I'll get around to it"
President, UNI Scuba Club
Senator, NISG, retired