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.
This fixes my ticket
http://www.curseforge.com/projects/curseforge/tickets/297-non-project-repos-for-concept-and-or-misc-ideas/
Very good idea!
Nice one!
@WilliamWhite No, it'd be obvious if yours was, there's a big message on the project page saying that the project is experimental.
Your projects just have no beta or release files. Technically downloadable through the Curse Client, but not to show up on Curse.com
Is this change, perchance, somehow causing my addon (which might be considered experimental) to have been stricken off Curse.com and rendered impossible to download with the Curse Client?
It's very inconvenient to test a multi-user addon when it cannot be distributed in any meaningful way...
thumb up