Terms of Use

We welcome you (“you” or the “user”) as a contributor, user, editor or reader, and we encourage you to join our community. Before you participate, however, we ask that you please read and agree to the following Terms of Use (“Terms of Use”).

§ 1 What we provide

(1) For Free and Libre Open Source Software (FLOSS) projects, the OpenGit Foundation provides various services like, but not limited to, a public repository and version control system, wiki and issue tracker, under certain terms and conditions. These services are referred to collectively as “service”, “hosting” and “platform” in this document.

(2) Our service is open for all projects covered by a free software or open source licence, as defined by either the Free Software Foundation (FSF) or the Open Source Initiative (OSI). We do reserve the right to limit the amount of resources, hosted projects and users to ensure stability and performance of the platform.

(3) OpenGit is a non-profit foundation funded by donations, sponsorships, subsidies, grants and sales of merchandise. The services provided by the OpenGit Foundation in the pursuit of its goals, rely on those donations, sponsorships, subsidies, grants and sales of merchandise.

(4) The main objective of OpenGit is to build, maintain and support infrastructure services used for the creation, maintenance, collection, dissemination, and archiving of Free and Libre Open Source Software (FLOSS).

§ 2 Allowed Content & Usage

(1) By using OpenGit, you agree to adhere to the following rules when posting content. Content can include, but is not limited to, repository contents, wiki articles, issue comments, etc.:

  1. Repository content shall be licensed under a free and libre open source software licence approved by the Free Software Foundation (see list of the FSF) or the Open Source Initiative (see list of the OSI).

    Reasonable exceptions are, to a very limited extent, considered acceptable.

    For example: releasing single logo image files of a FLOSS project under separate less free or non-free licence that requires derivative works to use their own logo that is clearly distinguishable from the original work even in absence of trademark registration.

  2. Private repositories are only allowed for things that are reasonably required for the maintenance of FLOSS projects, like storing secrets, team-internal discussions or temporarily hiding projects from the public until they are ready for usage and/or contribution. They are also allowed for really small & personal stuff like your journal, configuration files, ideas or notes, but explicitly not as a personal cloud or media storage.

  3. Forks, migrations and testing repositories are considered as inactive when they do not contain unique contributions and are inactive for more than a month. They should not be kept for a prolonged amount of time, and thus might be removed after notifying maintainers and providing a 90 days period to ask for preservation.

  4. Repositories and attachments may not contain harmful code that can be run accidentally during normal development workflow and should use proper disclaimers and protections if and where applicable. Furthermore, software that is clearly written to do harm to other computers is only allowed in the context of security research or education and must be flagged accordingly.

  5. You must not share any content that is expressing hate or encouraging violence towards a person or group for any reason. We also explicitly do not tolerate:

    • Discriminatory behaviour towards others or promoting oppression;
      especially of marginalized groups on grounds of ethnicity, gender, disability, nationality, education, age, or religion.
    • Violent nationalist propaganda, Nazi symbolism or promoting the ideology of National Socialism;
    • Mobbing;
      (either bullying in any context, or specifically to that within the workplace, especially when perpetrated by a group rather than an individual)
    • Stalking;
      (unwanted and/or repeated surveillance or contact by an individual or group toward another person)
    • Doxxing;
      (the act of publicly providing personally identifiable information about an individual or organization, usually via the Internet and without their consent)
    • Brigading;
      (a group banding together, or inciting to do so, in order to perform a coordinated, often negative, action against an individual, group or organization)
    • Threatening and harassment, as well as encouraging others to do those things;
    • Insults, discriminatory jokes, sexualized comments and other unwanted sexual attention;
    • Sexually explicit and/or obscene content, including content involving the exploitation or sexualization of minors;
    • Content that is glorifying violence. That includes any violent material without a proper content warning;
    • Content that harms the reputation of OpenGit, its staff members or the OpenGit Foundation;
    • Actively encouraging others to do any of the things mentioned in this section;

(2) Failure to comply with the rules in §2 (1) leads to immediate removal of the content together with a warning; further violations might result in immediate account suspension. In non-obvious cases, decisions about account suspensions and content removal are made in good faith by OpenGit staff.

(3) We additionally reserve the right to remove any content or account with a notice providing a reason and possibly conditions for re-uploading the content.

