@rvalyi > I think you should protect you against future licensing conflicts by issuing > a license agreement for the community committers like us. you can look at > what Sun or Mozilla did. I think that might be a good move to avoid people to > later on try to hijack the license. For instance it took so long for Sun to > release the full version of the open jdk just because fucking bastards were > not ready to open source what they previously contributed (media stuff for > instance).
Then you will have to go and sue Tiny, Axelor and others on doing just right that. Or other people will. > fucking bastards I think you are not so polite for the start, as you should be... If some involved companies do not respect other people involving in the project (I am not speaking now about our self), then go for it, double license code as Tiny & co. are doing it right now. > So since OpenERP is now getting very big I think it might be a good move to > protect you against all those nasty tricks. Tricks like some Partners are doing, effectively not making the code free and inaccessible to the community. Oh well, I forgot, you can't protect one from himself. OpenERP are rolling down to the same hole as other similar open business oriented software projects are. You will end up in many different forks, just because people will not agree to put up just like that. Is that any better? Oh, and please show some respect, do not say that I am not right, just like that, without explaining yourself. -sraps -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=35047#35047 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
