DEVELOPMENT
The A2Billing team would like to enable developers to contribute to the A2Billing project. Please review the notes below to decide how you would like to contribute.
Subversion
A2Billing has moved all its development on to an SVN server which can be found at http://svn.a2billing.net/svn/asterisk2billing/ based on the Subversion project - http://subversion.tigris.org/
SVN documentation is available at: -
- http://svnbook.red-bean.com/
- http://svnbook.red-bean.com/en/1.1/ch01s07.html
- http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html
Getting the latest code
In order to get the latest code, youu will need to check it out of the SVN
The command to do this is: -
svn co --username guest --password guest http://svn.a2billing.net/svn/asterisk2billing/
Anyone can check code out of the SVN, but special privileges are required to check code back in.
The code will be downloaded into a directory called asterisk2billing as a sub-directory of the directory in which you executed the above command.
Within the asterisk2billing directory, there are five directories that are of interest :
- tags : release tarballs are built from this archive of previous releases
- branches/1.3 : This is current stable release, which is now in 'feature-freeze', so it receives only bugfixes. This is where you would generally install the A2Billing application from.
- trunk : This is where development towards v1.4 goes. Help with testing is appreciated.
- external-addons : Contains the original high-quality .WAVs from which the included .GSM prompts were transcoded.
- experimental_v2 : Parts of the A2B codebase were starting to show their age and creak a little. This is a playground for experimentation with a long-term goal of a group-up rewrite labelled v2.00. Unless you're a developer, you'd be well advised to steer clear of this folder.
Reporting Bugs
Once you have downloaded the new code and you have discovered a bug, this needs to be submitted to the Bugs section of the Forum (http://forum.asterisk2billing.org/) for discussion. This will trigger an email to the A2Billing developers, who will raise a ticket on the trac.
The following information is useful and necessary for each bug report:-
- SVN Revision number - this is reported on download.
- Platform (O/S) Provide the Distribution version e.g. Linux Redhat 9.0
- Can you reliably reproduce the bug. If not, the more information you can supply the better in repeating the bug.
- Debugging Output - Please include files as attachments, rather than snippets, as the Forum software can do strange things to the formatting. The more information, the better.
- Finally search the bug tracker to ensure that the bug has not been reported before.
Adding New Features
If you have coding skills, and feel you can add new features to A2Billing, then we would be pleased to hear from you.
Please read the coding guidlines and make sure you are familiar with these, and also add comments that explain your code.
Coding Guidlines
The A2Billing Coding Guidelines attempts to explain the use, basic styles and formatting of code used :
We would ask that you submit code for inclusion initially to the developers via the forum, and at the discretion of the A2Billing Team, give you access to commit changes to the SVN.
Translation
A2Billing is aiming to be a multi-lingual product, therefore if you can translate sections of the website for us, it would be helpful. Please read the translation section below for more information.
Recording
As with translation, new recordings in different languages is also helpful, for more information, please access the wiki section below.
Documentation
We are improving the documentation all the time. If you feel you can contribute to the creation of the documentation, then send in your contributions, updates etc directly to us.
The areas that would be particularly useful to work on would be Installation, Upgrades and User Guidelines. Some work has already been done here - http://trac.asterisk2billing.org/cgi-bin/trac.cgi/wiki/Documentation
