Community mailing list archives
Re: publish your module if you want to protect against plagiarismby
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.
On Thu, Nov 26, 2015 at 4:23 PM, Dominique Chabord <firstname.lastname@example.org> wrote:
Ideally publish before the code is ready.
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.