Add a Code of Conduct page #157
Conversation
Borrowed from creative common sources: - Ubuntu Code of Conduct 2.0 http://www.ubuntu.com/about/about-ubuntu/conduct - antiharassment policy at the Geek Feminism Wiki http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy - https://gtalug.org/about/code-of-conduct/
|
As this is a big subject on it's own, this issue probably needs a vote, as it affects all members. |
|
@rwanyoike This is great! This is really good for community. |
|
C.o.Cs are mostly bullshit. I vote no. On 6/30/16, Njagi Mwaniki notifications@github.com wrote:
Mwaoshe Njemah |
|
I lean towards no too. With and without a Code of Conduct we will have good and bad people. What does having a piece of paper on the wall that we can point to change about that? We just +b you from the IRC channel and remove you from the GitHub organization and mailing list? That's all the "teeth" that we could possibly have, and it increases administrative burden of the organization (which we already kinda have problems with). |
|
Then what would have us decide that this or that is wrong or worth getting kicked out of the community over? Just common sense? |
|
We have banned people from the IRC channel before, and we don't have a code On Fri, Jul 1, 2016, 15:19 Njagi Mwaniki notifications@github.com wrote:
Alan Orth |
|
I don't feel strongly on the matter so I'm cool with whatever you guys choose. |
|
Joining the LUG (and staying) is mostly driven by personal interest rather than comfort of knowing there's protection from harassment, prejudice, disrespect, whatever else is out there... I don't personally think it's going to make a difference. Or do we have occurrences in the past that leads us to set up C.o.C? My two cents. |
|
I vote no too on this. Simpy because we are all adults and not in high school anymore plus writing down CoCs won't change a thing. People are still gonna do what they feel like doing. |
@netivity Lay out some context for me
@alanorth I agree, and that's something we need to work on
@alanorth a reference, rather than leaving it to "common sense"
@Muriukidavid Our mailing list is quite the case study ;)
@kevthanewversi Not unless there's support for a CoC |
|
Most comments here lean against having a CoC, with the idea that it's not going to make a difference, "assholes will be assholes" etc. I think it's easy to think that when you're already part of the LUG, and are used to the assholes :). But throw in a few strangers, and things go off the rails. Especially for the strangers (unless, they're assholes too) That said, my main argument for a CoC is newcomers. For people with different backgrounds, levels of confidence etc; experiences and stereotypes may block them from giving us a chance. Some edge case examples (forgive the stereotype): the n00b who fears bullying or the girl who sees a boys club... A CoC can overcome such hesitance. I'm going to steal this from https://twitter.com/lady_nerd
Notably, with more and more people attending meetups, we're no longer that small group the LUG started off as. Thanks for participating, 6/278 members ;) |
|
Now that we have a channel on Telegram 😅 (that might be much more prone to noise, and probably harder to moderate); don't you think we should at least put up a page explaining what can/can't be posted there and what actions will be taken if posted content is not 'up to spec'? |
|
^^ @poppingtonic you were suggesting? |
|
@rwanyoike The suggestion is sound. |
|
We have a telegram channel? Link please guys...?
Regards,
Kevin M. Mbarua
0702672922
stackoverflow: kevthanewversi
<http://stackoverflow.com/users/3469960/kevthanewversi>
linkedin: kevin murimi <http://ke.linkedin.com/in/kevinmurimi>
github: kevthanewversi <http://github.com/kevthanewversi>
twitter: kevthanewversi <http://twitter.com/kevthanewversi>
…On Fri, Jan 13, 2017 at 10:17 AM, Brian Muhia ***@***.***> wrote:
@rwanyoike <https://github.com/rwanyoike> The suggestion is sound.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#157 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFhu5MsWM_BnEwdnqSAdqV6Rmp0oWLXgks5rRyUSgaJpZM4JCaZ6>
.
|
|
A code of conduct and/or aims and purpose of the group may be helpful. |
|
Well, I suggest we just stick a CoC here, and adapt it as need be. i mean, this issue has been lurking here for 4 years lolz. |
|
Maybe worth discussing contents at meeting. |
|
What about having a draft, and then discussing that during a meeting. I
want to sit down and come up with one based on the things shared above.
Wdyt?
…--
Bonface M. K.
One Divine Emacs To Rule Them All
https://www.bonfacemunyoki.com
|
|
I called for a vote here: https://groups.google.com/g/nairobi-gnu/c/szM2BpWwJ5M and only 2 people voted. As such I'm going ahead to merge this. Also, later I'll create a separate MD off this and add to the repo's root as a standalone root. FWIW, I prefer this to: https://github.com/nairobilug/nairobilug.or.ke/pull/183/files since it's more encompassing. Should enough people complain, we'll just revert this commit! |
|
The votes were cast (only 2) here and merged this manually so that: (a) I can sign-off on the commits; and (b) Cc interested people. Relevant commits: @rwanyoike thanks for this! PS: Is there no easy way of signing off commits from the GH UI? Aaaargh [silly me] |
Borrowed from creative common sources:
Related to #153