Code of Conduct #586

willscott · 2020-06-19T18:43:28Z

Using the IPFS code of conduct as a baseline.

cc @hsanjuan as a member of that abuse team

CODE_OF_CONDUCT.md

alanshaw · 2020-06-19T20:44:57Z

CODE_OF_CONDUCT.md

+We expect all members of the community to abide by this Code of Conduct at all times in all community venues, online and in person, and in one-on-one communications pertaining to the project.
+
+This policy covers the usage of our public infrastructure, including the drand network, as well as drand related events, and any other services offered by or on behalf of the drand community. It also
+applies to behavior in the context of the IPFS Open Source project communities, including but not limited to public GitHub repositories, IRC channels, social media, mailing lists, and public events.


alanshaw · 2020-06-19T20:45:39Z

CODE_OF_CONDUCT.md

+
+Harassment includes, but is not limited to: any behavior that threatens or demeans another person or group, or produces an unsafe environment; harmful or prejudicial verbal or written comments related to gender, gender expression, gender identity, sexual orientation, disability, ethnicity, religion, age, physical appearance, body size, race, or similar personal characteristics; inappropriate use of nudity, sexual images, and/or sexually explicit language in public spaces; threats of physical or non-physical harm; deliberate intimidation, stalking or following; harassing photography or recording; sustained disruption of talks or other events; inappropriate physical contact; and unwelcome sexual attention.
+
+Media shared through public infrastructure run by the IPFS team must not contain illegal or infringing content. You should only publish content via IPFS public infrastructure if you have the right to do so. This includes complying with all software license agreements or other intellectual property restrictions. You will be solely responsible for any violation of laws or


This does not seem relevant to drand!

alanshaw · 2020-06-19T21:00:26Z

CODE_OF_CONDUCT.md

+
+## Contact Info
+
+The Drand team currently defers to the IPFS abuse team for Code of Conduct resolutions. Please contact abuse@ipfs.io if you need to report a problem or address a grievance related to an abuse report.


Just have an abuse@drand? I feel we should try to prioritise getting help in this document not who is providing it. Personally I’d remove references to IPFS here.

IPFS is large enough to have trained an abuse team to handle these issues, and can act as a neutral 3rd party arbiter. we could do much worse than deferring to that abuse team if us an them are willing to have that happen.

when there are code of conduct issues, it's important that the person sending the report knows who it's going to, and has transparency in that. Ideally we list the people here, but if we defer to IPFS i think it's okay to include a link to the IPFS code of conduct so that there's one authoritative source of that membership rather than this one potentially getting stale. (re your pointer to credit below)

IPFS is large enough to have trained an abuse team to handle these issues, and can act as a neutral 3rd party arbiter. we could do much worse than deferring to that abuse team if us an them are willing to have that happen.

Um, okay. Just to be clear I was not suggesting that it’s a bad idea to defer this to the IPFS abuse team or that they are in any way a bad choice for it.

My thoughts were just to ensure the contact info is front and centre, instead of an advertisement for IPFS, which is how I felt it could come across.

In hindsight I think you’re right and if we’re going to defer to IPFS for abuse issues then for transparency we actually shouldn’t have our own email address.

In which case we can easily resolve this by switching the sentence around so that the contact details come first, followed by clarification of who is receiving it and why.

CODE_OF_CONDUCT.md

daviddias

This PR adds an important piece to ensure that the Drand community, despite small, remains healthy as it grows.

I do see this PR making a lot of decisions though, for example, entangling Drand with IPFS. We can leverage the fact that IPFS (at PL) has a well trained team to handle abuse requests and will know what to do, however, we should not entangle as in "the IPFS team" will take responsibility without checking first.

Let's check with the Projects org to know how to better handle this.

hsanjuan · 2020-06-25T16:30:48Z

Let's nominate 2 or 3 people in Drand's orbit for this?

willscott · 2020-06-26T14:46:47Z

Let's nominate 2 or 3 people in Drand's orbit for this?

is it worth the complexity of a separate group for this? I think i'm vaguely in favor of centralization here so that a smaller number of people can be better trained. I think it's also useful for the abuse team to be able to approach CoC issues from a largely external / neutral-arbitrator perspective.

willscott · 2020-07-03T20:55:07Z

this is held on change requested from @daviddias - let me know resolution

CODE_OF_CONDUCT.md

daviddias

Good to go. Should this go on the website rather than here? Then the repo could just link to the version in the website. Thoughts? //cc @johnnymatthews @alanshaw

CODE_OF_CONDUCT.md

willscott · 2020-07-06T18:41:32Z

if we're maintaining a separate alias / abuse team we need to specify who they are in this document. (people reporting an issue care about who they're reporting it to - in particular caring if the email is going to the person they're reporting)

daviddias · 2020-07-08T07:27:15Z

CODE_OF_CONDUCT.md

+
+## Contact Info
+
+Please contact abuse@drand.love if you need to report a problem or address a grievance related to an abuse report.


Suggested change

Please contact abuse@drand.love if you need to report a problem or address a grievance related to an abuse report.

