1. *Consult this mailing list.* Provide a sample of the config file you are planning to add. Make sure that the file has a description header comment. 2. Update the relevant README files which describe the purpose of each of these files.
The same is applicable if you are planning to make changes to a config file. This includes removing existing elements or adding new elements. All such elements should ideally have a comment explaining its purpose & usage in the XML file itself. Some XML files have become messy and nobody except the person who added the files knows the usage of some of these files. -- *Afkham Azeez* Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, * * *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/> * email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
