11 | | You should fill in all applicable information when submitting a new product. It's required that a support topic be created in the forum, and must be linked to from the appropriate field. Products which have a download (i.e., not a service) available should include the actual product in that download. For example, including a text file and including additional steps is highly discouraged, unless required for some reason, in which case a note must be included in the product's description. |
| 13 | You should fill in all applicable information when submitting a new product. It's required that a support topic be created in the forum, and must be linked to from the appropriate field, unless the product is for a service. Products which have a download (i.e., not a service) available should include the actual product in that download. For example, including a text file and including additional steps is highly discouraged, unless required for some reason, in which case a note must be included in the product's description. |
| 47 | Products can be removed from sale for missing this information. Developers can even be suspended if a product is reported for missing this information, so including it is a must. |
| 48 | |
| 49 | === Integrations === |
| 50 | |
| 51 | You are allowed to offer integrations for third-party scripts, as long as the following requirements are met. |
| 52 | |
| 53 | An integration must make use of Dolphin features. For example, if a third-party script has support for accounts, that support should be removed and Dolphin's account system used instead. Do not use a cheap <iframe> embed of a script or linking to it from Dolphin's menu. Requiring the script be installed separately already means we're not dealing with an integration. The script should be released as a module with the installation taken care of like a normal module. This will require a lot of extra work in some cases, but that's part of the deal with releasing an integration. |
| 54 | |
| 55 | Also keep in mind the license of the script. If releasing the script as part of an integration is against the license, don't do it. If releasing the script as part of an integration and charging for it is against the license, also don't do it. Products which make use of third-party scripts will be checked to make sure there is nothing wrong on the legal side of things. |
| 56 | |
| 57 | === Legalities === |
| 58 | |
| 59 | Products must not violate the code's license, nor must it be considered illegal in the United States (which is where all these wires that serve the market are housed). |
| 60 | |
| 61 | === Further Reading === |
| 62 | |