On 8/31/07, Chad Z. Hower aka Kudzu <[EMAIL PROTECTED]> wrote: > > Hrm, no that was Bruce, not me. > > Sorry. :) Ok Bruce you then please. :) > > > Sure. About that code protection.... I would prefer that we keep some > > semblance of copyleft, as stinky as that may smell to the more > > Windowsy/Businessy people. If it comes down to it, I could deal with > > MPL. A mixed license system of some sort would be nice too, maybe a > > mix of GPL/MPL? > > I think its great that we are opening up now more as to WHAT we want from a > license rather then WHICH we want. I think this will be much more > constructive. > > My personal opinions (others weigh in of your own please): > > Copyright: Im fine with enforcing copyright, and even attribution. That is > inline with Creative Commons, IX?, BSD, etc. > > Copyleft: > For those not versed: http://en.wikipedia.org/wiki/Copyleft > > Im ok (again not my first preference, but Im ok with it) with a license that > says "Hey, we wrote this. We gave it to the community and we want it to be > free. If you change it, what you change has to be given back to the > community". But if someone wants to just use the code as is - and link to > it, either code wise (compile in, static) or dynamically (library) I don't > think they should have to give away their source code and use MY license.
That was the point of weakening the copyleft a bit by using MPL or LGPL. The MPL does not require that code linked to it is licensed under a compatible license. It just doesn't care. > Commercial usage of stuff is every bit as valid and vital to adoption as is > open source. In my experience, MOST people will still make open source. But > there are lots of commercial uses where giving out source code just isn't a > viable business model - ESPECIALLY if we are to say software patents are bad > (I don't think they are bad, I think they are evil) Yes, software patents are evil. > then we should allow > some protection. There are many commercial examples of usage of open source > libraries successfully while still retaining credit to the libraries authors > and often with some contributions back to it as well. The MPL would stop commercial entities from taking the SharpOS code, making some changes/improvements, and closing it off (a so-called "closed fork" in the BSD/permissive model). I'm interested in this because I want to see the improvements to my code, and they shouldn't be able to stop me from doing that. Especially if they build their business around my hard work. But like I said, I'm open to a weaker copyleft license, and even a more permissive license if that comes to be a general consensus. > Should every prescription drug you buy be required to include the exact > formula and production instructions? Should every prepackaged food you buy > be required to include not just ingredients but the recipe too? I do believe > in IP protection - but do not extend this to believe that I support DRM, and > what many call "IP protection". After all, even GPL and LGPL and the like > are all "IP protection" of sorts. Yes they should in my mind. I once worked at a restaurant where I had to sign an NDA for their recipes and I was appalled. I needed a job at the time but I cringed when my signature hit the line. It's a sin I'm still atoning for. Is it coincidence that your other example is one of the most corrupt industries in America today? > Think of Mono. If it was GPL - well it would be DOA and almost not used. Its > LGPL. The compilers are GPL - but the distinction is clear. But I think that > actually hinders usage a bit... We might have better dev tools if others > could reuse that code more freely instead of just calling it as an app..... Mono would still be used, I know. Why? Because I would use it. Would you use it? No, but not everyone agrees. But I'm not recommending a blanket GPL license here, I've already said MPL, LGPL or another weak copyleft license would do just fine as a compromise. > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > SharpOS-Developers mailing list > SharpOS-Developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sharpos-developers > -- fury long name: William Lahti handle :: fury freenode :: xfury blog :: http://xfurious.blogspot.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
