What is the licencing of the API?

[sydesy]

Hi,

Two related questions on the api/soap licensing:

- does a software using the soap interface need to be licensed gpl3 or can it be anything (MIT, agpl, cosed source ?)

- Is it possible to implement part or your interface on the top of another software so an existing software that integrates with sugar could integrate with another software (I'm thinking agpl v3).

Thanks in advance for the clarifications

Xavier

[eggsurplus]

- does a software using the soap interface need to be licensed gpl3 or can it be anything (MIT, agpl, cosed source ?)

No, it can be licensed under whatever you'd like.

- Is it possible to implement part or your interface on the top of another software so an existing software that integrates with sugar could integrate with another software (I'm thinking agpl v3).

Confusing but if I understand correctly you'd have to check with the license of the external 3rd party software that integrates with Sugar and see what license and restrictions they have.

[sydesy]

Hi,

Thanks for your answer.

To clarify my second question: what if I re-implement a sub-set of the api on the top of another software than sugarcrm, so my software behaves like sugarcrm, but instead of accessing sugar tables and so on, it will access my software, and store it the way I want.

Eg. I want to use the module that integrates sugarcrm with gmail. The gmail part is untouched but configured so it talks to my server, and it reaches my clone soap interface, asking for contacts, updating the contacts like if I was sugarcrm, and I store that in whatever format I want, eg on a LDAP server or with trained monkeys that types the soap answers directly.

If I take sugar, takes out everything but the soap code and release it as gpl3, that will simply be the dumbest fork ever, but I'm assuming I'm respecting the licence.

Was if I only use the specs and not the code ? Can I release it as agpl ?

Does it clarify ?

Xavier