webERP logoHomePage What Is webERP WeberpFeatures webERP Features WeberpFaq Documentation

WeberpSupport Support Forum Sourceforge Logo Download Demo WeberpDevelopment Development

Contributing to webERP

The guiding principles are driven by the ProjectGoals
All code contributions must comply with the CodingConventions

Procedure For Contributing

Contributions to the webERP project are encouraged - these simple procedures for doing so are aimed at reducing the confusion and co-ordinating the efforts of all contributors:

1.Join the developers mailing list.

Inform the list of your proposed developments and discuss the approach to be used. There are some knowledgeable people on the list and they can contribute ideas if you let them. This is also good to avoid overlapping effort or combine efforts in working on different elements of the same project.
A few points to remember about the mailing list:

2. Obtain the latest development scripts from SVN - see sourceforge instructions for anonymous SVN checkout the SVN files initially then updates daily - this only downloads any modified scripts, or update immediately before commencing any development.

IMPORTANT: Only do development work on the most recent scripts from SVN and update your copy of the SVN regularly. Instructions on the use of SVN at sourceforge can be found at the following URL:

3. This point is relevant only for developers that do not have SVN write access. After any modifications to the scripts - email (only) the modified scripts (and ideally a diff file between the latest SVN scripts and your updated scripts) to within 12 hours of your last update from SVN. The project admin will have to digest the modifications and ensure the coding style is consistent, test the scripts and consider the implications of the modifications in achieving the goals noted above. Plenty of narrative explaining the modifications should be posted in the developers list so all can consider the implications. They will be committed to SVN as soon as possible after receipt and testing.

4. Where modifications span 10 or more scripts at the same time, request a stay on development from other developers using the list.

5. All submissions of modifications or additions should be accompanied by a plain text change.log file describing the changes to each script. This 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. This file will be appended to the doc/change.log when the files are committed to SVN.

6. Requests for modification of the database structure - with an extract of the SQL required to effect the changes should be made to These will be included in the version upgrage script as well as the latest database structure.
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki