Changes between Version 4 and Version 5 of MarketEtiquette

Timestamp:

Jul 14, 2011, 2:29:19 PM (13 years ago)

Author:

YobiLab

Comment:

--

MarketEtiquette

@@ -2 +2 @@
 
 this page is under collaborative construction
-
-Discussion started here - http://www.boonex.com/n/development-etiquette 
 
 '''1) CSS coding way:'''
@@ -42 +40 @@
 
 -Each module should always include the english language file. Each module should not have any missing language string. Also the languages strings should be written in a way that the customer will be able to easily modify them.
+
+ 
+
+The above ones are only the very basic requirements. Every developer/designer interested in being part of this Development Etiquette should provide other requirements, that would be globally reviewed and then accepted.
+
+ 
+
+'''4) Licensing:
+'''
+-Licenses should be provided in a simple way. The customer should be able to understand how and when is necessary to get a license for our module.
+
+-The license system we are adopting must run on a secure server with at least 2 GB of RAM.
+
+-We must provide to the user the opportunity to change the domain associated to the license. Licenses can be for One Domain. But if the customer requires to change a specific domain name with another one we have to give this oppurtunity. We cannot use such restriction.
+
+-Continuos remote checks are not allowed as well.
+
+'''5) Encryption:'''
+
+Encryption is possible to protect our own work.
+
+- CSS, HTML, Javascript, jQuery code should not be encrypted, ever.
+
+- If possible only the Core of the module should be encrypted and not the entire code, in order to give the possibility to the customer to change the code where needed, after a proper communication to you, if the module is commercial.
+
+'''6) Support:'''
+
+-We should be available at least 5 days of the week
+
+-We should be able to provide answers by mail or PM at least every 24 hours
+
+-We should always open a specifc support Forum in the proper section for EACH module we sell on the market
+
+-Updates or Upgrades should be released for free for each customer when already has a previous version of the module/template. This also applies for new versions of Dolphin. If the module you are selling is the same for Different versions of Dolphin, then the customer can claim it for free. Updating the module for a new version of Dolphin is required if even only one customer (that has already bought your module) will require that. (Edited : 25/06/2011)
+
+-If we are going to not be available for a certain period, this should be well written in your Boonex Profile. We reject unsupported profiles for over 2 weeks.
+
+'''7) Branding:'''
+
+Logo Branding is permitted only for non-commercial scripts
+
+-No Logos, Names, Links should be in the code if you are selling a commercial product. This applies both on front-end and back-end.
+
+-If for any reason you must include your Brand, that must be specified in the Market post IN BOLD
+
+-The name of the module that will appear in the back-end and in the URL should not contain our Name or TradeMark. The Name of the module should not include in any way our Brand.
+
+-Modules should be listed under the "Modules" tab in the backend. If for any reason we have to use another tab for our module, that should not ever include our Brand.
+
+-The name of the module should be "generic". We can give a name to the module on the Market Post. We cannot do the same in the Module itself. This is also to avoid a "Way for Branding" in the customer admin panel or URL.
+
+'''8) Product description:'''
+
+The description of the product must be easy to understand. We should include any possible detail. Also a Chagelog is required when we are providing different versions of the same module. In the description we should include IN BOLD anything that differs from these requirements. We should also explain why there are differences. Also we should make a notice here if you are making a module that is different for any reason from these requirements. This should not happen, only if this is necessary, and that should be properly noticed and written, or we will be immediately rejected!
+
+-Every developer should have a Demo site where all the modules can be properly tested.
+