From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] rfc: github's copilot feature
Date: Sun, 17 Jul 2022 14:19:20 -0500 [thread overview]
Message-ID: <YtRguFd/O44pP55V@linux1.home> (raw)
In-Reply-To: <CAGfcS_nV36nTi4=qo84-+-9achCiE3Uxkw6dWRXDHEFgva2b+A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]
On Sat, Jul 16, 2022 at 04:27:38PM -0400, Rich Freeman wrote:
> On Sat, Jul 16, 2022 at 3:56 PM John Helmert III <ajak@gentoo.org> wrote:
> >
> > On Thu, Jul 14, 2022 at 06:35:32PM -0400, Rich Freeman wrote:
> > >
> > > 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.
> >
>
> Setting aside any concerns about pull requests/etc that are
> effectively stored only there, even if we deleted it we're still
> talking about git. Sooner or later somebody will push a copy of
> things there, so even if we aren't proactively mirroring repositories
> anything anybody does that is GPL is pretty likely to end up there. A
> repo might be gitlab-only for years, and then somebody does a git
> push, and now the entire history is on github the same as if we were
> doing every push there the whole time.
What someone else does is irrelivent. I'm just talking about the
cannonical places where we store repos and accept pull requests from.
Of course someone could push everything back to github; however, there
is nothing we can do about that so that is completely moot for this
discussion.
William
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-07-17 19:19 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 [this message]
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=YtRguFd/O44pP55V@linux1.home \
--to=williamh@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