<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
> @Niccolò: good point. Howevere one could write a non GPL piece of code (the minimum to keep the data undisclosable) and link qgis to it. Is it forbidden<BR>
> by GPL license? I don't think...<BR>
> I think it is.<BR>
<BR>
I also believe it might be forbidden by the GPL.<BR>
I think there might be a way to reconcile ethics, respect for the GPL and the client needs.<BR>
You would need to obfuscate the source code.<BR>
For example, you rename fonctions, classes, filenames etc according to an encryption mechanism. The encryption is based on a key chosen by the client.<BR>
<BR>
You need to take care of many things, e.g. if:<BR>
qgsapplication.cpp becomes qslghtygvr15ni189t.cpp<BR>
then:<BR>
qgsapplication.h becomes qslghtygvr15ni189t.h<BR>
Naming conventions which are understood by the framework should be respected as well (I do not know qgis's architecture well enough to be precise here).<BR>
In one part of the code, you put your mechanism decoding the data.<BR>
You then release the whole thing as GPL.<BR>
<BR>
Obviously, you work on the non-obfuscated code. You need to use or build a software to obfuscate the code (<A HREF="http://en.wikipedia.org/wiki/Obfuscated_code">http://en.wikipedia.org/wiki/Obfuscated_code</A> says there are open-source software to do so).<BR>
<BR>
Then, for the ethic part: you also share any improvement you do in non-obfuscated format (except maybe the data-decoding part). I wonder though if the major part of the data-decoding part could be generic enough to be shared as (non-obfuscated) GPL code. Then other sensitive projects may reuse it.<BR>
Is the whole approach ethical? I really don't know. Still, it would be funny to receive a dataset with a notice: to read this geotiff, you must use our version of QuantumGIS, not ArcGIS or Mapinfo! <BR>
<BR>
<BR>
EDIT: not sure the approach above is OK, see <A HREF="http://stackoverflow.com/questions/1086445/obfuscation-and-gpl">http://stackoverflow.com/questions/1086445/obfuscation-and-gpl</A><BR>
However GPL encryption software do exist. Maybe the data provider could give the data with a key. Of course it makes the system much weaker. However, the client should be aware that an external compiled piece of code is not much less easy to crack than it is to change an open source software.<BR>
<BR>
A final note:<BR>
I believe in free software and in free geo data. I contribute to QGIS and to OpenStreetMap. I've produced some of OSM icons and released them in public domain.<BR>
However, piracy exists and I condemn it; some organizations may rightfully search ways to protect themselves against unauthorized used of their data. I prefer companies that share their data, but <B>as long as you contribute yourself to QGIS in other domains</B>, then you would learn something from this work and I would say it's better than if they pay ESRI developers to do the same. <BR>
Still, if you can find another client/boss which is more open source minded, then I would encourage you to refuse this task. Otherwise, I'll pray for you soul!<BR>
<BR>
Hope this helps,<BR>
Mayeul<BR>
<BR>
> <BR>
> Probably you're right. <A HREF="http://blog.milkingthegnu.org/2008/04/gpl-for-dummies.html">http://blog.milkingthegnu.org/2008/04/gpl-for-dummies.html</A><BR>
> <BR>
> <BR>
> <BR>
> --strk;<BR>
> <BR>
> () Free GIS & Flash consultant/developer<BR>
> /\ http://strk.keybit.net/services.html<BR>
> <BR>
> <BR>
> _______________________________________________<BR>
> Qgis-developer mailing list<BR>
> <A HREF="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</A><BR>
> <A HREF="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</A><BR>
>
</BODY>
</HTML>