unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: Tim Meehan <btmeehan@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: re-writing algorithms in Guile
Date: Tue, 29 Jun 2021 09:56:32 +0200	[thread overview]
Message-ID: <20210629075632.GC31129@tuxteam.de> (raw)
In-Reply-To: <CACgrOxK1FNRArALUv_ZUryCk7rJwo6doSJA+Wu0aCh8EhRaauw@mail.gmail.com>

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

On Mon, Jun 28, 2021 at 04:38:50PM -0500, Tim Meehan wrote:
> Say for instance, I have found an algorithm for scalar function
> minimization on a website, written in C. It is posted with a license for
> use. If I write something based on this hypothetical code, is it then
> clearly also licensed in the same manner?

Definitely not: a license is about copyright, and copyright protects the
expression of an idea, not the idea itself (the Lord of the Rings is under
copyright, but if you write a novel involving very old talking trees, you
dont infringe on that).

For ideas there are patents. The situation on software patents is complicated,
to say the least.

You might want to not use exactly the same variable names, just to make sure :)

For an example where the line lies, more or less, in U.S. jurisdiction, see
the Oracle vs. Google case on the Java API (the question was whether the
"header files", which define the interface, are under copyright or not.

Note that this actually involves copying some files verbatim, so your example
lies far on the "safe side" of it.

NOTE: I'm not a lawyer, nor I play one on TV.

Cheers

[1] https://www.aei.org/technology-and-innovation/supreme-court-ingests-java-as-google-oracle-copyright-spat-boils-over/
[2] https://siliconangle.com/2021/04/05/supreme-court-rules-googles-favor-oracle-copyright-case-android-java-code-use/
[3] https://www.supremecourt.gov/opinions/20pdf/18-956_d18f.pdf
 - t

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2021-06-29  7:56 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
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 [this message]
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=20210629075632.GC31129@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=btmeehan@gmail.com \
    --cc=guile-user@gnu.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).