From: ludo@gnu.org (Ludovic Courtès)
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>, help-guix <help-guix@gnu.org>,
guix-blog@gnu.org
Subject: Re: Blog team
Date: Wed, 25 Apr 2018 14:41:36 +0200 [thread overview]
Message-ID: <87k1svsbjz.fsf@gnu.org> (raw)
In-Reply-To: <87fu3kyfx7.fsf@gmail.com> (Pierre Neidhardt's message of "Tue, 24 Apr 2018 17:28:28 +0530")
Hello!
I didn’t mention it but here are rough guidelines that I think we should
follow for blog posts:
• It should indeed be about free software and not promote non-free
software (it’s also a good idea to follow
<https://www.gnu.org/philosophy/words-to-avoid.html> IMO.) So the
topic of patching non-free binaries wouldn’t fit the bill, for
instance.
• It should be understandable by someone who’s not a die-hard Guix
or Scheme hacker. :-) So it’s good to provide enough context,
possibly with links to relevant parts of the manual, previous blog
posts, etc.
• It’s good to use appropriate Markdown markup (ah ha!), like
backquotes for file names, command names, and so on, or “```scheme”
to introduce Scheme snippets. See <http://spec.commonmark.org/0.27/>.
Apart from that, anything that teaches people how to solve a problem or
that explains neat hacks in or with Guix(SD) is very welcome IMO!
Articles don’t have to be super long or take days to write; more
informal or short articles can be useful too.
Ludo’.
prev parent reply other threads:[~2018-04-25 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 8:25 Blog team Ludovic Courtès
2018-04-24 11:58 ` Pierre Neidhardt
2018-04-24 15:05 ` Ricardo Wurmus
2018-04-24 15:57 ` Pierre Neidhardt
2018-04-25 12:41 ` Ludovic Courtès [this message]
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=87k1svsbjz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=ambrevar@gmail.com \
--cc=guix-blog@gnu.org \
--cc=guix-devel@gnu.org \
--cc=help-guix@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.
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).