From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: Raghav Gururajan <raghavgururajan@disroot.org>
Cc: guix-devel@gnu.org
Subject: Re: Proposal for Outreachy (May-August 2020)
Date: Wed, 8 Jan 2020 16:05:23 +0100 [thread overview]
Message-ID: <20200108160523.60f1e4f6@kompiuter> (raw)
In-Reply-To: <8d6e8525703d214f1e4e28dd1afb654e@disroot.org>
On Wed, 08 Jan 2020 07:06:26 +0000
"Raghav Gururajan" <raghavgururajan@disroot.org> wrote:
> Hello Jan!
>
> Yeah, I am too disappointed by some or half of the things they
> incorporated into the project. The thing is, I want to bring more
> newcomers of GNU+Linux System into Guix. I would like to see Guix
> being deployed as mainstream system for domestic and commercial
> purposes. For domestic users, there is a high requirement for
> graphical interfaces. Unfortunately, currently we have only GNOME and
> KDE as full-blown desktop environments. They both have similar issues
> regarding software freedom and software creep. GNOME Software,
> QtWebKIT etc. Also. they both are tightly integrated redhat creeps
> such as network-manager, pulseaudio, dbus and systemd. The only
> reasons for me to lean towards GNOME over KDE, is that 1) Being GNU
> Project (hope it stays) 2) Being GTK based (shared dependency with
> most other free softwares).
>
Okay then, if it is going to help promoting Guix, I'm okay with this.
>
> I also see another light. Enlightenment. The EFL library is
> independent of gnome, kde and redhat related stuffs. It has systemd
> only as optional dependency. Also uses connman over network-manager.
> May there is some hope here. Once Enlightenment grows into drop-in
> replacement of GNOME or KDE. I will definitely be shifting my focus
> from GNOME to Enlightenment.
>
I found it a bit strange, guess I'll have to write my own DE anyway :)
>
> I love the design principles of Xfce. Modularity and re-usability.
> The only downside I face with Xfce are 1) Depends on GNOME stuff,
> dbus etc. 2) Not as feature-rich as GNOME or KDE. Anyway, Xfce is
> good light-weight DE fpr new-comers. That's why Xfce is still on my
> hope list.
>
Understandable.
>
> Let's not constrain ourselves by stating something as just
> opinion. :-) The matters you mentioned are real issues and factually
> causing trouble in software freedom. :-)
>
What I meant by this is I can't really make decisions for the whole
community, because I'm just a package maintainer. But you're right
those are serious issues.
> Regards,
> RG.
Jan Wielkiewicz
next prev parent reply other threads:[~2020-01-08 15:05 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
2020-01-08 15:15 ` Jan
2020-01-08 7:06 ` Raghav Gururajan
2020-01-08 15:05 ` Jan [this message]
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=20200108160523.60f1e4f6@kompiuter \
--to=tona_kosmicznego_smiecia@interia.pl \
--cc=guix-devel@gnu.org \
--cc=raghavgururajan@disroot.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).