Community mailing list archives

Re: publish your module if you want to protect against plagiarism

Andi Becker
- 11/26/2015 02:11:02
Houssine you are absolutly right. 

According to AGPL v3 a module source has to be published as soon as a service get provided with that module. This is usually the case when it goes public on a website. Of course you can keep the module in your drawer as long as you don't publish it.

Unfortunately many developers don't seem to respect the AGPL v.3 nor other GPL v.3 or LGPL v.3 and this is actually the main problem. If you want to develop in Odoo respect the GPL versions used. And the best protection for yourself is like Abraham wrote, to publish the code and mention your name, email and link to your ite n it and update it regularly when those info changes as otherwise you can't be connected if other developers would like to extend the module, like to ask for a specific feature or simply like to provide feedback to your work. 

Reselling, copying the code etc is all OK by the way according to GPL Licenses as long as the copyright stays as is.

The best protection would be to subscribe the copyright to thr FSF and they will take care for legal stuff to if people violate those rules. Especially if your code gets included into proprietary code!


With kind regards,
Mit freundlichen Grüßen,
Con un cordial saludo,
с сердечным приветом,


CEO/General Manager LisAndi Co., Ltd.


LisAndi Co. Ltd., Phuket, Thailand (
15/21 M.2 Viset Road, Rawai, Muang, Phuket, Thailand 83130

Mobile: +66 (0)81 606 3378
VoIP:   +49 (0)711 50 88788 50
Fax:     +49 (0)711 50 88788 50
Skype:          lisandi
Facebook:     andibecker
Google Talk/Facetime/eMail:


This email may contain confidential and/or privileged information. If you are not the intended recipient (or have received this email by mistake), please notify the sender immediately and destroy this email. Any unauthorized copying, disclosure or distribution of the material in this email is strictly prohibited. Email transmission security and error-free status cannot be guaranteed as information could be intercepted, corrupted, destroyed, delayed, incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which may arise as a result of email transmission

On Wed, Nov 25, 2015 at 8:17 PM, Houssine BAKKALI <> wrote:
Hi Abdrahman,

about the stolen modules... I don't think that stolen in your specific case is the right word to use as those module where written and published under AGPL... Plagiarism is the only thing that you can maybe use if they didn't respected the authorsihp rules. Which is enough to give a blame to those guys...

2015-11-25 13:07 GMT+01:00 abdrahman elkafil <>:
A few weeks ago we sent a complaint to

about plagiarism of our cmms module with one of ex developper
Fortunately we had released the code which  enabled to Odoo who has done a good job to find plagiarism and order the person to respect the AGPL license and add nextma as an initial contributor (the module removed after refusing to correct the module by this person)
this is not the first plagiarism that we unfortunately find some modules that we have not published the code that was stolen by former trainees can not initiate similar proceedings but we will soon publish to protect us.

morality: if you want to protect your modules publish it

abdrahman elkafil

founder and manager NEXTMA


integrator tinyerp/openerp/odoo since 2006

Post to:

Post to: