From: Daintree F. <p.d...@xt...> - 2003-09-04 07:22:35
|
Men, First cut .... all comments appreciated: Phil Developer Guidelines for Contributions Contributions to webERP are encouraged - these simple procedures for doing so are aimed at reducing the effort for other developers and co-ordinating the efforts of all contributors: 1.. Join the list web...@li... and inform the list of your proposed developments to avoid overlapping effort. b.. Obtain the latest development scripts from CVS - see sourceforge instructions for anonymous cvs checkout the CVS files intially then updates daily - this only downloads any modified scripts, or update immediately before commencing any development. c.. After any modifications to the scripts - email (only) the modified scripts to dai...@so... within 12 hours of your last update from CVS. They will be committed to CVS as soon as possible after receipt and testing. If you wish to modify several scripts email only the scripts modified each day for submission to CVS rather than waiting for all the modifications to be complete. This will minimise any re-work for modifications done on the same script by other developers. d.. Create any new scripts in your own time frame and submit them to dai...@so.... They will be committed to CVS as soon as possible after receipt and testing. e.. Where modifications span 10 or more scripts at the same time, request a stay on development from other developers using the list web...@li... f.. All submissions of modifications or additions should be accompanied by an updated change.log file describing the changes to each script. This is a chore but explains to everyone the nature of the changes made. Each entry in the change log should state the developer name and date of the change/addition. g.. Requests for modification of the database structure or fields should be made to dai...@so... |