mumble-voip/mumble

Get rid of `net.sourceforge.mumble.Mumble` references

Open

#6963 opened on Oct 23, 2025

View on GitHub
 (9 comments) (0 reactions) (0 assignees)C++ (5,642 stars) (1,062 forks)batch import
bugclientgood first issueserverui

Description

Description

There are still a couple of places in which we use the old net.sourceforge.mumble.Mumble domain. This seems incorrect. Instead, it should be info.mumble.Mumble.

Steps to reproduce

See https://github.com/search?q=repo%3Amumble-voip%2Fmumble+sourceforge+language%3AC%2B%2B&type=code

Mumble version

No response

Mumble component

Both

OS

Linux

Reproducible?

Yes

Additional information

Especially for the DBus interface, one would have to check whether this affects donwstream users. I believe that it probably does as they use the domain as kind of a namespace. In this case, we should probably keep the old domain as-is but also provide an interface under the new domain. Maybe there even exists a way to deprecate the old namespace.

Relevant log output

Screenshots

No response

Contributor guide

Tech stack
cpp
Domain
backendapi
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
C++DBus basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Identify all occurrences of 'net.sourceforge.mumble.Mumble' in the codebase, particularly in DBus interface files. Assess whether changing them to 'info.mumble.Mumble' would break downstream users. Consider deprecating the old namespace while adding support for the new one. Review the search results linked in the issue and any maintainer comments for guidance.