Good Day,
I am working with a new startup that will be launching a premise based
VOIP/messaging/SMB solution.
We like what SipX does and are considering using in our solution.
But I have a question about etiquette and the LGPL license. If this is not dev
list material but someone wants to chime in offline please let me know.
What we will be offering will really be a bundling of several open source
solutions to provide a compete corporate messaging solution on a custom
hardware appliance. Our solution is really about proving 24x7 support on a
supported hardware appliance.
We certainly want to give credit where credit is due, but we also want to
modify each product to give them the same look and feel. This involves mostly
cosmetic changes to web gui's etc but also "re-branding" the software under a
common name and labeling each component as distinct modules.
How would the SipX community feel about this? Our changes would be GUI changes
and adding some integration to make a coherent interface etc so we would be
using a near identical codebase to SipX for the voip piece. We certainly do
not want the community to feel that we are trying to ripe them off, considering
we are highly dependent on the community.
Our marketing would certainly discuss opensource foundations and mention
"Powered by XXX" tag lines. We also plan to have a "License" section under our
unified GUI that list all the appropriate copyright details.
Thoughts and remarks?
Thank you,
Tim
_________________________________________________________________
Hotmail: Free, trusted and rich email service.
http://clk.atdmt.com/GBL/go/171222984/direct/01/_______________________________________________
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/
