voice wrote:
I have long contended that sipFoundry.org and openSipStack.org are
open source in NAME ONLY
Both *.org have a vested interest in maintaining control growth and
direction of both development endeavors/forums because they both have
a commercial product that competes with many of the goal and interest
of their collective list memberships interests.
In behalf of Solegy (Sponsor of OpenSBC), and as a co-founder of the
OpenSBC project, allow me to clarify that OpenSIPStack and OpenSBC are
both licensed under a pure MPL/GPL/LGPL tripple license. There is
currently no effective commercial license for OpenSBC nor are there
plans to have one in the near future. I am not saying this is a
permanent situation. We may or may not go "double breasted" (borrowing
Dale's words). We are developing OpenSBC to satisfy our own internal
needs and the needs of our customers. Having OpenSBC in open source
does not give us any direct commercial advantage nor does it give any to
our clients. However, our open source initiative allows us to get the
help of the community in terms of identifying needed features to further
enhance our applications. It is, therefore, to our best interest to
keep OpenSBC as part of Solegy's open source initiative. For all you
know, we might just have a good heart and sharing the code was an
irreducible primary.
All of the problems address by list members have been solved with each
respective sponsors commercial product.
There might be commercial functionalities in our internal application
that are not part of the open source release but I assure you that the
base of our internal application is exactly the same thing one can
download from the SourceForge CVS.
It is time for these open sources to be taken over by other
disinterested non-commercial third parties that could be interested in
creating their own commercial product. After all think, who are the
list membership members. Both of these *.org should immediately
publish their source code just like LINUX. Then they can created
their own commercial product HOOKs like RedHat etc....
openSBC publishes the source code, it's C++ and XML. It's nuts to
think of SIP or ipPBX without addressing SBC directly. Every
contribution to the list are incorporated into the respective
commercial products. I would love to be in a position to have the
strongest mind on earth working on my commercial product at no cost.
Wouldn't you?
sipX or some subgroup should immediately creating and incorporating
openSBC into sipXecs and add it two (2) sipX's Gateway menu right
under SIP TRUNK one called Peering Edge(sbc) the other called Access
Edge(sbc)
Are there any of you old Hackers out there still alive. openSBC
source code is available for download and it works. 100% RFC
compliant.. Both of these commercial sponsor can pull this open
source code and make it private any time. Think.... Long live the
Revolution.... Laughing as i write it.
We also use sipX/OpenSBC pairing in some of our deployments so I
understand your frustration why we simply can't glue these two
applications as a homogeneous whole. The truth is, well... we can.
However, a developers time is not free and if it is not to both projects
best commercial interest to support such endeavor, then it would have to
be suspended until a need arises that justifies the cost of
development. You are always free do it yourself. Fund the
development and hire developers to do it and give it back to the
community so everyone benefits. If you are lucky, you may even find
developers who will do it for free (just doing good to all men). But I
assure you this is a rare occasion.
Joegen
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
opensipstack-devel mailing list
opensipstack-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
