‍In this article

• Maintaining a strong community
• What if something or someone offends you?
• What happens if someone violates GitLaw's policies?
• Appeal and Reinstatement
• Legal Notices

By outlining what we think a safe, welcoming, and productive community looks like at GitLaw, we hope to help you understand how best to interact and collaborate on our platform in line with our Terms of Service and Acceptable Use Policies.

We encourage our community members to communicate expectations clearly, moderate their projects where possible, and report any content that may violate our policies. GitLaw Staff will investigate any reports of abuse, and may moderate public content on our site that we determine to be in violation of our Terms of Service.

Maintaining a strong community

The primary purpose of the GitLaw community is to collaborate on legal documents. We are committed to maintaining a community where users are free to express themselves and challenge one another's ideas, both technical and otherwise. At the same time, it's important that users remain respectful and allow space for others to contribute openly. In order to foster both a safe and productive environment, we encourage our community members to look to these guidelines to inform how they interact on our platform. Below, you’ll find some suggestions for how to have successful interactions as a valued member of the GitLaw community.

• Be welcoming and open-minded - New users join our community each day. Some are well-established developers, while others are just beginning. Be open to other ideas and experience levels. Make room for opinions other than your own and be welcoming to new collaborators and those just getting started.
• Be respectful - Working in a collaborative environment means disagreements may happen. But remember to criticize ideas, not people. Share thoughtful, constructive criticism and be courteous to those you interact with. If you’re unable to engage respectfully, consider taking a step back or using some of our moderation tools to deescalate a tense situation.
• Be empathetic - GitLaw is a global community with people from a wide variety of backgrounds and perspectives, many of which may not be your own. Try to put yourself in others’ shoes and understand their feelings before you address them. Do your best to help make GitLaw a community where others feel safe to make contributions, participate in discussions, and share different ideas.

What if something or someone offends you?

While some disagreements can be resolved with direct, respectful communication between community members, we understand that is not always the case. We encourage our community to contact GitLaw Support through the GitLaw Support portal when they believe content or activity they’ve encountered violates our policies. However, if you run into something or someone on the site that you find objectionable, here are some ways GitLaw enables you to take action:

• Communicate expectations - Maintainers can set community-specific guidelines to help users understand how to interact with their projects, for example, in a repository’s README (overview) or dedicated code of conduct.
• Moderate Comments - Users with write-access privileges for a repository can edit, delete, or hide anyone's comments on commits, pull requests, and issues. Anyone with read access to a repository can view a comment's edit history. Comment authors and people with write access to a repository can also delete sensitive information from a comment's edit history. Moderating your projects can feel like a big task if there is a lot of activity, but you can add collaborators to assist you in managing your community.
• Lock Conversations  - If a discussion in an issue, pull request, or commit gets out of hand, off topic, or violates your project’s code of conduct or GitLaw’s policies, owners, collaborators, and anyone else with write access can put a temporary or permanent lock on the conversation. For more information, see "Locking conversations."
• Block Users  - If you encounter a specific user who you would rather not engage with, you can block the user from your personal account or from your organization.
• Limit Interactions - If your public project is getting unwanted attention, being trolled, spammed, or otherwise, you have the option of setting temporary interaction limits to keep certain users from interacting with your repository.

While we are passionate about empowering maintainers to moderate their own projects, please contact us through the GitLaw Support portal if you need additional support in dealing with a situation.

What happens if someone violates GitLaw's policies?

We rely on reports from the community, as well as proactive detection, to help ensure that GitLaw is a safe, welcoming, and productive platform for users. There are a variety of factors we consider when we’re made aware of behavior or content not in line with GitLaw’s policies. However, our policy enforcement and content moderation approach prioritizes our vision to be the home for all users. This means:

• We optimize for legal document collaboration. We recognize that documents can have multiple uses and we distinguish between how the documents are being used on the platform and other uses. We also think about how our enforcement actions can affect a potentially complicated web of interdependencies across the platform and aim to restrict as little legitimate content as possible.
• We take a human-centered approach to content moderation and we tailor our responses to meet the needs of a specific situation. Our global team investigates the reports we receive on a case-by-case basis—considering context and the surrounding facts—before taking action. This could include taking into account potentially offensive content being posted in a way that lacks context or makes it easy for other users to unwittingly view or interact with while using GitLaw. In those instances, we may favor moderation in order to safeguard our community.
• Our decisions are rooted in our core belief that serving an interconnected community and empowering human progress through developer collaboration requires a commitment to diversity, inclusion, and belonging.

Where we have decided that moderation action is warranted, these are some of the ways we may respond:

• Removing the offending content
• Blocking or disabling the offending content
• Downgrading the visibility of the offending content
• Hiding a user account or organization from public view
• Suspending a user account or organization

Appeal and Reinstatement

If your content or account has been disabled or restricted and you seek reinstatement or wish to appeal, please see our Appeal and Reinstatement page for information about the process and use our Appeal and Reinstatement form to submit a request.

Legal Notices

We dedicate these Community Guidelines to the public domain for anyone to use, reuse, adapt, or whatever, under the terms of CC0-1.0.

These are only guidelines; they do not modify our Terms of Service and are not intended to be a complete list. Under those terms, GitLaw retains full discretion to remove any content or terminate any accounts for activity that violates our Acceptable Use Policies. These guidelines describe when we will exercise that discretion.

‍