3:24 p.m.
Hola a todos,
Michiel’s response re: license/copyright info in each file.
Thanks! Heather
---------- Forwarded message ----------
From: Michiel Leenaars <michiel at nlnet.nl>
Date: May 8, 2019, 8:15 AM -0700
To: Heather Flanagan <hlflanagan at sphericalcowgroup.com>
Subject: Re: IdentityPython Board approval to move ahead with Commons Conservancy
Hi Heather,
Why does CC think having a single license file
per project is
insufficient? Our thought is that if we can avoid adding a header to
every single file, that would be nice, esp. given we already have this
info in the license file and we have the Note Well.
this is not just our opinion, but something that is an industry and
community standard for legal compliance these days. When companies like
Siemens, Samsung or Honeywell use some code in one of the hundreds or
thousands of devices and systems in their product line, they need to be
able to provide the correct license and a download of the exact version.
This means machine readability too.
To quote from https://reuse.software/practices/2.0/ :
Scroll to the section "2. Include a copyright notice and license in each
file"...
"Source code files are often reused across multiple projects, taken from
their origin and repurposed, or otherwise end up in repositories where
they are separate from its origin. You should therefore ensure that all
files in your project have a comment header that convey that file’s
copyright and license information: Who are the copyright holders and
under which license(s) do they release the file?
It is highly recommended that you keep the format of these headers
consistent across your files. It is important, however, that you do not
remove any information from headers in files of which you are not the
sole author.
You must convey the license information of your source code file in a
standardised way, so that computers can interpret it. You can do this
with an SPDX-License-Identifier tag followed by an SPDX expression
defined by the SPDX specifications."
(the text goes on for a while after this, to clarify the point but this
is the basic gist of it)
There is a nice Python tool to check:
https://github.com/fsfe/reuse-tool
I hope this makes sense
--
Support NLnet, the open internet and open source with just 5 minutes of
your time. Make a difference today. Visit:
https://nlnet.nl/help (English)
https://nlnet.nl/ayuda (Espanol)
--
Michiel Leenaars
Director of Strategy
NLnet Foundation
Science Park 400 (Matrix 2)
1098 XH Amsterdam
The Netherlands
https://nlnet.nl
sip/xmpp: michiel [@t] nlnet.nl
---------------
'If you want the Internet to grow strong, safe and free,
but you don't know how to help, contribute to NLNet:
they do know and care."
Giorgio Maone, NoScript
Interested what Richard Stallman, Karsten Nohl, Andy Tanenbaum and
many others have to say about what NLnet helped them do for you?
Feel your wallet tingling already? Check out:
https://nlnet.nl/donating/quotes.html
7:56 a.m.
Hi all,
On Wed, 8 May 2019 at 17:24, Heather Flanagan
<hlflanagan at sphericalcowgroup.com> wrote:
Hola a todos,
Michiel’s response re: license/copyright info in each file.
Thanks! Heather
---------- Forwarded message ----------
From: Michiel Leenaars <michiel at nlnet.nl>
Date: May 8, 2019, 8:15 AM -0700
To: Heather Flanagan <hlflanagan at sphericalcowgroup.com>
Subject: Re: IdentityPython Board approval to move ahead with Commons Conservancy
Hi Heather,
Why does CC think having a single license file per project is
insufficient? Our thought is that if we can avoid adding a header to
every single file, that would be nice, esp. given we already have this
info in the license file and we have the Note Well.
this is not just our opinion, but something that is an industry and
community standard for legal compliance these days. When companies like
Siemens, Samsung or Honeywell use some code in one of the hundreds or
thousands of devices and systems in their product line, they need to be
able to provide the correct license and a download of the exact version.
This means machine readability too.
I've actually observed the opposite of that. Communities abandon the
"license in every file" model, and just use a single LICENSE file in
the root of the project. The LICENSE file contains license
information, that is, it is not a single license but it has exception
sections and so on.
To quote from https://reuse.software/practices/2.0/ :
Scroll to the section "2. Include a copyright notice and license in each
file"...
"Source code files are often reused across multiple projects, taken from
their origin and repurposed, or otherwise end up in repositories where
they are separate from its origin. You should therefore ensure that all
files in your project have a comment header that convey that file’s
copyright and license information: Who are the copyright holders and
under which license(s) do they release the file?
Continuing from above, the standardization of package-management
formats and tools has helped exactly with that: to avoid distribution
of single files, and instead provide packages and modules. It is bad
practice and considered a hack to copy files. Nobody liked that model
and everyone is moving away; it is unstructured, it becomes
unmanageable and it will cause problems.
It is highly recommended that you keep the format of
these headers
consistent across your files. It is important, however, that you do not
remove any information from headers in files of which you are not the
sole author.
You must convey the license information of your source code file in a
standardised way, so that computers can interpret it. You can do this
with an SPDX-License-Identifier tag followed by an SPDX expression
defined by the SPDX specifications."
(the text goes on for a while after this, to clarify the point but this
is the basic gist of it)
There is a nice Python tool to check:
https://github.com/fsfe/reuse-tool
I hope this makes sense
Well, it does not make complete sense. We're talking about licensing a
project. A project is not just code; there are data files (html, xml,
yaml, json files), binary files (archives/zip, images, audio, video,
etc), text files (configs, ini-files, etc) all "not-code". How do you
mark those files? Does the LICENSE file need a license-header? The
json format does not define comments, how do you add a header there?
If a binary file does not get a license header, why should a file with
code get one?
I would expect there to be a way to have the needed information
unified. If the files themselves cannot provide this information it
has to be external; thus the LICENSE file. If someone is worried about
somebody else re-using single files that do not have license
information (a python file, a png image, etc) there is really nothing
you can do (the DRM industry has been trying to solve for a long time;
and still your best bet is "social DRM").
Since, we're developing on open source with a permissive license, even
if someone does that, should we be happy that someone is actually
using what we built or sad that the files they copied did not have a
license header? And if they include the license information of that
copied file in their project's LICENSE file, is this solved?
Having pointed these contradictions, I am thinking that the "license
in every file" model seems to be a step backwards. It is introducing
overhead and does not really solve the problem, while at the same time
it enables a culture of bad practice (copying files around).
--
Ivan c00kiemon5ter Kanakarakis >:3
1829
days inactive
1837
days old
1 comments
2 participants
participants (2)
-
hlflanagan＠sphericalcowgroup.com -
ivan.kanak＠gmail.com