>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.
I agree completely. Except for one thing. Avaya remains in control of the some pretty important resources that the community depends on. If Avaya needs to take a break to figuring out their plans (and I'm not faulting them for it - it needs to be done) the rest of the project should not be in limbo. Avaya is a contributor, not an owner of the community effort no matter how much code they contribute. The way it should happen is there should be a public SVN that the community controls and contributes to, and Avaya contributes back their stuff as well. I don't believe the current state is an attempt by Avaya to control the project, rather that it is just the way things have been done till now. So the community needs to come together to figure out how that is going to work. I think in the end it will work out better for all parties involved, it's just frustrating as it now stands. _______________________________________________ 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/
