From: ludo@gnu.org (Ludovic Courtès)
To: Brandon Invergo <brandon@invergo.net>
Cc: guix-devel@gnu.org
Subject: Re: Synchronizing descriptions with GSRC?
Date: Thu, 11 Jul 2013 00:03:55 +0200 [thread overview]
Message-ID: <87hag26pis.fsf@gnu.org> (raw)
In-Reply-To: <87d2qqp0j7.fsf@naga.invergo.net> (Brandon Invergo's message of "Wed, 10 Jul 2013 23:28:44 +0200")
Hi Brandon,
Brandon Invergo <brandon@invergo.net> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> After a quick glance over the differences, it’s not clear to me what
>> should be done. Often, descriptions in GSRC are shorter that what we
>> have. Sometimes they’re the same, or stripped version of those we have.
>> Sometimes they paraphrase those we have.
>>
>> Descriptions in Guix are typically taken from the upstream web page or
>> README file, so I would intuitively feel like the upstream description
>> better characterizes the package.
>
> Just a quick response to this. When I was writing the descriptions for
> GSRC, I wasn't sure whether I could copy descriptions wholesale from the
> project websites due to copyright claims. I doubt that anyone would get
> upset but I was just playing it safe. For example, they take a similar
> precaution with the free software directory on fsf.org. So, that's the
> reason most of them are paraphrased.
Yes, but it’s unclear whether these are copyrightable, and since these
are GNU packages anyway, it’s safe to directly copy their descriptions,
I think.
> Anyway, I'm happy to sync in the other direction and pull some
> descriptions from Guix into GSRC.
>
> 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.
A related question is i18n: Guix uses gettext, and the plan is to use
the Translation Project for the translation of synopses/descriptions
too. Should that be handled externally too? If it is, we’d still need
to have a gettext catalog for our purposes. How could that work?
Thanks,
Ludo’.
next prev parent reply other threads:[~2013-07-10 22:09 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 [this message]
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
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=87hag26pis.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=brandon@invergo.net \
--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 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.