From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Synchronizing descriptions with GSRC? Date: Thu, 11 Jul 2013 00:03:55 +0200 Message-ID: <87hag26pis.fsf@gnu.org> References: <8738rm9lz5.fsf@gnu.org> <87d2qqp0j7.fsf@naga.invergo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52331) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ux2ZM-0004fz-PB for guix-devel@gnu.org; Wed, 10 Jul 2013 18:09:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ux2ZJ-0007ae-C8 for guix-devel@gnu.org; Wed, 10 Jul 2013 18:09:04 -0400 Received: from hera.aquilenet.fr ([141.255.128.1]:33374) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ux2ZJ-0007aX-6d for guix-devel@gnu.org; Wed, 10 Jul 2013 18:09:01 -0400 In-Reply-To: <87d2qqp0j7.fsf@naga.invergo.net> (Brandon Invergo's message of "Wed, 10 Jul 2013 23:28:44 +0200") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Brandon Invergo Cc: guix-devel@gnu.org Hi Brandon, Brandon Invergo skribis: > ludo@gnu.org (Ludovic Court=C3=A8s) writes: > >> After a quick glance over the differences, it=E2=80=99s not clear to me = what >> should be done. Often, descriptions in GSRC are shorter that what we >> have. Sometimes they=E2=80=99re 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=E2=80=99s unclear whether these are copyrightable, and since th= ese are GNU packages anyway, it=E2=80=99s safe to directly copy their descripti= ons, I think. > Anyway, I'm happy to sync in the other direction and pull some > descriptions from Guix into GSRC.=20 > > 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=E2=80=99d still = need to have a gettext catalog for our purposes. How could that work? Thanks, Ludo=E2=80=99.