From: J Leslie Turriff <jlturriff@mail.com>
To: libreplanet-discuss@libreplanet.org
Subject: Re: The beast is live - Github Copilot
Date: Wed, 29 Jun 2022 11:35:51 -0500 [thread overview]
Message-ID: <202206291135.51961.jlturriff@mail.com> (raw)
In-Reply-To: <87k091u3eh.fsf@ypei.me>
On 2022-06-27 17:50:46 Yuchen Pei wrote:
> On Sun 2022-06-26 17:25:24 -0700, Marc Sunet wrote:
> >> I feel that one difference between the values of free software and open
> >> source is that the free software does not have a problem with taking
> >> people's work and re-selling it, as long as the work being resold is
> >> free. Whereas open source focus more on what authors get out of "open
> >> source".
> >
> > And in this case it is SaaSS. Not only is it trained on the existing
> > code in the repositories, it also seems to siphon code off your editor
> > as you type:
> >
> > https://github.com/features/copilot/#faq-privacy
>
> Of course there are ways to make it not SaaSS or privacy invading, if
> one is going to work on a free software version of copilot - all they
> need to do is not replicate the antifeatures.
>
> >> GitHub Copilot relies on file content and additional data to
> >
> > work. It collects data both to provide the service and saves some of
> > the data to perform further analysis and enable improvements.
> >
> >> Depending on your preferred telemetry settings, GitHub Copilot may
> >
> > also collect and retain the following, collectively referred to as
> > “code snippets”: source code that you are editing, related files and
> > other files open in the same IDE or editor, URLs of repositories and
> > files paths.
>
> Best,
> Yuchen
My take on this is that software authors who value control of their code are well advised
to move it to another repository.
Leslie
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
Desktop Environment: Trinity
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2022-06-29 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 2:38 The beast is live - Github Copilot Marc Sunet
2022-06-24 0:10 ` Yuchen Pei
2022-06-25 20:47 ` Marc Sunet
2022-06-26 1:18 ` Yuchen Pei
2022-06-27 0:25 ` Marc Sunet
2022-06-27 22:50 ` Yuchen Pei
2022-06-29 9:51 ` Luna Jernberg
2022-06-29 16:35 ` J Leslie Turriff [this message]
[not found] <mailman.75.1656086431.25891.libreplanet-discuss@libreplanet.org>
2022-06-24 21:13 ` Shironeko
2022-07-02 14:48 ` Jorge P. de Morais Neto
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://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202206291135.51961.jlturriff@mail.com \
--to=jlturriff@mail.com \
--cc=libreplanet-discuss@libreplanet.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).