![]() | |
![]() |
| | Thread Tools | Display Modes |
#51
| |||
| |||
|
|
Healthpac Computer Systems has been with Pick Systems / Raining Data for 15 years, but we can no longer afford the user licensing fees at large installations. |
#52
| |||
| |||
|
|
Let's try to bring this to a close. We are beginning to go around in circles.... Mike Ryder summed it all up perfect when he wrote: 1. In order to run my programs I need QM - my programs, application, whatever are not independent. 2. If I sell my programs then my customer needs a commercial QM licence 3. If I am giving away the product and the source, I can use the GPL licence and thus the GPL licence QM There are two separate rules that affect what you can do: 1. The GPL sets out how the open source can be used and what you must do if you wish to distribute an application. The various postings that reference the difference between the GPL and LGPL are relevant to this. In our view, the open source is for the expert user who needs to modify the core components of QM to do something that we never envisaged. As one contributor observed, there is frequent confusion between "open source" and "free". The GPL explicitly draws this distinction and makes it clear that we are entitled to charge for the open source if we wish (something that has crossed our minds). 2. Our own software licence strictly bans moving applications between the open source and the commercial product. You are free to develop on the open source but must obtain a commercial licence before you distribute the application to users of the commercial product. A single user licence will do. Related to this, is a very important point that I made in a response yesterday. We give absolutely no guarantee about compatibility between the two versions of QM. Indeed, there are developments in the pipeline that will not appear in the open source and which may end up making the two incompatible at the compiled object code level even though they originate from a single source stream. One posting in this thread talked about the need for open source to allow self-fixing of bugs. We have received several comments about the speed of our response to support calls. It is highly likely that we could have a fix for a bug out before an open source user has even found where to look. The open source should not be looked on as a way to do your own maintenance. Finally, to put Tom Phillips' mind to rest, we have no interest in trying to grab copies of application developers' source code or interfere in any other way with their business. Commercial QM users purchase a licence in exactly the same way as from other vendors and then go about their business as usual. QM is sufficiently reliable that we never hear from most clients again unless we ask how they are getting on. And, remember that QM has no mandatory maintenance contracts so you are not paying for a support service that you hopefully never need. End of subject? Hopefully... Until this time next year, anyway. Martin Phillips, Ladybridge Systems |
#53
| |||
| |||
|
|
Hi Henry- You appear to be confusing the GPL with the LGPL. If the GCC compiler and libraries was GPL then every program compiled with them would be required to be GPL by definition. But as that compiler and libraries are released under the LGPL there is no such requirement. The difference here is that Martin has released OpenQM under the GPL not the LGPL which makes every program compiled under it a derivitive work. -Bob hbkeult... (AT) gmail (DOT) com> wrote in messagenews:1169127252.035794.64760 (AT) l53g2000cwa (DOT) googlegroups.com... Dale wrote: They also have an open source version but be very wary of the GPL agreement. Failure to comply could result in the requirement of your applications needing to be open source as well. While I am not a lawyer and presumably Dale is not either, the tie-in between applications and OpenQM that could lead to the requirement for having to Open Source applications is fictitious. The basic requirement is, for example, if this post's EMR provider decides to use OpenQM and makes modifications and/or additions to OpenQM that it then provides to its customers, for free or at a price, it has to post those modifications and/or additions to the OpenQM list. If Henry makes modifications and/or additions to OpenQM and uses those internally only, he has no requirement under the GPL to share that code. . The GPL is treacherous only because there are too many lawyers who absolutely don't understand the concept of Open Source and hence don't understand the contractual obligations of the GPL. Even Microsoft uses some GPL code and I have not seen any evidence of Wall Street dumping Microsoft stock because of the fear that its biggest money maker, it's Microsoft Office suite of applications, will be drawn in under the GPL. I go through the Free Software Foundationhttp://www.fsf.orgto get my advise. I strongly suggest that anyone who has questions about the GPL do likewise and also use their *state* bar association to find a lawyer who is competent in giving GPL advise. By making such a specific *written* request you give yourself a way to sue for incompetence if a lawyer mishandles your requirement, especially by advising against the GPL when there is no sound legal reason to do so and as a consequence your business is damaged because business opportunities are missed. Henry Keultjes Database Scientifics Projecthttp://www.ncolug.org/ppc.htm Mansfield Ohio USA Direct 419-525-1111 |
![]() |
| Thread Tools | |
| Display Modes | |
| |