mumble-iphoneos
mumble-iphoneos copied to clipboard
mumble-voip
Looking for new project maintainers
This project is looking for maintainers. If you are interested to give it a go, we would appreciate contributions and to further discuss maintenance.
As you can see this version for iOS was last updated in September 2017. The main developer is busy/inactive for now (see also: https://github.com/mumble-voip/mumble-www/issues/96#issuecomment-639209986 ), so maybe someone wants to take over the development of this app.
If you are interested, post a comment :slightly_smiling_face:.
@AToska21 Feel free to open pull requests or start discussions, outlining what you plan to do. You can also get into contact with the developers directly, see for example here: https://www.mumble.info/contribute/#getting-started
@Krzmbrzl Could you pin this issue maybe? Just a small idea. And could you maybe talk to @mkrautz ?; I know he does not have much time, but maybe he could give a little bit of information what probably needs to be done, where new devs should start etc.
Could you pin this issue maybe? Just a small idea.
What for? It's not like this issue gets lost in more recent reports.
I don't have any contact to mkrautz. So I can't really do much more than pinging him here as well :shrug:
@AToska21 That'd be much appreciated :+1:
What for? It's not like this issue gets lost in more recent reports.
I could also ask why not? It is the central topic for this repo imo.
I don't have any contact to mkrautz. So I can't really do much more than pinging him here as well :shrug:
I would assume that someone in the team has it.
The version number is confusing (1.3.1 in Appstore).
Confusing how?
I agree with Krzmbrzl. Pinning this ticket as it is doesn’t add much. If we want to clarify this project is up for adoption/seeking maintainers, we should do so more explicitly both in the README and pin a/this ticket with a more explicit title (like “Seeking maintainers”).
@AToska21 It would be great if you could work on this project, either one-off updates to make it work in current dev envs and end-user runtimes, or towards maintaining it.
The version number is confusing (1.3.1 in Appstore).
Confusing how?
It might misslead users into believing that version 1.3.1 is equal to the official version 1.3.1, while it is not.
I changed the title a bit, so maybe we could pin this now. If you can provide more useful information, that would be great too.
I could also take a look at maintaining this app.
I created an iOS App that also integrates MumbleKit (https://apps.apple.com/de/app/yourtalk-fm/id1171446553#?platform=iphone) so I understand the basic structure of the app. The thing is, that the app needs a lot of rewrite even to make it possible to publish an update. It would be more like re-starting than maintaining.
That would be great @vierzwei
Could you elaborate on what needs to be done and why? What are the big stepping stones/milestones?
If you are willing to commit setting up tickets and milestones, or a ticket with a todo list may be a good idea.
@AToska21 we have not heard back from you since your initial interest. Does that still stand? Are you able to commit some time? Do you have prior knowledge and an idea of what needs to be done too?
And could you maybe talk to @mkrautz ?; I know he does not have much time, but maybe he could give a little bit of information what probably needs to be done, where new devs should start etc.
This is very unlikely to happen. We are better off going on without waiting here.
Since we are still in the COVID-19 phase, and mumble appears to be one of the only working solutions to jam over the Internet, a development here would be much appreciated.
Especially if you want to use mumble, but theres no M1 support, so you use your smartphone, to also get Screenreader / VoiceOver support...
Since this repo looks like it's maintained once more it would be good to remove the part in the readme that references to his thread.
@davidebeatrici @Krzmbrzl @Kissaki Just an idea: maybe you could add a note about the search for new maintainers/team members on the website or at least also in the main repo, so more people see it :thinking:. Other projects such as the LibreOffice Team even showed a message in their app (even though that is maybe a bit too much).
I don't think a new maintainer is found by putting that on the website. Code contributors usually come if they have a personal interest in contributing and if they do they'll have a look at the source code at which point they will probably notice this issue.
I don't think a new maintainer is found by putting that on the website. Code contributors usually come if they have a personal interest in contributing and if they do they'll have a look at the source code at which point they will probably notice this issue.
Or just implement web-mumble with websockets and access through the browser... Its more of a pain though. Also you have to add some ARIA attributes for screenreader users etc.
I don't think a new maintainer is found by putting that on the website. Code contributors usually come if they have a personal interest in contributing and if they do they'll have a look at the source code at which point they will probably notice this issue.
I disagree. There are a lot of programmers out there and some of them will also use your software. How should they know that this project needs help? A Note is exactly what might get people's attention.
It would be very nice to see either a new Mumble app for iOS, or polish up the old one and maintain it. It is definitely quite dated, and missing a handful of features such as local volume adjustment according to some people. I was just talkikg with a friend and he was on iOS, honestly was surprised it went as smoothly as it did seeing the app has been unmaintained for so long.
Hello.
My Apple Developer Account expires in January.
Pinging this to see if anyone would like to take over the app. I can transfer the app to another Apple Developer account if so.
As mentioned, I don't have the time to maintain this, as is obvious by the lack of commits. But if anyone would like to take over, please let me know.
Hello! @mkrautz
My name is Carson, and I am a software developer and senior CS student. My friends and I use Mumble all of the time, and I am interested in taking over as a maintainer. I would like to modernize the app as well. I don’t have a ton of experience contributing to FOSS, but I am passionate about using it and would like to take this on.
@carsoncall thanks for stepping up! I would suggest you start by forking this repository and then contribute PRs. I will skim the first ones and if they seem reasonable I'll merge them and eventually give you direct write access to this repository.
Sounds good! Any suggestions on where to start? Is there a style guide etc for PRs? My buddy is a career Flutter dev, and the Android Mumble app is mostly unmaintained as well. Additionally, there already exists a Mumble client library in Dart (Dumble) that is only somewhat stale. We were thinking that, long term, this could be a good way to reduce maintenance costs for both platforms while also ensuring a consistent experience. What do you think?
Any suggestions on where to start?
I have literally zero knowledge of this app, so I'm afraid I can't help you there. But maybe some of the other users here could give an opinion on what's needed most direly.
Is there a style guide etc for PRs?
Not for this repo - we have one in the main Mumble repo. If you want, you can orient yourself by that but feel free to do whatever you see fit for this repo.
We were thinking that, long term, this could be a good way to reduce maintenance costs for both platforms while also ensuring a consistent experience. What do you think?
The idea of having a central implementation with multiple frontends is something that we think will be crucial long term. We have https://github.com/mumble-voip/libmumble and https://github.com/mumble-voip/libcrossaudio that we were planning on using for such a purpose. They are supposed to have a stable C API (eventually) so that bindings to other languages should be easy. If anyhow possible, I think it would be best if the mobile apps were using that same libraries under the hood. That way they would eventually share the same base implementations as the desktop client and server. Work on these libraries is still WIP though.
@carsoncall could you start by even just building+releasing a version of this for modern iOS targets?
The project still uses the "legacy build system" so it can't be built with XCode version 14. Upgrading the project to the new build system would be a great first task.
- 59b7b147b5dff67f003b8d28e8ede3452a1c0fe7
- https://github.com/mumble-voip/mumble-iphoneos/issues/131#issuecomment-1995615473