codeandcoffeelb / codeandcoffeelb.github.io

The repo for the official website for Code and Coffee in Long Beach, CA. Made with jekyll.
http://www.codeandcoffeelb.org
12 stars 14 forks source link

Adopt a Code of Conduct #39

Closed rogerhoward closed 8 years ago

rogerhoward commented 8 years ago

A Code of Conduct helps define expected behavior so that everyone understands what's considered appropriate in our community, both online and in person. Ideally a CoC will help everyone feel welcome.

Suggested Codes of Conduct we can use as a model?

torch2424 commented 8 years ago

Might I suggest the MLH code of conduct.

the usual tldr; is Don't be a jerk :)

http://static.mlh.io/docs/mlh-code-of-conduct.pdf

rogerhoward commented 8 years ago

:+1:

rogerhoward commented 8 years ago

@davidnuon @karimamer @torch2424 Quick, easy read. I suggest we adopt this unless there are objections.

I'll leave this issue open until Sat.

torch2424 commented 8 years ago

Sounds good! Of course, we reference the mlh code of conduct, and replace mlh with code and coffee haha

karimamer commented 8 years ago

i would like to add some stuff to that code of conduct

but other then that :+1:

rogerhoward commented 8 years ago

@karimamer i love that - a lot of it overlaps with the existing MLH CofC... i'd actually move that we just adopt this statement instead of MLH, maybe with a few minor edits.

torch2424 commented 8 years ago

@rogerhoward I agree with this

karimamer commented 8 years ago

:+1: I agree

poproar commented 8 years ago

:+1: @karimamer Quick, concise, clean, and simple.

masterH3X commented 8 years ago

I agree with @karimamer

thebeachdev commented 8 years ago

I like what Karim said, but I was wondering if we adopted the MLH, would we input member related contact info in it? I'm referencing to the Reporting Procedures part.

rogerhoward commented 8 years ago

I think the MLH is too formal, and too oriented around the kind of large scale events they run. That section was of some concern, though I simplified it alot and basically made me the primary reporter, with optional others available if im being reported.

I don't see an issue with the contact info, as much or as little as people are comfortable with. I'm easily found in meatspace.

karimamer commented 8 years ago

@poproar @Jadex1 it is not mine. it bases on lambda conf and strange loop code of conduct :+1: i should have made that clear i apologize

rogerhoward commented 8 years ago

@karimamer - since you (I think) have contacts within LambdaConf, can you secure permission for us to use their pledge as our own? I don't see an explicit license to do so, so we need permission from them.

karimamer commented 8 years ago

@rogerhoward yes i can ask them

karimamer commented 8 years ago
screen shot 2016-02-13 at 10 43 36 am
torch2424 commented 8 years ago

@karimamer YOU DA REAL MVP :100: :100: :100:

karimamer commented 8 years ago

bnz9te3ccaazzrd

karimamer commented 8 years ago

@rogerhoward @davidnuon could i make a page for the code of conduct ?

davidnuon commented 8 years ago

@karimamer I swear that somone posted a draft of one earlier...maybe I was imagining things. It was a lot like Lambda Conf's :confounded:

@rogerhoward didn't you draft one?

rogerhoward commented 8 years ago

@karimamer After re-reading their response... I've got misgivings.

No problem with either of those points, however the final point kinda concerns me...

This suggests to me that they think we want to adopt their CoC exactly as-is, in which case just linking to their copy makes sense. Instead, we're basing ours on theirs - I don't want ours to change every time theirs does...

@davidnuon - yes, I already created a page in branch "feature/#39-code-of-conduct"

rogerhoward commented 8 years ago

Am I overthinking this? I suggest we go with the page I crafted, put that online and send to Karim's contact asking for approval. That'll simplify.

karimamer commented 8 years ago

@rogerhoward reflecting their changes in the code of conduct could be an issue. if they ever put something we don't agree with in it (wich i personally think it is unlikely but you never know ) but i think we can go ahead with theirs for now and whenever they make a change we can discuss if we adopt it or write our own