unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Nate Rosenbloom <nate.rosenbloom@gmail.com>
To: Vivien Kraus <vivien@planete-kraus.eu>,
	Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: re-writing algorithms in Guile
Date: Tue, 29 Jun 2021 13:52:56 +0000	[thread overview]
Message-ID: <DM5PR04MB089091E1AD31007B33FF7247F6029@DM5PR04MB0890.namprd04.prod.outlook.com> (raw)
In-Reply-To: <33e84ca0925be2b0ee7d04e0e2c433bdee3e1911.camel@planete-kraus.eu>


> This reason is not stated in the Stack Exchange post, and I believe
> it’s inaccurate (although, I am not a lawyer either). I think the
> reason is that you are reading the original implementation to write
> your own, so you are some kind of a compiler, or translator (as for
> human spoken languages). As such, what you write is mostly the other
> person’s work, so you should not claim copyright about it.

Sorry, I should have been more specific, the rewritten algorithm would not be the same, but it would be a derivative work and still covered by copyright of the original work.

It’s possible that the current license allows derivative works to be licensed under a compatible license that would allow you do to what you need to do? I guess to for any suggestions we would need to know what the original use license is.

Nate


  reply	other threads:[~2021-06-29 13:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 21:38 re-writing algorithms in Guile Tim Meehan
2021-06-28 21:50 ` Zelphir Kaltstahl
2021-06-29  4:09   ` Nate Rosenbloom
2021-06-29  4:38     ` Vivien Kraus via General Guile related discussions
2021-06-29 13:52       ` Nate Rosenbloom [this message]
2021-06-29 14:20         ` tomas
2021-06-29 23:48           ` Tim Meehan
2021-06-30  7:29             ` tomas
2021-06-29  5:26 ` Jay Sulzberger
2021-06-29  6:08   ` Dr. Arne Babenhauserheide
2021-06-29  6:08 ` Dr. Arne Babenhauserheide
2021-06-29  7:56 ` tomas
2021-06-29  8:56   ` Vivien Kraus via General Guile related discussions

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM5PR04MB089091E1AD31007B33FF7247F6029@DM5PR04MB0890.namprd04.prod.outlook.com \
    --to=nate.rosenbloom@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=vivien@planete-kraus.eu \
    --cc=zelphirkaltstahl@posteo.de \
    /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).