Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify "community venues" in the Code of Conduct #32

Closed
k4y3ff opened this issue Oct 13, 2014 · 4 comments
Closed

Clarify "community venues" in the Code of Conduct #32

k4y3ff opened this issue Oct 13, 2014 · 4 comments

Comments

@k4y3ff
Copy link

k4y3ff commented Oct 13, 2014

The current Code of Conduct states,

We expect participants to follow these rules at all community venues (including online venues) and social events associated with the community.

We should clarify which venues and events this line refers to--the Github repos? Google Group? IRC channel? Other places not listed on the "About" page? What venues, specifically, fall under the Typelevel umbrella? We should provide a comprehensive list of (online and offline) venues within the Code of Conduct itself.

Or, alternatively, if we created this list as a separate page within the website--then linked to it from the Code of Conduct--it would be helpful not only in enforcing the Code of Conduct, but in serving as a place to point newcomers who are seeking assistance.
@puffnfresh
Copy link
Contributor

@kpfell thank you for filing this.

@k4y3ff
Copy link
Author

k4y3ff commented Oct 13, 2014

@puffnfresh No worries. ;)

@larsrh
Copy link
Contributor

larsrh commented Oct 19, 2014

Indeed, that is very important. There's typelevel/scala#66 already, which will hopefully also address #33. We're working on it.

ceedubs added a commit to ceedubs/typelevel.github.com that referenced this issue Nov 13, 2015
@ceedubs
Clarify "community venues" in CoC
a8fba57 
This is a first pass at a resolution for typelevel#32. There is almost certainly
room for improvement and expansion. I wanted to get _something_ out
there, as this has been delayed for far too long.
@ceedubs ceedubs mentioned this issue Nov 13, 2015
Merged
@adelbertc
Copy link
Contributor

Looks like this is done via #53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@puffnfresh @larsrh @adelbertc @k4y3ff