From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stefan@marxist.se, emacs-tangents@gnu.org, mullikine@gmail.com,
rms@gnu.org
Subject: Re: Help building Pen.el (GPT for emacs)
Date: Fri, 23 Jul 2021 14:32:00 +0300 [thread overview]
Message-ID: <YPqosCqAWlaRnRvZ@protected.localdomain> (raw)
In-Reply-To: <83r1fp1es9.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2021-07-23 13:55]:
> > Date: Fri, 23 Jul 2021 13:12:12 +0300
> > From: Jean Louis <bugs@gnu.support>
> > Cc: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefan@marxist.se>,
> > emacs-tangents@gnu.org, rms@gnu.org
> >
> > You are using artificial intelligence, but in fact pieces of codes are
> > in chunks copied from other sources without attribution and without
> > knowing if licenses are compatible.
>
> That's not what happens with these services: they don't _copy_ code
> from other software (that won't work, because the probability of the
> variables being called by other names is 100%, and thus such code, if
> pasted into your program, will not compile). What they do, they
> extract ideas and algorithms from those other places, and express them
> in terms of your variables and your data types. So licenses are not
> relevant here.
According to online reviews chunks of code is copied even verbatim and
people find from where. Even if modified, it still requires licensing
compliance.
If code compiles or not is irrelevant. If one runs it or not is also
irrelevant, code need not even run.
I do not believe that any of the AI-s so far "extract ideas". I never
heard of it. Which algorithms is there on this planet that may extract
idea?
I also do not believe that AI extract algorithms, though AI has its
own algorithms to generate the relevant possible code.
If newly generated code is modification from other code, what we know
now that it is, and is based on, that requires licensing
attributions.
That licenses are relevant one can see from online discussions related
to Github Copilot:
https://fossa.com/blog/analyzing-legal-implications-github-copilot/
https://medium.com/geekculture/githubs-ai-copilot-might-get-you-sued-if-you-use-it-c1cade1ea229
https://fosspost.org/github-copilot/
https://artificialintelligence-news.com/2021/07/06/experts-debate-github-latest-ai-tool-violates-copyright-law/
https://www.opensourceforu.com/2021/07/github-copilot-sparks-debates-around-open-source-licenses/
That is just a small excerpt from a very large debat online related to
licensing issues.
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2021-07-23 11:32 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACT87JohxuswvDcqGOiQR7BrHoqJFG252QD6XjEuAPU2HSuWOw@mail.gmail.com>
[not found] ` <CADwFkm=cN4W0Mgo_hYgwWgddoe=cXj5+WYJWnAHZmmd+rd7gKw@mail.gmail.com>
[not found] ` <E1m4YYb-0005Ds-GJ@fencepost.gnu.org>
[not found] ` <CACT87JqMZ+pbVDQ-5gZHMsGcfm04CoeKZn6sY5yy+1rnxCimOQ@mail.gmail.com>
[not found] ` <83im1948mj.fsf@gnu.org>
[not found] ` <CACT87JrCAi3Umdke6gL+_W_7k2j+21jsuT=1hq5kyOx19L2x+A@mail.gmail.com>
[not found] ` <CACT87Jo41S2FJKxfPs0qP=qkXvwvcc0xnf1X6oEkjuhmAJ6w3A@mail.gmail.com>
[not found] ` <YPO+bAMpqMhxDBxU@protected.localdomain>
[not found] ` <83lf642jeh.fsf@gnu.org>
[not found] ` <CACT87JriMaF1kFjEE_8=8FEQpAi6sxr3x3vZT3rafjY=4mQgZg@mail.gmail.com>
2021-07-19 17:00 ` Help building Pen.el (GPT for emacs) Jean Louis
2021-07-23 6:51 ` Shane Mulligan
2021-07-23 10:12 ` Jean Louis
2021-07-23 10:54 ` Eli Zaretskii
2021-07-23 11:32 ` Jean Louis [this message]
2021-07-23 11:51 ` Eli Zaretskii
2021-07-23 12:47 ` Jean Louis
2021-07-23 13:39 ` Shane Mulligan
2021-07-23 14:39 ` Jean Louis
2021-07-26 0:16 ` Richard Stallman
2021-07-26 0:28 ` Shane Mulligan
2021-07-30 3:20 ` Shane Mulligan
2021-07-30 6:55 ` Jean Louis
2021-07-23 19:33 ` Eli Zaretskii
2021-07-24 3:07 ` Jean Louis
2021-07-24 7:32 ` Eli Zaretskii
2021-07-24 7:54 ` Jean Louis
2021-07-24 8:50 ` Eli Zaretskii
2021-07-24 16:16 ` Jean Louis
2021-07-24 16:44 ` Eli Zaretskii
2021-07-24 18:01 ` Jean Louis
2021-07-25 1:09 ` Richard Stallman
2021-07-24 1:14 ` Richard Stallman
2021-07-24 2:10 ` Shane Mulligan
2021-07-24 2:34 ` Shane Mulligan
2021-07-24 3:14 ` Shane Mulligan
2021-07-24 6:49 ` Eli Zaretskii
2021-07-24 7:33 ` Jean Louis
2021-07-24 8:10 ` Eli Zaretskii
2021-07-24 8:21 ` Jean Louis
2021-07-24 8:35 ` Jean Louis
2021-07-24 8:59 ` Eli Zaretskii
2021-07-24 16:18 ` Jean Louis
2021-07-24 16:45 ` Eli Zaretskii
2021-07-24 17:57 ` Jean Louis
2021-07-24 18:15 ` Eli Zaretskii
2021-07-24 7:41 ` Philip Kaludercic
2021-07-24 7:59 ` Eli Zaretskii
2021-07-24 9:31 ` Philip Kaludercic
2021-07-24 11:19 ` Eli Zaretskii
2021-07-24 14:16 ` Philip Kaludercic
2021-07-24 14:37 ` Eli Zaretskii
2021-07-24 14:49 ` Philip Kaludercic
2021-07-24 15:13 ` Eli Zaretskii
2021-07-25 1:06 ` Richard Stallman
[not found] ` <YN8bZEJAkWyQwjrB@protected.localdomain>
[not found] ` <CACT87JpAcUfuRB01CcnfbL4yCTPyDoiG_WOzzxVvAW7rhj0=Mw@mail.gmail.com>
2021-07-23 15:37 ` Jean Louis
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YPqosCqAWlaRnRvZ@protected.localdomain \
--to=bugs@gnu.support \
--cc=eliz@gnu.org \
--cc=emacs-tangents@gnu.org \
--cc=mullikine@gmail.com \
--cc=rms@gnu.org \
--cc=stefan@marxist.se \
/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).