http://lists.sip-router.org/pipermail/sr-dev/2008-December/000202.html

Soon after:
- xlog module was ready too, with just an extra define in Makefile, marking the inclusion of pseudo-variable and transformation API in sip-router — one can do color printing via xlog. Note that all pseudo-variables and transformations will be moved in PV module as discussed some time ago on Kamailio devel mailing list.
- DB API of Kamailio and SER were included as library and other modules become compilable with sip-router

For reference:
http://lists.sip-router.org/pipermail/sr-dev/2008-November/000071.html
http://lists.sip-router.org/pipermail/sr-dev/2008-November/000077.html
http://lists.sip-router.org/pipermail/sr-dev/2008-November/000081.html
http://lists.sip-router.org/pipermail/sr-dev/2008-November/000082.html

Once MI and statistics APIs will become libraries as well, then many other Kamailio (OpenSER) modules shall work more or less out of the box (some statistics done in core and 1-2 mi commands will miss in the first phase). Then it comes the second big step, after module integration, config language update — after that point we are kind of 70% ready.

All these happened in just few days since source code repository (GIT) was up … it looks like we will get most of the features from Kamailio (OpenSER) and SIP Express Router (SER) together sooner than expected … let’s see …

http://sip-router.org/pub/photos/album-sip-router-karlsruhe/

Meeting minutes:

• development side: move forward, sip-router.org source repository should be up next week
• end of January we should have a runable core+tm with support for the most used features from both Kamailio (OpenSER) and SIP Express Router (SER) (100% support might be a little delayed as some features may become obsolete)
• Kamailo next-next release (probably after spring next year) will be based on sip-router core+tm
• next or next-next SER release will be based on sip-router (SER might make another 2.1 release from the current CVS, since the code is ready - to be discussed)
• future releases will most likely be common and will unify all or most of the modules (depending on everything up to that point working ok)
• copyright: patches that are not accompanied by (c) claims will not add to the (c). We should put this on a web page and when in doubt we can ask the patch author for confirmation. While it’s likely this has no or very limited legalvalue (especially in Europe), it will server at least as a gentleman agreement. We need this because:

1. we need the agreement of all (c) holders for the GPL code to add licensing exemptions (e.g. we need to add an openssl linking exemption) and it’s easy if we have a known “small” set of (c) holders
2. people might not like having multiple (c) notices on files they created, just because someone did send a trivial or not so significant patch (note: “trivial” and “significant” are very relative). On problems, probably the board will decide, if nobody gives up the claim we’ll fork the module (worst case, to be avoided as hard as possible).

• forking modules: highly discouraged, but allowed
• unmaintained and rarely used modules: removed after a grace period
• board: for now we continue to have 2 boards, SER and Kamailo at least until we have something runable. In the meantime we should think/discuss how the common board will look like: how it will be elected and for how long, “composition” (how many devels, how many from the user community, testers a.s.o)
• testing: very important, Jerome proposed having beta-tester groups and stressed out the importance of dynamic tested. Everybody seems to agree, but there are doubts about finding beta-testers volunteers.
• release management: we need a release manager for each release
• documentation: Kamailio uses a wiki for core, and docbook .xml for modules, SER use NEWS (txt file) for core and docbook for modules, but it’s in the process of migrating to a more man page friendly format (still .xml). More discussion is needed, between the main doc writers from both sided.

sip-router.org:

• GIT repository should be up next week
• sr-dev mailing list should be used for technical dicussions related to merging the cores
• new features mails should be cc’ed to sr-dev too (very important especially when core or tm is involved).
• todo: find easy to remember short name

Related projects:

• some modules may be on separate repositories for a while (e.g., openimscore), maintained by their devs for using them out of the box with sip-router
• stand-alone application servers (Voztelecom/WeSIP, Iptego/SASI) may merge the communication interface specs in the future.
• it is a need for a place where to collect basic info about related projects

Further steps:

• new meeting, to be organized somewhere end of winter/beginning of spring 2009 (topics: celebrate first integrated working version, discuss further development of sip-router)
• setup of adjacent tools that help developing code and documentation (e.g., wiki, tracker)

General opinions:

• there are x-ser platforms running milions of users, sip-router must provide a rock-solid SIP server, esure trust and project reliability
• while having a strong focus on above item, innovation shall not be stopped, new features to be added as module to avoid effects to core and main modules
• very important modules (e.g., usrloc, registrar, …) should be protected as much as possible, patches and new features to be carefully reviewed not to affect stability and interoperability
• improvements to most important parts to be discussed on sr-dev mailing list

http://sip-router.org/wiki

The wiki is open, anybody is welcome to contribute there. If you do not want to edit pages anonymously then you can create an account here.

• git://git.sip-router.org/sip-router (read only)
• http://git.sip-router.org/sip-router (read only, slower, git://… recomended)
• ssh://git.sip-router.org/sip-router (read write but account on git.sip-router.org needed)

Web interface:

• http://git.sip-router.org/cgi-bin/gitweb.cgi

Before commiting, please read:

• http://sip-router.org/wiki/git/quick-start-guide

For more info about GIT try:
http://git.or.cz/gitwiki/GitDocumentation

and if you want to know how it works:
http://eagain.net/articles/git-for-computer-scientists/
(highly recommended)

Special thanks go to Jan Janak, who not only did setup git.sip-router.org (including automatic cvs sync for some of the repos), but he’s also hosting it on one of his private machines.

More details here…

First, many thanks to 1&1 for hosting the event and everyone that participated in such short notice. There were representatives from 10 companies:

• 1&1
• FhG Fokus
• Telio
• Asipto
• iptelorg/Tekelec
• Voztelecom
• Iptego
• Itsyscom
• Longphone
• Basis AudioNet

Some pictures should be published in the near future.

After going in short introduction and presentation of the goals from the point of view of each project (SIP Express Router (SER) and Kamailio (OpenSER)), we focused on:

• identification of potential points of conflicts and how to get to a resolution in such case
• code integration for common layer of the first phase
• future development and proposals of new features
• management of the larger eco-system that includes related projects and business entities

There will be several posts detailing what was discussed and proposed there for SIP Router project in few days. meanwhile, the outlines:

• it is hard to avoid conflicts just by some clear and strict rules, so the common sense should lead the collaboration and discussions
• GIT repository should be up in several days so the work can start, with a time line of 2-3 months from now to get core and tm in a very good shape of integration
• another meeting shall be set in about 3 months time, to allow enough time for people to be able to attend, adjust the development and look more deep at the future. While a lot of focus in the next months will be on integration, development of new features won’t stop — for example, steps to a partial asynchronous processing are undertaking, couple of new modules are planned for release, several other modules to bring new functionalities
• we should encourage and promote the development of related applications, like web interfaces, management tools, applications servers — they add value for community and business

Developers of these two projects believe that an united and non-conflicting environment will bring many benefits, to them, community members and companies.

• bring together the developers and user communities of both projects
• reduce maintenance overhead
• avoid duplicated efforts in development
• develop a core framework that is flexible, extensible and scalable
• promote and build a solid open source SIP server project
• ensure business credibility
• make future forking undesirable, this harms everybody, affects credibility and business

You are welcome to join! Visit:

http://www.sip-router.org

Mailing list:

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev