From: ludo@gnu.org (Ludovic Courtès)
To: Quiliro <quiliro@riseup.net>
Cc: help-guix@gnu.org
Subject: Contributing to the manual
Date: Mon, 22 May 2017 10:52:11 +0200 [thread overview]
Message-ID: <87zie5w9xg.fsf_-_@gnu.org> (raw)
In-Reply-To: <20170521100937.4c5f822d@riseup.net> (quiliro@riseup.net's message of "Sun, 21 May 2017 10:09:37 -0500")
Hello!
Quiliro <quiliro@riseup.net> skribis:
> El Sun, 21 May 2017 13:43:02 +0200
> Fox <firefox@firemail.cc> escribió:
>
>> Adonay Felipe Nogueira wrote:
>> >
>> > Whenever possible, plase avoid duplicating efforts.
>> >
>> > Happy hacking! :)
>>
>>
>> yup, duplicated efforts are not cogent nor expedient. Everything of
>> importance ought to be part of the original GNUsite.
>
> How to contribute to the main site then?
The manual of Guix, a copy of which can be seen at
<https://gnu.org/s/guix/manual/html_node>, is maintained in Guix itself:
https://git.savannah.gnu.org/cgit/guix.git/tree/doc/guix.texi#n264
It is written in Texinfo, which is a lightweight markup language.
We definitely welcome improvements to the manual! Before adding
something to the manual, please make sure it’s not already there ;-),
and make sure that what you add is properly integrated and linked to the
rest of the manual.
Once you’re done, you can submit a patch in the usual way:
https://www.gnu.org/software/guix/manual/html_node/Submitting-Patches.html
Ludo’.
next prev parent reply other threads:[~2017-05-22 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 0:50 gitlab.com/rain1/guix-wiki Fox
2017-05-21 1:38 ` gitlab.com/rain1/guix-wiki Adonay Felipe Nogueira
2017-05-21 11:43 ` guix-wiki Fox
2017-05-21 15:09 ` guix-wiki Quiliro
2017-05-22 8:52 ` Ludovic Courtès [this message]
2017-05-21 3:18 ` gitlab.com/rain1/guix-wiki Quiliro
-- strict thread matches above, loose matches on Subject: below --
2018-11-09 5:28 Contributing to the manual Quiliro Ordonez
2018-11-09 7:40 ` Gábor Boskovits
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=87zie5w9xg.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=quiliro@riseup.net \
/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).