<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
El 01/08/12 17:09, José Antonio Canalejo Alonso escribió:<br>
<span style="white-space: pre;">> Hello Jorge,<br>
> gvSIG was born without trademarks [1]. The owners of the
copyright are now different than the ones at the beginning of the
project. Things have changed a lot since the gvSIG incubator
application request was sent to OSGeo [1]. This link should be
actualized and the actual situation of gvSIG should be new
exposed: names of all official committers, relationships with
commercial companies or products, patents, trademarks, copyright,
people actively contribute (code, documentation, other?), actual
sponsors, etc<br>
> These changes about trademarks were never notified in this
list. My apologies if the name of the project is creating
confusion. gvSIG CE was created as many other projects with the
name of gvSIG. After the creation of gvSIG CE, we were informed
about the existing trademarks.</span><br>
<br>
Yes you are correct, I'll update the incubation information as it
outdated.<br>
<br>
But it's not the responsibility of the trademark holder to inform to
anyone about this, is your responsibility to take or what you are
doing. As you state many communities and groups use the gvSIG logo
and brand and as far as they use a fair use nobody will ever think
on ban anything. That can be said also on projects that cooperate
with gvSIG project like EIEL, Fonsagua, etc. But creating a new
project that tries to rest efforts instead of adding is a completely
different matter. Comparing them is almost naïve. Except yours, any
previous fork of gvSIG was done by technical reasons, and with no
intention to replace official gvSIG development.<br>
<br>
<span style="white-space: pre;">> Instead of starting any
expensive and painful legal action, we should keep on working,
producing good code like we are making now. Developers from gvSIG
EIEL and gvSIG CE made important contributions to gvSIG 1.10, 1.11
and 1.12.<br>
> Let's keep working together in different repositories. We are
more effective and faster now than following the official
procedures. More contributions will come from gvSIG CE Team to
gvSIG 1x.<br>
> Otherwise, you have announced, the gvSIG Association will
invest its resources in gvSIG 2x. Let us then develop in peace
gvSIG 1x. and integrate SEXTANTE there as it should be done. No
matter of we are official or not. Do not try to make official a
community, this will never work.<br>
> Best regards!<br>
> Jose<br>
></span><br>
<br>
gvSIG association is investing resources on releasing gvSIG 1.12.
Directly. And with the amazing support of gvSIG Association members,
so don't try to spread FUD about gvSIG project not supporting its
current stable release because it's NOT TRUE.<br>
<br>
- -- <br>
Jorge Gaspar Sanz Salinas<br>
gvSIG Team at Prodevelop<br>
Technical Collaborations Manager<br>
<a class="moz-txt-link-freetext" href="http://www.gvsig.org">http://www.gvsig.org</a><br>
<a class="moz-txt-link-freetext" href="http://www.gvsig.com">http://www.gvsig.com</a><br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.11 (GNU/Linux)<br>
Comment: Using GnuPG with Mozilla - <a class="moz-txt-link-freetext" href="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</a><br>
<br>
iQEcBAEBAgAGBQJQGiLkAAoJEAOYD75lvHdB054IAJaP5FvWCRdFXr8fMjzWeRWZ<br>
BdSWTqr+mMHzeDq3lQ0eUPnWYLjr3GtDvklP/SZbIBHP3+Lu2yfFqZqJORCsbP+L<br>
Jr4FISmzTBPYMuKT96VMyRFZsH0f9tQvov9uvChV3ddVFQrvG2PTzH9MqwPk1x25<br>
AX11XVCZUbSxGHwTp+JdwmDjjg7SEETAd08M+BaUGMCGDaNG1pdYfk1HtMjQUD4H<br>
F8dindngdnIa8jBILAQ0hUPy/XzcgvLXIq/bPkFi8lmsFuV+qVFZFmES7/wi6hJm<br>
hu8pBd4YJ7MO1aq3/mI/E2snd1C6UdXHXGS4DUzlvVrFhYKqKhP8nR7TvppE2Ek=<br>
=RfWd<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>