elected technical board
iptel.org has now an
. The election was held on the serusers, serdev, and semsdev mailing lists. The term is from now until May 31, 2009. The board will govern on issues where consensus cannot be reached or where consensus is unsuitable.
Technical Board 2007-2009
The members of the technical board for the term starting June 15, 2007 and ending May 31, 2009 are: Jan Janak, Andrei Pelinescu-Onciul, Greger Viken Teigre, Stefan Sayer, and Martin Hoffmann.
These were the nominations for the mid-2007 technical board election (in the order of received nominations). Nominees who accepted the nomination are listed with "accepted".
The number of votes received is listed in paranthesis.
- Raphael Coeffic (SEMSi), accepted, (7 votes)
- Stefan Sayer (SEMS), accepted, (8 votes)
- Jan Janak, accepted, (13 votes)
- Andrei Pelinescu-Onciul, accepted, (13 votes)
- These election rules were established by consensus on the following mailing lists: firstname.lastname@example.org,email@example.com,firstname.lastname@example.org,email@example.com.
- The basic principles were discussed on the developers' meeting in Prague, April 12.
- The principles were put forward on the lists, discussed, and modified with a summary posted to the lists for approval on April 28 by Greger V. Teigre.
- This page documents the agreed rules and was edited by Greger V. Teigre on May 17, adding firstname.lastname@example.org as a voting list.
- Any modifications to these rules agreed by the community should be documented here with a history.
- May 18, 2007, GVT, updated #6, made explicit nomination/voting procedure by adding "(by posting to at least one of the lists)."
- May 29, 2007, GVT, reversed May 18 addition, and added items 9 to 13 suggested in GVT post on May 25 to make explicit nomination and voting procedures, including an option for secret voting (no comments were received on the suggesting, thus accepted by the community)
One big problem with SERi has been the complexity of the SER configuration language. Only apache (httpd) can (almost) compare in the flexibility and number of ways a piece of software can be configured. This has resulted in a pretty steep learning curve for beginners. SIP can be used for an increasing number of applications and each deployment has its own, specific needs. Thus, SER's configuration language must be powerful.
The professional SER user has other issues, like maintaining multiple configurations across server farms and setups, sharing some code, but still needing individual tailoring to each server. '
SERi USER GROUP MINUTES AND PRESENTATIONS, March 19th 2007, Prague
These are tentative meeting notes. If you participated, feel free to edit and add things you think should be covered.
) Jiri Kuthan opened up with his view of SER status. The status update concentrated on the newly coined SLAMP ecosystem (SIP/SER/SEMSi
+LAMP) and the motivation for the recent major Ottendorf release. The SLAMP system has been defined as environment for rapid innovation of open communication services using LAMP (Linux+Apache+Mysql+Python/perl) enhanced by SIP-based real communication.
Update version of all logos (SER
) is available at http://www.iptel.org/artwork.
The new graphics includes http://iptel.org as the URL for the software (instead of the old http://sip-router.org) and also the text in the images looks better now.
SERi Ottendorf module documentation is now available at iptel.org. The auto-generated module documentation (nightly from latest SER Ottendorf documentation sources) is commentable. We encourage everybody to add comments and experiences to the module documentation!
SER Ottendorf module documenation is not complete yet. There may miss documentation of functions and parameters and some modules are yet to be made available online. We are working on this, but again, we encourage you to comment in order to complete and improve the documentation.
The new http://iptel.org/, home of SERi, SEMSi, and SERWebi is now up. If you have an account from ONsip.org, you can log in using your old ONsip.org username/password. However, all content is available without registration.
The new site is supported by the joint efforts of the iptel.org and ONsip.org teams. Our aim is to dramatically improve the project communication, documentation, and development process. The start is already up there, and we have many plans. The best thing of all: The new http://iptel.org site is a great basis for contributions from anyone.
We are working on migrating and organizing the remaining content from the old site, but meanwhile you can access everything from the old site from http://dog.iptel.org/