>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. 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. 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. 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. 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. Please point out EXACTLY why you are so against a GPL exception? What's your hidden agenda cause I refuse to believe this is pure idealism. 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 -------- Original Message -------- Subject: [Openocd-development] OpenOCD license From: Zach Welch <z...@superlucidity.net> To: openocd-development <openocd-development@lists.berlios.de> Date: Wed Jun 24 2009 13:28:17 GMT+0200 (Romance Standard Time) > Hi all, > > In the face of Rick's abrupt departure, I feel that I need to provide > more status and summary of the licensing situation. > > Each copyright holder has the right to "dictate" whether or not they > will allow license terms to be changed in their derived works. That is > immutable, and I do not feel guilty for asserting my rights here. > > I feel bad if some think that I have been dictating beyond those rights, > more than just getting stuff done that needs to be done. Rick won the > uN versus uintN_t debate by the end of it, so his feedback was always > being heard and incorporated by me. I am steering with direction from > the community, as I have made my clear responsibility since becoming a > "maintainer". However, those responsibilities do not affect my rights > as a copyright holder, and here we see a conflict. > > Since my arrival, this OpenOCD list has often preferred talk over action > too often, and I far prefer to engage in discussion on constructive > issues like design, devices, and patches. I do not feel guilty for > taking actions to fix the problems that seem apparent after inspection, > because no one has been doing such work for the project > > Some decisions may prove to be wrong and need fixing, but others need > executive order to be carried out while awaiting those fixes. I intend > to carry on in this tradition, pro-actively addressing the community's > needs and defending the terms of the GPL. Licensing violations are one > such area where compliance action needs to be demanded immediately by > the appropriate stakeholders, to preserve the overall legal integrity of > the project. By protecting my own rights, I protect the rights of all > free software users that do not want to see the GPL compromised. > > Given that even Rick conceded the past and current repository contents > have been released under the GPL, further discussion is not a meaningful > solution to violations of the license. The means to achieve compliance > with technical solutions have been outlined and are wholly acceptable; > any exception would apply only to a fork of the project, branched before > any GPL-only revisions went into the repository. > > Because of my objections to an exception to the GPL, I will not allow a > change to the license in the trunk of the repository, so compliance > needs to be sought to ensure that distributors of binaries respect the > limitations of the GPL. That seems like straightforward legal logic, > not totalitarianism. > > The totalitarians are the FSF, who designed the legal language of the > license to be this way; however, I think that is tantamount to saying > the Founding Fathers were totalitarians seeking liberty, justice, and > the American way. Sadly, those same people would be called "terrorists" > in the US today; indeed, this should draw some meaningful parallels. > > These are the facts as I have come to understand them, and no one has > given me any solid evidence to refute these points. I wish there were, > because I tell you -- it sucks to have to be the one to push for license > compliance like this. I do not like being seen as the enemy in the eyes > of the community, but I feel it is necessary despite these consequences. > > Once the positive consequences have been seen and appreciated fully, > maybe everyone will come around (or even thank me... I can dream). > Until then, please feel free to hate me for sticking to my ideals and > believing in the wisdom of foresight on these matters. I can take it. > > Otherwise, I am looking forward to seeing the community move past these > issues and onto more constructive development matters. > > Cheers, > > Zach Welch > Corvallis, OR > > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development > _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
