unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: Robby Zambito <contact@robbyzambito.me>,
	Sarthak Shah <shahsarthakw@gmail.com>,
	guix-devel@gnu.org
Subject: Re: A Forum for Guix Users
Date: Sun, 16 Jul 2023 12:33:40 +0200	[thread overview]
Message-ID: <20230716103340.iy2ton3oxcc4kuqc@thebird.nl> (raw)
In-Reply-To: <CAFHYt57b1XZVaEMr9txDCuBha_+QMpTKPQos0HsW5oFoejHSDw@mail.gmail.com>

On Fri, Jul 14, 2023 at 02:10:49PM -0700, Felix Lechner via Development of GNU Guix and the GNU System distribution. wrote:
> Hi Robby and Sarthak,
> 
> On Thu, Jul 13, 2023 at 7:17 AM Robby Zambito <contact@robbyzambito.me> wrote:
> >
> > I personally think that it would be wiser to improve the documentation
> > relating to the mailing lists and IRC logs
> 
> I'm technically one of the administrators of forums.debian.net and
> would not recommend web-based "forums" to projects that do not have
> them. They are hard to search and even harder to police. Also, the
> software tends to be based on dated technologies. There are better
> ways to help people in need.
 
Thanks to Arun we rolled our own issue tracker and knowledge base with

https://issues.genenetwork.org/

Written in Guile the interface is simple, the backend is simply a git
repo (can be hosted anywhere), and it uses a xapian search indexer.
Personally I think this is an awesome way of tracking information and
allows reorganising information and rewriting history. The tags are
arbitrary - though we clearly focussed on an issue tracker here.

If the xapian indexer also analysed mailing list output (through
publicinbox, for example) and maybe debbugs and IRC logs it would be
complete. 

https://public-inbox.org/README.html

Key thing is that people can post, answer questions, track issues etc.
and make it all findable. Fun - but probably useless - fact is that we
can also serve it over gemini.

> The points that were mentioned resonate with me, but I actually find
> Guix's documentation quite good already (possibly even second after
> Arch).

+1. 

> We have five broad issues, however:
> 
> 1. Our community is small, and possibly shrinking.

I doubt that is true in absolute terms. You should see where we were
10 years ago :). Guile and Racket made impressive gains the last
years.

In relative terms we can't compete and should not aim
to do so with either Guix or Guile.

> 2. Scheme is a niche language that is not being promoted enough.

Lisp will always be niche. Why would it change in half a century? The
power of Lisp comes from its syntax - but it is a barrier to entry at
the same time. I am always amazed they came up with that early in CS
history.

> 3. Guix uses a complex file layout that's different from most other
> distributions.

We have the fhs bindings. But yeah, that is another barrier.

> 4. Our master branch often suffers from small defects that prevent
> declared systems (and home configurations) from being updated in full.

I think the stable releases try to address that. But I agree, Guix is
a moving target. I don't see that changing much. 

> 5. Substitute availability is good, but download speeds can be poor
> due to peering issues.

That is a matter of money, I guess.

> Personally, I think that promoting GNU Guile in other settings has
> perhaps the best potential to lower our barriers to entry. People
> should not be writing shell scripts in 2023.

They always will, including me. I am, however, giving Guile talks and
promote rash and gash. I am submitting a talk to ICFP Seattle.

https://icfp23.sigplan.org/home/declmed-2023

You can still do that too. I know they have slots.

> Other than that, everyone can make themselves available to help folks
> with difficulties on the existing mailing lists.
> 
> Everyone writes something silly from time to time. It's not a big
> deal. The helping hand is what counts!

Thanks!

Pj.


  parent reply	other threads:[~2023-07-16 10:34 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 13:52 A Forum for Guix Users 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 [this message]
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
  -- 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-18 11:45 Distopico
2023-07-21  8:37 ` Etienne B. Roesch
2023-07-23 16:17 ` Ahmed Khanzada
2023-07-24  2:41   ` Csepp
2023-08-19 10:59 ` 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=20230716103340.iy2ton3oxcc4kuqc@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=contact@robbyzambito.me \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    --cc=shahsarthakw@gmail.com \
    /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).