I think I detailed as much as can be detailed for now. Please see:
http://forum.sipfoundry.org/index.php?t=msg&th=13784&start=0&S=622c9c20470ef587cfa7003c839da7ef On Thu, Jul 15, 2010 at 8:52 AM, Paul Herron <p...@sagecraftsmen.com> wrote: > So, from a practical, sipx-users standpoint, it sounds like what is > really changing is the location of the issue tracker and roadmap. If we > want to post issues , enhancement requests (i.e. Jira) we need to use the > new Avaya site, correct? Will voting for an issue continue? > > > > > > *From:* Al Campbell [mailto:alb...@gmail.com] > *Sent:* Thursday, July 15, 2010 8:29 AM > *To:* Paul Scheepens > *Cc:* sipx-users@list.sipfoundry.org; sipx-...@list.sipfoundry.org > *Subject:* Re: [sipx-users] Future of sipXecs in SIPfoundry > > > > Paul, > > SIPfoundry isn't going anywhere and I expect Ezuce will become the primary > supporter along with anyone in the community. I am sure we will see some > communication on that today. > > The code was all contributed to SIPfoundry under LGPL so it can be used > without any issue. > > Al > > > > Hi Al, > > First, I started with 3.6 and have had a lot of fun as well. > Keep up the good work (development)! > > Could you be a little bit more clear about the future? > If I understand it correctly SipXecs is moving from sipfoundry to openscs. > That leaves sipfoundry with ??, or will they develop their own sipYecs? > Are they allowed to use/license the copyrighted part of the code? > Also Ezuce is contributing a lot to SipXecs at the moment, how does that > fit in the new situation? > > Any clarification is welcome (I think everybody knew something was coming, > I don't know > whether they suspected this and I think they were hoping for something > else) > > Regards, Paul > > > Al Campbell <alb...@gmail.com> <alb...@gmail.com> wrote on 15-07-2010 > 14:01:57: > > > Avaya is fully committed to supporting sipXecs as an open source > > project, and will continue to encourage contributions to this > > project from the community as well as continue with its own > > contributions. However, communications regarding the direction of > > sipXecs, feedback from the community on the roadmap and developer & > > user support will move to a new open source web portal hosted and > > supported by Avaya. This split from SIPfoundry has been something we > > have been contemplating for some time and it was not an easy > > decision. Bottom line is Avaya didn’t feel it could be a primary > > contributor in something and not control more of the messaging of > > the project. Avaya will strive to make this project more compelling > > for developers and users and will provide linkages to its commercial > > version SCS, so that there is an easy migration path from an > > unsupported open source version to a fully supported commercial > > version. This split will happen over the next week and is something > > being coordinated with SIPfoundry. The migration may yield small > > outages of tools however we will do our best to minimize this. Just > > so everyone knows sipFoundry has been working with us on this and > > although we may have different perspectives on a path forward for > > sipXecs we both want the technology to succeed. > > > > Going forward Avaya is starting a new project (openscs.org) which > > will allow any of you to participate. As the copyright owner of the > > sipXecs codebase, and with many users/companies running sipXecs for > > their telephony needs, we will keep the sipXec name and evolve the > > code base as part of openscs.org. The new project will focus on > > getting a broader developer community and lowering the barriers > > associated with developing sipXecs software. We are very excited > > about the new project and welcome participation. > > http://openscs.org > > > > Now that the company message has been delivered I wanted to say on a > > personal note it’s been an incredible few years watching this > > technology mature and become something quite different than the > > early 3.X versions I first used. Thank you all for the frustrations and > fun... > > > > Best wishes, > > > > Al Campbell > > Avaya Software Development_______________________________________________ > > sipx-users mailing list sipx-users@list.sipfoundry.org > > List Archive: http://list.sipfoundry.org/archive/sipx-users > > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > > sipXecs IP PBX -- http://www.sipfoundry.org/ > > > > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: tgrazi...@voice.myitdepartment.net Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpd...@voice.myitdepartment.net Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
