From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 2/2] doc: Add Maintainer Patch Review Checklist
Date: Fri, 19 Mar 2021 13:13:34 +0100 [thread overview]
Message-ID: <YFSVbmQ7T0kPnlXs@yuki.lan> (raw)
In-Reply-To: <YFSGZ9YKo/JUHMtm@pevik>
Hi!
> > Good point, we should state the default license for new tests and also
> > state that the licence for tests should not change unless they are
> > completely rewritten.
>
>
> Maybe:
>
> * license: the default license for new tests is GPL v2 or later, use
> GPL-2.0-or-later; the licence for test (e.g. GPL-2.0) should not change unless
> it's completely rewritten
> * old copyrights should be kept unless test is completely rewritten
>
> BTW this is important, specially for DMCA from Wipro. Cyril, can you point some
> test from Wipro which could be considered as "completely rewritten"?
This is tricky topic and I'm not a lawyer, so I guess that we better
consult one.
I would expect that if you remove all the previous test code and start
from a scratch the old copyrights would not apply, but again I'm not
lawyer and I do not have in depth understanding of the copyright laws
and treaties.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2021-03-19 12:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 18:16 [LTP] [PATCH v2 0/2] doc: Add Maintainer Patch Review Checklist Petr Vorel
2021-03-18 18:16 ` [LTP] [PATCH v2 1/2] doc: Document test tags Petr Vorel
2021-03-19 4:17 ` Li Wang
2021-03-19 9:01 ` Petr Vorel
2021-03-19 9:30 ` Cyril Hrubis
2021-03-18 18:16 ` [LTP] [PATCH v2 2/2] doc: Add Maintainer Patch Review Checklist Petr Vorel
2021-03-19 4:34 ` Li Wang
2021-03-19 4:56 ` Li Wang
2021-03-19 9:04 ` Petr Vorel
2021-03-19 9:23 ` Cyril Hrubis
2021-03-19 10:05 ` Petr Vorel
2021-03-19 9:25 ` xuyang2018.jy
2021-03-19 9:31 ` Cyril Hrubis
2021-03-19 11:09 ` Petr Vorel
2021-03-19 12:13 ` Cyril Hrubis [this message]
2021-03-19 12:43 ` Li Wang
2021-04-01 10:30 ` Petr Vorel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YFSVbmQ7T0kPnlXs@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox