Hello:

   I'll just participate in this horrible flame once.

On Wednesday 24 June 2009 14:02:26 Ronald Vanschoren wrote:
> >it sucks to have to be the one to push for license
> >compliance like this
>
> Then don't! I'm just a user of OpenOCD so you have all right to ignore what
> I'm saying as you'll find that I'm less important, but it's about time
> people here start to realize the real "clients" are users and not
> developers and users don't give a sh*t about GPL violations.

  You are not less important, you are just another kind. "Clients" are 
important as well, just that you (we) don't pay for using the software. Having 
said this I don't understand how you (or anyone sensible) could support 
violating licenses. Do you have the habit of breaking laws for the sake of it?

>
> Why would anyone want to waste time and effort on fixing this purely
> theoretic issue? Use the time to implement useful features like SWD or
> threadsupport instead.
>
> You're acting like you have no choice but to point out this issue and write
> 700 mails about it. You of all people can fix it easily. Give up your
> copyright or allow relicensing it under anything that is not as gray and
> debatable as GPL.

  I don't think enforcing one's rights is loosing time. This is not a 
theoretic issue. GPL is the license and it states that whatever you link 
against and distribute should respect GPL freedom, among others, being able to 
get the source code.

  You can do things about this, for instance persuading FTDI to free the 
FTD2xx driver source and relicense it with GPL or any other compatible license 
for the issue: [email protected]

>
> As a sidenote I still don't see the issue. The spirit of GPL is to allow to
> make modifications to an application that is distributed in binary form.
> OpenOCD with FTD2xx allows this, no discussion! So stop using the FAQ of
> people holier then the pope to argument OpenOCD can't be released on
> Windows.

  You wouldn't be able to do modifications on the FTD2xx library, so no point 
for this.

>
> I really don't get it. If OpenOCD were my "baby" I would like to see it get
> popular and loved around the world. What's the use of having a super-great
> application that nobody will use because some people are stubborn and don't
> see further then idealistic BS.

  If OpenOCD or whatever other is my "baby", I would do what I would like with 
it. Trying to get it popular, maybe not, give it for free, get paid for it or 
even license it under GPL terms. In this case rules were dictated from the 
beginning.

>
> Just my 2 cents but I'm quite sure a lot more people are getting tired of
> this. Change the license or ignore the theoretic violation and get the next
> version out there in binary form for Windows using FTD2xx.
>

  If you (or others) are so interested in a license change, then answer this 
questions:

  · Have you contacted every copyright holder and ask for his opinion?
  · if (s)he is reluctant to change license what will give you in 
compensation?
  · Are you willing to pay money for the work they have done to change 
license?
  · Are you willing to accept anyone is not going to admit a license change?

  License is not democracy, not even meritocracy, is consensus. License is 
what it is and only an agreement of all copyright holders can change that.

> If I had something to say I would ask every contributor to state if they
> allow a relicense. If not, strip out their code and rewrite it. That can't
> take longer then making the workarounds people are discussing now. While
> we're at it, demand that contributors donate their copyright to the OpenOCD
> foundation or whatever, so these discussions are a thing of the past. I
> don't want to run a 2nd application to be able to use FTD2xx on windows. I
> already have to run OpenOCD and gdb, more then enough to keep track off.
>
> gr.
>
> Ronald

  What I don't understand so far is why it is so important to add an exception 
to the license instead of:

  · Improving free FTDI library
  · Asking FTDI to release and free the FTD2xx library
  · Make people interested in running FTD2xx build his own copy/binary of 
openocd

  Most of this options requires less work than tirelessly quarreling on the 
list. It is possible not using FTD2xx, it is also possible using it. Whoever 
is interested enough on any of those aspects should care for it, but not 
putting pressure or insulting(*) developers to do what they claim. Why is it 
easier to put pressure on developers who actually does a great job and not on 
a company that should encourage its products to be sell?

(*) I don't refer you, Ronald.

  Regards,

Pd: This e-mail express a strictly individual position.

-- 
Raúl Sánchez Siles

Departamento de Montaje

INFOGLOBAL, S. A.

* C/ Virgilio, 2. Ciudad de la Imagen.
28223 Pozuelo de Alarcón (Madrid), España
* T: +34 91 506 40 00
* F: +34 91 506 40 01


_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to