From debbugs-submit-bounces@debbugs.gnu.org Sun Apr 18 13:25:17 2021 Received: (at 47104) by debbugs.gnu.org; 18 Apr 2021 17:25:17 +0000 Received: from localhost ([127.0.0.1]:47696 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lYBAa-0004aR-ON for submit@debbugs.gnu.org; Sun, 18 Apr 2021 13:25:17 -0400 Received: from mx1.dismail.de ([78.46.223.134]:23311) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lYBAZ-0004Zz-0v for 47104@debbugs.gnu.org; Sun, 18 Apr 2021 13:25:16 -0400 Received: from mx1.dismail.de (localhost [127.0.0.1]) by mx1.dismail.de (OpenSMTPD) with ESMTP id ff014eab; Sun, 18 Apr 2021 19:25:08 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=dismail.de; h= mime-version:date:content-type:content-transfer-encoding:from :message-id:subject:to:cc; s=20190914; bh=YMT2mgUXPK2GhvMHRQyBB8 wO+3tD4Y/4kD6yi3NnHb4=; b=cqbokQt2o8xFLJY7VXL3v3cvRHBqsdn/8Yd5XI GJ/vSn2T8RyDrOsQ0Gif0lZnH3g3uIpSPpkaz2ClURyP6CQfTxJCsKxRois7QGeN EvwBHe7IoazY/4yQeE1weiQRgryAXo+qCLPNNCr/+0wJMTVk/IJ9cHeqWBZKINF2 tVwpuB4ZBLgxr1A2aFEimOZ74iVqythvltn2o/wYOFycvn6ivQYuBrXa6+Xipf4H GybJlVLJpXD0zWtvoAsIpnOOKJLpdjOA6knTPRRJXAM/wlyawqFzuf99bUwq1bXY Y9t+uJLhICRsZRQwFyGyZTt6GMz/zMQgwl1k6Pnmjm2Js64w== Received: from smtp1.dismail.de ( [10.240.26.11]) by mx1.dismail.de (OpenSMTPD) with ESMTP id a203964c; Sun, 18 Apr 2021 19:25:07 +0200 (CEST) Received: from smtp1.dismail.de (localhost [127.0.0.1]) by smtp1.dismail.de (OpenSMTPD) with ESMTP id 4145e19b; Sun, 18 Apr 2021 19:25:07 +0200 (CEST) Received: by dismail.de (OpenSMTPD) with ESMTPSA id 16d0e11e (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Sun, 18 Apr 2021 19:25:06 +0200 (CEST) MIME-Version: 1.0 Date: Sun, 18 Apr 2021 17:25:06 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: RainLoop/1.14.0a From: "jgart" Message-ID: Subject: grumble status update To: 47104@debbugs.gnu.org X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 47104 Cc: raghavgururajan@disroot.org, Raghav Gururajan X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) Hi Leo,=0A=0A> I know you mean this somewhat jokingly, but is there anyth= ing (apart=0A> maybe from the name of the binary), that would keep you fr= om reusing=0A> murmur-service-type?=0A=0ASee here: =0A=0Ahttps://github.c= om/mumble-voip/grumble/issues/21=0Ahttps://github.com/mumble-voip/grumble= /pull/26=0A=0AThere are more sources related to the grumble config that's= currently implemented that I can't locate at the moment. =0A=0AI remembe= r reading that they didn't necessarily want to maintain feature parity wi= th the grumble config format.=0A=0A> 1. Is this package in its current st= ate usable?=0A=0AI would say yes. We packaged grumble while talking over = grumble. It feels pretty solid. =0A=0AGrumble also has an active fork as = a library and being used by wahay: https://wahay.org/=0A=0AIt is currentl= y 16 commits ahead of upstream:=0A=0Ahttps://github.com/digitalautonomy/g= rumble=0A=0A> 2. Is it still maintained upstream? It is a little stretch= to say=0A> Grumble is undergoing active development after a year of no a= ctivity. =0A=0AIt sounds like the project maintainers of the upstream gru= mble project are very slow to review pull requests. It sounds like they a= re too busy with other projects/work.=0A=0ASee the complaint here by one = of the contributors that chimed in when I opened an issue:=0A=0Ahttps://g= ithub.com/mumble-voip/grumble/issues/76=0A=0A> 3. https://github.com/mumb= le-voip/grumble#project-statuslists quite a=0A> few features that are lac= king, but does it maybe contain features, that=0A> would make it worth pa= ckaging?=0A=0ASee https://github.com/mumble-voip/grumble/issues/76=0A=0A"= ... Grumble has the distinguishing feature of native support for Websocke= ts (because I was a lot worse at C++ back then and so I contributed a pat= ch here instead), and Murmur will probably not have that for the foreseea= ble future. You could of course just configure a proxy in front of Murmur= if you need this. A lot of the plans for work we were making a few years= ago pointed towards Grumble being more focused on ease-of-use and these = small workloads I talked about above. It makes sense: the Murmur static b= inary has issues and so a Grumble static (just how Go works) binary that = you can download and run, trivially configure and easily negotiate certs = over LE (unfortunately never happened due to LE issues, but it would be v= iable now), accessible over the Web could fulfil a sort of "batteries-inc= luded" user-friendly niche."=0A=0A> If the answer is "no" to any of the a= bove, I'm not too sure whether it=0A> would be wise to have this in Guix = upstream. If LibreMiami wanted to=0A> host grumble instances on Guix reg= ardless, perhaps a channel might be a=0A> better fit?=0A=0AWe can put thi= s in a LibreMiami channel with a service for it if you insist it not be i= ncluded in upstream guix. =0A=0AIf upstream grumble picks up development = then I can send a patch again for review.=0A=0AThat said, can you take th= e patch for go-github-com-gorilla-websocket?=0A=0AWe will need go-github-= com-gorilla-websocket for many other packages that we're working on. One = of them being the hugo static site generator that we're working on with R= yan Prior.=0A=0ARelatedly, we're planning on packaging wahay (https://wah= ay.org/). =0A=0Awahay depends on the fork of grumble that I linked above.= =0A=0AShould we package only the fork of grumble in that case and not up= stream grumble?=0A=0Aall the best,=0A=0Ajgart