From: Andy Tai <atai@atai.org>
To: guix-devel@gnu.org
Subject: Re: Next Steps For the Software Heritage Problem (Dale Mellor)
Date: Thu, 20 Jun 2024 14:43:30 -0700 [thread overview]
Message-ID: <CAJsg1E9PB5CnFZK68-937hGGg0YC0DBMSoX99KFvP8zUnr4kJg@mail.gmail.com> (raw)
In-Reply-To: <mailman.9704.1718917197.1277.guix-devel@gnu.org>
> Date: Wed, 19 Jun 2024 09:36:29 +0100
> From: Dale Mellor <guix-devel-0brg6a@rdmp.org>
> I use Guix as a tool to develop my own projects, private and
> personal for reasons I'm keeping to myself. As part of that I write package
> definitions for them, and use the Guix machinery to build and test. I *cannot*
> have Guix just giving my code away to anybody, that is just fundamentally wrong.
>
If you release software as free software, you are giving away
software, to anybody and everybody.
> We need to ask what is Guix? A free operating system, a framework for
> developing free operating systems, or a more generic tool for software
> development and deployment? If the latter it *cannot* do nefarious things
> without explicit consent.
Guix is a free operating system _and_ a generic tool for software
development and deployment. It makes no sense to say it does nefarious things
without explicit consent. Just like you cannot try to prohibit GNU
Make from being used to do nefarious things like building malware.
You cannot place usage restriction on free software.
>
> I think at least there should be a /restricted/ license type available to
> package definitions, and the system absolutely should not give source code away
> from packages which use this (of course, they won't get into the official
> distribution, but that's fine).
>
How can you restrict others from posting links to your content, as
what essentially package definitions in Guix are.
> More broadly, I think they should just stop inter-operating with SH. Just
> walk away.
>
> Dale
next parent reply other threads:[~2024-06-20 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.9704.1718917197.1277.guix-devel@gnu.org>
2024-06-20 21:43 ` Andy Tai [this message]
2024-06-21 8:14 ` Next Steps For the Software Heritage Problem (Dale Mellor) MSavoritias
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJsg1E9PB5CnFZK68-937hGGg0YC0DBMSoX99KFvP8zUnr4kJg@mail.gmail.com \
--to=atai@atai.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).