From: Lars Kurth <lars.kurth@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>,
Mike Belopuhov <mike@esdenera.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Missing copyright in the Xen header files
Date: Thu, 10 Sep 2015 17:05:26 +0000 [thread overview]
Message-ID: <D217843D.20EA9%lars.kurth@citrix.com> (raw)
In-Reply-To: <55F1A13B.5070401@citrix.com>
On 10/09/2015 17:26, "Roger Pau Monné" <roger.pau@citrix.com> wrote:
>CCing Lars (the community manager).
>
>El 09/09/15 a les 14.11, Mike Belopuhov ha escrit:
>> Hi,
>>
>> We're in the process of porting Xen PVHVM drivers to OpenBSD
>> and have come across missing copyright lines on some of Xen
>> interface header files, for instance:
>>
>>
>>https://svnweb.freebsd.org/base/head/sys/xen/interface/hvm/hvm_op.h?revis
>>ion=251767&view=markup
>>
>>https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/incl
>>ude/xen/interface/hvm/hvm_op.h
>>
>> This is not common and we have some concerns whether it is
>> valid to release source code w/o stating who has granted those
>> rights that are stated in the license.
>>
>> Would it be possible to amend the license and add a Copyright
>> line mentioning Xen project or an individual contributor like
>> it's done it othe places in the Xen source code?
I don't think this should be an issue. The (c) holders are all the people
who contributed to a specific file and can be retrieved from the git
history for the file. Each contributor explicitly agrees to the DCO, which
means he/she retains the (c) to the file. But copying the file, does imply
the loss of the change-history, so it makes sense in such situations to
update the license statement.
The work just needs to be done by someone.
Best Regards
Lars
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-09-10 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 12:11 Missing copyright in the Xen header files Mike Belopuhov
2015-09-10 15:26 ` Roger Pau Monné
2015-09-10 17:05 ` Lars Kurth [this message]
2015-09-16 14:10 ` Mike Belopuhov
2015-09-16 14:36 ` Ian Campbell
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=D217843D.20EA9%lars.kurth@citrix.com \
--to=lars.kurth@citrix.com \
--cc=mike@esdenera.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.org \
/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;
as well as URLs for NNTP newsgroup(s).