SER Development Documentation

Get Started Following SERi Development

If you are interested in following the development of SER, there are several sources of information that you should be aware of. First of all, you should subscribe to (You can also search the mailing lists for previous discussions.)

The roadmap will show you an overview of planned features and improvements for future releases. Bugs and minor improvements, as well as work in progress can be found on the tracker roadmap.

If you have ideas for improvements or new features, the wishlist is the place to look (and add your stuff). You can post to to get feedback on your idea before updating the wishlist. Also, minor stuff can be registered directly in the tracker, and here is an overview of stuff that is on the wishlist.

Both roadmap and wishlist features may require more detailed specification before they are split into work tasks. Thus, there is a number of past and on-going discussions/specifications that you can look at and edit or add your comments to.

Developer's Resources

If you want to develop your own module or want to contribute to SER with patches etc, you should know that the code is held in a CVS repository at Berlios. The bug tracker we use is JIRA. The current trunk's module documentation can also be useful.

Read/Write Access To CVSi

If you have a CVS account then you will be using SSH to access the CVS repositoryi, do the following:
set CVS_RSH=ssh
export CVS_RSH

set CVSROOT=:ext:<username>
export CVSROOT
and replace <username> with your username.

To get stable code use cvs co -r rel_0_8_14 sip_router
To get unstable code use cvs co sip_router
and the entire source tree will be created in sip_router subdirectory.

Developer Documentation

Also, Doxygen documentation is generated every night using the CVS headi. To get the latest code, you need to use a CVS client.  See the downloads section for more information.

Also, you should read the programmer's guide. It is a bit outdated (made for version 0.8.x), but the basic structure of SER is relatively unchanged and you should read the guide before starting to create a module.  The dispatcher or textops modules are good, simple candidates as starting points for your own module.

Select format of the programmer's guide:

SER 2.0 (aka Ottendorf) has a changed database mode, see below for documentation of the new data model.

db-structure-0.10.pdf179.27 KB
Home |  Recent changes |  Search |  Glossary |  Sitemap |  Login