all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tomas Cech <tcech@suse.com>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>, David Craven <david@craven.ch>
Subject: Re: Leaving the guix project
Date: Mon, 20 Feb 2017 09:59:05 +0100	[thread overview]
Message-ID: <878tp1ck6e.wl-tcech@suse.com> (raw)
In-Reply-To: <87y3x2m3so.fsf@gmail.com>

On Sun, 19 Feb 2017 19:30:31 +0100,
Alex Kost wrote:
> 
> David Craven (2017-02-17 13:56 +0100) wrote:
> 
> >> I think if you posit a free software project that works in the way you
> >> describe ("on its own"), it would work very much like Guile works
> >> right now.
> >
> > An operating system has to work on all hardware. Asking people to buy a
> > RYF approved device to run guixsd is no different than apple requiring you
> > to buy an apple computer to run mac os x. Turning guixsd into an embedded
> > system for RYF devices is not something I want to spend time and effort on. I
> > can't with good conscience recommend to people to buy a usb wifi adapter to
> > use guixsd when I believe they have much larger privacy issues in their devices.
> >
> > To be comfortable contributing to a free project I need to know that people are
> > able to do whatever THEY want, with those contributions, and not what the FSF
> > wants. The FSDG and GNU philosophy prevent me from offering any kind of help
> > and require me to do it hidden. What really gets to me is that I feel
> > - whether justly
> > or not - that the FSF believes I need to feel shame for doing and recommending
> > whatever I believe is best. The word "immoral" in this context is
> > simply unacceptable
> > to me.
> >
> > Compliance with the FSDG makes guix very much dependent on an
> > external entity.
> 
> Thanks for this explanation.  Now I understand your point and I agree
> with it!  I also don't like that by default GuixSD stricts itself to the
> hardware supported by linux-libre.  If linux-libre didn't support all
> the hardware on my computer, most likely I would not used GuixSD at all.

Running GuixSD on HW not fully supported by linux-libre is painful for
me as well. I remember my first time success with GuixSD - after some
coffee and sweating I managed to deploy and boot GuixSD on my notebook
which had WiFi card requiring firmware to run. I wasn't able to fix
missing package without reboot.

It took me some time to get with my own kernel (vanilla
based) and initrd on top of Guix (especially as Guile is still
language barrier for me).

I'd love to see some coordinated effort outside of (or better on top of)
Guix to share such work.

I value the freedom, I like the way that Guix cares about it. Yet I
want and need to do something with my computer as well and this could
help sometimes:)

So, guys, where are your GIT repositories for GUIX_PACKAGE_PATH?

S_W

  reply	other threads:[~2017-02-20  8:59 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16  0:14 Leaving the guix project David Craven
2017-02-16  1:40 ` Leo Famulari
2017-02-16  8:24 ` Alex Kost
2017-02-16  8:38 ` Ricardo Wurmus
2017-02-16  8:40 ` Hartmut Goebel
2017-02-16 11:35 ` Alex Vong
2017-02-16 13:17 ` Andy Wingo
2017-02-16 13:20   ` Andy Wingo
2017-02-17 12:56   ` David Craven
2017-02-17 13:48     ` Adonay Felipe Nogueira
2017-02-17 14:05     ` John Darrington
2017-02-17 16:37     ` Ricardo Wurmus
2017-02-17 23:47       ` David Craven
2017-02-18  0:25         ` David Craven
2017-02-18 13:02           ` Ricardo Wurmus
2017-02-19 11:13             ` David Craven
2017-02-18 12:24         ` Ricardo Wurmus
2017-02-19 18:30     ` Alex Kost
2017-02-20  8:59       ` Tomas Cech [this message]
2017-02-20 13:25         ` John Darrington
2017-02-20 22:08           ` ng0
2017-02-21  1:51           ` Mike Gerwitz
2017-02-21 13:13             ` David Craven
2017-02-22  4:52               ` Mike Gerwitz
2017-02-22 13:54                 ` David Craven
2017-02-22 13:58                   ` John Darrington
2017-02-22 14:06                     ` David Craven
2017-02-22 14:14                       ` David Craven
2017-02-22 14:44                         ` Clément Lassieur
     [not found]                           ` <CAL1_imn=D3oEYgUBO4r2dao+a0pypXdwLNxGjPDpRbgOvHj39w@mail.gmail.com>
     [not found]                             ` <CAL1_immw5JQWC1n08SNS+d6-MnL9ZZfe1EmoSMUJuBk0ucsutg@mail.gmail.com>
     [not found]                               ` <CAL1_im=Ffa+k6poKUjygFpUFenbWsQXc-swCyfMErWyE-Yq9pw@mail.gmail.com>
     [not found]                                 ` <CAL1_im=3ib4HD2SD0Vg8EiLxnuNrOP2LcYLsyZTa-TuOLFw6WA@mail.gmail.com>
     [not found]                                   ` <CAL1_im=K96Prp0bQxyqwQ1RkqzYGk1ZKm=B8tPEQG9Fr8sNPLA@mail.gmail.com>
     [not found]                                     ` <CAL1_imnRiwOKv6LrviRmRwpS8NbFC7EFrzx5U5XnukC6OUewFw@mail.gmail.com>
     [not found]                                       ` <CAL1_imkWXa_rm=MLusHcF60hrFACD-R8f4P7pKLgt9Vg_PKxqQ@mail.gmail.com>
     [not found]                                         ` <CAL1_im=bVB=LhojoTdfE4YNBUD05ykeZb+uSqjcG=59hV3=0fg@mail.gmail.com>
2017-02-22 15:00                                           ` David Craven
2017-02-22 15:30                                             ` Pjotr Prins
2017-02-22 14:30                       ` Clément Lassieur
2017-02-22 15:42                       ` Leo Famulari
2017-02-22 15:58                         ` Mathieu Lirzin
2017-02-22 17:14                       ` Ricardo Wurmus
2017-02-21  8:31         ` Alex Kost
2017-02-21 10:26 ` Leaving the guix project (rust question) ng0
2017-02-21 17:40   ` Leaving the guix project Jan Nieuwenhuizen
2017-03-06  9:44 ` Ludovic Courtès
2017-03-10 20:20   ` David Craven
2017-03-10 21:39     ` Ludovic Courtès
2017-03-11 11:57       ` ng0
2017-03-11  1:30     ` Adonay Felipe Nogueira
     [not found] <mailman.54233.1487782142.22739.guix-devel@gnu.org>
2017-02-22 17:29 ` Rodger Fox

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=878tp1ck6e.wl-tcech@suse.com \
    --to=tcech@suse.com \
    --cc=alezost@gmail.com \
    --cc=david@craven.ch \
    --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.