Experimental Projects

Hey beautiful people, ckknight here.

There has been some hub-bub about project approvals recently and one way we figured that we could help on the backend side of things is to introduce the concept of experimental projects. If you have a cool idea but nothing fleshed out, your project is best considered "experimental". This is especially true for libraries. Many of the best libraries out there have a lot of rehashing, discussing, even without much in the way of code. Previously, a lot of projects (especially libraries) were left in a limbo state where this should fill that gap.

You can flag your project as experimental when creating, or it may be flagged for you by an administrator while in the approval queue.

If you flag your project as experimental:

  • It will not sync to Curse.com
  • Unless it violates the terms of service or is plagiarism, it is likely to be accepted.
  • You will be able to use all the features of a normal project, including repositories, pages, etc.
  • Once a release file is uploaded (or created through the packager), it will be flagged as needing standard approval.

At any time, you may resubmit your project for approval to make it a non-experimental project.