From: Oliver Propst <oliver.propst@fripost.org>
To: Matt <matt@excalamus.com>
Cc: guix-devel <guix-devel@gnu.org>, jgart <jgart@dismail.de>
Subject: Re: Guix Documentation Meetup
Date: Mon, 10 Jan 2022 10:47:08 +0100 [thread overview]
Message-ID: <7c183c7158018b819449cd6acc5bfb41@fripost.org> (raw)
In-Reply-To: <17e3807ae22.f1a020781024687.6953504682822686403@excalamus.com>
Hi Matt I thanks for your very elaborate and insightful mail. As a Guix
user and enthusiast I definitely agree that documentation is important
for the project. Also if I understand things correctly there are
actually plans to host a documentation meetup this Saturday (maybe at
around 10:30 AM ET as the last ones).
On 2022-01-08 05:52, Matt wrote:
> I want to be a part of this. I feel like I've been rubbing two sticks
> together while it seems some people out there have Zippo lighters
Cool.
> One final question:
>
> How might announcements of the "Guix Documentation Meetup" (and
> "Guix Packaging Meetup)" be made more prominent?
>
> I check the mailing list from time to time, but missed the
> announcements because they were buried. Maybe meetings could be
> announced on info-guix?
Sounds as good ideas to me and something that I think the project should
consider.
> If they become regular, maybe put them on
> https://guix.gnu.org/en/contribute/? FWIW, I'm willing to be present
> so that a documentation meetup could run monthly. I'm an FSF member
> and could use the FSF Jitsi service if I needed to host it. I've not
> used Big Blue Button before.
I'm sure your participation and potential contributions to the
documentation meetup would be very welcome at this point in time :)
next prev parent reply other threads:[~2022-01-10 9:48 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 [this message]
2022-01-10 13:15 ` Matt
2022-01-11 16:24 ` jgart
2022-01-12 0:59 ` Matt
2022-01-12 1:20 ` jgart
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=7c183c7158018b819449cd6acc5bfb41@fripost.org \
--to=oliver.propst@fripost.org \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--cc=matt@excalamus.com \
/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).