unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jgart <jgart@dismail.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Guix "R" Us - GNU's joy store!
Date: Tue, 28 Dec 2021 08:40:20 -0500	[thread overview]
Message-ID: <20211228084020.GB29659@gac.attlocal.net> (raw)
In-Reply-To: <87y244j54c.fsf@elephly.net>

On Tue, 28 Dec 2021 13:14:45 +0100 Ricardo Wurmus <rekado@elephly.net> wrote:
> 
> jgart <jgart@dismail.de> writes:
> 
> > * Yet to be merged upstream.
> 
> Are these going to be submitted and merged upstream eventually?  

Hi Ricardo,

From our README:

```
The goal of this guix channel is to provide packages and services that are:

* Yet to be merged upstream.
* In alpha or beta stage of development.
* Customized to certain use-cases.
* Nightly releases.
```

To expound on the above a bit:

> Yet to be merged upstream.

You can think of GuixRUs as a pre-release channel for software that is waiting to be reviewed upstream.

Sometimes patches can sit for a while while waiting for upstream review
and GuixRUs hopes to alleviate some of this anxiety by providing those
patches as "pre-releases" in a community channel that makes them available
through an expedited review process. We're interested in developing tooling
to help facilitate this ambitious endeavour.

> In alpha or beta stage of development.

We'll make grumble available through GuixRUs and provide a service:

https://issues.guix.gnu.org/

Another software that is in heavy development but useable:

https://wahay.org/

> Nightly releases.

GuixRUs will start by tracking olive-editor nightlies:

https://www.olivevideoeditor.org/nightly.php

> What's the intended process to avoid this?

Packages that are suitable for upstream will be sent in batches. 

whereiseveryone community are active contributors and we'll make sure to send over any developments suitable for upstream.

We welcome anyone to help contribute in those efforts. 

Feel free to upstream anything in GuixRUs that you see suitable if we don't get around to it.

If you remember to list the original author/packager when upstreaming from GuixRUs it would be much appreciated.

The first batch to be sent from GuixRUs for upstream will be these emacs packages we recently packaged:

https://git.sr.ht/~whereiseveryone/guixrus/tree/master/item/guixrus/packages/emacs.scm

> Customized to certain use-cases.

I recently forked vis to provide language server protocol support "out of the box".[1]

We're also packaging all the suckless patches for dwm, st, dmenu,
surf, etc... and making them available as guile variables/code in order
to easily assemble your own suckless forks with guix[2][3]. In other words,
GuixRUs can also be thought of as a library for assembling your own suckless fork.

> Is only free software acceptable in this channel?

Yes, we only accept free software. GuixRUs is a free software bazaar.

GuixRUs is at the service of assisting upstream and the Guix community at large.

all best,

jgart


[1] https://github.com/fischerling/vis-lspc#easy-vis-lspc-installation-with-guixrus
[2] https://git.sr.ht/~whereiseveryone/guixrus/tree/master/item/guixrus/patches/suckless.scm#L28
[3] https://git.sr.ht/~whereiseveryone/guixrus/tree/master/item/guixrus/packages/suckless.scm#L44


  reply	other threads:[~2021-12-28 13:41 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 [this message]
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

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=20211228084020.GB29659@gac.attlocal.net \
    --to=jgart@dismail.de \
    --cc=guix-devel@gnu.org \
    --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).