--4zI0WCX1RcnW9Hbu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 24, 2001 at 09:20:04AM -0700, Shawn Gordon wrote: > Oh come on Thomas. I've talked about all this stuff repeatedly and usual= ly=20 > at the request of others for me to clarify it. We still want to have a= =20 > free (as in cost) light version of Rekall, but neither one has anything t= o=20 > do with KOffice as they are Qt based applications. It's just going to ta= ke=20 > us a while to finish the full version and then partition out the lite=20 > version. >=20 > We've been talking about this license for months and months, and it's the= =20 > license that has been in Rekall since the beginning I believe. I try to= =20 > have concise emails and not regurgitate every piece of information every= =20 > time I am asked about some peripheral topic. It's not a matter of=20 > spreading disinformation or self promotion, but simply stating informatio= n=20 > that someone may not be aware of. I didn't promote Rekall at all in my= =20 > first response to the topic. All of these points are irrelevant to my statement below. Your answer (even further below) pointed a developer with a clear interest of creating an=20 application for KDE in the direction of Katabase. For a developer the licence is very important, I think you know that. Knowi= ng your thoughts about any Open Source licence I know how to handle your state= ment, But new users do not. =20 > I got reamed by RMS a few months ago and in the process he also proceeded= =20 > to say crap about the KDE project in general and because of that and his= =20 > attitude I've pretty much sworn off the GPL now. It's really ridiculous= =20 > that as programmers we are all forced to be lawyers perpetually and we ta= lk=20 > about licenses almost as much as we talk about code. I have no opinion on RMS. The GPL is one OpenSource licence and it protects= =20 my rights to use and distribute the software I care about. This is importan= t=20 to me.=20 The fact that I use a product from someone does not mean I like what that person does/says... > At 09:07 AM 9/24/2001, you wrote: > >Shawn, your product Rekall is not for users of KOffice until they buy it= =20 > >from > >you, this means that the original poster is not helped at all with your= =20 > >statement. > > > >To state my meaning with this email; please don't abuse the KOffice list= =20 > >for > >advertising of your products, this only leads to confuse users and=20 > >developers. > > > >I really dislike the way you don't answer the licencing questions until= =20 > >they > >are asked very specifically, this only adds to the confusion of our user= s,=20 > >and > >will not really help them into your direction as well. (can you say=20 > >disinformation?) > > > >Sorry for the harsh words, but I think this is a known concept for a=20 > >mailing > >list in the Open Source world. You could have known better. > > > > > >> Rekall is going to pretty much do all this and will be available in it= 's > >> new incarnation in a few weeks. > >> > >> At 11:03 AM 9/23/2001, you wrote: > >> >On September 23, 2001 07:53 am, Richard Bos wrote: > >> >> > I am beginning work on a database front-end. I need to be > >> >cross-platform > >> >> > and GNUe has done some interesting work in python, so it will=20 > >probably > >> >be > >> >> > a python interface, but it will be just a rendered for XML-defined > >> >> > interfaces. I am interested in integrating this with KOffice... > >> >> > >> >> QT-3.0 provides native database support, you may have a look at tha= t=20 > >as > >> >> well. > >> >I was planning on using another database access core that I will=20 > >develop to > >> >allow special control over the formatting of new data types and the u= se=20 > >of > >> >XML, but I could easily add support to QT/KDE database libraries from > >> >there. --=20 Thomas Zander zander@earthling.n= et The only thing worse than failure is the fear of trying something new --4zI0WCX1RcnW9Hbu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7r2fWCojCW6H2z/QRAlAAAKDnh86wrpD6RoeJEB8Uas6Mnb8sNgCgovSt uWbwJV2wfN5kfMO3t94OXXY= =pCnn -----END PGP SIGNATURE----- --4zI0WCX1RcnW9Hbu--