Please contact abuse@drand.love if you need to report a problem or address a grievance related to an abuse report. Currently, this address inbox is handled by [Protocol Labs](https://protocol.ai).

@willscott good?

i meant more that as in https://github.com/ipfs/community/blob/master/code-of-conduct.md#contact-info it's generally expected that the people who are responsible for handling problems are listed.

johnnymatthews · 2020-07-12T17:27:52Z

Good to go. Should this go on the website rather than here? Then the repo could just link to the version in the website. Thoughts? //cc @johnnymatthews @alanshaw

Doesn't hurt to have this in both repos.

Having a CODE_OF_CONDUCT here along side things like LICENSE and COPYRIGHT helps keep this repo fleshed out. This comes with the minor inconvenience of having to update the drand/website version when this gets changed, but it's not too much trouble.

alanshaw · 2020-07-13T13:58:46Z

Good to go. Should this go on the website rather than here? Then the repo could just link to the version in the website. Thoughts? //cc @johnnymatthews @alanshaw

The code of conduct applies to the drand project as a whole not just this repo, so I'd probably move it to the website but retain a CODE_OF_CONDUCT.md here with a link to it. We should add a CODE_OF_CONDUCT.md to other repos that are likely to get community attention as well (the drand JS client for example).

github-actions · 2020-08-07T22:09:01Z

Command results

Details:

Run doctoc

changed:
  - /home/runner/work/drand/drand/README.md
  - /home/runner/work/drand/drand/cmd/relay-gossip/README.md
unchanged:

Changed files

Changed 2 files:

README.md
cmd/relay-gossip/README.md

Repo | 📝 Issues | 🏬 Marketplace

daviddias · 2020-08-10T05:15:58Z

@alanshaw not opposed to your plan of #586 (comment). I'm merging this one as "The CoC has been reviewed and approved", can you then handle the wrangling of moving things around and adding to the website?

alanshaw · 2020-08-10T08:26:09Z

Move Code of Conduct to the website: drand/website#75
Reference Code of Conduct from drand repo: #741
Add Code of Conduct (referencing website) to JS client: drand/drand-client#5

draft code of conduct

d43eaa8

willscott requested review from alanshaw, hsanjuan and nikkolasg June 19, 2020 18:43

alanshaw reviewed Jun 19, 2020

View reviewed changes

updates

677714e

alanshaw approved these changes Jun 22, 2020

View reviewed changes

daviddias suggested changes Jun 22, 2020

View reviewed changes

daviddias reviewed Jul 6, 2020

View reviewed changes

CODE_OF_CONDUCT.md Show resolved Hide resolved

Update CODE_OF_CONDUCT.md

1b393d1

daviddias approved these changes Jul 6, 2020

View reviewed changes

daviddias changed the title ~~draft code of conduct~~ Code of Conduct Jul 6, 2020

daviddias reviewed Jul 6, 2020

View reviewed changes

CODE_OF_CONDUCT.md Outdated Show resolved Hide resolved

Update CODE_OF_CONDUCT.md

1890eea

daviddias reviewed Jul 8, 2020

View reviewed changes

willscott and others added 2 commits August 7, 2020 15:08

Update CODE_OF_CONDUCT.md

8b27e0c

docs: update TOC

f862126

daviddias requested a review from jpeg07 August 9, 2020 08:44

Merge branch 'master' into conduct

81978c6

daviddias approved these changes Aug 10, 2020

View reviewed changes

daviddias merged commit 4fb4125 into master Aug 10, 2020

daviddias deleted the conduct branch August 10, 2020 05:38

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Code of Conduct #586

Code of Conduct #586

willscott commented Jun 19, 2020

alanshaw Jun 19, 2020

alanshaw Jun 19, 2020

alanshaw Jun 19, 2020

willscott Jun 21, 2020

willscott Jun 21, 2020

alanshaw Jun 21, 2020

daviddias left a comment

hsanjuan commented Jun 25, 2020

willscott commented Jun 26, 2020

willscott commented Jul 3, 2020

daviddias left a comment

willscott commented Jul 6, 2020

daviddias Jul 8, 2020

daviddias Jul 8, 2020

willscott Jul 8, 2020

johnnymatthews commented Jul 12, 2020

alanshaw commented Jul 13, 2020

github-actions bot commented Aug 7, 2020

daviddias commented Aug 10, 2020

alanshaw commented Aug 10, 2020


		Harassment includes, but is not limited to: any behavior that threatens or demeans another person or group, or produces an unsafe environment; harmful or prejudicial verbal or written comments related to gender, gender expression, gender identity, sexual orientation, disability, ethnicity, religion, age, physical appearance, body size, race, or similar personal characteristics; inappropriate use of nudity, sexual images, and/or sexually explicit language in public spaces; threats of physical or non-physical harm; deliberate intimidation, stalking or following; harassing photography or recording; sustained disruption of talks or other events; inappropriate physical contact; and unwelcome sexual attention.

		Media shared through public infrastructure run by the IPFS team must not contain illegal or infringing content. You should only publish content via IPFS public infrastructure if you have the right to do so. This includes complying with all software license agreements or other intellectual property restrictions. You will be solely responsible for any violation of laws or


		## Contact Info

		The Drand team currently defers to the IPFS abuse team for Code of Conduct resolutions. Please contact abuse@ipfs.io if you need to report a problem or address a grievance related to an abuse report.


		## Contact Info

		Please contact abuse@drand.love if you need to report a problem or address a grievance related to an abuse report.

Code of Conduct #586

Code of Conduct #586

Conversation

willscott commented Jun 19, 2020

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

daviddias left a comment

Choose a reason for hiding this comment

hsanjuan commented Jun 25, 2020

willscott commented Jun 26, 2020

willscott commented Jul 3, 2020

daviddias left a comment

Choose a reason for hiding this comment

willscott commented Jul 6, 2020

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

johnnymatthews commented Jul 12, 2020

alanshaw commented Jul 13, 2020

github-actions bot commented Aug 7, 2020

Command results

Changed files

daviddias commented Aug 10, 2020

alanshaw commented Aug 10, 2020