all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Larissa Leite <lari.leite88@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>,
	Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: GNU Guix Video Documentation
Date: Thu, 25 Oct 2018 18:52:24 +0200	[thread overview]
Message-ID: <CAE4v=pgyWS7sVpPrYOkNHx2Pgzzo1NOgeZyAuGtfm3m=ayM9Yg@mail.gmail.com> (raw)
In-Reply-To: <CAG=FMuXFs=4diHpYfRuwW3TxnVor9izEgNWkc-M0+ZyHFMVkbg@mail.gmail.com>

Hello Larissa,

Larissa Leite <lari.leite88@gmail.com> ezt írta (időpont: 2018. okt.
25., Cs, 18:26):
>
> Hello,
>
> Thank you for your help.
> Is programming the only way of contributing?
> I would like to contribute through documentation, video or translation, if possible.
>

No, documentation improvements are considered contribution for this project.

However, it is really hard to document something that you are not familiar with.

At least installing Guix or GuixSD is a hard requirement.

We recommend packaging something easy, as this will be one of the things that
will have to be documented, and usually these type of contributions
are faster to
make. Also note, that in case of these simple CRAN packages this is rather a
data recording like task, than programming. (Consider that we would
like to create
a 3 minutes tutorial video to have this covered.)

With all that said, you can modify the texinfo documentation of guix,
it is located at
doc/guix.texi in the source. These type of contributions tend to take longer, as
community consensus is needed on the sytle and wording. A recommended way to
create a documentation contribution is to add some @cindex entires to
the manual.

All the contribution guidelines apply, like for all other patches.

Translation is delegated to the Translation Project, and is
coordianted by their per
language communities, and outside the scope of this project right now. However
you are welcome to provide translated verisons of the videos, once the
internship
begins.

> Thank you,
> Larissa Leite
>
> Em qui, 25 de out de 2018 às 10:19, Gábor Boskovits <boskovits@gmail.com> escreveu:

Best regards,
g_bor

  reply	other threads:[~2018-10-25 16:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAG=FMuXO7X0j-D_SMWNgxO0p_0xsyJ_eahDGDjtuv465Y3Xk0A@mail.gmail.com>
2018-10-25  6:17 ` GNU Guix Video Documentation Björn Höfling
2018-10-25  9:18   ` Gábor Boskovits
2018-10-25 16:25     ` Larissa Leite
2018-10-25 16:52       ` Gábor Boskovits [this message]
2018-10-29  9:31         ` Gábor Boskovits
2018-10-25 12:39 Gábor Boskovits
2018-10-25 21:53 ` Björn Höfling
2018-10-26  4:13   ` Ricardo Wurmus
2018-10-26  6:22     ` Gábor Boskovits
2018-10-26  9:59     ` Giovanni Biscuolo
2018-10-26 10:00     ` Björn Höfling
2018-10-26 11:09       ` Gábor Boskovits
2018-10-28  0:32       ` Laura Lazzati
2018-10-28  9:13         ` Gábor Boskovits
2018-10-28 19:14           ` Laura Lazzati
2018-10-28 20:19             ` Gábor Boskovits
2018-10-28 23:26               ` Laura Lazzati
2018-10-29  8:17                 ` Gábor Boskovits
2018-10-29 12:47                   ` Laura Lazzati
2018-10-29  9:10                 ` Björn Höfling
2018-10-29 12:49                   ` 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=pgyWS7sVpPrYOkNHx2Pgzzo1NOgeZyAuGtfm3m=ayM9Yg@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=lari.leite88@gmail.com \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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.