From: MSavoritias <email@msavoritias.me>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: About SWH, let avoid the wrong discussion
Date: Fri, 21 Jun 2024 13:44:39 +0300 [thread overview]
Message-ID: <20240621134439.5bc324b4@fannys.me> (raw)
In-Reply-To: <ZnVMEGIRikQp9m_F@jurong>
On Fri, 21 Jun 2024 11:46:56 +0200
Andreas Enge <andreas@enge.fr> wrote:
> Am Fri, Jun 21, 2024 at 12:12:13PM +0300 schrieb MSavoritias:
> > and as I mention in my first email I want to apply social pressure and make it clear to package authors what is happening so we can move to an opt-in model.
>
> Well, the opt-in model is in place: As soon as I put my code under a free
> license on the Internet, I opt in for it to be harvested by SWH (and anybody
> else, including non-friendly companies and state actors).
That may be how you have understood it but that is not how most people understand it.
See for example mirroring videos that creators have made online, or more recently some activitypub software harvesting posts for a search engine.
As I have been saying a lot in this thread (because there seem to be a lot of people in the Guix community not familiar that legal are not the same as social rules):
-Just because you CAN do something doesn't mean you SHOULD. In the sense that yes somebody can probably harvest all my posts from activitypub and post them somewhere else,
in practise they are an asshole tho and probably are going to be deferated pretty fast for breaking the social rules of common human decency :)
This is by design in activitypub btw the social rule of don't harvest stuff. Same way that it is in xmpp. Not that assholes don't exist of course, but nobody is exempt from common human decency and
a following the rules of a place. See also https://www.consentfultech.io/ for a good read. Hope it answers some questions.
- What you are saying even if it was true, is not indicated anywhere in the manual or the website. (which is part of what I want to do.) Add a warning for package authors and commiters and a proper procedure.
We are ultimately living in a society that we have some good faith by default that everybody acts respectfully (dont leak my messages that i sent to you in private for example). If they don't
we take measures to not include them anymore. I am not saying this for SWH mind you, its just an example.
Saying that I can do whatever I want is a very reductionist point of view that I doubt would be acceptable inside Guix and FSF even. Given that GPL itself doesn't allow you to do whatever you want.
TBH it seems you are not the only one in this thread not knowing that laws (legal rules of states) ie. the FSF licenses and work and whatever, are not the same as social rules.
But given that Guix has a CoC and social rules on top of that I am hopeful :)
> Now the code may not be found by SWH, and the moment someone makes a Guix
> package out of it and adds it to the Guix main channel, SWH will find and
> archive it; but the opt-in has happened before at the moment I put the code
> online with its license.
>
> Maybe I misunderstood to what you want to apply the term "opt-in" (after
> reading your other message in which you use the term, this seems to be
> the case). If it is to source code of packages being used for AI training,
> there is actually no need to have a separate opt-in. Either it is legal
> under your license (and then you have effectively opted in), or it is
> illegal (in which case explicit opt-in already is a requirement).
Again as I wrote above legal has nothing to do with it really. Its about our social rules and what we have as common understanding in Guix.
if you just do something just because you can, then that makes you an asshole in my book. See hostile forks for example that have happened.
> Am Fri, Jun 21, 2024 at 11:14:18AM +0300 schrieb MSavoritias:
> > Aside from that even Guix uploading all code from the packages to
> > SWH that basically feeds it to a LLM model is indeed not honoring consent of the author of the package.
>
> Guix does not upload code to SWH. It gives them a pointer to a public git
> repository that SWH then harvests or not according to their rules (see my
> reply to Dale yesterday). These are not the same things at all.
This is bikeshedding and arguing on schemantics. Guix gives them a url to download the source code from, so ultimately we (the Guix project) is responsible for the code showing up in there.
Lets not argue over schemantics like this. It is even posted on their website in case you want to argue otherwise https://www.softwareheritage.org/2019/04/18/software-heritage-and-gnu-guix-join-forces-to-enable-long-term-reproducibility/
> Whether or not one agrees with the SWH policy on LLM training (and I have
> not looked at it well enough to form my opinion), I do not think there
> is anything we should change at the level of the Guix project. Maybe SWH
> should put into place an opt-in procedure for feeding LLM; but I do not
> think we in Guix should put into place an opt-in procedure for informing
> SWH of the source code we package. (Which would be completely ineffective
> anyway: One single person in the world would be enough to run the code in
> "guix lint -c archival" on all Guix packages in all channels they have
> access to. For instance, SWH themselves.)
Sure they can. But it starts with showing an example ourselves how it is done. If we wait on others we might as well shut guix down and go develop on macs or something :P
Putting it in Guix is the optimal way to act in good faith towards our community imo. Is it harder? sure. But its always harder to care about consent and privacy and such than otherwise.
MSavoritias
>
> Andreas
>
next prev parent reply other threads:[~2024-06-21 11:04 UTC|newest]
Thread overview: 49+ 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
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 [this message]
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
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=20240621134439.5bc324b4@fannys.me \
--to=email@msavoritias.me \
--cc=andreas@enge.fr \
--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.