From: Benjamin Slade <beoram@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, guix-blog@gnu.org
Subject: Re: Blog: Guix packaging tutorial
Date: Thu, 11 Oct 2018 19:05:28 -0600 [thread overview]
Message-ID: <87lg74nfdz.fsf@jnanam.net> (raw)
In-Reply-To: <87y3b44n6q.fsf@gnu.org>
On 2018-10-11T07:39:41-0600, Ludovic Courtès <ludo@gnu.org> wrote:
> Perhaps one option would be to have a specific “Contributing
> Packages” sub-section, where it’s simple to have an ordered list, and
> then another subsection (“Contribution Guidelines” maybe?) with other
> items such as gender-neutral wording.
> Thoughts? Would you like to give it a try?
Thanks, Ludo'. I think would you suggest makes sense.
I'm happy to work with someone on it - I'd be hesitant
to try to take it on single-handed as I'm still a neophyte Guix packager.
—Ben
--
Benjamin Slade - https://babbagefiles.xyz
`(pgp_fp: ,(21BA 2AE1 28F6 DF36 110A 0E9C A320 BBE8 2B52 EE19))
'(sent by mu4e on Emacs running under GNU/Linux . https://gnu.org )
`(Choose Linux ,(Choose Freedom) . https://linux.com )
next prev parent reply other threads:[~2018-10-12 1:05 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 22:54 Blog: Guix packaging tutorial Benjamin Slade
2018-10-08 23:05 ` Pierre Neidhardt
2018-10-09 0:04 ` Benjamin Slade
2018-10-10 9:02 ` Ludovic Courtès
2018-10-11 1:38 ` Benjamin Slade
2018-10-11 9:37 ` Gábor Boskovits
2018-10-11 13:39 ` Ludovic Courtès
2018-10-12 1:05 ` Benjamin Slade [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-13 10:50 Pierre Neidhardt
2018-09-13 11:16 ` Pjotr Prins
2018-09-13 11:53 ` Ricardo Wurmus
2018-09-13 12:04 ` Pjotr Prins
2018-09-13 19:11 ` Andreas Enge
2018-09-14 11:07 ` Pierre Neidhardt
2018-09-14 11:33 ` Pjotr Prins
2018-09-24 17:00 ` Pierre Neidhardt
2018-09-24 17:37 ` Pierre Neidhardt
2018-09-27 13:43 ` Ludovic Courtès
2018-09-27 17:34 ` Pierre Neidhardt
2018-09-29 16:28 ` Ludovic Courtès
2018-09-29 21:18 ` Ricardo Wurmus
2018-09-30 19:01 ` Pierre Neidhardt
2018-09-30 19:44 ` Ludovic Courtès
2018-09-30 21:14 ` Pierre Neidhardt
2018-10-02 12:12 ` Ludovic Courtès
2018-10-02 16:02 ` Pierre Neidhardt
2018-10-02 19:46 ` Ricardo Wurmus
2018-10-03 8:10 ` Pierre Neidhardt
2018-10-03 18:16 ` Pierre Neidhardt
2018-10-08 12:20 ` Ludovic Courtès
2018-10-08 15:18 ` Ricardo Wurmus
2018-10-08 18:41 ` Pierre Neidhardt
2018-10-08 19:06 ` Pierre Neidhardt
2018-10-08 19:59 ` Ricardo Wurmus
2018-10-08 22:09 ` Pierre Neidhardt
2018-10-08 22:33 ` Pierre Neidhardt
2018-10-08 23:45 ` Pierre Neidhardt
2018-10-10 11:56 ` Ludovic Courtès
2018-10-10 13:20 ` George Clemmer
2018-10-10 13:31 ` Pierre Neidhardt
2018-10-10 14:13 ` Ricardo Wurmus
2018-10-20 19:58 ` Divan
2018-10-21 10:30 ` Pierre Neidhardt
2018-10-21 11:21 ` Pierre Neidhardt
2018-10-22 20:40 ` Divan Santana
2018-10-22 21:11 ` Pierre Neidhardt
2018-09-26 10:20 ` Ludovic Courtès
2018-09-26 10:28 ` Pierre Neidhardt
2018-09-27 11:56 ` 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
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=87lg74nfdz.fsf@jnanam.net \
--to=beoram@gmail.com \
--cc=guix-blog@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).