[Serusers] [Sems] SIP Express Bundle - let's get started

[Jiri Kuthan]

At 11:16 09/12/2007, Greger V. Teigre wrote:
>Hi guys, thanks a bunch for lots of input and I really appreciate the willingness to contribute.
>Thus, I have created a "project page":
>http://www.iptel.org/sip_express_bundle_sip_service_in_15_minutes
>
>I thought we could gather the current perspective on that page and document our decisions as we go. It will hopefully be useful in our process, as well as documentation for us and others later.
>
>I have noted the following volunteers:
>Jai: testing and installation work
>ram: testing
>SIP: tesing
>Jiri: anyting?

we most likely will contribute with all-in-one debian packaging built on top of oob.
not sure how that fits in the wide desire for CentOs though :-)

-jiri

>Mike: testing and documentation
>
>Maybe we should set up a small mailing list for coordination emails, but for now, let's use serusers (where I think all the comments came). (I copy the other lists on this post, so the other lists know that the discussion will move to serusers).
>
>Out of the comments, I read CentOS and vmware as the most wanted combination. I have documented the pros and cons on the project page, and suggest that we do some testing before we decide. I also tried out rpath (which I have no previous experience with). My observations are documented on the same page.
>
>Thus, I have started setting up a minimal CentOS virtual appliance found in vmware's appliance directory on an esx server. I will send details on accessing it to the volunteers once it is up and running (decompressing, unpacking, and building a non-split disk takes an awful lot of time :-( ).
>
>Ok, further comments, ideas, etc, please post to serusers or edit/add comments to the project page (requires an iptel.org account).  I see the following steps with documentation as we go (steps also found on the project page):
>1. Testing and specification of what we want to accomplish
>2. Environment and OS setup to ensure that we easily can release new versions
>3. Installation and configuration of the software. I assume this step also will involve development of some tools we need, as well as adaptation of existing stuff
>4. Testing and user documentation
>5. Packaging and deployment
>
>Let's get going!
>g-)
>
>
>
>_______________________________________________
>Sems mailing list
>Sems at lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/sems



--
Jiri Kuthan            http://iptel.org/~jiri/