Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- Date: Wed, 04 Jul 2007 11:46:33 +0900
- From: Darren Cook <darren@example.com>
- Subject: Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- References: <8572e260707012045p7483918fmd047b67a20f53943@mail.gmail.com> <d8fcc0800707012308m2d60dc2cof9e56c7b8a4a8b12@mail.gmail.com> <7d27112b0707020508l6d14f787q169af170ecb54f01@mail.gmail.com> <877ipizwg4.fsf@uwakimon.sk.tsukuba.ac.jp> <Pine.NEB.4.64.0707030304380.29360@homeric.cynic.net> <876452z250.fsf@uwakimon.sk.tsukuba.ac.jp> <468AED14.8030908@dcook.org> <E59CA5C5-59F9-40D5-9919-4737A507AC47@mx6.tiki.ne.jp>
- User-agent: Thunderbird 1.5.0.10 (X11/20070301)
> How do you convince developers that giving others the right to close the > code they took so much time to write is a benefit ? Because it attracts more users and developers, and the altruistic ones will outnumber the selfish ones. When I need a library for a client project typically I only consider MIT/BSD. If it is GPL I'll need to spend time clearing its use with my client's lawyers: quicker to write it myself. If it is commercial I'll need to get budget approved: quicker to write it myself. (Of course, large or complex libraries are a different matter; then there are hard decisions to be made.) > And I did not declare that use of "liberal-open-source-license code" was > stealing, it is closing the code and/or not contributing back that is > stealing. Most companies are more than happy to get their bug fixes and new features rolled back into open source projects: it is in their own best interest. They don't need the strong-arm of GPL to force them. Once a project is branched and only used internally all the benefits of open source are lost. But companies like to have that option. And so they avoid GPL. So GPL projects miss out on lots of developers and users, and instead the functionality of that project has to be re-invented. Darren
- Follow-Ups:
- Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- From: david.blomberg@example.com
- Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- From: Jean-Christophe Helary
- Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- From: Josh Glover
- References:
- [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- From: Pietro Zuco
- Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- From: Josh Glover
- Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- From: Dave Gutteridge
- Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- From: Stephen J. Turnbull
- Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- From: Curt Sampson
- Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- From: Stephen J. Turnbull
- Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- From: Darren Cook
- Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- From: Jean-Christophe Helary
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- Next by Date: Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- Previous by thread: Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- Next by thread: Re: [tlug] [OT] Say _no_ to the Microsoft Office format as an ISO standard
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links