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: Sat, 24 Jul 2021 06:07:18 +0300 [thread overview]
Message-ID: <YPuD5nqe0lwB+a7j@protected.localdomain> (raw)
In-Reply-To: <83im1025b7.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2021-07-23 22:34]:
> > Here are references disputing how "it cannot be true":
>
> You take everything you read in these blogs for granted? Did you
> actually see the original code which these allude to?
In case of Copilot, Github admits:
https://docs.github.com/en/github/copilot/research-recitation
"This investigation demonstrates that GitHub Copilot can quote a body
of code verbatim, but that it rarely does so, and when it does, it
mostly quotes code that everybody quotes, and mostly at the beginning
of a file, as if to break the ice.This investigation demonstrates that
GitHub Copilot can quote a body of code verbatim, but that it rarely
does so, and when it does, it mostly quotes code that everybody
quotes, and mostly at the beginning of a file, as if to break the
ice."
And fact that it is "rare" does not make it a less problem for
copyright purposes as the new author cannot know which part of the
code has used "rare" verbatim.
> > Question is very particular, specific and concrete:
> > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> >
> > How does Pen.el and background AI services ensure of licensing
> > compliance?
> >
> > I would appreciate if you find solution to that or stay on that
> > subject, as if I am wrong or right is not relevant, what I wish is to
> > have assurance that it is free software. Prove me wrong by providing
> > exact references in not only on country's law but also other
> > countries' laws, the lows that make it legal, or how otherwise the
> > legality of such code is justified and how users may get free
> > software.
>
> I'm sorry, but I don't work for you. If you have problems with using
> code from these services, then the onus is on you to do the research
> and make up your own mind. The discussion here is not about the code
> these services give their users, it's whether and how Emacs can make
> use of those services. Emacs allows the user to write proprietary
> code, and there's no legal issues when the user does that. Emacs also
> allows the user to copy someone else's code without permission, and
> that's not a problem for Emacs when the user does that.
If you don't wish to correspond, don't, you are free.
I have never said nor implied "you work for me" and I cannot see how
is that relevant to the question. If you participate in discussion and
respond to my question relating to licensing compliance, then provide
a reference justifying its legality. Or simply say you don't have
such. Your employment is not subject of my question nor relevant.
I am not user of proprietary software and I don't consider options of
writing proprietary software. Neither I am participating in discussion
to foster ideas of creation of proprietary software.
I am free software user and for that specific case I am interested how
the licensing issue is solved.
However, my question is at least answered by my online research as I
have already found the refrences:
1. Julia Reda's reference; and
2. OpenAI_RFC-84-FR-58141.pdf
https://www.uspto.gov/sites/default/files/documents/OpenAI_RFC-84-FR-58141.pdf
Conclusions are:
- legal justifications exists for US jurisdiction as the companies
providing the AI are strong enough to find their ways, they are
playing on the card as given in references above; as somebody
already said, I doubt they would use "fair use" doctrine if the AI
would be trained on proprietary software such as Windows;
- conflict is serious and it is out there among the people and remains
unsolved; AI has been trained on GPL and other free software and is
used by corporations to generate new code without attributions;
people complain that it is misuse of intentions of authors;
- overall international legal situation is thus unclear, especially
considering that free software spans the whole world, not just the
US jurisdiction, as what may work within US is not same among all
jurisdictions;
> > As long as you don't tackle those subjects there is no legal solution
> > for Pen.el and background AI to be used with assurance that software
> > is truly free software.
>
> You confuse "free software" with "software being used to write free
> programs". They are not the same.
Maybe I have expressed myself in such way as not to get the point
understood. It must be so, as I have finally found the first legal
references myself.
For Pen.el I have never made any relevance to legality question I
made, and I have the pen.el repository over here and license is
clear. Never mentioned it.
I have not made reference to "software being used to write free
programs" as a server side service I did not tackle that, it is most
probably proprietary software or some versions could be free
software. But that is not relevant.
What is at hand is:
━━━━━━━━━━━━━━━━━━━
1. There is pool of GPL and other free software which authors expect
compliance to their licenses;
2. Large corporation is trying to use "fair use" doctrine on the pool
of software to create a service;
3. Service generates new software, sometimes duplicating verbatim
code;
Question was and still remains largely unsolved is how authors who use
newly generated code can be sure that generated software is free
software and to comply to GPL and other free software licenses?
Conclusion as of 2021-07-24 is that authors cannot be sure as there
are legal uncertainties.
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-24 3:07 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 4:36 Help building Pen.el (GPT for emacs) Shane Mulligan
2021-07-02 13:30 ` Jean Louis
2021-07-02 13:40 ` Jean Louis
2021-07-02 13:57 ` Jean Louis
2021-07-03 6:34 ` Shane Mulligan
2021-07-03 22:21 ` Jean Louis
2021-07-03 23:21 ` Arthur Miller
2021-07-03 23:42 ` Jean Louis
2021-07-12 3:24 ` Shane Mulligan
2021-07-17 23:53 ` Richard Stallman
2021-07-23 15:37 ` Jean Louis
2021-07-15 11:58 ` Stefan Kangas
2021-07-15 12:40 ` dick
2021-07-15 23:52 ` Shane Mulligan
2021-07-16 7:30 ` tomas
2021-07-17 0:33 ` Shane Mulligan
2021-07-17 7:54 ` tomas
2021-07-17 7:52 ` Jean Louis
2021-07-17 0:51 ` Richard Stallman
2021-07-17 2:36 ` Shane Mulligan
2021-07-17 9:01 ` Eli Zaretskii
2021-07-17 9:27 ` Shane Mulligan
2021-07-17 21:02 ` Shane Mulligan
2021-07-18 5:38 ` Jean Louis
2021-07-18 5:38 ` Jean Louis
2021-07-18 7:03 ` Eli Zaretskii
2021-07-18 8:00 ` Shane Mulligan
2021-07-19 17:00 ` 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
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 [this message]
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
2021-07-18 6:42 ` Eli Zaretskii
2021-07-17 21:35 ` Juri Linkov
2021-07-17 23:53 ` Richard Stallman
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=YPuD5nqe0lwB+a7j@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.