(4) Content that is deemed illegal in The Netherlands (e.g. by violating copyright or privacy laws) will be taken offline and may lead to immediate account suspension.

(5) Actions intended to damage the OpenGit Foundation, its platform or services, its reputation, service availability, performance or any other form of harm, may lead to immediate account suspension. In the case of excessive traffic/resource usage, or unreasonable storage requirements, a warning will normally be issued at first, unless the actions are obviously done with malicious intent.

(6) Maintainers of a project can enforce stricter rules, for example by adding an easily discoverable Code of Conduct as a file in the repository root. It’s the maintainers’ task to enforce such additional rules.

§ 3 Responsibilities, Copyright & Guarantees

(1) You are responsible for your own actions. Please act accordingly and apply appropriate security measures to protect your own data and account access credentials. This means especially that:

  1. You are legally responsible for your edits and contributions on the platform, so for your own protection you should exercise caution and avoid contributing any content that may result in criminal or civil liability under any applicable laws (e.g. copyright and patent infringements, but also things like age-restricted content without age confirmation). Both the Dutch legislation and the legislation in your country of residence may be relevant here.

  2. You are solely responsible for your use of any third-party websites or resources. Although some projects may contain links to third-party websites and resources, we do not endorse and are not responsible or liable for their availability, accuracy, or the related content, products, or services, nor do we have any obligation to monitor such third-party content.

  3. You are responsible for safeguarding your account credentials and should never disclose them to any third party.

  4. You must make sure that we have a way to contact you by keeping the email address of your account up-to-date.

(2) All content on the Version Control System and other facilities provided on the platform are uploaded by end users. Contributors own all rights and ownership for content and contributions they provided. Using the platform does not imply any transfer of ownership or copyright.

(3) We make no guarantees about the availability of the content hosted on our platform. Although we try to preserve all content for the future, you are solely responsible for making regular backups of everything you rely on.

(4) Changes to the Terms of Use are communicated via an announcement banner in your dashboard, blog post and/or other communication means provided by the platform. If you do not login for longer than three months, it is your own responsibility to re-check the current Terms of Use. If you disagree to a change, you are solely responsible for closing your account.

§ 4 Cancellation and Termination

(1) You may close your account at any time. Please be aware that it is your responsibility to remove content and contributions that you no longer wish to persist. All other content previously contributed by you might remain visible to other users of the platform.

(2) Abandoned user accounts or organizations with no (or extremely few) all-time contributions may be deleted after being unused for 365 days. A warning via email is sent 1 month in advance.

(3) Accounts created for the sole purpose of advertisement (excessive or obvious promotion of a product, service or company) are removed immediately.

(4) Accounts created for the sole purpose of illegal activities (under Dutch and/or European law) are suspended and/or removed immediately.

(5) OpenGit reserves the right to suspend and/or remove any account at any time if it is used for activities harming OpenGit or its associated platform and services, directly or indirectly, even if these activities are not explicitly listed in the examples above.

§ 5 Disclaimer of Warranties and Liability

(1) The materials on our platform are provided on an ‘as is’ basis. OpenGit makes no warranties, expressed or implied, and hereby disclaims and negates all other warranties including, without limitation, implied warranties or conditions of merchantability, fitness for a particular purpose, or non-infringement of intellectual property or other violation of rights.

(2) Further, OpenGit does not warrant or make any representations concerning the accuracy, likely results, or reliability of the use of the materials on its website or otherwise relating to such materials or on any sites linked to this site.

(3) In no event shall OpenGit or its suppliers be liable for any damages (including, without limitation, damages for loss of data or profit, or due to business interruption) arising out of the use or inability to use the materials on OpenGit’s platform, even if OpenGit or an OpenGit-authorized representative has been notified orally or in writing of the possibility of such damage. Because some jurisdictions do not allow limitations on implied warranties, or limitations of liability for consequential or incidental damages, these limitations may not apply to you.

§ 6 Sources & License of this text

(1) The rules (§ 2) were inspired by the chaos.social Terms, licensed under CC BY-SA 4.0, as well as by the JetBrains Open Source and Community Code of Conduct, licensed under CC BY-SA 3.0 and the CodeBerg Terms of Use, licensed under the CC-BY-SA (Attribution-ShareAlike 4.0 International) license.

(2) This text is free to be adapted and remixed under the CC-BY-SA (Attribution-ShareAlike 4.0 International) license.