public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
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 15:45:30 -0500	[thread overview]
Message-ID: <YtR06kv3SN7031vi@linux1.home> (raw)
In-Reply-To: <YtRyCXRkcj7FWIEi@linux1.home>

[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]

On Sun, Jul 17, 2022 at 03:33:13PM -0500, William Hubbs wrote:
> On Sun, Jul 17, 2022 at 03:42:52PM -0400, Rich Freeman wrote:
> > On Sun, Jul 17, 2022 at 3:19 PM William Hubbs <williamh@gentoo.org> wrote:
> > >
> > > 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.
> > 
> > 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.
> > 
> > The social contract talks about how "Gentoo will never depend upon
> > [proprietary software]."  It doesn't mention anything about Gentoo not
> > enabling it/etc.  In fact our policies allow proprietary software to
> > be in our repository (obviously with restrictions on mirroring/etc).
> > Some argue that this is enabling proprietary software, but even if so
> > we're not breaking any promises.
> 
> Rich,
> 
> The question is around the GPL specifically.
> 
> the point is, are we as a project ok with copylot re-appropriating
> our GPL code, possibly to proprietary projects, which could be argued
> violates the GPL?

heh, that was a typo, s/copylot/copilot/, but I guess it fits; that's
what it does. ;-)

William

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-07-17 20:45 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 [this message]
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=YtR06kv3SN7031vi@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