From: John Darrington <john@darrington.wattle.id.au>
To: Ludovic Court??s <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Call for screencasts!
Date: Thu, 28 Apr 2016 17:44:10 +0200 [thread overview]
Message-ID: <20160428154410.GA9030@jocasta.intra> (raw)
In-Reply-To: <871t649qx7.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
On Sun, Apr 17, 2016 at 05:49:08PM +0200, Ludovic Court??s wrote:
It???s Sunday and you???re probably wondering what you could to help this
wonderful project. Here???s an idea: make a screencast! :-)
I???d like a video of at most 5 minutes to put on the home page that would
showcase, for example (with explanations in English; bonus points if you
have a good mic and are a native speaker ;-)):
Doing decent video presentations requires a diverse range of skills.
I think that rather than simply appealing to individuals to create such a thing,
a better approach is to organise a small team to do it as a collective effort.
It just needs someone to put such a team together and coordinate it. Now that
Guix is an official, legally sanctioned organisation they should be able
to do that!
J'
--
Avoid eavesdropping. Send strong encryted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-04-28 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 15:49 Call for screencasts! Ludovic Courtès
2016-04-28 8:37 ` Alex Kost
2016-04-28 9:11 ` Alex Sassmannshausen
2016-04-28 12:13 ` Ludovic Courtès
2016-04-28 15:44 ` John Darrington [this message]
2016-04-29 12:42 ` Ludovic Courtès
2016-07-27 15:05 ` Ludovic Courtès
2016-07-27 17:29 ` Mathieu Lirzin
2016-07-28 20:53 ` Ludovic Courtès
2016-07-31 11:28 ` Ludovic Courtès
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=20160428154410.GA9030@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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 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.