- freeswitch-maintainers@lists.freeswitch.org

[Freeswitch-maintainers] That time of the week again
by Ken Rice 28 Mar '12

28 Mar '12

Hey guys weekly status call... I think we should look at any outstanding bugs you might have this week... I would like to open this up community wide, so lets get together normal time on 888 instead of 996 this week... If anyone is being to annoying we can gag them on the conf K

1 0

[Freeswitch-maintainers] Maintainers Call Today at 12:15 EST before the Weekly Conference Call
by Ken Rice 14 Mar '12

14 Mar '12

Hey guys, Lets start 15 minutes early today if you are available at that time, if not normal time is good... Want to take a few extra minutes with everyone... Main Topic 1.2 Freeze and getting ready for 1.2 RC1. sip:996@conference.freeswitch.org as normal Ken

1 0

[Freeswitch-maintainers] Feature Freeze Coming quickly
by Ken Rice 12 Mar '12

12 Mar '12

Hey Guys, We have some good timing here... Feature Freeze Starts Wed March 14th. This will coincide with the standard Wed Conference Call. We will freeze on Wed... From there we will start merging Bug/Security Fixes only. If you have something you want to get in, nows the time. Wed, I would like to start Maintainers Call at 11:15 EST (that¹s 15 minutes earlier then normal) to do some module reviews. This is a very opportune time for the freeze and testing period as it will not affect Tony¹s productivity as he will be traveling for a bit. So, FreeSWITCH 1.2 here we come. If you have any concerns in the mean time please let me know... Find me on IRC, Email, or IM krice(a)tollfreegateway.com on MSN/Jabber/Gtalk or ken4voip on AIM lets get this ball really moving. K

2 2

[Freeswitch-maintainers] Quick Reminder: FreeSWITCH Maintainers call today 11:30CST
by Ken Rice 15 Feb '12

15 Feb '12

