From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Subject: Re: does this match an SPDX license?
Date: Mon, 10 Apr 2023 10:29:16 -0600 [thread overview]
Message-ID: <6ae47784-fd12-66e4-5d77-d3966e1b64cf@Shaw.ca> (raw)
In-Reply-To: <q2c83idc7lkl73rk35duq59t67plko612l@4ax.com>
On 2023-04-10 09:54, Andrew Schulman via Cygwin-apps wrote:
>> On 2023-04-10 07:17, Andrew Schulman via Cygwin-apps wrote:
>>> autossh comes with the license shown below. Is there an SPDX license identifier
>>> (https://spdx.org/licenses/) that I can associate with this? It looks most like
>>> public domain to me. Thanks, Andrew
>>>
>>> autossh is copyright (c) Carson Harding, 2005.
>>> All rights reserved.
>>>
>>> Redistribution and use in source and binary forms, with or without
>>> modification, are freely permitted.
>>>
>>> THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
>>> INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
>>> AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
>>> THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
>>> SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
>>> PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
>>> OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
>>> WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
>>> OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
>>> ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>>
>> Not that I have seen or can find: where did you find the text, so I can ask?
>
> The author of autossh, Carson Harding, emailed me the license text years ago,
> after I asked him what license he wanted to use. I could email him again to ask
> if there's a standard license he wants to use; just thought I'd check here
> first.
>
>> This is a totally permissive licence, without any conditions, just warranty and
>> liability disclaimers.
>>
>> You could use e.g. LicenseRef-motd-autossh-permissive-no-conditions for now.
>
> Thanks. I think that will do for now.
Thanks, I will use your explanatory post as the reference, and ask on GH
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
prev parent reply other threads:[~2023-04-10 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 13:17 Andrew Schulman
2023-04-10 15:18 ` Brian Inglis
2023-04-10 15:54 ` Andrew Schulman
2023-04-10 16:29 ` Brian Inglis [this message]
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=6ae47784-fd12-66e4-5d77-d3966e1b64cf@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin-apps@cygwin.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).