From: John Helmert III <ajak@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] rfc: github's copilot feature
Date: Sat, 16 Jul 2022 14:56:27 -0500 [thread overview]
Message-ID: <YtMX61Arezuuua9U@gentoo.org> (raw)
In-Reply-To: <CAGfcS_keJkQLTeCf-_n-O8dhL7pCsZDxBpad4XyywFb1tcwprQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
On Thu, Jul 14, 2022 at 06:35:32PM -0400, Rich Freeman wrote:
> On Thu, Jul 14, 2022 at 5:43 PM William Hubbs <williamh@gentoo.org> wrote:
> >
> > On Thu, Jul 14, 2022 at 04:33:43PM -0500, William Hubbs wrote:
> > >
> > > I just found out while I was on vacation about Github's copilot feature.
> > >
> >
> > It looks like the SFC is urging foss developers to ditch github over
> > this.
> >
>
> I get the sentiment, but I don't see what direct impact it will have.
> If Gentoo stops using Github all our code will inevitably still be on
> there and will still end up being used to train copilot.
Inevitably? If most of our activity moves somewhere else, I don't see
why we couldn't blow away all of https://github.com/gentoo.
> I'm not sure how strong the copyright argument even is. Your own
> brain is a neural network that has been trained on copyrighted
> textbooks, lectures, code from every employer you ever worked at, and
> so on. Human beings don't even have the ability to avoid learning
> from things they are exposed to; it is a completely involuntary
> process.
>
> In any case, it seems like the general preference has been to move
> towards something else anyway, so it seems a bit of a moot point.
> Most already want to move something else, and after we move basically
> everything we have ever done and will ever do will still end up
> embedded in the mind of copilot anyway.
>
> --
> Rich
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-07-16 19:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 21:33 [gentoo-project] rfc: github's copilot feature William Hubbs
2022-07-14 21:43 ` William Hubbs
2022-07-14 22:35 ` James Le Cuirot
2022-07-15 3:22 ` Ulrich Mueller
2022-07-15 7:35 ` James Le Cuirot
2022-07-14 22:35 ` Rich Freeman
2022-07-16 19:56 ` John Helmert III [this message]
2022-07-16 20:27 ` Rich Freeman
2022-07-17 19:19 ` William Hubbs
2022-07-17 19:42 ` Rich Freeman
2022-07-17 20:33 ` William Hubbs
2022-07-17 20:45 ` William Hubbs
2022-07-18 6:03 ` Michał Górny
2022-07-19 8:41 ` Roy Bamford
2022-07-18 10:22 ` Matthias Maier
2022-07-18 11:52 ` Ulrich Mueller
2022-07-18 13:04 ` Rich Freeman
2022-07-17 6:27 ` Anna
2022-07-17 20:08 ` William Hubbs
2022-07-18 6:21 ` Anna
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=YtMX61Arezuuua9U@gentoo.org \
--to=ajak@gentoo.org \
--cc=gentoo-project@lists.gentoo.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