Of all the options, I'd lean more on 1 & 2, with 2 being my preference, as that fits more closely with a focused game jam.
However, as 1 has had more people leaning on it, may I suggest a slight tweak to it?
With much more time time being allocated for the coding, which allows for a bigger and complex game, I think allowing more time for judging (2 or 3 weeks?) would be a good idea - rather than having to speed through them all and only scratch the surface of the game.
Part of my idea of what relaxation is, is playing computer games, and I really would love to give my attention to what people have put their effort into at the same time :)
Just to note - game jams are really meant to be short - the last one we did here, the Procedural Death Jam, you only had a week (it was actually 7 days, 23 hours and 59 mins ;p) to produce the game.
Two weeks I would say is more than enough for any sort of idea. I could even say that a 10 day coding jam would totally work as well. It takes about a week to build an idea, and then the rest of the time for polishing it.
Going longer than 2 weeks I think loses the identity of a game jam, as people can lose focus with more time - of course if you are going for challenges rather than jams, then the longer times are cool as well :)
And I wouldn't fret about having a month cool down (alternate months) - if you couldn't assign time to do it that month, then don't worry, join in on the next month - it's not as if we *have* to do something, it is just for fun :)
No, the license only applies to the assets in question. You can have a combination of cc-by-sa assets and private assets, but the license is per asset that it applies to.
Your code and other assets you own are not applied. You are confusing the cc license with a GPL license, and they are very different.
The creative commons abbreviations is fairly simple. The first, "cc" is obviously short for "Creative Commons", which tells you what the license is. The groups of letters that follow the "cc" then details the requirements of the creative commons license.
So, armed with that knowledge, "cc by sa" requires two things:
1. "by" is reference to the author. You must give appropriate credit, provide a link to the license, and indicate if changes were made.
Usually the "appropriate credit" is the artists name and the url to find their work. A lot of artists here will just say to link to OGA, however some will require their own website instead. Check with each author first how they want to be attributed.
2. "sa" is "share alike", so if you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
For example, you take an image where the background of an image is white, and for your game you remove the white background to be transparent, the license requires you with the by clause to note what assets you changed, and with the sa clause to share your modifications. Embedding them inside a game isn't "shared" - however posting the modified art here or on your own website for others to freely download is definitely shared, but you will have to link to it.
One of the things about the work that is available here on OGA is that the "nc" clause (non commercial use only) is not allowed here, so the commercial aspect of your game is irrelevant to the usage of the asset.
Cards, both front and back (especially trading cards - there is only one trading card design that I could find on here!)
and also, not "Weekly Challenge" either, as that wouldn't be picked up with the tag "challenge"
Of all the options, I'd lean more on 1 & 2, with 2 being my preference, as that fits more closely with a focused game jam.
However, as 1 has had more people leaning on it, may I suggest a slight tweak to it?
With much more time time being allocated for the coding, which allows for a bigger and complex game, I think allowing more time for judging (2 or 3 weeks?) would be a good idea - rather than having to speed through them all and only scratch the surface of the game.
Part of my idea of what relaxation is, is playing computer games, and I really would love to give my attention to what people have put their effort into at the same time :)
Could do with a poll. For now though: 2
Just to note - game jams are really meant to be short - the last one we did here, the Procedural Death Jam, you only had a week (it was actually 7 days, 23 hours and 59 mins ;p) to produce the game.
Two weeks I would say is more than enough for any sort of idea. I could even say that a 10 day coding jam would totally work as well. It takes about a week to build an idea, and then the rest of the time for polishing it.
Going longer than 2 weeks I think loses the identity of a game jam, as people can lose focus with more time - of course if you are going for challenges rather than jams, then the longer times are cool as well :)
And I wouldn't fret about having a month cool down (alternate months) - if you couldn't assign time to do it that month, then don't worry, join in on the next month - it's not as if we *have* to do something, it is just for fun :)
If we do a monthly, could I suggest 2 weeks coding, 1 week voting, remainder days for rest
Also, when are you thinking of starting this? I can get started whenever you're ready to say "go" :)
Some suggestions that are a little more mundane and generic:
* Interface designs
* Parallax looping backgrounds
I don't want to pester, but as the second art challenge will be finishing soon, how are you doing with the rules?
No, the license only applies to the assets in question. You can have a combination of cc-by-sa assets and private assets, but the license is per asset that it applies to.
Your code and other assets you own are not applied. You are confusing the cc license with a GPL license, and they are very different.
The creative commons abbreviations is fairly simple. The first, "cc" is obviously short for "Creative Commons", which tells you what the license is. The groups of letters that follow the "cc" then details the requirements of the creative commons license.
So, armed with that knowledge, "cc by sa" requires two things:
1. "by" is reference to the author. You must give appropriate credit, provide a link to the license, and indicate if changes were made.
Usually the "appropriate credit" is the artists name and the url to find their work. A lot of artists here will just say to link to OGA, however some will require their own website instead. Check with each author first how they want to be attributed.
2. "sa" is "share alike", so if you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
For example, you take an image where the background of an image is white, and for your game you remove the white background to be transparent, the license requires you with the by clause to note what assets you changed, and with the sa clause to share your modifications. Embedding them inside a game isn't "shared" - however posting the modified art here or on your own website for others to freely download is definitely shared, but you will have to link to it.
One of the things about the work that is available here on OGA is that the "nc" clause (non commercial use only) is not allowed here, so the commercial aspect of your game is irrelevant to the usage of the asset.
Pages