Whopsie, box of pandora.
[quote=“dragonCASTjosh”]Just to clear things up about Clockwork and where it sits from Urho. Clockwork is my attempt to turn Urho into a commercial style engine with everything available through 1 editor. Despite the editor not being part of the repo yet it’s on the roadmap currently I want to improve the renderer to more modern standards, changes like the rendering that fit in with Urhos targets will get PR’s to the master. As for the website that was linked the information there is not correct, the web developer use placeholders and never finished. I do not intend to sell any part of the engine, although I have considered selling themed starter packs to build things like a Sci-Fi game, to be clear this does not mean example and tutorial projects. Any money I gain from the project will be put into Urho3D in some form, but I believe this is a long way off.
If there comes a point where the Urho developers want to streamline the workflow I am happy to drop Clockwork In order to merge all changes to the master and then focus my effort on Urho alone. When i first started I considered doing all my chances to Urho3D but believed it was to big of a change from the current engine goals.[/quote]
Ah, that makes things a lot clearer. That also explains why the licenses seemed so weird and contradictory (that I meant by “not getting the licenses”).
(My post was also meant quite general.)
There’s no “moral stealing” since permission was given, not just for any specific user but to everyone including you and me.
[/quote]
Yes, that’s why I wrote “moral stealing” not “stealing” or “copyright infringement”. I meant the thinking of “hey they are giving stuff away for free, lets make a profit out of it by reselling it!”. Some greedy companies take free software, put a new logo and name on it and sell it as if they made the whole thing on their own. (and again I meant that quite general and not specifically this case, which I don’t know that well and I already said that it doesn’t seem that unreasonable)
[quote=“Enhex”]
And don’t use GPL, it’s such a nasty “free as in complies with our totalitarian ideology”, a legal minefield with tons of restrictions.
I don’t think it’s possible to grow a professional game development community around Urho3D with GPL (It’s kinda hard to sell a game when you must make it available for free).
Not to mention that at that point developers will just go with other engines.
…
Also a license means nothing if you’re not going to enforce it. You’ll needs laywers and to spy on your users, do you really want to go down that route?
To sum up, if you’re doing an open source project just keep it simple and use MIT license and let the users do whatever they want.[/quote]
I didn’t say that I suggest putting Urho or something like it under a copyleft license, I was talking about general options regarding software. Also I agree with you, there are other engines who would “take it’s place”.
Saying that everyone should do MIT is pretty stupid though. There’s a reason for all the licenses (more or less, some are quite similar or even stupid). Not everyone wants to get sucked up into a proprietary product.
Commercial licenses are often a “totalitarian ideology” and a “legal minefield with tons of restrictions” and if you want to enforce those you need lawyers as well.
This is the whole copyleft debate which was discussed countless times. I mentioned that with the “Though copyleft too is often seen as contrary to “real free software” (BSD-, MIT- style license).” part.
I think I even released every software that I really released as MIT, so I’m not a “GPL fan” (nor generally against it). I see the motivation behind (L)GPL but also the problems and the difficulties (“minefield-ness”).
Should have made myself clearer. I was already thinking if it was clear that I’m talking in general, but I thought mentioning Copyleft, Apple and Microsoft made that clear (as those are clearly not related to this case).
I also didn’t want to suggest that Urho’s license should be changed (or that it shouldn’t), it was completely general talk.
My point was also about contribution from users back to the project, usual options and my “older” ideas about that.
[quote=“cadaver”]
The MIT was chosen way back with the full understanding that such scenarios would happen. Of the alternatives, technically speaking LGPL is nasty on platforms where you can’t reasonably allow the user to actually replace / update the library. Then there are other licenses such as EPL which to my understanding have the clause to give back contributions, but don’t have the static / dynamic linking hassle. But all in all I believe MIT is still the right choice for its simplicity and permissiveness, as I’d consider it a greater loss if someone could not use Urho in their scenario because of the license, compared to the risk of being commercially extended without contribution back. A person or team who decides to fork will always create more difficulty for themselves to follow the upstream development, as well as dividing the userbase in case we’re talking of the same set of users.[/quote]
Oh how well I know these thoughts.
All this stuff about dynamic and static linking and code in header files is really weird. A lot of the LGPL “minefield-ness” comes from such things. Especially with header only libraries, what is that? Licenses don’t really cover that and don’t explain such things in “developer terms”.
I think most people don’t want to be exploited by getting their work taken, barely modified, sold and others earning money with it. In regards of fairness, there should ideally be at least a more or less appropriate compensation/share. That was my point basically. Though it depends on the case, some projects are small enough that I just don’t care (or the developer in general may not care) what happens to them.