On 15 Oct 2008, at 07:59 , Sebastien Lelong wrote: > Aaah.... THE famous question, I was waiting for it :)
Actually, it is not that bad. We just declare it moot. The code we distribute is high-level. That is the intellectual property. Compiling it makes machine code which nobody can read. We don't mind people profiting from our code IN THE FORM OF PROGRAMMED PICS. We DO mind profiting from our high level code as in a "PIC programming environment", without attribution. As long as we explicitly state that profit from selling programmed PICs is OK, we have no problem. We can put anything we want in this license. It is our code. Since the JAL code itself is the main intellectual property, there is no such thing as a "binary form". Either the code is there, in JAL form, or not. If it is, the attribution should be there. If it isn't, it shouldn't. > So, does the "binary form" include a programmed PIC? How could it > reproduces it ? Printing it ? Not enough memory, etc... Yeah, open- > source licenses sucks, they just did not considered our sweet > little PICs... No, it DOES NOT include a programmed PIC. If we state this, we are done. > What is the real problem ? I mean, when people face this problem, > do they want to actually distribute it *without* any license, that > is, *hiding* it ? Or do they *want* to reproduce it, but they just > can't they don't know how to do it ? People might make a fancy JAL editor and profit from it, distributing our code with it, claiming copyright on this code and forbidding US to change it. That is why we need a license. > Now consider this. Do you think all binary executables, open-source > inside, reproduce their license notice ? No. Does the place where > people actually get thesebinaries have a way (whatever it is) to > reproduce their license. Yes. > > So, if the problem is really that you can't know where you could > reproduce this license, I'd say: on a website, on a documentation, > on a tarball/zip, on a bill,... There's always a way to tell the > world: "I've used jallib, it's great". I agree. Explicitly stating that programmed PICs or hex files do not constitute "distribution in binary form" solves this. > > > > > > Isn't it ? > > > Seb > > > 2008/10/14 Eur van Andel <[EMAIL PROTECTED]> > On 14 Oct 2008, at 18:12 , Sebastien Lelong wrote: > >> Hi guys, >> >> In order to release, we need to add a LICENSE file to the >> repository (and even without releasing). I've taken the template >> from OSI (http://www.opensource.org/licenses/bsd-license.php) and >> tried to adapt it. I've committed it to the repos, at the root >> (same level as /tools). >> >> Could you please guys have a look at this important file, and give >> feedback about the content ? > > > I hate license talk, but this has to be said: > >> # Redistributions in binary form must reproduce the above >> copyright notice, this list of conditions and the following >> disclaimer in the documentation and/or other materials provided >> with the distribution. > > That binary form, does that include a programmed PIC? A code > protected PIC? > > I couldn't care less about licenses, so if we declare (and we have > the right to do that!) that a burned PIC does NOT count as binary > distribution, than I see no problem. > > PIC code is machine language, that is not even assembler. Nothing > we do here can be reverse-engineered from a PIC, so to hell with it. > > > --- > ir EE van Andel [EMAIL PROTECTED] http://www.fiwihex.nl > Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands > tel+31-546-491106 fax+31-546-491107 > > > > > > > > --- ir EE van Andel [EMAIL PROTECTED] http://www.fiwihex.nl Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands tel+31-546-491106 fax+31-546-491107 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
