Steve Langasek vorlon@dodds.net wrote:
Under the LGPL, everyone /will/ contribute back, because that's what the LGPL requires.
If you are using marketing speak for "contribute". GPL requires 1) for you to show your work 2) You effectively license your software to the FSF. It doesn't say it has to be in any useful form to be worked back into the originating project (if any).
Under the LGPL, it's not for them (or for you) to decide whether they have anything to contribute back; if they make modifications, they must be shared openly. And you're right that some people don't want to contribute back. That's precisely WHY we would consider relicensing under the LGPL. If everyone shared of their own free will, why would we need a license that said they had to share? The question at hand is whether or not we want to allow others to benefit from Wine without sharing their changes.
Here we go again.... If this is *all* it did, LGPL is far less objectionable. The problem with *GPL is that it also regulates the UNMODIFIED use of the software.
I make no bones about the fact that I'm a staunch believer in copyleft. If Free Software has value, then there's also value in keeping it Free.
Freedom means allowing people to do things, even things that you don't agree with. BSD = Free. GPL is not. Call a spade a spade....
As for commercial interest, I see that Apache+modssl has done quite well against any closed-source versions.
I would argue that this is a different ballgame. In the web serving field, There's More Than One Way To Do It,
there shouldn't be... http and ssl are 'well' defined protocols.
and trying to avoid forks leads to infrastructure issues as you need more and more management to make decisions and guide the project.
this is a project SIZE issue and has very little to do with the license.
In Wine, most of the decisions have already been made by Microsoft for us, it's simply a question of implementation; and most of that implementation is parallelizable to a high degree.
and what gives you this impression about wine? Seems that many of the subsystems are interconnected (look at the recent thread on dll mapping). Can't imagine that DX support wouldn't impact anything else.
Having a license that allows commercial offshoots of a webserver lets companies come up with innovative new designs that wouldn't have been incorporated into the main tree. Having a license that allows commercial offshoots of Wine potentially leads to a bunch of different Windows emulators, each of which is 98% complete and none of which works with half the software people want it to.
If it works 100% with the 1-3 pieces of software a user needs it for, the user certainly wouldn't care. The question is whether the alternative would be better or not.....
I'm sure that under a BSD-style license, Wine could continue to outcompete any commercial offshoots. The question is, which license model gives us the best chance of competing with *Microsoft*, who already has the lead?
If this is the goal (it certainly is mine), then *GPL is not a good choice, because it would interfere with deployment (*GPL wouldn't allow being bundled with the playstation2 or other HW platforms as an example). If acceptance is the goal and you care about wine in a non-linux context, stay with BSD/X11. If you don't care about expanding the pie, go *GPL....
-r
On Thu, Feb 07, 2002 at 05:45:36PM -0500, Roger Fujii wrote:
Steve Langasek vorlon@dodds.net wrote:
Under the LGPL, everyone /will/ contribute back, because that's what the LGPL requires.
If you are using marketing speak for "contribute". GPL requires 1) for you to show your work 2) You effectively license your software to the FSF. It doesn't say it has to be in any useful form to be worked back into the originating project (if any).
We're talking about the LGPL, not the GPL. The rest of this paragraph shows a serious disconnect with the text of the LGPL. Have you actually read the license in question?
"Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library.
Under the LGPL, it's not for them (or for you) to decide whether they have anything to contribute back; if they make modifications, they must be shared openly. And you're right that some people don't want to contribute back. That's precisely WHY we would consider relicensing under the LGPL. If everyone shared of their own free will, why would we need a license that said they had to share? The question at hand is whether or not we want to allow others to benefit from Wine without sharing their changes.
Here we go again.... If this is *all* it did, LGPL is far less objectionable. The problem with *GPL is that it also regulates the UNMODIFIED use of the software.
The creation of derived works does not constitute "unmodified use of the software" under any legal definition I've ever seen, if that's what you're referring to.
I make no bones about the fact that I'm a staunch believer in copyleft. If Free Software has value, then there's also value in keeping it Free.
Freedom means allowing people to do things, even things that you don't agree with. BSD = Free. GPL is not. Call a spade a spade....
Nonsense. To extend your definition to the proper conclusion, it's not Free unless it's placed in the public domain, and any software license that permits you to maintain any portion of your copyright is a fraud if it claims to be Free. If you really cared about giving absolute freedom to the users of code that you write, you would place all of your code in the public domain.
Not planning to do that any time soon? Then spare us the bullshit arguments about the BSD being Free and the GPL not. (Yes, it is bullshit. Call a spade a spade, right?) All Free Software licenses attempt to find an equitable balance between the freedoms and rights of the authors, and the freedoms and rights of the users. You are free to favor one balance point over the others, but that doesn't make other licenses and other balance points non-free.
But neither philosophy nor politics is the issue at hand. The issue at hand is whether the LGPL, or a similar license, would be better or worse for growing the Wine community. For that, there are good arguments on both sides. It's true that the current business model of TransGaming is not compatible with the LGPL, and that's a point that weighs heavily on me, because they truly are being good Wine citizens in their fashion; as a result, I'm very interested in hearing the results of Gavriel's ponderings on the license subject.
On the other side, companies like Lindows.com don't impress me as bringing any added value back to the community -- they may succeed in increasing the percentage of non-Windows desktops in the world, but the current Wine license makes it possible for all the profits from their OS to pad the wallets of marketroids, sales critters and smooth-talking business execs, without contributing anything back to the Wine tree. I have no problem at all with the idea of eliminating that particular business model.
I'm sure that under a BSD-style license, Wine could continue to outcompete any commercial offshoots. The question is, which license model gives us the best chance of competing with *Microsoft*, who already has the lead?
If this is the goal (it certainly is mine), then *GPL is not a good choice, because it would interfere with deployment (*GPL wouldn't allow being bundled with the playstation2 or other HW platforms as an example). If acceptance is the goal and you care about wine in a non-linux context, stay with BSD/X11. If you don't care about expanding the pie, go *GPL....
Please write what you mean, which seems to be "Sony would never accept the terms of the LGPL, which would prevent them from being able to bundle Wine with the PlayStation2". Again, I don't see where this would be a loss. Companies that are unwilling to contribute back to the community are not any concern of mine; if they want to compete with Microsoft on the desktop, let them fund their own software development instead of leeching off of the community. My only concern with the LGPL is making sure that well-intentioned companies that DO give back to the community aren't caught in the middle.
Steve Langasek postmodern programmer
Hi,
On Thu, Feb 07, 2002 at 05:45:36PM -0500, Roger Fujii wrote:
Steve Langasek vorlon@dodds.net wrote:
Under the LGPL, everyone /will/ contribute back, because that's what the LGPL requires.
If you are using marketing speak for "contribute". GPL requires 1) for you to show your work 2) You effectively license your software to the FSF. It doesn't say it has to be in any useful form to be worked back into the originating project (if any).
License is not equal Copyright.
You don't automatically sign away your Copyright when switching to the GPL.
Freedom means allowing people to do things, even things that you don't agree with. BSD = Free. GPL is not. Call a spade a spade....
Quoting: When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things.
The problem is not other people doing things with my stuff, the problem is restricting ME as a developer.
Ciao, Marcus
Roger Fujii wrote:
Freedom means allowing people to do things, even things that you don't agree with. BSD = Free. GPL is not. Call a spade a spade....
If this freedom means that I contribute my private time for developing on wine and then some companies are going to rip it off then I don't like the idea of being too free. I want to work on wine because I think it is a good project and many people are interested in because it allows you to continue to use your old software. I have quite a bunch of games I can't really play anymore because they are to old by now and I like to play them again. I'm willing to do my share for that but I don't intend to help big companies earning money without getting anything back. If a company makes money and contributes to wine as a payback, then that's ok for me. If a company makes money and keeps everything for itself (like one of my previous employees did), then I don't like to be part of it. This would mean that we are contributing valuable time and are always getting more and more behind because the number of poeple and the time we can afford is rather small in comparison to the changes that are coming up.
If this is the goal (it certainly is mine), then *GPL is not a good choice, because it would interfere with deployment (*GPL wouldn't allow being bundled with the playstation2 or other HW platforms as an example). If acceptance is the goal and you care about wine in a non-linux context, stay with BSD/X11. If you don't care about expanding the pie, go *GPL....
If wine makes the big market who is going to get the benefits?
-
Gerhard W. Gruber -
Marcus Meissner -
Roger Fujii -
Steve Langasek