From: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: debian-legal-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org,
List Linux RDMA Mailing
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Open source files without copyright holder
Date: Mon, 26 Jun 2017 16:44:00 +0200 [thread overview]
Message-ID: <1498488240.3543.4.camel@profitbricks.com> (raw)
[ Note the cross-posting... ]
Hi debian-legal,
The COPYING.md file of rdma-core [1] says: "Refer to individual files
for information on the copyright holders." but some files (e.g.
ibacm/man/ibacm.1) do not specify a copyright holder. The copyright
holder grants the user additional rights by putting the code under a
open source license. Is it okay to benefit from these rights without
knowing the copyright holder? How could someone verify that the
copyright claim is correct?
If not, please ensure that every file has specified a copyright holder
(or having a default copyright holder).
[1] https://github.com/linux-rdma/rdma-core/blob/master/COPYING.md
--
Benjamin Drung
System Developer
Debian & Ubuntu Developer
ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin
Email: benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org
Web: https://www.profitbricks.com
Sitz der Gesellschaft: Berlin.
Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
Geschäftsführer: Achim Weiss.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2017-06-26 14:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1498488240.3543.4.camel@profitbricks.com \
--to=benjamin.drung-eikl63zcoxah+58jc4qpia@public.gmane.org \
--cc=debian-legal-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.