From: Matthias Maier <tamiko@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] rfc: github's copilot feature
Date: Mon, 18 Jul 2022 05:22:09 -0500 [thread overview]
Message-ID: <87sfmy201a.fsf@gentoo.org> (raw)
In-Reply-To: <CAGfcS_no1D4q5S4weVRv8spFcAc=-46k-17LdB2eAfYF7ac+Gg@mail.gmail.com> (Rich Freeman's message of "Sun, 17 Jul 2022 15:42:52 -0400")
On Sun, Jul 17, 2022, at 14:42 CDT, Rich Freeman <rich0@gentoo.org> wrote:
> Well, what exactly does copilot have to do with anything? If the
> concern is about copilot "misappropriating" Gentoo's code, then it
> seems we agree that moving off of Github won't change anything.
I completely agree.
I think this is the main point.
There is no way of preventing our publicly available source repository
to be used for machine learning - at least if we want to make it
available at all...
It is just a coincidence that Github is using public git repositories
hosted at Github and that Github *is informing us about the fact*. For
example, Amazon has launched/is launching a competitor [1] that had been
trained on an undisclosed number of public open source code.
Best,
Matthias
[1] https://aws.amazon.com/codewhisperer/faqs/
next prev parent reply other threads:[~2022-07-18 10:22 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
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 [this message]
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=87sfmy201a.fsf@gentoo.org \
--to=tamiko@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