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.

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

Create CODE_OF_CONDUCT.md #36

Closed
wants to merge 1 commit into from
Closed

Create CODE_OF_CONDUCT.md #36

wants to merge 1 commit into from

Conversation

kousu
Copy link
Member

@kousu kousu commented Nov 18, 2021

Fixes neuropoly/intranet.neuro.polymtl.ca#23 (I know that that's in the other repo 🤷)

Fixes neuropoly/intranet.neuro.polymtl.ca#23 (I know that that's in the other repo 🤷)
Copy link
Member

@jcohenadad jcohenadad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @kousu
i suppose we also need to add an entry in the TOC

@kousu
Copy link
Member Author

kousu commented Nov 18, 2021

Hang on, is there a pre-existing policy somewhere? Was there something on the old site?

I blindly copy-pasted the most common CoC thinking it would apply to the wiki(s) itself; like, the abstract space of code. But putting it on the ToC implies it's wider than I thought. There must be university policy that we need to make sure it's compatible with.

I'm not that comfortable with just pasting this on top without knowing we can mean it. We need to know what procedures would be in place to actually enforce it, and what parts intersect with university admin.

A lot of the examples in neuropoly/intranet.neuro.polymtl.ca#25 (comment) have expectations/harrassement/etc. sections. I'm sure those were informed by their own niches.

@jcohenadad
Copy link
Member

unfortunately i have other priorities now and i cannot spend more than 2min in choosing/fixing the appropriate CoC-- so i see 2 options:

  • @kousu you take the lead and choose what's best
  • we merge this so at least we have something (better than nothing) and in the future we improve

@kousu
Copy link
Member Author

kousu commented Nov 19, 2021

I would rather not do something as important as a CoC as a throw-away PR like that. Fixing a CoC isn't like fixing a broken link, it's important to get it pretty much right on the first try.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Code of conduct needed
2 participants