From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: jgart <jgart@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: Guix "R" Us - GNU's joy store!
Date: Thu, 06 Jan 2022 09:44:27 -0600 [thread overview]
Message-ID: <87ee5kvpgk.fsf@gmail.com> (raw)
In-Reply-To: <20211228192213.GB16610@gac.attlocal.net> (jgart@dismail.de's message of "Tue, 28 Dec 2021 19:22:13 -0500")
jgart <jgart@dismail.de> writes:
> On Wed, 29 Dec 2021 00:27:04 +0100 raingloom <raingloom@riseup.net> wrote:
>> TLDR how much of the effort spent on this channel is really justified
>> compared to making the underserved use-cases easier in upstream Guix?
I also have my own personal "upstream staging" channel so that I can continue contributing to Guix at my own pace, in my own way, until I can get enough velocity to really internalize contributing in the way Guix would like me to. I also tend to hack on things there, and then batch my changes for upstream so that I can keep everything consistent and make sure all my code meets upstream standards. In the meantime, I'm able to actually use the code.
My only concern with organizing this activity into a group is that it is a kind of "community fork". I hope we can take the reasons people make these channels and bring them back to Guix proper to make contributing here just as easy.
At any rate, any energy put into the ecosystem is good in my book. Cheers! :)
--
Katherine
next prev parent reply other threads:[~2022-01-06 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 5:42 Guix "R" Us - GNU's joy store! jgart
2021-12-28 12:14 ` Ricardo Wurmus
2021-12-28 13:40 ` jgart
2021-12-28 23:27 ` raingloom
2021-12-29 0:22 ` jgart
2022-01-06 15:44 ` Katherine Cox-Buday [this message]
2022-01-06 17:45 ` jgart
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=87ee5kvpgk.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
/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).