unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Steve George <steve@futurile.net>
To: Christopher Howard <christopher@librehacker.com>
Cc: "Thompson, David" <dthompson2@worcester.edu>,
	 Ekaitz Zarraga <ekaitz@elenq.tech>,
	"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Discussion on Guix funding // future
Date: Sat, 26 Oct 2024 07:57:07 +0100	[thread overview]
Message-ID: <hfvbket43ydcuic446ilbqot72rzmaua6wwvw6mq6il6ezgryf@uimpcca5h5mo> (raw)
In-Reply-To: <87bjz8meyi.fsf@librehacker.com>

Hi Christopher,

Thanks adding your thoughts, we're all trying to be "humble and enthusiastic" for Guix here!

On 25 Oct, Christopher Howard wrote:
> A few thoughts, as a humble but enthusiastic guix user. I'll try to be brief:
> 
> - Having a full-time job already, I don't mind making some free contributions (patches, troubleshooting) for Guix, even if somebody else is getting paid to do it.
> - I like that idea of donation money being spent to contract people to do bug killing, package maintenance, or to work on specific development projects.

Thanks, that's a useful to have input from our users and advocates on this topic. 

> - For me, it is critical that Guix remain a purist free-software project, in the way that the FSF and the GNU project promote this.
>
> - I wonder if existing FSF systems or tooling, for their campaigns work, could be of benefit to Guix. FSF has an energetic system for campaigning for donations that seems to work pretty well for them.
> - Personally, I like doing development over e-mail and debbugs, due to how this integrates well with Emacs functionality. It does not appeal to me to have to log in to some heavyweight forge Web site, through a Web browser I despise, to have to participate. I would be interested in other APIs and tools if I can utilize them all through just Emacs.
 
If you're interested in this topic there's quite a few different discussions in the email archive, but it's never really achieved a conclusion. There are many contributors who enjoy the current process, so I don't think anyone's proposing removing that. It's about whether the project could 'add' a forge-pr process - so it's an 'Email *and* <insert something>'. This is just background info as it's not the main aim of this thread.

Steve / Futurile


  reply	other threads:[~2024-10-26  6:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 22:08 Discussion on Guix funding // future Ekaitz Zarraga
2024-10-25  8:12 ` Steve George
2024-10-25  9:11   ` Ricardo Wurmus
2024-10-25  9:16     ` Ekaitz Zarraga
2024-10-25  9:37       ` Ricardo Wurmus
2024-10-25 11:05         ` indieterminacy
2024-10-25 11:22           ` Steve George
2024-10-25 11:51             ` indieterminacy
2024-10-25 12:05         ` Efraim Flashner
2024-10-26 17:16         ` Tomas Volf
2024-10-25 11:06     ` Steve George
2024-10-25 12:13       ` Ricardo Wurmus
2024-10-25 12:18     ` Efraim Flashner
2024-10-25 15:49       ` Steve George
2024-10-25 12:58 ` Thompson, David
2024-10-25 14:31   ` Christopher Howard
2024-10-26  6:57     ` Steve George [this message]
2024-10-25 19:13   ` Ekaitz Zarraga
2024-10-25 23:25     ` Attila Lendvai
2024-10-26 12:49       ` Greg Hogan
2024-10-26 13:48   ` Guix (and Guile's) promise, and how to (hopefully) get there Christine Lemmer-Webber
2024-10-26 14:49     ` Ekaitz Zarraga
2024-10-26 20:22       ` Ludovic Courtès
2024-10-27  0:38         ` Ekaitz Zarraga
2024-10-26 16:40     ` Suhail Singh
2024-10-26 22:07       ` Ludovic Courtès
2024-10-27  1:33         ` Suhail Singh
2024-10-26 22:28       ` indieterminacy
2024-10-26 21:12     ` Ludovic Courtès
2024-10-26 15:04 ` Discussion on Guix funding // future Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2024-10-25 14:21 Noé Lopez via Development of GNU Guix and the GNU System distribution.
2024-10-25 21:26 ` Greg Hogan

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=hfvbket43ydcuic446ilbqot72rzmaua6wwvw6mq6il6ezgryf@uimpcca5h5mo \
    --to=steve@futurile.net \
    --cc=christopher@librehacker.com \
    --cc=dthompson2@worcester.edu \
    --cc=ekaitz@elenq.tech \
    --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 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).