From: Adam McCartney <adam@mur.at>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Google Season of Docs 2024
Date: Fri, 23 Feb 2024 10:18:33 +0100 [thread overview]
Message-ID: <tguraxw55zvdq7rz5pbj44myox2kedrjf24rg6r5i7lnrt3qyb@htuxjjtd5ysw> (raw)
In-Reply-To: <87jzn97f5f.fsf@gmail.com>
Hi Simon,
First, apologies for being a bit late to the party here!
> 2. Would one of you readers be interested by being technical writer?
> 3. Any for improving the documentation?
I'm quite new to guix, so reading through many docs for the first time and
trying out various workflows. I'm taking notes on the various things that work.
Happy to help with this in any way I can!
In the past I've enjoyed using tutorials like "vimtutor" or emacs' "M-x
help-with-tutorial" when trying to break the ice with a completely new piece of
software. Writing something similar for guix might be fun?
>
>Last, keep in mind the deadline is less than 10 days from now.
>1: https://developers.google.com/season-of-docs/docs/project-ideas
>2: https://developers.google.com/season-of-docs/docs/case-study-example
>3: https://developers.google.com/season-of-docs/docs/2022/participants
Maybe I'm not reading this correctly, but it looks like the application window
opened yesterday, 22nd February and will close for organizations on the 2nd
April 2024?
--
Adam McCartney - https://admccartney.mur.at
/
next prev parent reply other threads:[~2024-02-24 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 17:42 Google Season of Docs 2024 Simon Tournier
2024-02-12 19:39 ` Attila Lendvai
2024-02-12 23:06 ` Rostislav Svoboda
2024-02-23 9:18 ` Adam McCartney [this message]
2024-02-28 7:51 ` Matt
-- strict thread matches above, loose matches on Subject: below --
2024-02-13 15:10 Juliana Sims
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=tguraxw55zvdq7rz5pbj44myox2kedrjf24rg6r5i7lnrt3qyb@htuxjjtd5ysw \
--to=adam@mur.at \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.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).