Community mailing list archives

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

Andi Becker
- 11/26/2015 04:38:01
Step 1 when creating a module under AGPL GPL or LGPL it is advicesed to setup a git repository
and fill in the naked frame of your module (with no special code in ) but with the name of the module and YOUR copyright notice.

Than step by step fill it up.

Otherwise your trainees can simply take YOUR code and publish it as theirs.

And than you are in need to proove that it is actually yours.

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 Thu, Nov 26, 2015 at 4:23 PM, Dominique Chabord <> wrote:

I would say that if your work leaks before it is published, the risk is that YOU won't be allowed to use it as yours.
The sooner you publish, the better you are protected.
Ideally publish before the code is ready.

Post to: