Solid Community Code of Conduct

We as members of the Solid community pledge to make participation in our community a positive experience for everyone, regardless of identity.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

We defer to the W3C Code of Conduct for Expected Behavior, Unacceptable Behavior and Safety versus Comfort.

If you experience a situation that this Code of Conduct does not cover, please get in touch with the Solid-ODI Ombuds (solid-ombuds@theodi.org). If you would like to propose changes or improvements to this document, please create an issue and notify the Solid-ODI Ombuds.

Code of Conduct violations will be handled Solid-ODI Ombuds (solid-ombuds@theodi.org). Specifically the Ombuds is responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any Code of Conduct violations.

Corrective actions may include removing, editing, or rejecting comments, commits, code, wiki edits, issues, and other contributions. The Ombuds will communicate reasons for moderation decisions when appropriate.

This Code of Conduct applies to any Solid Github Repos, Chats and Forums that are not already governed by the W3C Ombuds. It also applies when an individual is officially representing the community in public spaces such as using an official e-mail address, posting via an official social media account, or acting as a representative at an online or offline event.

There are a number of channels for communicating about Solid on Matrix. To support keeping these conversations focussed - we encourage conversation to be kept to the appropriate channels; and will moderate repeated and intentional off-topic discussions as unprofessional behavior.

Scope of Matrix Channels

• solid-odi: Sharing updates, ideas, and questions directly relevant to the ODI's work on Solid. Collaborating on projects, initiatives, and research that further the ODI’s mission in the Solid ecosystem.
• solid/solidos: For conversation directly relating to the development of, or questions about, the Solid Operating System.
• solid/app-development: Topics related to application development for Solid. If this channel appeals to you, you may also be interested in joining the “Solid Practitioners” group.
• solid/specification: For work developing the Solid Community Group Specification(s). Applicable topics include: Work on the specification; Application developers providing feedback on the specification; Application developers are asking questions about the specification.
• Solid Practitioners A communication channel for the Solid Practitioners group
• solid/solidcommunity.net: Topics related to the solidcommunity.net server - a hosted Solid Server now maintained by the Open Data Institute. Outages should be reported to: The ODI's Solid technical support.
• CommunitySolidServer/community: Discussion related to the Community Solid Server. Questions for maintainers should be directed to the GitHub discussions page.
• linkeddata/chat: General conversations about linked data topics and tooling that do not specifically relate to Solid.
• linkeddata/rdflib.js: Topics related to rdflib.js
• solid/test-suite: Discussion related to the test suites for the Solid Community Group specification. The current test suites are
• solid/node-solid-server: Discussion related to the Node Solid Server.
• Activitypub-interop: Discussion for interoperability between Solid and the ActivityPub specification.
• Solid: General discussion related to the Solid project.

Deprecated channels

The following channels are deprecated and should not be used.

• solid/team
• solid/community-server
• solid/ux-research
• solid/solid-spec
• solid/authorization-panel

Instances of abusive, harassing, or otherwise unacceptable behaviour as defined in the W3C Code of Conduct should be reported to the ODI Ombuds.

All reports of violations will be reviewed and investigated promptly and fairly and handled under confidentiality.

The Code of Conduct Committee, made up of one or more ODI Solid Ombuds, will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

Continued behavior

The Code of Conduct Committee, made up of one or more ODI Solid Ombuds, will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from the Ombuds, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate.

2. Warning

Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No unsolicited interaction with the people involved in the incident(s), including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

3. Temporary Ban

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period. No public or private interaction with the people involved, including unsolicited interaction with the Ombuds, is allowed during this period. Violating these terms will lead to a permanent ban.

4. Permanent Ban

Community Impact: Demonstrating a pattern of violation of the community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within then community.

To promote accountability and allow community members to correct behaviour before facing serious consequences.

Strike 1: Warning

For the first time or a minor violation of a code of conduct.

Strike 2: Final warning

Repeated violation or a more serious infraction.

Strike 3: Consequences / Removal

Final action due to repeated or severe misconduct.

Large portions of the text for this policy: Positive Work Environment at W3C: Code of Ethics and ProfessionalConduct are taken from the following resources:

W3C Code of Ethics and Professional Conduct 2014.

Geek Feminism Community anti-harassment/Policy.

For guidelines on how to give constructive and positive feedback, please see How to give better feedback.