Project Reality Forums

Since PR Mumble is a fork of a GPL product, the source code must be made available. I would like a copy of the PR Mumble source code. Where can I get it?

http://sourceforge.net/projects/mumble/files/

install it there

I believe that is it

Sp1d3rX wrote:Since PR Mumble is a fork of a GPL product, the source code must be made available. I would like a copy of the PR Mumble source code. Where can I get it?

I think contacting the DEV's would be better.
Also it is upto the maker of the program wether to realese his own code?

killonsight95 wrote:Also it is upto the maker of the program wether to realese his own code?

Not if the original program is released under an open source licence that requires any modified versions to also be released openly. Which I think Mumble is with the GPL license.

Zrix wrote:Not if the original program is released under an open source licence that requires any modified versions to also be released openly. Which I think Mumble is with the GPL license.

However isn't PR still being beta tested and therefore still private?

Mumble is licensed under "New BSD license" -> Wikipedia is ur friend.
So PR Mumble source code needn't made public unless it is stated in the copyright of Mumble Vanilla.

I have no idea of such things, I'm sure someone who does will be along in due course. I was just wondering why you wanted it?

Murmur and Mumble is BSD and GPL licensed, which means that much like the Linux kernel, you are free to use it in commercial hosting without royalties. You are selling a service, not a program.

If you want to repackage and rebrand the client without also distributing its source code, the Mumble source code is BSD licensed, which allows you to do this.You will also need commercial licenses for the packages Mumble uses, namely Qt and Ice, as well as a patent license for OCB. The owners of these packages and patents have all kindly granted Mumble a license, but that only covers open source distribution. Note that if you just use our binaries from sourceforge, you don't need to worry about any of this.

Its a grey area. Theoretically yes we would need to either release the source or buy commercial licenses to Qt and Ice. Neither of which is a huge expense, but maybe a bit steep for a private individual making no profit from their work. However those companies are mainly interested in stopping unlicensed commercial exploitation of their material and would unlikely be that bothered with what we are doing. Also their licenses pertain to the use and alteration of their material and as its Mumble and not us that is doing that its questionable whether we have to release our code (if Mumble was more data driven we would not even need to touch the source).

The main reason the source is not available is that there are things in there which would allow people to recompile their own versions of the PRMumble and hence cheat by altering the settings. I think thats a reasonable enough reason to keep stuff private. Their has been a request to Thorvald to include some way of binding a derived version of mumble to a derived server, or to set settings on the client from the server ... but I am not involved with the mumble coding anymore so I don't know if thats in the active branch yet.


Its a shame about the GPL basis of Mumble, as it means its going to have to be dropped from all future PR projects.

[R-DEV]Twisted Helix wrote: Its a shame about the GPL basis of Mumble, as it means its going to have to be dropped from all future PR projects.

Sorry for my stupid question, but why? I dont understand, why an open source license would be a problem?

Due to the extremely minimal restrictions of BSD-style licenses, software released under such licenses can be freely modified and used in proprietary (i.e., commercial) software for which the source code is kept secret.

BSD license definition
Alltought it's stated not to be legally binding material I hope it's valid.

NVM, indeed gray with qt and ice on mumble backend.

[R-DEV]Twisted Helix wrote:... (if Mumble was more data driven we would not even need to touch the source)...

How hard is it to make mumble data driven? And then release that package as GPL.

hotty wrote:Sorry for my stupid question, but why? I dont understand, why an open source license would be a problem?

Its not the Open Source, its the GPL basis.

GPL just places far to many restrictions on developers using it.

MIT or BSD licenses are far more suitable for open source projects that want their software to be used and adapted.

The way GPL perpetuates to derivative works is quite unacceptable.

As a programmer who deals with this stuff for my day job (USA license compliance among other things) GPL is a huge PITA and usually not worth it. If you distribute software that uses something that is GPL your software too must conform to GPL (distribute the source). This is why as stated before that GPL is really only suitable for those who have business models that don't distribute software (a common example would be companies that sell software as a service from a web host).

What is usually done to get around the BS that is GPL is usually:

• Don't use GPL
• Modify the GPL code such that you can make an entirely separate module that plugs into your modified GPL code that is NOT part of the GPL project (you still have to distribute the source of your GPL modified project), keeping your changes under what ever license you like.

As far as companies not coming after you even though you are violating the license because you are "independent", "not trying to make money" or "the little guy" you could be in for a rude wakeup. Companies that have license on these sorts of things are required to protect it in all instances that they are aware of or the license might not be enforceable when it matters. It's very similar to copyright law. Now I'm not a lawyer, but I work with lawyers on this stuff and it's easy to get burned.

Consider the second approach in the list above to avoid GPL hell.

I don't see the issue with releasing the source. Sure, I suppose some hackers could write an overlay which would pinpoint on screen where a mumble voice was coming from, then just join the enemy mumble channel, and you'd have dots of where the enemies are. Of course, I doubt you'd get the height correct.

I'd rather use the normal mumble client, but I guess the normal mumble client doesn't have support for the 'squad leader radio' option. However, it looks like the regular mumble client can also do it, though the shortcut would need to be configured for each server...
Mumble Setup - Whispering Across Squad Channels - For Official Squad Leaders

Sp1d3rX wrote:I don't see the issue with releasing the source. Sure, I suppose some hackers could write an overlay which would pinpoint on screen where a mumble voice was coming from, then just join the enemy mumble channel, and you'd have dots of where the enemies are. Of course, I doubt you'd get the height correct.

Which is why they wouldn't realese it. Also you have yet to state why you want it, also if you don't know how to use original mumble then you don't need the source code. Seriously even i knew mumble had force center.

Sp1d3rX wrote:I don't see the issue with releasing the source. Sure, I suppose some hackers could write an overlay which would pinpoint on screen where a mumble voice was coming from, then just join the enemy mumble channel, and you'd have dots of where the enemies are. Of course, I doubt you'd get the height correct.

I'd rather use the normal mumble client, but I guess the normal mumble client doesn't have support for the 'squad leader radio' option. However, it looks like the regular mumble client can also do it, though the shortcut would need to be configured for each server...
Mumble Setup - Whispering Across Squad Channels - For Official Squad Leaders

................

That seems oddly specific... o.O

killonsight95 wrote:Which is why they wouldn't realese it. Also you have yet to state why you want it, also if you don't know how to use original mumble then you don't need the source code. Seriously even i knew mumble had force center.

I would like the source code so I can upgrade to the latest mumble with the latest speex codec, which is superior to the 0.50 version. I'd just need to merge the code changes. Programming is my day job.

LithiumFox wrote:................

That seems oddly specific... o.O

well, i can't imagine any other kind of hack that would benefit you.

Sp1d3rX wrote:well, i can't imagine any other kind of hack that would benefit you.

I can't imagine any other reason to need the source code other than to hack it to benefit yourself.