starred/mumble-mumble-voip

Fork 0

mirror of https://github.com/mumble-voip/mumble.git synced 2026-03-03 00:46:56 -05:00

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

New issue

Open

opened 2026-02-20 22:17:23 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-20 22:17:23 -05:00

Owner

Originally created by @Krzmbrzl on GitHub (Oct 23, 2025).

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

Originally created by @Krzmbrzl on GitHub (Oct 23, 2025). ### 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 ```shell ``` ### Screenshots _No response_

deekerman added the

labels

2026-02-20 22:17:23 -05:00

deekerman commented

2026-02-20 22:17:24 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Oct 23, 2025):

I was aware of net.sourceforge.mumble.Mumble still being used in some places, but I never fixed that because I'm not convinced about the new domain.

info.mumble.Mumble is definitely better and also shorter to write, but info is kind of misleading. What about using software.mumble.Mumble since we also own the mumble.software domain?

@davidebeatrici commented on GitHub (Oct 23, 2025): I was aware of `net.sourceforge.mumble.Mumble` still being used in some places, but I never fixed that because I'm not convinced about the new domain. `info.mumble.Mumble` is definitely better and also shorter to write, but `info` is kind of misleading. What about using `software.mumble.Mumble` since we also own the `mumble.software` domain?

deekerman commented

2026-02-20 22:17:25 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Oct 23, 2025):

No, we should use the domain that we also use for our website. Anything else seems weird to me.

@Krzmbrzl commented on GitHub (Oct 23, 2025): No, we should use the domain that we also use for our website. Anything else seems weird to me.

deekerman commented

2026-02-20 22:17:25 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Oct 23, 2025):

That would be for consistency, but the .info TLD is kind of weird for a chat application...

@davidebeatrici commented on GitHub (Oct 23, 2025): That would be for consistency, but the `.info` TLD is kind of weird for a chat application...

deekerman commented

2026-02-20 22:17:25 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Oct 23, 2025):

I don't see anything weird with it 🤷

@Krzmbrzl commented on GitHub (Oct 23, 2025): I don't see anything weird with it :shrug:

deekerman commented

2026-02-20 22:17:25 -05:00

Author

Owner

@Praveenabi commented on GitHub (Jan 6, 2026):

Hi, I would like to contribute on this issue.

@Praveenabi commented on GitHub (Jan 6, 2026): Hi, I would like to contribute on this issue.

deekerman commented

2026-02-20 22:17:25 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Jan 7, 2026):

@Praveenabi that'd be great. By now, only the DBus interface remains and as written in the original post, we'll want to remain backwards compatible. Hence, the way to go with this would be to additionally provide the DBus interface on info.mumble.…

@Krzmbrzl commented on GitHub (Jan 7, 2026): @Praveenabi that'd be great. By now, only the DBus interface remains and as written in the original post, we'll want to remain backwards compatible. Hence, the way to go with this would be to additionally provide the DBus interface on `info.mumble.…`

deekerman referenced this issue

2026-02-20 22:17:58 -05:00

Question about Restricting Channel Visibility in Mumble #3092