From: Julian Daich <julian.daich@freecomputerlabs.org>
To: Pen-Yuan Hsing <penyuanhsing@gmail.com>,
libreplanet-discuss@libreplanet.org
Subject: Re: For reviewing a new free license. People who have read and understand the GPL
Date: Fri, 11 Mar 2022 16:27:04 +0200 [thread overview]
Message-ID: <0d6b4680-d22e-89ec-04f4-1a444660f480@freecomputerlabs.org> (raw)
In-Reply-To: <CAAePrtHq+Uuc4xFqxU05k5JotRupLMv7wKewcUhos4rFopNxoQ@mail.gmail.com>
El 8/3/22 a las 17:54, Pen-Yuan Hsing escribió:
> On 08/03/2022, Julian Daich <julian.daich@freecomputerlabs.org> wrote:
>> El 6/3/22 a las 14:27, Pen-Yuan Hsing escribió:
>>>
>>> Dear Julian,
>>>
>>> Have you looked at the CERN Open Hardware License 2.0?
>>>
>>> https://ohwr.org/project/cernohl/wikis/Documents/CERN-OHL-version-2
>>>> It has a strongly-reciprocal variant which is like the GPL but for
>>> physical objects:
>>>
>>> https://ohwr.org/cern_ohl_s_v2.txt
>>>
>>
>> Hi Pen-Yuan,
>>
>> I read both licenses. They have very limited enforceability.
>>
>>> Is there something you're trying to do with this LINDS license that the
>>> CERN OHL 2.0 does not?
>>>
>> Yes, better legal enforceability and the way in which trademarks are
>> handled.
>>
>> You are welcome to read and compare.
>>
>> Best,
>> Julian
>
> Dear Julian,
>
> What do you mean by "legal enforceability"? What makes a license more
> or less enforceable? It would be important to define this clearly. And
> can you explain why the CERN OHL 2.0 licenses are not enforceable
> enough?
>
Hi Pen-Yuan,
Legal enforceability is the capability of any licensor to bring to the
court to any licensee who will breach the license to correct the
licensee behavior or otherwise restrict access to the licensed work and/
or eventually pay for damages and legal costs.
> Can you explain in detail what your concerns about
> trademarks are regarding existing licenses such as, but not limited
> to, the CERN OHL 2.0 licenses?
There are many. I recall few. The holding of copyrights is no well
defined for contributors. The terms conditions do not request that the
documenting of changes will be done in a fashion that it produces a
copyright. It is not concise in how a patent claim from a contributor is
linked to a licensed work and does not differentiate properly between
patent claim owner, holder or person in control.
In the above I used the GPL definition of contributor and the WPO
definition of patent claim.
Best,
Julian
--
Julian Daich
julian.daich@freecomputerlabs.org
FCL
www.freecomputerlabs.org
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2022-03-11 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 10:40 For reviewing a new free license. People who have read and understand the GPL Julian Daich
2022-03-06 12:27 ` Pen-Yuan Hsing
[not found] ` <c71c5644-87a7-9cf9-53b7-0eb0d800d6eb@freecomputerlabs.org>
2022-03-08 15:54 ` Pen-Yuan Hsing
2022-03-11 14:27 ` Julian Daich [this message]
2022-03-11 14:26 ` Julian Daich
2022-03-06 15:34 ` Valentino Giudice
2022-03-07 15:33 ` Jean Louis
2022-03-11 14:27 ` Julian Daich
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
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0d6b4680-d22e-89ec-04f4-1a444660f480@freecomputerlabs.org \
--to=julian.daich@freecomputerlabs.org \
--cc=libreplanet-discuss@libreplanet.org \
--cc=penyuanhsing@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).