From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:48967) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iAYTC-00022N-Vz for guix-patches@gnu.org; Wed, 18 Sep 2019 07:50:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iAYTB-0004Oz-Uf for guix-patches@gnu.org; Wed, 18 Sep 2019 07:50:02 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:44857) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iAYTB-0004Oq-QR for guix-patches@gnu.org; Wed, 18 Sep 2019 07:50:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iAYTB-0007Qz-NW for guix-patches@gnu.org; Wed, 18 Sep 2019 07:50:01 -0400 Subject: [bug#37413] [PATCH 0/9] Channel news distribution mechanism Resent-Message-ID: Date: Wed, 18 Sep 2019 13:49:46 +0200 From: "pelzflorian (Florian Pelz)" Message-ID: <20190918114945.elbzrp6sqziylkz2@pelzflorian.localdomain> References: <20190916225258.yd4uzgcm4lyr5zgz@pelzflorian.localdomain> <87improzwm.fsf@gnu.org> <20190917133307.lhsouulr5yynzzrd@pelzflorian.localdomain> <87blvjm485.fsf@gnu.org> <20190917142819.qk6thhoocnci6svn@pelzflorian.localdomain> <87ef0fkknq.fsf@gnu.org> <20190917174102.edmbljhpte5rklsr@pelzflorian.localdomain> <20190917202035.1e2e5515@sybil.lepiller.eu> <20190917194415.ripfxwfmpx337z4d@pelzflorian.localdomain> <87woe5disi.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <87woe5disi.fsf@gnu.org> 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 37413@debbugs.gnu.org On Wed, Sep 18, 2019 at 12:02:05PM +0200, Ludovic Courtès wrote: > Ah OK. Having an optional add-on process to work with PO files would be > nice too have. My concerns were about having PO files at the core of > the news mechanism. > > If you’re fine with the news format as it is in this patch series, then > I guess we can go ahead and push the patches? > Yes. > My feeling is that this use case doesn’t correspond to what the TP is > about, but yeah, you could ask them. > I will ask them, but later after Guix website translation is online. > Also, “urgently” won’t work because they would have to be manual > intervention by at least two people before the info reaches translators: > someone on the Guix side who’d submit a tarball (?) to the TP, and the The channel author would submit the tarball. No Guix team involved. > TP coordinator who’d notify translation teams. That’s another reason > why I’m skeptical about the applicability of this workflow for news. > […] On Wed, Sep 18, 2019 at 11:12:31AM +0200, Ludovic Courtès wrote: > > [pelzflorian wrote:] > >> I do not know what Benno thinks about this. I would prefer this to be > >> handled by some Translation Project eventually. > > You mean by some external project focused on translation, not > necessarily by the Translation Project, right? > Yes, but I still prefer the Translation Project to be where translators gather. Regards, Florian