Skip to content

aspire_cloud_hosting_policy.md

Latest commit

 

History

History
51 lines (34 loc) · 3.19 KB

aspire_cloud_hosting_policy.md

File metadata and controls

51 lines (34 loc) · 3.19 KB

Aspire Cloud Hosting Policy

Preamble

The goal of Aspire Cloud Repository is to provide a robust distributed source for downloading software for extending WordPress and related compatible CMSs. The Distributed Software Repository project is released freely in order to establish a network of trusted repositories which democratize software distribution free from the control of any one person or organization.

This DRAFT policy governs what software will be accepted to host on AspirePress Cloud. At the project's inception, we are providing a general list of requirements and deferring to the corresponding guidelines available at wordpress.org for interpretation until they have been fully rewritten in this document. While this document is in draft form, in case of conflicts or updates, the guideline explanations below will supersede any others.

If you believe you have a case where a software package would not be accepted for hosting on wordpress.org, but believe it should be allowed on Aspire Cloud, please contact [email protected].

Aspire Cloud Guidelines, Terms, & Conditions

Licensing & Other Requirements

  1. Plugins must be compatible with the GNU General Public License v2, but may use any license which qualifies.
  2. By submitting your software and updates, you agree to indemnify and hold harmless AspirePress and its network partners for any actions resulting from your software.
  3. Code must be (mostly) human readable.
  4. Developers are responsible for the contents and actions of their plugins.
  5. A stable version of a plugin must be available from its WordPress Plugin Directory page.
  6. Plugins must respect trademarks, copyrights, and project names.
  7. Developers and their plugins must not do anything illegal, dishonest, or morally offensive.
  8. A complete plugin must be available at the time of submission.

Features & Functions Not Permitted

  1. Trialware is not permitted.
  2. Plugins may not track users without their explicit consent, and must offer a means for the user to opt out.
  3. Plugins may not send executable code via third-party systems.

Best Practice Guidelines

  1. Plugins should not hijack the admin dashboard.
  2. Plugins must use WordPress’ default libraries.
  3. Frequent commits to a plugin should be avoided.
  4. Plugin version numbers must be incremented for each new release. Semantic versioning is encouraged but not required.

Additional Conditions & Permission

  1. We reserve the right to maintain the Plugin Directory to the best of our ability.
  2. Software as a Service is permitted.

Community Requirements

  1. Software contributors are expected to abide by the AspirePress Code of Conduct.
  2. Public facing pages on WordPress.org (readmes) must not spam.
  3. Plugins may not embed external links or credits on the public site without explicitly asking the user’s permission.
  4. Plugins may not include affiliate links or similar codes which provide revenue to the developer without disclosing them, and must allow users to opt out or change the affiliate code.
  5. While permissible under some software licenses, we will not accept for hosting any "nulled" software.