From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: Blog team
Date: Wed, 25 Apr 2018 14:41:36 +0200
Message-ID: <87k1svsbjz.fsf@gnu.org>
References: <87wowx2eqn.fsf@gnu.org> <87fu3kyfx7.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55248)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1fBJk2-0006il-II
	for help-guix@gnu.org; Wed, 25 Apr 2018 08:41:47 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1fBJk1-000417-N1
	for help-guix@gnu.org; Wed, 25 Apr 2018 08:41:46 -0400
In-Reply-To: <87fu3kyfx7.fsf@gmail.com> (Pierre Neidhardt's message of "Tue,
	24 Apr 2018 17:28:28 +0530")
List-Id: <help-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/help-guix/>
List-Post: <mailto:help-guix@gnu.org>
List-Help: <mailto:help-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=subscribe>
Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org
Sender: "Help-Guix" <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>, help-guix <help-guix@gnu.org>, guix-blog@gnu.org

Hello!

I didn=E2=80=99t mention it but here are rough guidelines that I think we s=
hould
follow for blog posts:

  =E2=80=A2 It should indeed be about free software and not promote non-free
    software (it=E2=80=99s 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=E2=80=99t fit the bill, for
    instance.

  =E2=80=A2 It should be understandable by someone who=E2=80=99s not a die-=
hard Guix
    or Scheme hacker.  :-)  So it=E2=80=99s good to provide enough context,
    possibly with links to relevant parts of the manual, previous blog
    posts, etc.

  =E2=80=A2 It=E2=80=99s good to use appropriate Markdown markup (ah ha!), =
like
    backquotes for file names, command names, and so on, or =E2=80=9C```sch=
eme=E2=80=9D
    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=E2=80=99t have to be super long or take days to write; more
informal or short articles can be useful too.

Ludo=E2=80=99.