| |||||||||||
Lack of developers delays OpenOffice.org (ComputerWorld)Lack of developers delays OpenOffice.org (ComputerWorld)Posted Apr 20, 2005 0:11 UTC (Wed) by JoeBuck (subscriber, #2330)In reply to: Lack of developers delays OpenOffice.org (ComputerWorld) by jdave23 Parent article: Lack of developers delays OpenOffice.org (ComputerWorld) It's not just the Sun governance, it's also the assignment language. All contributions become the joint property of the contributor and Sun, and Sun is allowed to use all contributions in their proprietary StarOffice, but no one else has similar rights. Under these conditions, it's still advantageous for OpenOffice users to contribute bug fixes to Sun, but I can see why IBM might have reservations about putting large numbers of people onto developing proprietary code for Sun.
(Log in to post comments)
Lack of developers delays OpenOffice.org (ComputerWorld) Posted Apr 20, 2005 0:14 UTC (Wed) by beoba (guest, #16942) [Link] Does, say, Abiword have similar terms for their product(s)?
Lack of developers delays OpenOffice.org (ComputerWorld) Posted Apr 20, 2005 0:24 UTC (Wed) by JoeBuck (subscriber, #2330) [Link] I don't know about AbiWord. The FSF also requires legal assignment. The distinction, though, is that the FSF's standard assignment contract prevents the FSF from taking the code proprietary.Now, one nice thing about Sun's assignment terms is that, after it is executed, the contributor and Sun both retain copyright. With the FSF, the contributor signs over copyright, and is granted back rights to use the contributed work without restriction (including in a proprietary work), but that's weaker than remaining a joint owner. Please note that I'm not saying that Sun is wrong for choosing the terms that they did, it's just that these terms will tend to limit Sun's competitors' incentive to contribute.
Lack of developers delays OpenOffice.org (ComputerWorld) Posted Apr 20, 2005 1:48 UTC (Wed) by British (guest, #19768) [Link] The reason the FSF do that I understand is that only the copyright owner can take someone to court over infringment. So it makes it easy for them to do that.
I think Sun's remark was a cheap shot at IBM, how many opensource programs do Sun use that they do not contribute to?
Lack of developers delays OpenOffice.org (ComputerWorld) Posted Apr 20, 2005 12:35 UTC (Wed) by forthy (guest, #1525) [Link] With the FSF, the contributor signs over copyright Nope. With the FSF, the contributor still retains all original author's rights. Since the FSF also promises not to exercise the "take it proprietary" right it would have from a copyright assignment, the only one who can dual-license the product is the author(s).
Lack of developers delays OpenOffice.org (ComputerWorld) Posted Apr 20, 2005 13:08 UTC (Wed) by nathan (subscriber, #3559) [Link] With the FSF you sign a 'copyright assignment' thereby giving the FSF the copyright on the work -- for the reasons mentioned above about being able to sue.
The nice thing about the GPL is it protects you, the author, from the FSF going nuts. They could decide to relicense it under some other licence (they are the copyright owner, so can do that). In the insanely unlikely event they did so under a non-GPL like license, you still have access to the work under the GPL license anyway -- because unlike certain other licenses it can't be retroactively terminated.
Lack of developers delays OpenOffice.org (ComputerWorld) Posted Apr 20, 2005 14:12 UTC (Wed) by Ross (subscriber, #4065) [Link] You are both wrong. The assignment is a contract, of course. The copyrightdoes go to the FSF, but the FSF licenses back all of the original rights so you can still use your work in a proprietary work or whatever. However the contract forbids the FSF from releasing the work under a non-GPL license so you don't have to worry about them turning into a company or something. And, as you said, you always have access to the work based on any license you distributed it with before the assignment of copyright.
Lack of developers delays OpenOffice.org (ComputerWorld) Posted Apr 20, 2005 20:26 UTC (Wed) by hmmm (guest, #28931) [Link] Its the stupid, stupid.
This is on a per application basis. Something like GCC expects you to sign over copyright for any contributions you want included into their distribution. You can always take their code, add you modifications, keep your copyright and distribute it without any problems, but if you want your code to make it into GCC 4.0 you need to sign over copyright so they can legally enforce the GPL on their software.
The FSF does not do this. The copyright owners do this. The same thing happens for the Linux kernel.
Lack of developers delays OpenOffice.org (ComputerWorld) Posted Apr 21, 2005 0:49 UTC (Thu) by Ross (subscriber, #4065) [Link] The FSF certainly does do this. Or, if you prefer, the GNU project does.All non-trivial changes require copyright assignment to the FSF in order to be incorporated into the FSF-distributed version. Of course you an fork, as that is your right under the GPL; that has nothing to do with who holds the copyright.
Joint ownership of copyright is a problem Posted Apr 20, 2005 12:41 UTC (Wed) by utoddl (subscriber, #1232) [Link] Now, one nice thing about Sun's assignment terms is that, after it is executed, the contributor and Sun both retain copyright.So Sun says Joe Thirdparty can't use the code you wrote, and you say he can. This puts you and Sun at legal odds, and suddenly the "nice thing" is not so nice anymore. In fact, it's just as if it belongs only to Sun 'cause they have more legal resources than JoeBuck has to draw on. Clear transfer to the FSF, without waffling about whether the code becomes proprietary later, is for most people a much better way to ensure the code stays Free. Go ahead, ask IBM why they don't contribute to OOo. The answer pretty much pulls the rug out from under Sun's open governance ruse. Please note that I'm not saying that Sun is wrong for choosing the terms that they did, it's just that these terms will tend to limit Sun's competitors' incentive to contribute. It also limits Sun's customers' incentive to contribute.
Joint ownership of copyright is a problem Posted Apr 20, 2005 14:13 UTC (Wed) by jamesh (subscriber, #1159) [Link] > So Sun says Joe Thirdparty can't use the code you wrote, and you say> he can. This puts you and Sun at legal odds, and suddenly the "nice > thing" is not so nice anymore. In fact, it's just as if it belongs > only to Sun 'cause they have more legal resources than JoeBuck has to > draw on.
With joint copyright holders, either party can license the work without the consent of the other party. So if you give a license to Joe Thirdparty, Sun can't take them to court.
Of course, this would only apply to your own code -- not other people's contributions. It does put Sun in the unique position of being able to license OpenOffice as a whole though, which is the idea of the copyright assignment (like it or not).
Lack of developers delays OpenOffice.org (ComputerWorld) Posted Apr 20, 2005 0:47 UTC (Wed) by flewellyn (subscriber, #5047) [Link] AbiWord is straight GPL, so, no.
Lack of developers delays OpenOffice.org (ComputerWorld) Posted Apr 20, 2005 3:23 UTC (Wed) by newren (subscriber, #5160) [Link] The license under which code that has already been written is not what is relevant to the current discussion. The discussion is about requirements placed on contributions to the product. OpenOffice and AbiWord are both available under the GPL (http://www.openoffice.org/license.html, http://www.abisource.com/), but have different requirements on how they accept contributions. Of course, under the GPL, you are free to fork either project. But if you want a patch you have written incorporated into their work, the process is different. AbiWord requires less work--basically just send in your patch and describe it to see if the other developers think it is useful (http://www.abisource.com/developers/). With OpenOffice, you need to submit a copyright assignment form (making your contribution the property of Sun) in addition to getting the patch approved (http://www.openoffice.org/license.html). OpenOffice is not unique in this regard; gcc also wants copyright assignment to the FSF (http://gcc.gnu.org/contribute.html#legal) though they say that a "disclaimer" is sufficient, Evolution requires copyright assignment to Novell (http://forge.novell.com/modules/xoopsfaq/?cat_id=30%23q60...), and there are other examples as well...
The requirement of copyright assignment has various advantages and disadvantages. It makes it much easier legally to defend the software if copyrights are held by a single owner in case anyone tries to use the code without authorization (e.g. putting the code into some proprietary product; see, for example, http://forge.novell.com/modules/xoopsfaq/?cat_id=30%23q60..., http://www.gnu.org/prep/maintain/maintain.html#Copyright-...). But, it also discourages some contributors who don't like the hassle of paperwork or don't like the idea of giving up ownership of what they have worked to create (http://www.xemacs.org/Architecting-XEmacs/xemacs-tour.html, http://mail.gnome.org/archives/foundation-list/2004-Augus...).
It's a mixed bag, you'll have to come to your own conclusions about it.
Incorrect Posted Apr 20, 2005 3:58 UTC (Wed) by JoeBuck (subscriber, #2330) [Link] The FSF requires actual assignment in addition to a disclaimer from the employer. The reason is not just so that the FSF can enforce the copyright in court, it is also so that the FSF itself does not get sued later by some employer who claims that their employee had no right to contribute code and that the company owns the code (most working programmers in the US sign employment agreements that assign the copyright to all code they produce to their employer, some even claim that the employer owns every idea the employee comes up with that vaguely relates to the job).
Incorrect Posted Apr 20, 2005 4:37 UTC (Wed) by newren (subscriber, #5160) [Link] If I was incorrect, then the gcc site which explains how to contribute to gcc (http://gcc.gnu.org/contribute.html#legal)--and which I linked to to back up what I said--is wrong. That URL states that "If a contributor is reluctant to sign a copyright assignment for a large change, a disclaimer is acceptable as well. However, a copyright assignment is more convenient if a contributor plans to make several separate contributions."
However, digging further, it turns out that what you claim does match what is said at http://www.gnu.org/prep/maintain/maintain.html#Copyright-..., which states that "Before incorporating significant changes, make sure that the person who wrote the changes has signed copyright papers and that the Free Software Foundation has received and signed them. We may also need a disclaimer from the person's employer."
So, it looks like the general gnu maintainer guidelines conflict with the information on the gcc site.... odd.
Incorrect Posted Apr 20, 2005 14:43 UTC (Wed) by jamesh (subscriber, #1159) [Link] The copyright disclaimer form does provide similar legal protection to the FSF as a copyright assignment form. The main difference is that code covered by a disclaimer is essentially public domain, so the FSF can't bring a GPL violation case with respect to that code.
Incorrect -- again Posted Apr 21, 2005 0:53 UTC (Thu) by Ross (subscriber, #4065) [Link] You misunderstand. There are two types of copyright disclaimers beingdiscussed. One is disclaiming copyright interest by directly putting a work into the public domain. The other is getting a sign-off from employers and schools that they do not claim ownership of a contribution by one of their employees or students. This does not mean the employee or student wishes to place the work in the public domain. It simply means that if they assign the copyright to the FSF that it would be a legitimate act and that the employer or school can't come along later and say they are the "real" owner and didn't consent to the copyright assignment.
Forking instead of patch submission Posted Apr 20, 2005 15:24 UTC (Wed) by JLCdjinn (subscriber, #1905) [Link] Thank you for that analysis; it helped me to understand the situation better. I have a follow-up question. Let's consider one of the projects that requires copyright assignment in some form, but which is licensed under the GPL. What happens if you fork this project and then later the original project wants to merge some of your work (each action being allowed by the terms of the GPL, as far as I understand)? Does such a project refuse to cherry-pick from good forks because of a lack of copyright assignment? If they do take code from your fork, is it true that you (the creator of the fork) still hold the copyright to any modifications in the fork? If so, doesn't this circumvent the patch submitting rules?
Forking instead of patch submission Posted Apr 20, 2005 15:57 UTC (Wed) by newren (subscriber, #5160) [Link] Patch submission rules aren't legal requirements; they're practice that a project has decided upon. They can decide to change their practices. It's just that they need to weigh the consequences--if they take patches without a copyright assignment then they are no longer the sole copyright owners and thus legal cases to defend against copyright infringement of the code becomes more difficult.
In fact, there's a real world example of the exact situation you propose--emacs and xemacs. According to http://www.xemacs.org/About/XEmacsVsGNUemacs.html, RMS has stated, "we can't use XEmacs in the GNU system: using it would mean paying a price in terms of our ability to enforce the GPL....There is good code in XEmacs, which I'd be happy to have in a merged Emacs any day. But I cannot copy it out of XEmacs myself because of the uncertain authorship and/or lack of legal papers."
Lack of developers delays OpenOffice.org (ComputerWorld) Posted Apr 20, 2005 16:56 UTC (Wed) by AJWM (subscriber, #15888) [Link] The assignment language also prevents OpenOffice.org developers from incorporating code from other GPL projects, GPL'd libraries, etc, unless they can track down and get assignment from the authors of same. You won't see a Qt-based version of OOo anytime soon, for example, because of the licensing issue. (Aside from whatever horror would be involved in ripping out the GUI and replacing it with another -- rarely a trivial undertaking.)
That leads to countless re-invented wheels and a yet-steeper learning curve for any would-be developer. It's missing one of the key advantages of releasing it GPL-only, namely being able to take advantage of the existing GPL codebase and developers' expertise in that.
It'd be interesting to see how quickly a GPL-only fork (FreeOffice?) would outpace Star/OpenOffice, if that were ever to happen.
|
|||||||||||