all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dimakakos Dimos <bendersteed@teknik.io>
To: swedebugia <swedebugia@riseup.net>, Guix-devel <guix-devel@gnu.org>
Subject: Re: Regarding freedom issues
Date: Tue, 12 Mar 2019 12:50:05 +0200	[thread overview]
Message-ID: <87ftrsnz8i.fsf@teknik.io> (raw)
In-Reply-To: <EC8E1B55-9A17-4CBC-B1A5-7B91EE277C61@riseup.net>

swedebugia <swedebugia@riseup.net> writes:

> Hi.
> I had the idea of integrating guix more with GNU when it comes to packages with freedom issues.
>
> The idea is to add to guix a way to inform the user that the package they just searched for is not included in guix because of freedom issues.
>
> The idea is that when we refuse a package to be included we add it with a short reason to this list.
>
> Something like this
> (issues
>   (package odoo
>   (reason "trapping users by withholding update scripts, see gnu.org/link.to.article"
>   (alternatives '(dolibarr tryton smbledger ledger hledger gnucash)))
>
> This makes it clear to the user that they can scratch the itch and fix the problems by contacting upstream, fork or whatever or choose a better alternative. 
>
> What do you think?
> -- 
> Sent from my k-9 mail for Android.

I like this as well. We could then make lists of alternatives, so they
could be resusable in similar contexts.

The thing is this seems quite a bit of work, but I think it's in the
right direction. Maybe reuse some catalogs of "non-freedom respecting"
software is doable.

  parent reply	other threads:[~2019-03-12 11:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11  6:56 Regarding freedom issues swedebugia
2019-03-12  8:20 ` Pierre Neidhardt
2019-03-12 10:50 ` Dimakakos Dimos [this message]
2019-03-12 11:05 ` Boris A. Dekshteyn
2019-03-12 12:32 ` Ricardo Wurmus
2019-03-12 15:26   ` swedebugia

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=87ftrsnz8i.fsf@teknik.io \
    --to=bendersteed@teknik.io \
    --cc=guix-devel@gnu.org \
    --cc=swedebugia@riseup.net \
    /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.