public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Damian Williamson <willtech@live.com.au>
To: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev]  Possible change to the MIT license
Date: Wed, 14 Feb 2018 10:09:25 +0000	[thread overview]
Message-ID: <PS2P216MB01795F951980A6681D81582B9DF50@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 610 bytes --]

I do not know that Bitcoin's position is any weaker because of the terms that the software is licenced under.


Cory Fields said:

>Let other projects faff about with copyright litigation and trademark dilution concerns


I disagree completely with any licence change. As well as allowing for the use of a software, a licence is also a disclaimer for those responsible for the release. Changing a single word can have drastic implications should there ever be any action considered against any involved party or group. The current MIT licence is IMHO the right fit.


Regards,

Damian Williamson

[-- Attachment #2: Type: text/html, Size: 1605 bytes --]

             reply	other threads:[~2018-02-14 10:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 10:09 Damian Williamson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-02-13 17:25 [bitcoin-dev] Possible change to the MIT license Adam Ficsor
2018-02-13 17:46 ` Daniel Robinson
2018-02-13 12:25 JOSE FEMENIAS CAÑUELO
2018-02-13 14:25 ` Natanael
2018-02-13 15:24   ` Jameson Lopp
2018-02-13 15:37     ` Brian Lockhart
2018-02-13 15:45       ` Jameson Lopp
2018-02-13 17:04       ` Patrick Murck
2018-02-13 15:45     ` Aymeric Vitte
2018-02-13 15:47     ` Bedri Ozgur Guler
2018-02-13 17:28       ` Felix Wolfsteller
2018-02-13 19:08         ` Cory Fields
2018-02-13 19:08         ` CryptAxe
2018-02-13 15:22 ` Aymeric Vitte
2018-02-13 17:53 ` Luke Dashjr

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=PS2P216MB01795F951980A6681D81582B9DF50@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM \
    --to=willtech@live.com.au \
    --cc=bitcoin-dev@lists.linuxfoundation.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