Hey Guys Quick Reminder FS Mainters call today 11:30 CST on 996... We missed the last one so lets get one inhere real quick... I just have updates today... RPMs have rolled out...still need some updates and testing Need to recruit someone to help some no the debs Travis-CI as previously mentioned is probably a no go on the recommendation of the travis-ci developers they supplest we look at Jenkins (Don't we have someone already running Jenkins on this list?) Simplified Config Changes... I think I have something that works for everyone... follow up... FS_SPECS Cucumber based testing FrameWork K

3 3

[Freeswitch-maintainers] Well this is a little late now since google waited so long to bounce it back to me...
by Ken Rice 02 Feb '12

02 Feb '12

Hey Guys, Reminder Call today on 996... Items we have to hit 1. RPMs are rolling out... Expect Community Announcement 2. Travis-CI 3. Testing Framework in Ruby 4. Config changes the work for everyone (including windows) 5. Question/Answer... Short call today guys... And a Pre Announcement K Quick update in its place... Community announcement on RPMs today we¹re announcing general availability of the RPMs for Cent5 and 6 32 and 64 bit today. This is what I believe will be the final packaging structure. I do want to move to FHS for the final Release RPMs. That will also be announced today I am looking at Travis-CI for the a CI environment Why? It looks just as good as all the rest and via Bougyman aka TJ we have direct contact with the developers. This will give us the CI goodness that keeps the FS project independent of other projects/services for CI and allow us to roll nightly builds that are atleast tested to some extent. Testing Framework in Ruby is underway by Community Member Deryl. This framework is well underwant and supports testing the current default dialplan and will be extended with more test over time. See http://cukes.info/ for the framework he is using. Leads us into the future with general unit testing. On the config changes. I have figured out a super simple way to support the current dev environment while not breaking future config deployment. We have a pre-processor on the XML with including capability why not just use that... Installed configsets from the RPMs will be separate and linked into place so we don¹t break things... But what happens as a developer when I try to run freeswitch from inside the source tree? It breaks... Simple file... Freeswitch.xml in conf that points to the right configsets freeswitch.xml and boom we¹re set... This should fix windows and *nix issues for dev at the same time. I would still like to find someone intimate witht he windows installer for production/stable builds to help out with a proper installed for Windows where we can give endusers this same type of choice Sorry for the delayed email I sent the other stuff out about 10:30 my time this morning and google failed to notify me of the bounce antil 11:40 (10 minutes after we were supposed to be on the call... In this case we¹ll try another call at everyones convience... Any questions or comments place get with me Ken

2 4

[Freeswitch-maintainers] Remind... Call in 10 minutes
by Ken Rice 18 Jan '12

18 Jan '12

Hey Guys Just a reminder... Call today... Starts in about 10 minutes... I¹ll make it quick today... sip:996@conference.freeswitch.org K

1 0

[Freeswitch-maintainers] That time of the week again
by Ken Rice 17 Jan '12

17 Jan '12

Hey Guys Just a reminder This wed 30 minutes before the standard weekly call. (that¹s 12:30EST, 9:30 PST) on sip:996@conference.freeswitch.com Before we get there tho I am looking for a little feedback I have started out as I have mentioned to a couple of you will making some prelim changes to source tree and top level makefile to support various config sets (or styles) You can see this on my github repo at https://github.com/swk/fs_test/ see https://github.com/swk/fs_test/tree/master/conf to see the proposed layout... Also in the src/mod/${mod_group}/${module}/conf directory I have started moving configs. Currently there is just a conf directory, but I think whatI have there now needs to be changes to something more akin to how we have the current Generic configs. ie: src/mod/${mod_group}/${mod}/conf/autoload_configs/${mod}.xml.conf This way we can build a crazy config... Configs in these dirs should be the source from which we build a test or clean defaults only config set. Any suggestions complaints on this welcome. The other thing I have been working on is the base ³core² package and standard supported vs un-supported (in dev tree) modules. I¹ll be posting a list of these things to this list tomorrow. In the meantime does any one have any specific module that might be used off to the side but they still like to see kept around? As far as license Issues I think at this time we are clear on those things. If anyone has any questions or comments on those things let me know. Thanks for the input so far guys. Ken

1 0

[Freeswitch-maintainers] Follow up from the Maintainers Conference Call
by Ken Rice 06 Jan '12

06 Jan '12

First off let me thank all of you for taking the time today. We discussed various Items which I hope I don¹t leave any out here, in the future we will record these calls. We talked about the need for a testing frame work and documentation of all the modules along with sample configs and usages for each of them. Meaning updated Wiki Page, Simple configs and dialplan or script demonstrating the use of the functionality. The later leading to unit/regression testing at some point in the future. Continuous Build Environment. This is something that comes up quite often even on the weekly call. Darren has stated that he has some of these things built and will be getting me access to this. Configuration changes to FreeSWITCH to support easier/better packaging. We need to come up with a good way to split the configs out so that installing a module then installs its relevant config files. One option we might want to look at here is changing default module load policy slightly with a config option, if modules are built and installed into the proper module directory they load. Packaging Requirements. Going forward we want to provide proper packages for a number of platforms to make installation easier and consistent. Several of you have existing packaging you are using, lets get these together somewhere and start reviewing these for daily and RC builts. These should also be documented. And will be dependant on any config packaging changes we may want to make. On the Licensing issues, Kristian Kielhofner has offered up some legal support from his Licensing/IP Lawyers. Lets get a List of Action Items we need to do due diligence against and I'll get started on those so that we can get this ball rolling. As part of this, I will be reviewing all modules and libraries currently in tree to see if there needs further attention. In relation to the licensing issues, Brian West, Travis Cross and a few others are already in touch with Phil Zimmerman re: ZRTP code licensing to address a possible conflict. We'll get more on this as that process moves forward. Our Next Call will be on Wed the 18th at 12:30PM EST, 9:30AM PST. This will be 30 minutes before the normal weekly FreeSwitch conf call. And as discussed we will do these calls on a bi-weekly basis for time being. We will continue to use the 996 bridge for this call. So gentlemen, let the car herding begin. If I have missed anything I apologize. Please feel free to chime in on this thread. Ken

1 0

Re: [Freeswitch-maintainers] Ok will it work this time?
by Kristian Kielhofner 05 Jan '12

05 Jan '12

Ok will it work this time? Got it -- Kristian Kielhofner Sent from a mobile device. ------------------------------ *From*: freeswitch-maintainers-bounces(a)lists.freeswitch.org < freeswitch-maintainers-bounces(a)lists.freeswitch.org> *To*: freeswitch-maintainers(a)lists.freeswitch.org < freeswitch-maintainers(a)lists.freeswitch.org> *Sent*: Thu Jan 05 18:02:56 2012 *Subject*: [Freeswitch-maintainers] Ok will it work this time? The things I do to send a simple email lol Ken

4 3

[Freeswitch-maintainers] Ok will it work this time?
by Ken Rice 05 Jan '12

05 Jan '12

The things I do to send a simple email lol Ken

1 0