From: ludo@gnu.org (Ludovic Courtès)
To: Brandon Invergo <brandon@gnu.org>
Cc: guix-devel@gnu.org, bug-gsrc@gnu.org
Subject: Re: Synchronizing descriptions with GSRC?
Date: Wed, 09 Oct 2013 16:21:45 +0200 [thread overview]
Message-ID: <87txgqtthi.fsf@gnu.org> (raw)
In-Reply-To: <87eh7uvgh3.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 09 Oct 2013 13:19:52 +0200")
ludo@gnu.org (Ludovic Courtès) skribis:
> Brandon Invergo <brandon@gnu.org> skribis:
>
>>>> Perhaps it would be best to keep all canonical package descriptions,
>>>> short and long, in a single file under revision control somewhere, such
>>>> as in womb. They would then be available for anyone who needs them,
>>>> should any need arise in the future and it would be easier for all
>>>> involved to stay in sync. What do you think?
>>>
>>> Sounds good to me.
>>
>> OK, I've finally gotten around to moving package descriptions (long and
>> short) to a file in Womb (gnumaint/pkgdescr.txt). The file is
>> recutils-compatible.
>>
>> Currently, all of the long descriptions ("blurbs") are taken from GSRC.
>> Between Karl and I, we're currently in agreement that writing/adapting
>> new descriptions for all of the packages is better than straight copying
>> From websites/READMEs, mainly for keeping a certain level of consistency
>> (length, style, level of detail, etc.) between the descriptions. It
>> also avoids any potential copyright problem, no matter how unlikely it
>> may be. In addition to Guix and GSRC, these descriptions will also be
>> used to provide descriptions for featured packages on gnu.org, so they
>> can't be too long.
>>
>> The file is fresh out of the oven, so there may be some changes after
>> Karl reviews it. But anyway, it's there as a starting point.
>
> Excellent, thanks! I’ve updated the synchronization tool in Guix to use
> this file, and then I’ll update the descriptions
Done:
<http://git.savannah.gnu.org/cgit/guix.git/commit/?id=a22dc0c49aed0babe16ef92ae24847b343b7eb02>.
Ludo’.
prev parent reply other threads:[~2013-10-09 14:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 20:52 Synchronizing descriptions with GSRC? Ludovic Courtès
2013-07-10 21:28 ` Brandon Invergo
2013-07-10 22:03 ` Ludovic Courtès
2013-07-15 21:44 ` Brandon Invergo
2013-07-15 22:45 ` Nikita Karetnikov
2013-07-16 14:06 ` Ludovic Courtès
2013-07-16 22:54 ` Nikita Karetnikov
2013-10-08 21:44 ` Brandon Invergo
2013-10-08 22:16 ` Karl Berry
2013-10-09 10:14 ` Translation of package descriptions and synopses Ludovic Courtès
2013-10-09 21:48 ` Karl Berry
2013-10-08 21:45 ` Synchronizing descriptions with GSRC? Brandon Invergo
2013-10-09 11:19 ` Ludovic Courtès
2013-10-09 13:55 ` Brandon Invergo
2013-10-09 14:21 ` 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=87txgqtthi.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=brandon@gnu.org \
--cc=bug-gsrc@gnu.org \
--cc=guix-devel@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).