From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:33349) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i9yWd-0007hZ-4l for guix-patches@gnu.org; Mon, 16 Sep 2019 17:27:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i9yWX-0002e7-Bt for guix-patches@gnu.org; Mon, 16 Sep 2019 17:27:07 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:42395) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i9yWU-0002bi-0F for guix-patches@gnu.org; Mon, 16 Sep 2019 17:27:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1i9yWT-00069h-PM for guix-patches@gnu.org; Mon, 16 Sep 2019 17:27:01 -0400 Subject: [bug#37413] [PATCH 0/9] Channel news distribution mechanism Resent-Message-ID: From: Ludovic =?UTF-8?Q?Court=C3=A8s?= References: <20190915221021.4165-1-ludo@gnu.org> Date: Mon, 16 Sep 2019 23:25:55 +0200 In-Reply-To: <20190915221021.4165-1-ludo@gnu.org> ("Ludovic \=\?utf-8\?Q\?Cour\?\= \=\?utf-8\?Q\?t\=C3\=A8s\=22's\?\= message of "Mon, 16 Sep 2019 00:10:21 +0200") Message-ID: <87sgow0w7w.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: 37413@debbugs.gnu.org, Julien Lepiller , "\"pelzflorian (Florian Pelz)\"" Howdy, Ludovic Court=C3=A8s skribis: > This patch series adds a mechanism for channel authors to distribute > =E2=80=9Cnews entries=E2=80=9D alongside their channels. The goal is to = provide a > way for channel authors (including authors of the 'guix channel!) > to inform their users about important changes. > > For example, you=E2=80=99d tell people about package upgrades that require > manual intervention, about important new features, bug fixes, etc. [...] > Regarding i18n, the title and body of an entry can be provided in > several languages. I wonder what workflow we should adopt; > obviously the TP wouldn=E2=80=99t be appropriate, and there=E2=80=99s no = gettext > involved. Julien, Florian: any thoughts on how we could organize to translate these news entries? (See .) I=E2=80=99m thinking we could have an alias with volunteer translators who would provide text fragments by email to the developer who wrote the news? Does that sound reasonable? Thanks, Ludo=E2=80=99.