unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jgart <jgart@dismail.de>
To: Matt <matt@excalamus.com>
Cc: Oliver Propst <oliver.propst@fripost.org>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Guix Documentation Meetup
Date: Tue, 11 Jan 2022 20:20:30 -0500	[thread overview]
Message-ID: <20220111202030.GB29420@gac.attlocal.net> (raw)
In-Reply-To: <17e4bcc256a.f46f9938363877.5893641743841097444@excalamus.com>

On Tue, 11 Jan 2022 19:59:37 -0500 Matt <matt@excalamus.com> wrote:
>  ---- On Tue, 11 Jan 2022 11:24:20 -0500 jgart <jgart@dismail.de> wrote ----
> 
>  > I'm looking forward to having you at the next docs meetup:
>  > 
>  > https://lists.gnu.org/archive/html/guix-devel/2022-01/msg00189.html
>  > 
>  > Are there any particular sections in the guix manual that you would like
>  > to work on in the meetup?
> 
> I outlined some interests here:  https://lists.gnu.org/archive/html/guix-devel/2022-01/msg00105.html

Hi Matt,

I skimmed that thread. Let me reread and I'll keep it in mind for this
Saturday's meetup. Thank you for taking the time to share your thoughts
and user experiences with guix.

> I was just learning about profiles and how to use them to install
> multiple versions of a software. So, my head is there at the moment.

Have you read ambrevar's post called 'Guix Profiles in Practice'?

Unfortunately ambrevar's blog seems to be down at the moment:

https://ambrevar.xyz/guix-profiles/index.html

> Cohesion is a big point in my outline. Maybe I could check for that as
> regards profiles?  

> Otherwise, maybe look over the contribute section. It
> seems like I could use a rereading of it. If there's anything that's
> unclear, the meeting might be a good space to address it.

roptat made a nice guide for learning texinfo:

https://learnxinyminutes.com/docs/texinfo/

I'm also accepting patches for the guixrus wiki on sourcehut:

https://man.sr.ht/~whereiseveryone/guixrus/

Patches can be sent to ~whereiseveryone/guixrus@lists.sr.ht

The guixrus wiki is being used by the whereiseveryone community as a
staging area for discussing proposals to upstream docs and for any guix
docs that are not ready for whatever reason. I can usually review and
merge any docs for the guixrus wiki within a day or two of submitting
it. If not, ping me on irc.

We accept guixrus wiki docs in markdown. When sending anything in the
guixrus wiki make sure to translate it to texinfo. You can use pandoc
to assist with that. I'll add an entry to the wiki soon for instructions
on how to do that:

```
guix shell pandoc -- pandoc index.md -o index.texi
```

If you'd like to discuss more about the guixrus wiki come chat with us
at #whereiseveryone on the irc.libera.chat network.

> Mainly, I'm interested in getting to meet you and others from the
> community and hear what they value.

Likewise! I'm looking forward to meeting you also and everyone that
might show up.

all best,

jgart

gemini://whereiseveryone.srht.site/
https://whereiseveryone.srht.site/


  reply	other threads:[~2022-01-12  1:23 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08  4:52 Guix Documentation Meetup Matt
2022-01-10  9:47 ` Oliver Propst
2022-01-10 13:15   ` Matt
2022-01-11 16:24     ` jgart
2022-01-12  0:59       ` Matt
2022-01-12  1:20         ` jgart [this message]
2022-01-12  2:57           ` Matt
2022-01-12  3:10             ` Matt
  -- strict thread matches above, loose matches on Subject: below --
2022-03-10 17:02 Raghav Gururajan
2022-03-10 17:11 ` Raghav Gururajan
     [not found] <mailman.34870.1641617883.18145.guix-devel@gnu.org>
2022-01-08  8:42 ` calcium
2022-01-08 11:35   ` Ricardo Wurmus
2022-01-08 11:49     ` calcium
2022-01-08 16:24     ` Matt
2022-01-08 18:58       ` Ricardo Wurmus
2022-01-08 19:06       ` Leo Famulari
2022-01-09 21:12         ` Matt
2022-01-10  9:05           ` André A. Gomes
2022-01-10 13:40             ` Matt
2022-01-10 16:05               ` André A. Gomes
2022-01-11 18:45                 ` Matt
2022-01-12 18:41           ` Leo Famulari
2022-01-13  0:04             ` Matt
2022-01-13  0:22       ` Leo Famulari
2022-01-13 13:15         ` ilmu
2022-01-08 13:41   ` Matt
2022-01-08 14:09     ` Julien Lepiller
2022-01-08 14:54       ` Matt
2022-01-08 14:39     ` Josselin Poiret
2021-12-13 13:45 Blake Shaw
2021-12-13 15:55 ` Katherine Cox-Buday
2021-12-13 12:41 Blake Shaw
2021-12-13 12:33 Blake Shaw
2021-12-15 17:37 ` Blake Shaw
2021-12-15 19:12   ` zimoun
2021-12-15 22:37     ` jgart
2021-12-11  1:42 Blake Shaw
2021-12-10 22:40 Blake Shaw
2021-12-10 23:18 ` Ryan Prior
2021-12-11 18:55   ` Katherine Cox-Buday
     [not found]     ` <87lf0q2m7n.fsf@nonconstructivism.com>
2021-12-13  3:50       ` Katherine Cox-Buday
2021-12-30 21:52         ` adriano
2022-01-06 15:58           ` Katherine Cox-Buday
2021-12-13  8:29 ` zimoun
2021-12-14 16:01   ` Katherine Cox-Buday
2021-12-14 17:38     ` Luis Felipe
2021-12-14 17:52       ` Katherine Cox-Buday
2021-12-21  6:41 ` adriano
2021-12-09  9:28 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=20220111202030.GB29420@gac.attlocal.net \
    --to=jgart@dismail.de \
    --cc=guix-devel@gnu.org \
    --cc=matt@excalamus.com \
    --cc=oliver.propst@fripost.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).