> I just want to preface it by saying that I am not an expert on licensing,
> and you probably should talk to someone who is.
>
> What follows is my take on sipXconfig changes.
>
> I would think that if your UI modifications are contained in a separate
> skinning module (and this is what sipXconfig provides for) you are under no
> obligation to share any of that code. It would be nice if you let us to put
> your skin in the gallery on the wiki but you don't even need to do that.
>
> If you need to modify any of the sipXconfig code to achieve what you need,
> you are under LGPL obligation to publish your changes. You don't have to
> actually contribute you code to sipfoundry, you just need to make it
> available for others to look at.
>
> That said I'd like to think that you *will* attempt to contribute any
> changes to sipfoundry since it might make sipXconfig better and it'll
> probably make you code modifications easier to maintain.
>
> Good luck with your start-up,
> Damian
>
Damian,
We certainly plan to make our changes/skin available for the community.
We want to work well with the communities we use in our product, and do not
want to create the sediment that we are stealing peoples hard work by
re-branding their work and taking the credit.
We are hoping that by rebranding several seperate packages and adding
connections between them, users will be more ept to select an opensource
solution that "feels" complete.
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/
