From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] rfc: github's copilot feature
Date: Thu, 14 Jul 2022 23:35:17 +0100 [thread overview]
Message-ID: <f0e06584d1c151502e3b1114f9882061fe343596.camel@gentoo.org> (raw)
In-Reply-To: <YtCN7OXGjob4ocAo@linux1.home>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
On Thu, 2022-07-14 at 16:43 -0500, William Hubbs wrote:
> On Thu, Jul 14, 2022 at 04:33:43PM -0500, William Hubbs wrote:
> > Hey all,
> >
> > I just found out while I was on vacation about Github's copilot feature.
> >
> > Basically, it appears to be a machine learning feature that trains
> > itself on all publically available code on github and provides
> > code suggestions to any public or private repository.
> >
> > https://github.com/features/copilot
> >
> > There appears to be a lot of controversy around it in foss groups, so I
> > thought it might be worth bringing up here. I added the council and
> > trustees because I thought it might be worth bringing to their attention
> > as well. In particular, I see concerns about gpl projects being on github
> > if they can't opt out of this.
>
> It looks like the SFC is urging foss developers to ditch github over
> this.
>
> https://techcrunch.com/2022/07/01/open-source-developers-urged-to-ditch-github-following-copilot-launch/
>
> William
Although I don't work for GitHub specifically, it would still not be
appropriate for me to wade far into this debate. In the interest of keeping
things balanced though, I'll start and finish by referencing this
counter-opinion.
https://www.theregister.com/2022/07/11/robots_open_source/
Chewi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
next prev parent reply other threads:[~2022-07-14 22:35 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 [this message]
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
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=f0e06584d1c151502e3b1114f9882061fe343596.camel@gentoo.org \
--to=chewi@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