> All this talk about the different license schemes lately, has me > wondering... > > What do I do with my blinder.lrp (it's getting closer to > releaseability)... licensing-wise?
Pretty much whatever you want :) > The majority of the code is written by myself. But there *are* snippets of > code here and there (mainly the C-parts) where I've basically cut/pasted > and slightly modified examples I've found around the web... > > I'm not exactly sure if any *code* still survives, but in any case I've > been looking heavily at some of the viewlogs etc. cgi-scripts that come > with the weblet/bering-1rc2... > > I'll track down and ask the people who published aforementioned > C-snippets, but what are my options/obligations in general? IMHO, writing code is a lot like writing books. Everyone copies everyone else's ideas, but you need to stay away from actually plagerizing something. Of course, trying to define exactly how much modification makes something entirely yours vs. a modified version of another author's code (or story, or whatever) is a pretty blurry line... > Does anyone have any good links on the subject? Saddly, no. Please share with the list if you find some good references. > Personally I'd be only happy to see people using this thingie, but I > would prolly be pretty upset if someone were to grab the code and > advertise it as theirs... (not that I imagine anyone would *want* to do > that since it's all still pretty sloppy/ugly anyway) Most of the open-source licenses are pretty strong about continuing to credit previous authors (one of the biggest sins in the open-source world is to deny credit to someone whose work you have built on). I doubt you found any major pieces of code that are reproduced in your new blind application (ie your work is basically original, not derrived), so you probably don't have to worry too much about licensing, but it would still maybe be nice if you included references to some of the material you used as references. Of course, if a big chunk of your code is lifted from somewhere, you will definately need to acknowledge that fact, and consider any licensing implications. BTW: I consider the weblet code (cgi-bin scripts) to be GPL'd, although there is no license specified. I guess I haven't worried about it too much because: - Adding licensing notices and author credits takes space, and I was trying to make everything as small as possible - I'm not particularly worried about recieving ongoing credit for the cgi-bin stuff...it wasn't that much work. - The shell-script stuff is pretty much open-source anyway...it's kind of hard to release a "closed-source" shell script :-) NOTE: There *IS* a GPL notification at the start of sh-httpd, it was a bit more work :) Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
