|
| 1 | +# IPFS Community Code of Conduct |
| 2 | + |
| 3 | +We believe that our mission is best served in an environment that is friendly, |
| 4 | +safe, and accepting; free from intimidation or harassment. |
| 5 | + |
| 6 | +Towards this end, certain behaviors and practices will not be tolerated. |
| 7 | + |
| 8 | +## tl;dr |
| 9 | + |
| 10 | +- Be respectful. |
| 11 | +- We're here to help: [email protected] |
| 12 | +- Abusive behavior is never tolerated. |
| 13 | +- Violations of this code may result in swift and permanent expulsion from the IPFS community. |
| 14 | +- "Too long, didn't read" is not a valid excuse for not knowing what is in this document. |
| 15 | + |
| 16 | +## Table of Contents |
| 17 | + |
| 18 | +- [Scope](#scope) |
| 19 | +- [Friendly Harassment-Free Space](#friendly-harassment-free-space) |
| 20 | +- [Reporting Violations of this Code of Conduct](#reporting-violations-of-this-code-of-conduct) |
| 21 | +- [Copyright Violations](#copyright-violations) |
| 22 | +- [Consequences](#consequences) |
| 23 | +- [Addressing Grievances](#addressing-grievances) |
| 24 | +- [Contact Info](#contact-info) |
| 25 | +- [Changes](#changes) |
| 26 | +- [Credit and License](#credit-and-license) |
| 27 | + |
| 28 | +## Scope |
| 29 | + |
| 30 | +We expect all members of the IPFS community to abide by this Code of Conduct |
| 31 | +at all times in all IPFS community venues, online and in person, and in one-on-one |
| 32 | +communications pertaining to IPFS affairs. |
| 33 | + |
| 34 | +This policy covers the usage of IPFS public infrastructure, including the |
| 35 | +IPFS.io HTTP gateways, as well as other IPFS websites, IPFS related events, |
| 36 | +and any other services offered by or on behalf of the IPFS community. It also |
| 37 | +applies to behavior in the context of the IPFS Open Source project |
| 38 | +communities, including but not limited to public GitHub repositories, IRC |
| 39 | +channels, social media, mailing lists, and public events. |
| 40 | + |
| 41 | +This Code of Conduct is in addition to, and does not in any way nullify or |
| 42 | +invalidate, any other terms or conditions related to use of IPFS services. |
| 43 | + |
| 44 | +The definitions of various subjective terms such as "discriminatory", |
| 45 | +"hateful", or "confusing" will be decided at the sole discretion of the IPFS |
| 46 | +abuse team. |
| 47 | + |
| 48 | +## Friendly Harassment-Free Space |
| 49 | + |
| 50 | +We are committed to providing a friendly, safe and welcoming environment for |
| 51 | +all, regardless of gender identity, sexual orientation, disability, ethnicity, |
| 52 | +religion, age, physical appearance, body size, race, or similar personal |
| 53 | +characteristics. |
| 54 | + |
| 55 | +We ask that you please respect that people have differences of opinion |
| 56 | +regarding technical choices, and that every design or implementation choice |
| 57 | +carries a trade-off and numerous costs. There is seldom a single right answer. |
| 58 | +A difference of technology preferences is not a license to be rude. |
| 59 | + |
| 60 | +Any spamming, trolling, flaming, baiting, or other attention-stealing |
| 61 | +behavior is not welcome, and will not be tolerated. |
| 62 | + |
| 63 | +Harassing other users is never tolerated, whether via public or private media. |
| 64 | + |
| 65 | +Avoid using offensive or harassing nicknames, or other identifiers that might |
| 66 | +detract from a friendly, safe, and welcoming environment for all. |
| 67 | + |
| 68 | +Harassment includes, but is not limited to: harmful or prejudicial verbal or |
| 69 | +written comments related to gender identity, sexual orientation, disability, |
| 70 | +ethnicity, religion, age, physical appearance, body size, race, or similar |
| 71 | +personal characteristics; inappropriate use of nudity, sexual images, and/or |
| 72 | +sexually explicit language in public spaces; threats of physical or non- |
| 73 | +physical harm; deliberate intimidation, stalking or following; harassing |
| 74 | +photography or recording; sustained disruption of talks or other events; |
| 75 | +inappropriate physical contact; and unwelcome sexual attention. |
| 76 | + |
| 77 | +Media shared through public infrastructure run by the IPFS team must not |
| 78 | +contain illegal or infringing content. You should only publish content via |
| 79 | +IPFS public infrastructure if you have the right to do so. This includes |
| 80 | +complying with all software license agreements or other intellectual property |
| 81 | +restrictions. You will be solely responsible for any violation of laws or |
| 82 | +others’ intellectual property rights. |
| 83 | + |
| 84 | +## Reporting Violations of this Code of Conduct |
| 85 | + |
| 86 | +If you believe someone is harassing you or has otherwise violated this Code of |
| 87 | +Conduct, please contact us at [email protected] to send us an abuse report. If |
| 88 | +this is the initial report of a problem, please include as much detail as |
| 89 | +possible. It is easiest for us to address issues when we have more context. |
| 90 | + |
| 91 | +## Copyright Violations |
| 92 | + |
| 93 | +We respect the intellectual property of others and ask that you do too. If you |
| 94 | +believe any content or other materials available through public IPFS |
| 95 | +infrastructure violates a copyright held by you and you would like to submit a |
| 96 | +notice pursuant to the Digital Millennium Copyright Act or other similar |
| 97 | +international law, you can submit a notice to our agent for service of notice |
| 98 | + |
| 99 | + |
| 100 | +(We will add a physical mailing address here when we acquire one). |
| 101 | + |
| 102 | +Please make sure your notice meets the Digital Millennium Copyright Act |
| 103 | +requirements. |
| 104 | + |
| 105 | +## Consequences |
| 106 | + |
| 107 | +All content published to public IPFS infrastructure is hosted at the sole |
| 108 | +discretion of the IPFS team. |
| 109 | + |
| 110 | +Unacceptable behavior from any community member will not be tolerated. |
| 111 | + |
| 112 | +Anyone asked to stop unacceptable behavior is expected to comply immediately. |
| 113 | + |
| 114 | +If a community member engages in unacceptable behavior, the ipfs team |
| 115 | +may take any action they deem appropriate, up to and including a temporary ban |
| 116 | +or permanent expulsion from the community without warning (and without refund |
| 117 | +in the case of a paid event or service). |
| 118 | + |
| 119 | +## Addressing Grievances |
| 120 | + |
| 121 | +If you feel you have been falsely or unfairly accused of violating this Code |
| 122 | +of Conduct, you should notify the IPFS team. We will do our best to ensure |
| 123 | +that your grievance is handled appropriately. |
| 124 | + |
| 125 | +In general, we will choose the course of action that we judge as being most in |
| 126 | +the interest of fostering a safe and friendly community. |
| 127 | + |
| 128 | +On IRC, let one of the ops know if you think that someone has transgressed |
| 129 | +against the Code of Conduct. If you would like to be an op and promise to |
| 130 | +help maintain and abide by the code, please let us know. |
| 131 | + |
| 132 | +## Contact Info |
| 133 | + |
| 134 | +Please contact [email protected] if you need to report a problem or address a |
| 135 | +grievance related to an abuse report. |
| 136 | + |
| 137 | +You are also encouraged to contact us if you are curious about something that |
| 138 | +might be "on the line" between appropriate and inappropriate content. We are |
| 139 | +happy to provide guidance to help you be a successful part of our community. |
| 140 | + |
| 141 | +## Changes |
| 142 | + |
| 143 | +This is a living document and may be updated from time to time. Please refer |
| 144 | +to the git history for this document to view the changes. |
| 145 | + |
| 146 | +## Credit and License |
| 147 | +This Code of Conduct is based on the |
| 148 | +[npm Code of Conduct](https://www.npmjs.com/policies/conduct). |
| 149 | + |
| 150 | +This document may be reused under a [Creative Commons Attribution-ShareAlike |
| 151 | +License](http://creativecommons.org/licenses/by-sa/4.0/). |
0 commit comments