Well, technically Avaya is forking the code. There will now be an Avaya openscs codebase and a SIPFoundry sipx codebase.
Users will need to choose between reporting bugs, viewing wiki's or roadmaps to either follow and install the Avaya project or the SIPFoundry project. Or report to both and duplicate it. Contributing to one project does not necessarily flow into the other codebase. However if Avaya keeps the openscs code base under a compatible opensource license then you could see the SIPFoundry codebase incorporate those changes. This would be similar to the asterisk community. Digum and Trixbox both use asterisk and much of the code and information between the two apply...but not always. SIPFoundry is moving the community builds forward and expect more info on that soon. -M >>> "Paul Herron" <[email protected]> 07/15/10 8:53 AM >>> <o:shapedefaults v:ext="edit" spidmax="1026" /> <![endif]--> <o:shapelayout v:ext="edit"> <o:idmap v:ext="edit" data="1" /> </o:shapelayout><![endif]-->So, from a practical, sipx-users standpoint, it sounds like whatis really changing is the location of the issue tracker and roadmap. If wewant to post issues , enhancement requests (i.e. Jira) we need to use the newAvaya site, correct? Will voting for an issue continue?<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p></o:p> </[email protected]>
_______________________________________________ sipx-users mailing list [email protected] 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/
