Developer Guidelines

This Developer Guidelines covers all extensions and themes for 6A72 CMS.

Definitions

• "Project" Means Extension or Theme.
• "You" means an individual or a legal entity that created the project.
• "Open Source License" refers to a license that allows end-user to modify and/or share the source code under defined terms and conditions.

Publishing

You are responsible for what you publish.

You will not promote violence, pornographic material, or discrimination based on race, sex, religion, nationality or age. Also your content will not violate the legal rights.

You will not impersonate or attempt to impersonate another user, 6A72 employee or any company.

You will not introduce or publish any viruses or any kind of malicious and harmful materials.

You will only release stable version of your project from 6A72 developers panel.

You will not advertise anything but you can advertise the paid version of the project (only via text format).

You can publish your project based on any open source license. The License for the project and third party libraries should be included as a text file in your project root folder.

You will not uglify or obfuscate the codes. Project codes should be human readable.

You will not sell a project for a period of time (but you can sell support for a period of time). If your open source license allows to sell the project, you will give the end-user any next version of updates.

You will not track users without their consent. You will mention any kind of tracking method on your project about page and readme file.

When third party library is included in 6A72 CMS (such as jQuery), you will use that instead of importing another instance. Your project should be updated if that library is updated and your project cannot work with new version of that library.

6A72 employees will review your project in each version release. Each review may take 1 to 15 days. If your project has a problem, 6A72 employee will change your version status to the "Correction Requested" and you fix the problem and then send the version again. Next review may take 1 to 15 days again. We are trying our best to make this process as fast as possible.

Changing Developer Guidelines

This page can be updated in the future. Your continued use after any change in this developer guidelines will constitute your acceptance of such change.