> From: "Dallas Bolyard" <[EMAIL PROTECTED]> You suck!
Okay, with that out of the way.... > My DM urged me too write a DM utility Hehe. > Now as a side interest I'd like to make this thing OGL/D20 compliant and You probably won't be able to make it d20 compliant, even doing the slightest bit of calculation based on user input pretty much makes that impossible. OGL is no problem, of course. > maybe sprinkle a little GPL around the interface and logic code in case > the app turned out to be a hit with the fellas. You'll need to use an Open Source license of some kind, since the code itself is bound to include some derivative material of some sort. > Custom > data such as new monsters and such entered into the system will be > stored in separate so as to not contaminate the data gained from the > SRD. Doesn't really matter. New entries will be derivative work, and must be Open anyway. > Obviously the install routine will display both licenses and > require acceptance to complete installation. Again, doesn't matter. Accepting a license is not required to use any Open products, only for distributing them. > Now does this sound ok. Probably, yeah. The more Open, the safer, of course. I had also considered the information > in the data base as I wonder if having the agreement in the program > would be enough or if that data would need to be tagged with a copy of > the OGL separately since it could be distributed separate from the > program, but I could easily add the text of the OGL to the summery > property for the file. You'll need to talk to someone with legal knowledge about that. You're not responsible for how people redistribute things, including a single copy of the license with your distribution package would probably be sufficient. There's a few different schools of though on that though, I think it comes down to how the end user would use it. > Could I please have some feedback (even if it amounts to "you suck") > before I start my project? You're not doing anything outside the bounds of the OGL, and if you Open Source everything you're safer. I think your second biggest concern will be finding and commenting as OGL everything in your code that's derivative. You can get around that by OGLing all your code. Your biggest concern will be distribution, this could be a showstopper with VB. Unless you plan to make your users compile the code themselves, you run into the binary distribution issue. You need to label the OGL you distribute everywhere it appears, that's something that's very, very difficult to do in a compiled language. You can't even get around this by OGLing everything, since libraries will be compiled in that you don't have the authority to Open. -Damian _______________________________________________ Ogf-l mailing list [EMAIL PROTECTED] http://mail.opengamingfoundation.org/mailman/listinfo/ogf-l
