From: Ian Eure <ian@retrospec.tv>
To: guix-devel@gnu.org
Subject: Re: Next Steps For the Software Heritage Problem
Date: Tue, 18 Jun 2024 10:57:35 -0700 [thread overview]
Message-ID: <87y1723z4j.fsf@meson> (raw)
In-Reply-To: <CA+3U0ZkLYtWdAqjJ0UoqgaP4WmMjmgaG_nrEpmaJrC3buP0O-g@mail.gmail.com>
Hi Greg,
Please read my earlier reply in this thread[1].
HuggingFace is demonstrably violating the licenses of the Free
Software used to train its StarCoder2 LLM.
Software Heritage is continuing to partner with HuggingFace in
spite of these violations.
Guix is continuing to partner with SWH in spite of their continued
support of these violations.
Guix is indirectly enabling the violation of the license for the
Free Software it packages. Guix has the power to stop doing that.
What is your specific rationale for continuing to enable these
clear license violations?
Thanks,
— Ian
[1]:
https://lists.gnu.org/archive/html/guix-devel/2024-06/msg00195.html
Greg Hogan <code@greghogan.com> writes:
> On Tue, Jun 18, 2024 at 12:33 PM MSavoritias
> <email@msavoritias.me> wrote:
>>
>> Ah it seems I wasn't clear enough.
>> I meant write something like:
>>
>> By packaging a software project for Guix you are exposing said
>> software
>> to a code harvesting project (also known as LLMs or "AI") run
>> by
>> Software Heritage and/or their partners. Make sure you have
>> gotten
>> fully informed consent and that the author of this package
>> fully
>> understands what the implications are.
>>
>> Something like that. To make it clear that the package that is
>> about to
>> be added to Guix is going to be harvested for the LLM models
>> Software
>> Heritage decided to share the code with.
>>
>> Hope this is more clear.
>
> Free software licenses do not require bespoke consent to "to run
> the
> program, to study and change the program in source code form, to
> redistribute exact copies, and to distribute modified versions"
> (and
> "Being free to do these things means (among other things) that
> you do
> not have to ask or pay for permission to do so.").
>
> Your fear mongering against free software runs afoul of Guix
> project
> guidelines ("In addition, the GNU distribution follow [sic] the
> free
> software distribution guidelines. Among other things, these
> guidelines
> reject non-free firmware, recommendations of non-free software,
> and
> discuss ways to deal with trademarks and patents.").
>
> If you feel that LLMs/AI are violating the terms of a license,
> then
> feel free to pursue that through the legal system (potentially
> very
> profitable given the monetary penalties for violations of
> copyright).
> Otherwise, we should be celebrating the users and use of free
> software. I'm old enough to remember "Only wimps use tape
> backup:
> _real_ men just upload their important stuff on ftp, and let the
> rest
> of the world mirror it ;)"
> [https://lkml.iu.edu/hypermail/linux/kernel/9607.2/0292.html].
next prev parent reply other threads:[~2024-06-18 21:43 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 8:37 Next Steps For the Software Heritage Problem MSavoritias
2024-06-18 14:19 ` Ian Eure
2024-06-19 8:36 ` Dale Mellor
2024-06-20 17:00 ` Andreas Enge
2024-06-20 18:42 ` Dale Mellor
2024-06-20 20:54 ` Andreas Enge
2024-06-20 20:59 ` Ekaitz Zarraga
2024-06-20 21:12 ` Andreas Enge
2024-06-21 8:41 ` Dale Mellor
2024-06-21 9:19 ` MSavoritias
2024-06-21 13:33 ` Luis Felipe
2024-06-21 17:51 ` Exclude checker with package properties [draft PATCH] Simon Tournier
2024-06-21 18:37 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-21 18:44 ` Simon Tournier
2024-06-21 18:42 ` Simon Tournier
2024-06-22 15:54 ` Draft: dry-run + Exclude checker with package properties Simon Tournier
2024-06-20 21:27 ` Next Steps For the Software Heritage Problem Simon Tournier
2024-06-18 16:21 ` Greg Hogan
2024-06-18 16:33 ` MSavoritias
2024-06-18 17:31 ` Greg Hogan
2024-06-18 17:57 ` Ian Eure [this message]
2024-06-19 7:01 ` MSavoritias
2024-06-19 9:57 ` Efraim Flashner
2024-06-20 2:56 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-20 5:18 ` MSavoritias
2024-06-19 10:10 ` Efraim Flashner
2024-06-21 8:39 ` About SWH, let avoid the wrong discussion Simon Tournier
2024-06-21 9:12 ` MSavoritias
2024-06-21 9:46 ` Andreas Enge
2024-06-21 10:44 ` MSavoritias
2024-06-21 13:45 ` Luis Felipe
2024-06-21 14:15 ` MSavoritias
2024-06-21 16:33 ` Luis Felipe
2024-06-21 17:04 ` Msavoritias
2024-06-21 16:34 ` Liliana Marie Prikler
2024-06-21 16:51 ` Vagrant Cascadian
2024-06-21 17:22 ` MSavoritias
2024-06-21 20:51 ` Vagrant Cascadian
2024-06-22 15:46 ` MSavoritias
2024-06-22 17:55 ` Breath, let take a short break :-) Simon Tournier
2024-06-24 7:30 ` MSavoritias
2024-06-24 10:23 ` Tomas Volf
2024-06-24 11:56 ` Lets cut this off Efraim Flashner
2024-06-21 17:25 ` About SWH, let avoid the wrong discussion Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-22 13:06 ` Richard Sent
2024-06-22 14:42 ` MSavoritias
2024-06-22 19:53 ` Ricardo Wurmus
2024-06-24 7:55 ` MSavoritias
2024-06-24 9:13 ` Ricardo Wurmus
-- strict thread matches above, loose matches on Subject: below --
2024-06-18 17:12 Next Steps For the Software Heritage Problem Andy Tai
2024-06-18 18:08 ` Ian Eure
2024-06-19 10:31 ` raingloom
2024-06-27 12:27 ` Ludovic Courtès
2024-06-27 15:30 ` Ian Eure
2024-06-27 16:48 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-27 16:58 ` Ludovic Courtès
2024-06-19 7:52 Simon Tournier
2024-06-19 9:13 ` MSavoritias
2024-06-19 9:54 ` Efraim Flashner
2024-06-19 10:25 ` raingloom
2024-06-19 15:46 ` Ekaitz Zarraga
2024-06-20 6:36 ` MSavoritias
2024-06-20 14:35 ` Ekaitz Zarraga
2024-06-21 8:51 ` MSavoritias
2024-06-19 10:34 ` MSavoritias
2024-06-19 14:41 ` Simon Tournier
2024-06-20 6:51 ` MSavoritias
2024-06-20 14:40 ` Simon Tournier
2024-06-21 9:08 ` MSavoritias
2024-06-28 18:01 Juliana Sims
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=87y1723z4j.fsf@meson \
--to=ian@retrospec.tv \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.