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 10:54:07 +0300 [thread overview]
Message-ID: <YPvHH5nNVAFiRV6R@protected.localdomain> (raw)
In-Reply-To: <8335s4180s.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2021-07-24 10:33]:
> > I have never said nor implied "you work for me" and I cannot see how
> > is that relevant to the question.
>
> You consistently take the stance that implies, and many times
> explicitly states, that (a) you represent the views of the GNU
> project
I have never in my life said so, you please stop with it.
> and (b) the GNU project should or should not do this and that.
I have always beeing following GNU project as such because I agree to
its principles and guidances as published on GNU website. I will
definitely compare issues at hand with the already well known GNU
guidelines just as you and other people do.
For example when there is recommendation of proprietary software I
will say that GNU project does not endorse such.
> Then, when people like me object, you demand that they prove
> something to you, or else.
The issues are totally unrelated. I am sorry for your
misunderstandings.
I was interested to find out how is legality solved when re-using the
code generated by AI. Nothing else beyond that. And I have found
references and made conclusions.
> > 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 could ask you to do the same. You never provided any reference
> justifying the legality, just a lot of blogs that spread FUD (whose
> motivation, which many times is struggle against Free Software, I
> described in my previous message).
Take it easy.
I asked simple question, refined the question, and found references,
made conclusions of legality justification in US jurisdiction and that
there are unsolved global problem.
There is no need to expand discussion into directions which is purely
irrelevant to the question about licensing compliance.
> > 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;
>
> That's not what the above document concludes. Quote:
My conclusions are not what document conclude. I never said so. The
document is related exclusively to US jurisdiction and its final
determination is vague. It is their proposal, and not a court
decision. They have openly said that they are financially strong
enough and will try to defend any cases by using "fair use" doctrine
in the US.
This however, does not solve all jurisdictions. "fair use" doctrine is
also not finally solved in the US.
> Conclusion
>
> We submit that:
>
> I. Under current law, training AI systems constitutes fair use.
That is their opinion, as that is a corporation that has the strength
to submit such document and of course that they found some legal
defense. If anybody starts complaining it will be a court case that
will give final judgments.
> II. Policy considerations underlying fair use doctrine support the
> finding that training AI systems constitute fair use.
>
> III. Nevertheless, legal uncertainty on the copyright implications
> of training AI systems imposes substantial costs on AI developers
> and so should be authoritatively resolved.
Everything from that document relates to US jurisdiction only. It is
one-sided thus biased document, clearly opposing the views of many GPL
authors.
It is the corporations defense argument for ripping off the GPL
software. They found the way and wish to play on that card.
It is document of conflict, not document of friendship or
collaboration. It is document of one-sidede defense, not a document
that contributes to free software.
It is document that defend proprietary software, not document that
fosters free software.
Thus it does not resolve anything in the community. It serves to one
party only.
Would that corporation release all software as free software that
would bring or make a new leap forward. They are making one big step
backwards. One can see that by number of aware free software
developers canceling the Github accounts.
> > Conclusion as of 2021-07-24 is that authors cannot be sure as there
> > are legal uncertainties.
>
> Those are your personal conclusions.
Personal definitely, but not as the only one with the same opinion,
which should be clear from references which left probably unread.
Legality of free software on the planet was ensured by the GPL
license. Maybe the license was never planned to be international, but
it does function well internationally.
Legality of AI generated code and "free use" doctrine in the US is at
this point of development yet far from functioning well
internationally.
> (Full disclosure: part of my daytime job is development of
> sophisticated AI-based algorithms that use machine learning
> technologies for various practical purposes, including analysis of
> "natural language" text.)
That is great, it is technical part of software. Keep doing.
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 7:54 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
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 [this message]
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=YPvHH5nNVAFiRV6R@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).