Main Menu Theme ready, and the 'fresh air' of License struggle

DarkStalion has just finished creating the complete version of the Main Theme for jClassicRPG! It's very well worth the listening, so don't hesitate to follow to his blog and grab it! I love it!

The big silence here at the blog for a longer period is due to the process that I'm currently in. The process of creating a new free & open source license for supporting easier free game development (easier from my point of view and with my considerations at least). There are already draft versions of the two planned flavors of it. Both are copyleft license flavors based on the Apache 2.0 license, appended with copyleft part. Copyleft means that it is required to distribute the sources of a work as well if someone distributes such work under the copyleft license.

The new licenses which are in the works offer patent license part, GPL compliance, non-conflictive nature, separative nature, copyleft nature, open source: the things that I consider important. I'm willing to use this new open source license for later releases of jClassicRPG to make it easier for those contributors to contribute to the project, who can't cope with some of the aspects of GPL-compliance for their media. Check this thread here about the creation of the licenses. (There's another lengthy but interesting thread about interpretations of GPL too here.)

There is two flavors of this new license we're creating: one is called Strong Flavor which contains stronger restrictions to make it stronger copyleft - redistributors of original work and derivative works has to make publicly available or distribute the source too. The other is the Weak Flavor, weaker copyleft - the redistributor only has to distribute or make the source publicly available if he distributes a new Derivative work.

If you're good at lawyer stuff, and willing to read it and suggest things, please visit the forums and reply!

PS: ah, after a half hour of thinking just after writing this post, we've concluded that the Weak Flavor is useless, so we've just dropped it (because redistributing a one copy distribution of a Derivative work would mean no source redistribution required only the very first time it's released, so it is basically very easily lost in the chain.)