Search results

Oh, it's absolutely not a waste of time. Most of the FUD is due to ignorance, and ignorance is like kudzu - You have to keep fighting it or you'll drown in it. I myself was wrong a week ago. Now I know better, and I wish to help others know better too. If I thought this was a waste of time I'd...

I'm sure there will be several, all of which rehash the same old FUD from earlier in the thread.

Then I'll make it, for the I-don't-know-how-many-ith time: The GPL is OK for Orbiter addons. The only ways to create a legally actionable GPL violation in an Orbiter addon are to include code you don't have permission to include (which would get you into trouble regardless of the license) or to...

Nobody says this won't change later. Maybe NASSP or SSU will be what gets people's attention. Maybe Orbiter 2015. Maybe both of those. Maybe neither - Maybe it's something we haven't thought of yet that someone else is developing right now. As long as you don't scare off everyone who wants to...

You're not. I really didn't plan to spend 50 posts on why NASSP is the turbosatanhitler that is killing the Orbiter community.

Oh, that's not what I meant at all. I mean in terms of uniqueness. Some people like things that are obscure and unknown because it makes them feel superior to others that don't know about it. When new people arrive they are driven away to protect the obscurity of the thing and by extension the...

Why not? If Orbiter gets popular then people are learning, and that's what we need. KSP is nice because it gives people a taste of space, but it's just the first step - Orbiter should be the next step in the line. I feel it's immoral to scare people off just to preserve your individual feeling...

Like I said, he's deliberately trying to drive people away so Orbiter remains some private special thing that makes him special rather than a wider community. If Orbiter goes huge like KSP did, it won't be special anymore.

The problem here seems to be that people see the license as something that INCREASES liability. This is not the case. If someone uploads something they don't have the right to distribute, and OHM redistributes it, the uploader is liable and OHM is liable. Whatever license the uploader used is...

There's never a better solution than the BOFH approach.

Another thing - FSF's stance against dynamic linking is based on protection against threats to the Free Software community. Nothing I am doing presents such a threat. The interface I am using to communicate with Orbiter is published. There is nothing to prevent an enterprising group of Free...

The GPL doesn't have a termination clause that would permit the FSF to rescind it against me. I have to violate the license for it to be terminated. This makes the copyright holder's approval or disapproval even more irrelevant. If I am not violating the license, I am safe. Any attempt to sue me...

Well, if that's your criteria for danger, in the US at least anyone can sue you at any time for just about any reason. It doesn't mean they'll -win-, but they can still sue you. Avoiding GPL'd or FSF code because someone might file a lawsuit they're almost certain to lose is pointless. It's more...

This time with FOUR-PART HARMONY and feelin': If you take FSF code and put it into your GPL'd Orbiter Addon FSF can't sue you because you didn't violate the GPL. The linking that FSF objects to doesn't happen until the end-user installs your addon into Orbiter and the end-user doesn't...

Next time someone asks me why NASSP is taking so long I'm pointing them to this thread. Ninja Edit: Would that be cruel and unusual punishment?

Yes, but not the SOURCE. You can't BSD-license the addon source and distribute it because you can't grant the right to reuse the mesh and texture. You have to make your own license that preserves the restrictions given to you by your friends. Edit: To make things easy, here's two-clause BSD...

Doesn't matter. The license doesn't say so. They can't sue you unless they're the copyright holder you do something the license says you can't do it. The combining is being done by your users, and the combined result isn't being distributed. FSF has no standing to sue either party.

If you don't have the right to distribute the item beyond the binary distribution of your addon, then you can't open-source it under any common license at all. BSD,MIT,GPL,whatever. It does not matter. If it cannot be reused would have to make your own license that restricts usage of the source...

Yes. You just can't package OrbiterSound with your addon. (OrbiterSound's license doesn't allow this anyway) LGPL has no linking restrictions at all, but LGPL is GPL-incompatible. You cannot use GPL software in a LGPL project. (You can do the reverse. GPL projects can use LGPL software.)...

The reason the FSF opposes DLL linking of GPL and non-GPL code is because someone could then make a non-Free program that requires a mandatory Free "plugin" and therefore get around the restriction that you cannot GPL only parts of a program. No matter what, in no case can anyone sue you for...