> > >>I use this to keep track of all the code that gets committed: >>http://code.sipfoundry.org/changelog/sipXecs/branches/4.2 > >I'm doing the same thing. I subscribe to the RSS feed for that...
Let me make sure you understand that this does not mean that the project will fall apart or stop. Quite the contrary is true. Avaya has assured me repeatedly that they plan to come back into open source with main. When that happens and in what form is not information that has been made available by them just yet. In the mean time we will have to find a place to put new code that gets developed in the community and we need builds of that development branch for people to test. We are 6 years into the history of SIPfoundry and the sipXecs solution is quite mature now. Everything Nortel and Avaya have done and continue to do has been excellent and their team is not only very competent but has been a pleasure to work with. I have the highest admiration for the people and the direction and contributions that came in over the last 2.5 years since the cooperation with Nortel started, and we certainly would like to see them continue. It's been a lot of fun. What we are seeing are the remnants of the Nortel - Avaya acquisition. SIPfoundry was created to be open to all and therefore the organization and project should not depend on a single contributor. It's up to all interested parties to influence and set the direction and I am open to suggestions. --martin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
