Skip to content

CodeMC Usage Guidelines

By joining CodeMC are you agreeing to the below written Usage Guidelines ("Guidelines"). Not following them will result in punishments, as described within the Punishments section of this page.

Project Standards

Projects on the CodeMC CI need to follow certain standards to be allowed to stay on it.

Project must be of good quality

The Code of your project should display a high level of quality and effort.
This includes, but isn't limited to following Coding Practices such as Don't Repeat Yourself (DRY), SOLID, etc., properly documenting code to explain more complicated parts and similar.

Project must be of use for others

While it can be nice to have a CI for your library to upload and share, should you limit it to libraries and projects that can have a use for others.
Effectively, if the project's purpose is to ease your coding of other Projects, while not having any use outside of that for others, is it something you shouldn't put on our CI.

Project must be properly maintained

CodeMC is not meant as a cheap way of storing your project's final jar file without any updates to it. As such are we requiring your project to be actively maintained by receiving regular updates.
Do note that we consider the following as maintaining a project:

  • Creating commits with proper messages.
  • Keeping dependencies updated.
  • Keeping the project's issue and Pull request tracker clean by closing issues, closing/merging pull requests, labeling them, assigning people, etc.

With all this said are we aware that there can be justifiable reasons for a projects being stale. In such cases do we ask you to inform us about it, so that we are aware.

Project cannot encourage nor support illegal activities or content

We want the programming community to be as welcoming and inclusive as possible. As such are we not tollerating projects that encourage, include or support hate-speech, racism, sexism, bigotry or any other form of harassment, or illegal content.
Should you find such a project on our CI are your obligated to report it to us as soon as possible to be dealt with.

Project should have an english documentation available

CodeMC accepts non-english projects. However, to allow a user to easily understand what this project does and is about, should it provide easy access to an english documentation of the Project's README or other noteworthy documentation a user may want to read.

Translations done through a translator without proofreading by an English-speaking person should note less than 100% accuracy, indicating the use of a translator.

Reasonable Usage Limits

We do not apply usage limits (Rate limits) on most of our Services. For parts where we do this are we giving relatively generous limits.
In order to keep this state and not force harsher limits on anyone are we requesting you to not abuse these limits in any way. This means to keep frequency of builds and uploads to the Nexus to a reasonable limit.

Punishments

We reserve the right to punish you in the following ways, should you be confirmed to have broken these guidelines:

  • Restricting access to our Nexus and CI.
  • Removal of builds and Nexus uploads.
  • Removal of your Project(s).
  • Removal of your account(s).
  • Partial or complete blocking of access to our Services.

CodeMC may issue one or multiple of the above punishments at any given time at our discretion. Any of these actions may happen in any order of any severity.

Guideline Updates and Opting out

These guidelines may be updated at any given moment and we will inform about those on our Discord Server unless not possible for technical reasons.
Should we update these Guidelines will we grant a 1 Week (7 Days) Period to Opt out of these Guidelines. You may Opt-out by no longer using our Services. By continuing to use our services after the aforementioned period are you agreeing to the updated Guidelines.

You may find the date of last update at the bottom.