unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jgart <jgart@dismail.de>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: raingloom <raingloom@riseup.net>,
	Ricardo Wurmus <rekado@elephly.net>,
	guix-devel@gnu.org
Subject: Re: Guix "R" Us - GNU's joy store!
Date: Thu, 6 Jan 2022 12:45:23 -0500	[thread overview]
Message-ID: <20220106124523.GB7102@gac.attlocal.net> (raw)
In-Reply-To: <87ee5kvpgk.fsf@gmail.com>

On Thu, 06 Jan 2022 09:44:27 -0600 Katherine Cox-Buday <cox.katherine.e@gmail.com> wrote:
Hi Katherine,

> 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.

Contributing to Guix upstream is definitely high priority for the guixrus
channel and the whereiseverone community.

For example, as a small community we are planning to organize a monthly
channel cleanup day in which we look at all the packages in guixrus and
determine which packages should be sent upstream and which packages still
need more work. This style of iteration can serve as an additional and
more intimate layer of onboarding for newer users because we review
patches on https://lists.sr.ht/~whereiseveryone/guixrus as well as
discuss package issues on #whereiseveryone (libera.chat) in a short
feedback loop. In the process of doing the above we also explain the
upstream contribution process to newcomers. My hope is that higher-quality
packages by first-time Guixers will become more commonplace in upstream
issue trackers.

We are also experimenting with using builds.sr.ht to run the guix lint
checker, and more when submitting patches to guixrus/upstream thanks
to dhruvin:

https://builds.sr.ht/~dhruvin/job/665098
https://builds.sr.ht/~dhruvin/job/665205

We are developing a package search[1] in the context of the guixrus
channel web site:

https://paste.sr.ht/~dhruvin/0828f7b1df2ffa7b7b31c50e07ef043d94caeea0

guixrus had 83 packages that day. If interested in the library that was
used to generate the json paste output see this repo:

https://git.sr.ht/~dhruvin/doug

A top priority goal of the whereiseveryone community is to encourage
new Guixers to contribute to Guix (upstream as well as whereiseveryone
community projects). We want to facilitate, develop, and discuss that
process, as well as experiment with fun ideas and tools for Guix. It's
ambitious, I know. We'll take it one S-expression at a time.

happy hacking,

https://sr.ht/~whereiseveryone/


      reply	other threads:[~2022-01-06 17:46 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
2022-01-06 17:45           ` jgart [this message]

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=20220106124523.GB7102@gac.attlocal.net \
    --to=jgart@dismail.de \
    --cc=cox.katherine.e@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=raingloom@riseup.net \
    --cc=rekado@elephly.net \
    /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).