CRGreathouse said:Never the d20 STL, but I've considered opening my generators under the OGL.
Twin Rose said:Are you currently using Open Content within the source code? This is a big no-no and WOTC has been looking very closely at software AND websites lately.
CRGreathouse said:
Yes, I'm using OGC in my source code. This is OK for many reasons:
* The source code is open - since it's not compiled, the source can be viewed. Even if it did compile, providing source code is sufficient.
* The d20 STL does not forbid using OGC in source code - the FAQ doesn't like it, but it's non-normative.
* I'm not using the d20 STL. The OGL has no such restrictions.
Edit: Here's a list of pages relevant to this post:
http://www.wizards.com/D20/article.asp?x=dt20010417d
http://www.wizards.com/d20/files/d20guide.rtf
http://www.wizards.com/d20/files/d20stlv3.rtf
http://www.wizards.com/d20/files/OGLv1.0a.rtf
http://www.wizards.com/D20/article.asp?x=dt20010417g
Twin Rose said:Are you currently using Open Content within the source code? This is a big no-no and WOTC has been looking very closely at software AND websites lately.
Twin Rose said:Oh I'm intimately familiar with the faqs on d20 source code.
Twin Rose said:The OGL does stipulate clear indication of what is Open Content and what is not is required - commenting the source, for example, goes a long way towards this.
Twin Rose said:Is this some sort of a script you are running in?
CRGreathouse said:
(Honest question) If you're intimately familiar with the FAQs and the licenses (as I would have originally assumed you were), why did you claim OGC in source code is a "no-no"?
Yes, the content is clearly indicated. It's actually not hard at all.
I'm not suggesting tha you should do the same - ther are obvious benefits in commercial programming to keeping the source private. Since I'm noncommercial, I don't have that concern - all I need to follow is the OGL.
Yes, JavaScript. It runs on web pages, cross-platform compatible, lightweight, and fast enough for my needs. What more could I ask for?
(Yes, actually, the speed is something of a drag - but what could I *realistically* ask for?)
Twin Rose said:Well, if Java becomes compiled, then the 'clear indication' is not really there anymore.
Twin Rose said:The OGC issue in code is a no-no in closed sourc,e I just load it at run time.
CRGreathouse said:
False. As long as the open portions are identified (for example, by distributing the souce along with the compiled file), the software is OGL-compliant.
Twin Rose said:
I was at a meeting at WOTC, and have discussed this issue with Anthony Valterra on a couple of occasions. The impression that I'm under is that if it's compiled, it's not really 'clearly marked'.