While our intent is to not have a lot of rules about what can go into the Rock Shop, we do reserve the right to decline a package's inclusion. Please see our Terms and Conditions for Rock Shop Vendors for details on our policies. Communicating with us before development will help improve the chance that your package will be included without delay.

In general, the evaluation process will include (but is not limited to) the points below:

• Make sure your package file meets the specs. We'll especially be looking to see that you are not putting files in core folders and that the uninstall steps you provide are accurate.
• Check to ensure that your plugin meets all of the guidelines below.
• We will do a very quick visual inspection of the code to make sure that it's in good standing. We will not be policing code heavily for quality nor will we be looking for bugs. We just want to make sure that it won't adversely impact the performance or integrity of the customer's system.
• Check to see if all of the proper information is provided for your package and that this information is of reasonable quality.
• We'll also check to ensure that the application functions and performs as advertised and documented post install.
• While we don't anticipate this being a problem, we will, of course, not post packages that are inappropriate or not germane to Rock's intended audiences.

Unlike many product app stores, we will not reject packages that compete with features already in Rock. We believe that choice is good and that rising tides raise all boats.

We do reserve the right to reject a package from the Rock Shop for reasons other than those listed above. Again our intent is not be rigid, but to ensure the quality and reliability of the packages that are in the Rock Shop.