From: Csepp <raingloom@riseup.net>
To: Ahmed Khanzada <me@enzu.ru>
Cc: Distopico <distopico@riseup.net>, guix-devel@gnu.org
Subject: Re: A Forum for Guix Users
Date: Mon, 24 Jul 2023 04:41:25 +0200 [thread overview]
Message-ID: <87pm4i9ejc.fsf@riseup.net> (raw)
In-Reply-To: <87wmyq8uwx.fsf@enzu.ru>
Ahmed Khanzada <me@enzu.ru> writes:
> I like this forum idea.
>
> In fact, I really think a forum / presence for GNU more generally would
> be excellent.
>
> Yes, you can find dedicated spaces for Emacs, Guix, etc, and there is
> #gnu on Libera and some mailing lists.
>
> But I think we are sorely missing a central point where users can go and
> see how they might use Guix, Emacs, etc in conjunction. As well as join
> a community centered on GNU as an OS.
>
> I document using Guix, Emacs, exwm and etc together on various
> proprietary online spaces like GitHub, Medium, and Reddit. This is
> because there is good foot traffic in these spaces. Both old and new
> hackers are present in these spaces. But their proprietary nature is
> unfortunate. It would be more ideal to document how to use GNU on an
> official GNU platform.
>
> As of right now, if you approach the GNU community, it just feels like a
> disconnected set of packages. I spend a lot of time explaining to people
> how GNU is a unique libre operating system which you can extend using
> Lisp. I show them examples of how I have a "fullstack" Lisp workstation
> with Guix, Emacs, and exwm. After seeing such an example, the concept of
> GNU really "clicks" for them.
>
> I make my living deploying and monitoring applications on servers, so
> let me know if I can help setup a social GNU presence.
I'm not sure if focusing so much on GNU is a good idea.
next prev parent reply other threads:[~2023-07-24 3:26 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 11:45 A Forum for Guix Users Distopico
2023-07-21 8:37 ` Etienne B. Roesch
2023-07-23 16:17 ` Ahmed Khanzada
2023-07-24 2:41 ` Csepp [this message]
2023-08-19 10:59 ` Simon Tournier
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 20:19 Andy Tai
2023-07-14 21:17 ` Sarthak Shah
2023-07-14 21:26 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-07-14 22:12 ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-07-14 23:50 ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-07-21 13:30 ` 宋文武
2023-07-13 13:52 Sarthak Shah
2023-07-13 14:05 ` Robby Zambito
2023-07-13 15:21 ` Csepp
2023-07-14 11:31 ` Msavoritias
2023-07-15 13:43 ` Attila Lendvai
2023-07-15 21:00 ` MSavoritias
2023-07-16 5:55 ` Julien Lepiller
2023-07-15 2:45 ` kiasoc5
2023-07-15 13:59 ` Attila Lendvai
2023-07-15 13:14 ` Tobias Geerinckx-Rice
2023-07-14 21:10 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-07-15 13:27 ` Attila Lendvai
2023-07-16 10:33 ` Pjotr Prins
2023-07-16 23:30 ` Csepp
2023-07-17 17:41 ` Attila Lendvai
2023-07-17 7:37 ` Ricardo Wurmus
2023-07-17 8:17 ` MSavoritias
2023-07-17 20:29 ` Csepp
2023-07-13 14:40 ` Andrea Rossi
2023-07-13 22:38 ` vidak
2023-07-17 7:58 ` Etienne B. Roesch
2023-08-19 12:47 ` Simon Tournier
2023-07-18 1:52 ` Wilko Meyer
2023-07-18 16:39 ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-07-18 21:12 ` Ricardo Wurmus
2023-08-19 11:54 ` Simon Tournier
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=87pm4i9ejc.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=distopico@riseup.net \
--cc=guix-devel@gnu.org \
--cc=me@enzu.ru \
/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).