On Wed, 2009-06-24 at 00:55 +0200, Magnus Lundin wrote: > Thomas A. Moulton wrote: > > On Tue, 2009-06-23 at 15:33 -0700, Rick Altherr wrote: > > > > > >> The community as a whole can easily decide to remove your code, > >> replace it, and relicense. The community can also choose to follow an > >> alternate interpretation of the license that you may not agree with. > >> Again, you have no rights to declare which interpretation must be > >> followed. Your rights only extend to bring a court case to decide the > >> claims. The community must reach a resolution and individual members > >> don't have the rights to assert that theirs must be used. > >> > > > > Rick, > > > > The term community and authors are not interchangeable. > > > > What you are suggesting is not a trivial task. > > > > > And what is your position in this ? > Author or community? > And what is your opinion ? > /M >
I am a developer in a number of (minor patches in most, core developer in one) Open Source projects (mostly GPLv2) and a developer on a ARM related project. I have not even looked at the OpenOCD code yet... The version of OpenOCD I have does not work for me 100% but I have not looked at the source yet... I was going to but the windows build complexity has deterred me from attempting it. My position is that GPL is the best license to use for most group projects of this nature (ad hoc developers, etc) My opinion in this is there is no way to control what has been released in the past and the future releases should adhere to the license. If this means some limitations then that is acceptable, since the community will implement features to remove those limitations. That is a very nature of open source... when a bug pisses me off enough I take time to find and/or fix it. It seems while this list is called openocd-development it may have more users than developers. That is my observation... besides we all were users before we became developers! Tom _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
