|
| 1 | +# Code of Conduct |
| 2 | + |
| 3 | +This Code of Conduct describes how we expect people to behave in spaces run by Yourself To Science™. |
| 4 | + |
| 5 | +Our goal is simple: build the world’s simplest way for anyone, anywhere, to contribute to science. To do that, we need community spaces that stay focused on science, data, and useful discussion — not on personal attacks or unrelated fights. |
| 6 | + |
| 7 | +This Code applies to all interactions in official Yourself To Science spaces, including GitHub issues and pull requests, project discussions, and any other channels listed in the documentation. |
| 8 | + |
| 9 | +## Canon 1 – Integrity |
| 10 | + |
| 11 | +- Do not misrepresent data, sources, or your own role or expertise. |
| 12 | +- Make a clear distinction between evidence, opinion, and speculation when you contribute. |
| 13 | +- You are welcome to share tools, services, or resources you are involved with, as long as they are relevant and discussed on their merits. |
| 14 | + |
| 15 | +## Canon 2 – Conduct in Community Spaces |
| 16 | + |
| 17 | +- Do not harass, threaten, or deliberately intimidate anyone. |
| 18 | +- Do not use personal attacks, slurs, or targeted insults. |
| 19 | +- Keep discussion roughly on-topic for this initiative and the specific thread (issues, pull requests, or discussions). |
| 20 | +- Do not use project spaces to provide personalised medical advice or to ask others for diagnoses or treatment decisions. |
| 21 | + |
| 22 | +## Canon 3 – Collaboration and Review |
| 23 | + |
| 24 | +- Focus comments and reviews on ideas, data, and code — not on personal characteristics. |
| 25 | +- When you disagree, explain why in clear terms and, where possible, point to evidence or alternatives. |
| 26 | +- Maintainers may close or redirect threads that become repetitive, off-topic, or hostile. |
| 27 | + |
| 28 | +## Canon 4 – Use of the Yourself To Science’s Name and Infrastructure |
| 29 | + |
| 30 | +- Do not present unofficial work as if it were an official part of Yourself To Science. |
| 31 | +- Do not use project spaces to run unrelated political campaigns or personal attacks. |
| 32 | +- Do not claim project endorsement for products, services, or organizations without explicit permission from the maintainers. |
| 33 | + |
| 34 | +## Canon 5 – External Opinions and Politics |
| 35 | + |
| 36 | +- You are free to hold and express any views elsewhere. In project spaces, keep discussion tied to Yourself To Science’s purpose: helping people discover and evaluate ways to contribute to science. |
| 37 | +- Avoid importing external political or cultural fights into project channels when they are not directly relevant to the work. |
| 38 | + |
| 39 | +## Canon 6 – Reporting and Consequences |
| 40 | + |
| 41 | +If you believe this Code of Conduct has been violated in project spaces, you can report it by contacting the maintainers at [email protected] or via the channels listed in the project documentation. |
| 42 | + |
| 43 | +Maintainers may respond to violations in one or more of the following ways, depending on severity and context: |
| 44 | + |
| 45 | +- Clarifying expectations in the relevant thread. |
| 46 | +- A private or public warning. |
| 47 | +- Limiting or removing a person’s ability to participate in some or all project spaces. |
| 48 | + |
| 49 | +Maintainers should not retaliate against anyone who reports a concern in good faith. |
0 commit comments