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

Add instruction of how to report coc violation #71

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Mariatta
Copy link
Member

@Mariatta Mariatta commented Apr 8, 2017

Closes #70

cEP-0006.md Outdated

Finally, the coala Code of Conduct Committee will make a report on the situation
to coala Community Team Leader. The coala Community Team Leader may choose to
make public

Choose a reason for hiding this comment

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

Line contains following spacing inconsistencies:

  • Trailing whitespaces.

SpaceConsistencyBear, severity NORMAL, section spacing.

The issue can be fixed by applying the following patch:

--- a/cEP-0006.md
+++ b/cEP-0006.md
@@ -143,7 +143,7 @@
 
 Finally, the coala Code of Conduct Committee will make a report on the situation
 to coala Community Team Leader.  The coala Community Team Leader may choose to
-make public 
+make public
 
 # Conflicts of Interest
 

@sils
Copy link
Member

sils commented Apr 9, 2017

apart from some spacing issues it's totally good, ack from me!

@sils
Copy link
Member

sils commented Apr 9, 2017

@sims1253 ?


# What happens after you file a report?

You will receive an email from a member coala Code of Conduct Commitee
Copy link
Member

Choose a reason for hiding this comment

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

From a member of ...

Copy link

Choose a reason for hiding this comment

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

Typo: Commitee -> Committee

* An imposed vacation (i.e. asking someone to "take a week off" from coala spaces).
* A permanent or temporary ban from all of coala spaces (gitter, GitHub, GitLab, etc)
* A request for a public or private apology.
* We'll respond within one week to the person who filed the report with either
Copy link
Member

Choose a reason for hiding this comment

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

I don't believe this needs to be in this bulleted list

@Makman2
Copy link
Member

Makman2 commented Apr 9, 2017

Sounds good, also ack from me

@Nosferatul
Copy link
Member

ack

Copy link

@NiklasMM NiklasMM left a comment

Choose a reason for hiding this comment

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

Is the coala Code of Conduct Committee ever defined anywhere? Maybe we should clarify what it is?

* Names (real, nicknames, or pseudonyms) of any individuals involved.
If there were other witnesses besides you, please try to include them as well.
* When and where the incident occurred. Please be as specific as possible.
* Your account of what occurred. If there is a publicly available record (e.g.
Copy link

Choose a reason for hiding this comment

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

Maybe add something like "Which part of the CoC specificaly do you think was violated?"? Should be clear in most cases, but just to be sure.

Copy link
Member

Choose a reason for hiding this comment

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

I think this is good as it is needed for a coc violation and helps us to make faster decisions.


# What happens after you file a report?

You will receive an email from a member coala Code of Conduct Commitee
Copy link

Choose a reason for hiding this comment

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

Typo: Commitee -> Committee

it by creating an issue at https://gitlab.com/coala-coc/coc-issues, and check
the "This issue is confidential and should only be visible to team members with
at least Reporter access." checkbox. We strive to keep all issues confidential.

Copy link
Member

Choose a reason for hiding this comment

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

maybe also enable emails to the coc email? If they are, for whatever reason unable to create issues. We can create the issues ourselves in those (hopefully rare) cases.

Copy link
Member Author

Choose a reason for hiding this comment

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

We don't have coc email. Should it just come from community email then?

Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure only the community team leader can read the community mails so this would be a privacy problem.

* Whether this event constitutes a code of conduct violation.
* Who the bad actor was.
* Whether this is an ongoing situation, or if there is a threat to anyone's
physical safety.
Copy link
Member

Choose a reason for hiding this comment

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

in regards to online bullying, this might not only be physical safety but general well being.

guarantee we'll act on it.

Finally, the coala Code of Conduct Committee will make a report on the situation
to coala Community Team Leader.
Copy link
Member

Choose a reason for hiding this comment

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

Right now, The Commitee consists of the BDFL, the community team leader and the coc maintainer. So this point is obsolete. Also maybe define the commitee somewhere?

Copy link
Member Author

Choose a reason for hiding this comment

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

I can remove this part. Will add a section of who the committee are.


In the event of any conflict of interest, or when the incident involves one of
coala Code of Conduct Committee, the member must immediately notify the other
members, and recuse themselves if necessary.
Copy link
Member

Choose a reason for hiding this comment

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

This might lead to all members leaving (if they are all involved) and thus, leading to no action, which is not desirable.

Copy link
Member Author

@Mariatta Mariatta Apr 9, 2017

Choose a reason for hiding this comment

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

Maybe when such conflict of interest happens, the member can appoint another non-conflicted coala member to act in their place?
I just want to make sure that the people making decision is as neutral as possible.

Copy link
Member

Choose a reason for hiding this comment

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

Replacing people has permission implications, such as incoming member having access to old cases about them, and how to prevent the conflicted member from participating (reading) the case potentially involving them, and what to do if there are two cases concurrently, only one with a conflict.

The stand-in is also not going to settle in quickly to meet deadlines mentioned above.

A permanent stand-by non-voting member would reduce these issues.

In my experience it is better to remove the conflicted member immediately, and proceed promptly with a reduced bench, and then reinstate conflicted member or permanently replace them if report warrants it.

protect everyone involved. This means we may delay an "official" response
until we believe that the situation has ended and that everyone is physically
safe.

Copy link
Member

Choose a reason for hiding this comment

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

Maybe add that reports might be forwarded to the police (or similar) if we find it appropriate/necessary.


In the event of any conflict of interest, or when the incident involves one of
coala Code of Conduct Committee, the member must immediately notify the other
members, and recuse themselves if necessary.
Copy link
Member

Choose a reason for hiding this comment

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

Replacing people has permission implications, such as incoming member having access to old cases about them, and how to prevent the conflicted member from participating (reading) the case potentially involving them, and what to do if there are two cases concurrently, only one with a conflict.

The stand-in is also not going to settle in quickly to meet deadlines mentioned above.

A permanent stand-by non-voting member would reduce these issues.

In my experience it is better to remove the conflicted member immediately, and proceed promptly with a reduced bench, and then reinstate conflicted member or permanently replace them if report warrants it.

* A permanent or temporary ban from all of coala spaces (gitter, GitHub, GitLab, etc)
* A request for a public or private apology.
* We'll respond within one week to the person who filed the report with either
a resolution or an explanation of why the situation is not yet resolved.
Copy link
Member

Choose a reason for hiding this comment

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

Should we include some kind of minor penalty for frivolous complaints? Only for the absolutely ridiculous ones.

Copy link
Member

Choose a reason for hiding this comment

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

This would be hard to get 'right'.

Are there other CoC that have included something like that?

If not, I think we should consider that when we've actually seen it occur.

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

12 similar comments
@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

8 similar comments
@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

@gitmate-bot
Copy link

Hey! This pull request hasn't been updated for a while :/ It would be nice if we could get this going again!

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

Successfully merging this pull request may close these issues.

10 participants