unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Jan <tona_kosmicznego_smiecia@interia.pl>
Cc: guix-devel@gnu.org
Subject: Re: Proposal for Outreachy (May-August 2020)
Date: Wed, 8 Jan 2020 12:40:52 +0200	[thread overview]
Message-ID: <20200108104052.GA3568@E5400> (raw)
In-Reply-To: <20200107190658.5f35fcbe@kompiuter>

[-- Attachment #1: Type: text/plain, Size: 1932 bytes --]

On Tue, Jan 07, 2020 at 07:06:58PM +0100, Jan wrote:
> Hi!
> 
> On Tue, 07 Jan 2020 11:32:10 +0000
> "Raghav Gururajan" <raghavgururajan@disroot.org> wrote:
> 
> > Hello Guix Folks!
> > 
> > 1) Improve GNOME Software Stack and GNOME Desktop Environment's
> > user-experience in Guix.
> > 
> In my opinion we should stay away from GNOME, because it is a Red Hat
> project, rather than GNU now. More than this, GNOME makes some bad for
> user freedom decisions, for example they promote nonfree software in
> their "Software" application. They also promote nonfree services such as
> Facebook, Google mail, etc. in their "Online accounts" application.
> They also make some poor design decisions such as adding support for
> flatpak, which is going to have support for "paid", which most
> probably means nonfree applications and they add more and more
> systemd-only features (systemd's problem is feature creep, software
> bloat, uncooperative developers and merging projects into systemd,
> without any reason).
> That's why I would like to see XFCE being improved rather than
> GNOME.
> Ideally both GNOME and XFCE should work well on Guix, but if we have to
> choose between those two, I vote for XFCE.
> 
> But that's my private opinion, it'd be better, if Guix maintainers told
> what they think about it.
> 

For better or worse Gnome is the dominant desktop in the GNU/Linux
market space and we do have it packaged and offer it as part of our
default desktop example. Furthermore Raghav has already been working on
making Gnome better in Guix.

As far as the privacy concerns, those can be addressed on a
package-by-package basis but shouldn't be cause to skip it entirely.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-01-08 10:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 11:31 Proposal for Outreachy (May-August 2020) Raghav Gururajan
2020-01-07 11:32 ` Raghav Gururajan
2020-01-07 18:06   ` Jan
2020-01-08 10:40     ` Efraim Flashner [this message]
2020-01-08 15:15       ` Jan
2020-01-08  7:06   ` Raghav Gururajan
2020-01-08 15:05     ` Jan
2020-01-08  7:42   ` Raghav Gururajan
2020-01-08 14:59   ` Jesse Gibbons
2020-01-08 15:02     ` Raghav Gururajan
2020-01-09 19:54 ` Jan
2020-01-11 23:39   ` Ludovic Courtès
2020-01-12  1:15     ` Jan

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=20200108104052.GA3568@E5400 \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=tona_kosmicznego_smiecia@interia.pl \
    /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).