Derived or not derived?

[amisiak]

Hi

I plan to start a project to build some ERP functionality based on SugarCRM. I would like to licence new modules like:
- orders
- warehouse management
- production processes
- invoicing
to be proprietary license. My company will create completely new modules but we would like to link them somehow with existing ones. Will the following modifications make new modules a derived work?

1. List of invoices on Account detalis

2. A button "show invoices" on Account details

Is there any way put any UI on existing modules and don't make new modules a derived work?

Thank you in advances for any comments or suggestions

Andrzej Misiak

[andydreisch]

From the Downloads page on SugarOpenSource.org:

"...you are free to download, modify and redistribute Sugar Open Source".

Access to the entire Sugar Public License can be referenced there.

Andy

[amisiak]

Hello Andy

Thank you very much for a quick response.

I didn't stated it clear(my fault) but we want to publish new modules as a multi-license code. With the core functionality as OS and premium version as proprietary license.

I have read the license and faq several times and searched the forum for several hours but I have found the statement like this:
You create derived work when you modify any file other then configuration files

That's why I asked how far can I go still do not create derived work.
1. Is there any list of configuration files? Or is it just config.php
2. Can I add new controls on existing modules using API without changing source code (I will find out if that is technically possible, maybe you know?) It shouldn't be considered derived work. how do you think?
3. Is there any way to add new controls to the existing source code then add new modules and keep these new modules non open Source?

Thank you in advance

Andrzej Misiak

[kpit]

Hello Andrzej,

The derived means that if you indend to take the existing code make your changes and and distribute it as your own package of crm. If you wish to do something like this you will need to join the Powered By SugarCRM Program(OEM). That program will allow you to commercially bundle SugarCRM with your modifications and extensions. More information can be found in the Partners page here.

If you are intending to sell installable module into SugarCRM that do not duplicate function of existing modules. Altering modules that are existing in SugarCRM is permissable with commercial licenses. Just be aware of upgradabilty problems. (see below on upgrade safe)

I am writing a module that adds functionality to the Leads in that it will assign them when captured by a portal user. This is a whole and seprate module and will be licensed commercially. The commercial application can apply patches to other modules including but not limited to SugarCRM's modules without violating the Licensing of OS. As long as your module is your creation completely.

One note you should not apply patches to core SugarCRM files as this will make your module non upgrade safe. This will make your module a maitenance nightmare for every SugarCRM upgrade and patch. Instead of adding a button you could add a subpanel for orders, invoices that can be associated to Accounts/Contacts. You can save yourself a ton of work by leveraging existing code and structures in SugarCRM. Look into some free recorded Webinars on Developing for SugarCRM in SugarForge Community Developer/User Group here. If you need to extend the logic functionality you will want to look into Logic hooks an upgrade safe way to manipulate data at specific points such as before save, after retrieve and other hooks. Using logic hooks makes upgrade safe extensions to existing module beans.

One other note. Sugar Professional and Enterprise contain a Quotes and Products Module all ready.