LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Pen-Yuan Hsing <penyuanhsing@gmail.com>
To: Julian Daich <julian.daich@freecomputerlabs.org>,
	libreplanet-discuss@libreplanet.org
Subject: Re: For reviewing a new free license. People who have read and understand the GPL
Date: Sun, 6 Mar 2022 12:27:11 +0000	[thread overview]
Message-ID: <e8c46632-79f9-a785-6fda-ef120df98ac2@gmail.com> (raw)
In-Reply-To: <CAFhQbGgnukNaKxRPtJP8gojez=syaCCnuMTmsEjszhpu9vq_mw@mail.gmail.com>


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

Is there something you're trying to do with this LINDS license that the 
CERN OHL 2.0 does not?

On 3/6/22 10:40, Julian Daich wrote:
> Hi,
> 
> I am looking for volunteers to review a free license very close to the
> GPL v.3  but with some key differences
> 
> It is intended to be used for licensing physical things and other
> aspects of technology in general in addition to copyright as methods,
> formulations. etc
> 
> The license is copyleft and patent left. Patents are not necessary to
> be used with it, however the license works better combined with
> patents for works not purely covered by copyright.
> 
> Trademarks are handled very differently than the GPL.
> 
> The first work to be released under this license is a therapeutic
> device, however it was designed to be used to release any work that
> can derive in a copyright, patent claim or trademark. The last version
> of the license can be found here
> https://www.lindsinnersole.org/wp-content/uploads/2022/02/LINDS-General-Public-Agreement-V1.4.rtf
> We( me and other developers involved) are using the term Free Acces
> Technology to refer to works released under this license.
> 
> The purpose of the review is to have feedback and to identify possible
> problems, bugs and improvements. Everyone interested in the task can
> contact me in private. Having previously read and understood the GPL
> is very preferable for the task.
> 
> Best,
> Julian

_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

  reply	other threads:[~2022-03-06 14:53 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 [this message]
     [not found]   ` <c71c5644-87a7-9cf9-53b7-0eb0d800d6eb@freecomputerlabs.org>
2022-03-08 15:54     ` Pen-Yuan Hsing
2022-03-11 14:27       ` Julian Daich
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=e8c46632-79f9-a785-6fda-ef120df98ac2@gmail.com \
    --to=penyuanhsing@gmail.com \
    --cc=julian.daich@freecomputerlabs.org \
    --cc=libreplanet-discuss@libreplanet.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 read-only IMAP folder(s) and NNTP newsgroup(s).