Board Thread:News and Announcements/@comment-24473195-20150815154410/@comment-24473195-20150818090814

Curiouscrab wrote:

Dessamator wrote: The best case scenario would be two new namespaces here, one code library namespace, and one namespace for scripts awaiting review. Categories would probably be much easier to keep track of with less title renaming (or at least for the scripts awaiting review). The category would be added to the documentation page (whether it exists or not at the time). There are many problems associated with using the main namespace:


 * Code-editor can't work properly - because it has to change between editing code/ documentation/ normal article.


 * Preventing scripts with severe errors -  Like the lua namespace it is possible to prevent scripts being saved with severe errors


 * Documentation - if the main namespace is locked to code editors only. That means only code editors can create or update the documentation, increasing the chances of it becoming outdated.


 * The main space has a lot of uses aside from code - portals, talk pages, guides, and so forrth.

I agree, that two namespaces might not be necessary, but there's definitely a need for a separate namespace for code, and maybe a page to put review requests, for scripts stored in the user namespace.