GPL v3: Can I add some features and sell SugarCRM?

[metapin]

If I take soon released SugarCRM 5.0, add some modifications, improvements and would like to resell it. Will it be possible?

What about v.4?

Please help

Thanks a lot in advance.

Kind regards,

Met

[ruchida]

Metapin,
Yes, you can sell it but you need to make the source code available to public.
Please see below for details;
http://www.sugarcrm.com/crm/gplv3-faq.html#partner10

[metapin]

Ryuhei,

thanks a lot for your reply. I read a lot of information.
But still have some questions.

If I developed new module/extension/add-on and sell it via SugarExchange at some price. Somebody can buy my module/extension/add-on and make it public? So near my module/extension/add-on at e.g. 200USD will be my module/extension/add-on but for free. Am I right?


Thanks a lot in advance

Regards,

Met

[longreach]

Yes Metapin - you are correct

[metapin]

:-) Guys, so what the sense is?

If I have great idea, I would like to invest money into this idea, how will I protect my investments?

Another point. I can buy Sugar Pro Onsite and make it available also?
Why do I need to pay every year again?


Thanks in advance.

Kind regards,

Met

[simple]

Only the Community Edition (previously know as Open Source Edition) will be under GPL3 (afaik).

[andydreisch]

Hi metapin, if your extension is purely API-based (uses Sugar web service calls) then it will not form a larger work under GPL and you'll be able to provide it on SugarExchange without being bound by GPLv3 requirements surrounding the release of source code.

If your extension is a module that extends Sugar 5.0 in any way then it constitutes a larger work and is bound by GPLv3 requirements if provided to Sugar Community Edition users.

If your extension is a module the extends Sugar but is targeted to Sugar Professional and Enterprise users then you are not bound by GPLv3 requirements since these editions are provided under our commercial license and not GPLv3.

We anticipate SugarExchange providers of modules will provide a two-level offering, one for Community Edition users (under GPLv3 or compatible license) and the other for Pro/Ent users.

I hope this clarifies issues. As always, please view this as guidance and not as legal direction.

Andy

[andydreisch]

Hi simple, yes, only Sugar Community Edition (formerly Sugar Open Source) will be offered under GPLv3 beginning with Release 5.0.

Sugar Professional and Sugar Enterprise editions will remain under the Sugar commercial license.

HTH,

Andy

[metapin]

I see.
So no protection for 3rd party developers.

I understood the main point.
I noticed that comparing to Salesforce 3rd party program SugarExchange 3rd party modules are a little bit amateur.

I know some companies that are trying to work with both programs and they are not very popular here comparing to Salesforce. Some of the modules for Salesforce are more extended than for SugarExhange.

If program can't protect 3rd party rights it won't unite very good and professional products. On SugarExchange I saw some good inventions just in premium list or popular - but they are few unfortunately.

I understood the principle.

What do you think?

Thanks

/Met

PS.Btw, as I understand SugarForge doesn't control the quality of source code, so I can obfuscate before uploading?

[andydreisch]

Hi metapin, we disagree with your conclusion about "... no protection for 3rd party developers" as we provided two instances where GPLv3 provisions regarding source distribution would not apply. Then, for Community Edition users, you could supply a subset of functionality and release code for that subset. If this approach sounds a little like what we do here at Sugar, you're right. And we're running a very significant business here.

What is it that you're intending to build for SugarExchange anyway? Give us your real-life example and we can walk it through. Perhaps your application will fill some gap for the Sugar user base.

Andy