unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Shane Mulligan <mullikine@gmail.com>
Cc: stefan@marxist.se, emacs-devel@gnu.org
Subject: Re: Help building Pen.el (GPT for emacs)
Date: Sat, 17 Jul 2021 19:53:22 -0400	[thread overview]
Message-ID: <E1m4u7W-0003wM-Au@fencepost.gnu.org> (raw)
In-Reply-To: <CACT87JqMZ+pbVDQ-5gZHMsGcfm04CoeKZn6sY5yy+1rnxCimOQ@mail.gmail.com> (message from Shane Mulligan on Sat, 17 Jul 2021 14:36:15 +1200)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > I think the end-goal should be to have a close collaboration with
  > EleutherAI, who already have an open-source alternative to the Copilot
  > model. It's called GPT-j.

Perhaps that is a good path, but we need to know more.

You've described this as an "open-source alternative".  Most of the
time, when developers describe their work as "open-source", it is
because they don't share our ethical principles and criteria.  For
instance, most open-source programs are free/libre, but there are
exceptions.

So we need to look at what they are developing to see what software it
consists of, and whether it consists entirely of free software that
can be included in a version of the GNU system.

See https://gnu.org/philosophy/open-source-misses-the-point.html.

  > The problem is that there are very few people within EleutherAI using emacs
  > and few people who can help.

Assuming they are heading for the right goal, it would be great for
you to offer your help, and I'm sure they will find plenty of people
here who would like to do that.

If they could make their system keep track of licenses from which text
was obtained, they could implement something to avoid one of the
pitfalls of Copilot: that it gives you a substantial amount of code
that is substantially similar to one copyright work and thus leads
you unknowing into infringement.



-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





      parent reply	other threads:[~2021-07-17 23:53 UTC|newest]

Thread overview: 29+ 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-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-18  6:42             ` Eli Zaretskii
2021-07-17 21:35           ` Juri Linkov
2021-07-17 23:53       ` Richard Stallman [this message]

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=E1m4u7W-0003wM-Au@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mullikine@gmail.com \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).