Gitlab

You can find Gitlab's Code of Conduct at https://about.gitlab.com/community/contribute/code-of-conduct .

Repercussions

Violation of either Codes of Conduct may result in a warning, suspensions or restriction from the Gitlab or Permanent bans from the Gitlab.

There are no hard limitations on the Gitlab instance. However, once usage of individuals impacts the stability of the system or hinders others from using the same, or is designed to prevent usage of the same, limitations can be imposed on a case by case basis.

Reason

Stability and Usability of the provided Gitlab instance.

Repercussions

• In case of designed DoS attacks, the account(-s) in violation may be immediately banned and all related content archived or deleted.

• In case of (unintentional) misuse, projects in violation will be archived and the maintainers contacted by the administration in order to resolve the issue.

• In case of vast overuse compared to the average, limits may be imposed.

Keep git repositories for what they're for. Do not use them for

• Image collections

• Blob storage (outside LFS)

• Backups

Reason

Repository misuse puts immense stress on gitaly, especially during housekeeping. In extreme cases, this can cause gitaly to become unresponsive, causing a partial outage.

Repercussions

• The repository in question will be archived and read-only access granted to the maintainer limited to a week, after which the repository will be deleted

• The maintainer will be disallowed from creating new projects until contacting the administration/reacting to their contact about repository misuse

• In a repeated case, access to the Gitlab will be restricted.