Contents
Experimental Repository
There is a separate repository for new/experimental code, mostly contributed by community.
For svn clients, the repo is at:
https://svn.erp5.org/repos/public/experimental
There is also a ViewVC at:
http://svn.erp5.org/experimental
Operating rules
Business Templates
The naming convention is that every business templates should be suffixed with "_experimental", whether it is an overlay to an existing bt (like erp5_crm_experimental) or something new.
Products
Modifications to core code is done in the form of monkey-patches. There is a product called Experimental, which contains some patches to ERP5 core code. The product can be simply installed and all patches will apply, or you can edit Experimental/ZopePatch.py to apply only selected patches.
(The structure should probably be changed so that patches are stored in a more orderly structure.)
The name of a patch should tell to which class it applies and what it is for.
A patch should contain the standard GPL header and a docstring explaining in detail what the patch does and containing a RATIONALE part - an explanation why it is needed or useful.
Tests
Everything should be tested. Automatic test runner is not there yet, but some day it will be. For now, authors are reponsible for testing their bt's and patches.
(where should tests be stored? Experimental/tests as others ERP5 Products)
Access
It is public-readable, write access can be obtained from Nexedi. You can also write to bartek(at)erp5.pl who is a volunteer coordinator of this repository.
Experimental contents
Business Templates
Patches