From: "Gábor Boskovits" <boskovits@gmail.com>
To: Laura Lazzati <laura.lazzati.15@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: GNU Guix Video Documentation discussing priorities
Date: Mon, 19 Nov 2018 13:09:14 +0100 [thread overview]
Message-ID: <CAE4v=pj3dt4f0APcGojJtJ8_h6utTtmdpLmi7BpyzuaN0n5Jog@mail.gmail.com> (raw)
In-Reply-To: <CAPNLzUPyZ_WV3QVi=q_ExNmZANAXSNbkGWeFrjFiesZ5nYBPDw@mail.gmail.com>
Hello guix!
Now that we have our intern announced I would like to bring this
thread back to life.
So regarding the Outreachy Project for Creating Video Documentation
for GNU Guix,
we come to a point where we should set up the priorities:
1. What types of videos should be created first:
a. introducing concepts,
b. practical howtos.
2. What audience to target:
a. people not yet interested in guix
b. people new to guix
c. users
d. developers.
3. What topics to cover first.
What we have so far:
Based on Julien's suggestions:
* Focus on more practical howtos aimed at people new to guix.
** installing guix on a foreign distro
** installing guixsd
** using guix: installing, upgrading and removing packages
** guix pull
** MAYBE guix gc
* Developers (not guix, but general devs)
** environments vs profiles
** developing on guixsd
** "getting back to work" when something goes wrong
** roll-back profile, system-profile, guix
Additional questions based on Laura's suggestions:
* Should we aim some videos at contributors?
* Should we create videos related to getting help or troubleshooting?
Please feel free to add to the list above, if you feel anything is missing.
Any suggestions are welcome.
Best regards,
g_bor
next prev parent reply other threads:[~2018-11-19 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 7:53 GNU Guix Video Documentation discussing priorities Gábor Boskovits
2018-10-29 11:00 ` Julien Lepiller
2018-10-29 16:59 ` Laura Lazzati
2018-11-19 12:09 ` Gábor Boskovits [this message]
2018-11-20 22:37 ` Björn Höfling
2018-11-21 12:45 ` Laura Lazzati
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=pj3dt4f0APcGojJtJ8_h6utTtmdpLmi7BpyzuaN0n5Jog@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=laura.lazzati.15@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.