I want to give grumble (and therefore mumble) the 2016 treatment

[mumble-voip]

I want to give grumble (and therefore mumble) the 2016 treatment

[mkrautz]

Hi Jacob.

This is great. The general goals: API, Web UI, CLI UI, and an improved configuration system, and bridging Mumble to the web are all features we need.

Of the above, the ones I am interested in working on are getting the protocol bridged to the web. The first step would be to expose the Mumble protocol via websockets. See mumble-voip/mumble#2131.

I am not going to have much time to look at any of the other stuff, so if you're interested in hacking on it, please go ahead. I am happy to review any changes -- or, if you wish, I can make you the grumble maintainer and give you commit access. I don't know if you have the time to commit to it -- but if we could kickstart the development, it would be awesome.

It would be wonderful if we could ship everything from your list above in a single static binary, and easily build that static binary as well.

[faddat]

So, I'm going to have time in a couple of weeks. I'm doing dev work for two mumble users at the moment, and they want their pages to be more interactive in terms of the experience with their raido shows.

I should say-- I'm not all that familiar with the mumble-using gaming community, both of my clients run crypto/fintech related interactive radio programs. So, once I am done getting a couple of databases to eat a blockchain's blocks, I'll be able to dedicate some real time to improving grumble :). I'm curious: Any idea how to go about surveying users of grumble/mumble? I figure that getting user stories in place now can only help guide the dev process once I get rolling....

Edit:
Somewhat delayed but will still be progressing to this :).

PS: Code reviews sound super-helpful. I am a newer gopher, and your assistance in that dept would surely be appreciated.

[mkrautz]

If there is still interest, please ping this thread or me. For now, I'll close it. :-)