I would love that! Though, a custom app would need to be a community collaborative endeavor. DeviantArt has an official app mostly because of their nearly $22,000,000.00 USD ad revenue. Since OGA is completely free for users and free of advertising, the site has ~$6000 anually. which is almost entirely dedicated to servers and hosting.
What is this about "the API" people are referencing? Is there an established drupal API? If not, an API would need to be developed alongside the app or mobile version of the site. I'm for it. Working on getting the site code made available on github. :)
@VinnNo.0: well, for the CC0 license it is sufficient, but from what I understand the jam needs credits as if it were essentially CC-BY. That probably doesn't mean you need to do much more than what you've indicated, but I'm guessing it should at least have a URL listed or credits.txt referenced in it so people can find the asset page it came from.
EDIT: maybe I'm overthinking it:
"3) You must credit the Author of the assets used, even if it's not required by the license. (Because this is nice thing to do)"
I assume that means props are sufficient(?) for cc0, though I guess you still could include a URL or credits.txt reference "because this is a nice thing to do". :)
Having clickable links in credits is more of a convenience than a requirement of the license. My entry for last year didn't display the URL for the assets at all, which is actually less in-line with the letter of the license requirements than displaying a non-interactive URL.
It's not about making sure you pronounce all the magic words exactly right to summon the legal-compliance-demon. Just give the player some way to see where the asset came from. click to open webpage, or display url text (clickable or not), or reference to credits file, whatever.
If the framework you're using doesn't make an interactive credits screen easy, just put something like "EpicSong5 by Joth, CC-BY. See credits.txt for more information." That's sufficient and perfectly compliant with the license and jam rules. I know that makes Chaser's job a little harder, but if it's the difference between completely reworking existing assets just to avoid a bureaucratic version of the requirements- or worse- not submitting a jam entry altogether, Chaser's suffering is a risk I'm willing to take. :)
The Bounty system was never formalized, but informally, as the bounty initiator, you would be setting the terms. A few options:
artists comment indicating their interest and a link to their portfolio, then you would select the one you feel best fits the request. Once they finish the request, you pay them via paypal or whatever payment scheme you and the artist prefer. This method allows artists to be more secure about the bounty since only the artist who will get paid will need to perform the work. On the other hand, the bounty poster may not like the final product but has few options to go with a different artist once one is selected.
Artists perform the work and create the art (or parts of it, proof of concepts, etc.) before anyone is selected. The bounty poster then selects the art (or partial art) that seems to fit the requirements best. The selected artist completes the art and is paid via paypal or whatever payment scheme you and the artist prefer. This gives the bounty poster more security in being able to see what the final product will look like before selecting the artist. On the other hand, the artists may be performing work without getting paid for it if they are not the artist selected.
If the request is general enough, it could be useful to more than just one requestor, so many people may contribute to the bounty. This will increase the bounty and attract more artists and collaboration. On the other hand, individual requestors may want very specific details that are not compatible with the needs of other requestors. By opening the bounty to multiple requestors, you may have to forego some specifics so that the asset is useful to everyone.
There is no formal payment system in place. Just a paypal transfer, typically. In the past, payment was based on the honor system. If you promise to pay an artist for meeting the requirements, but don't like the result even if it meets the requirements, you're honor-bound to pay the artist anyway. If an artist shows a proof-of-concept or portfolio that implies a certain level of quality and style, the artist is honor-bound to deliver on a quality final product even if it is taking longer than expected and my no longer be worth the bounty offered. These situations are unlikely, but they should be considered when posting or fulfilling a bounty.
If an honor-based system of bounty and trade seems... unappealing to some, I can act as an escrow and arbitrator. Ultimately, you'll be placing your trust in me, though. At the conclusion of the request, I will do my best to weigh the situation fairly and without bias and determine if the artist acted in good faith or if the payment should be returned to the bounty poster.
As for determining price point, there's really no easy way to determine a decent market price other than talking to multiple artists or perhaps a bidding system. different artists have different rates, styles, and levels of quality. I am wondering if it may work to simply post (detailed) requirements for the asset, and encourage artists to post how much they would be willing to take for performing the task.
Does anyone else have some suggestions on how to handle this?
Weird. I'm not sure how I missed this. Was the original under CC0 temporarily? Well, I have to adjust the licensing until we know more. Thanks for pointing that out, Angelee.
Thanks, MDV.ecb. The previews now include a full spritesheet to better show what's inside the package. New spritesheet w/ transparency and also individual tiles & sprites with descriptive names categorized by folder and type. :)
I would love that! Though, a custom app would need to be a community collaborative endeavor. DeviantArt has an official app mostly because of their nearly $22,000,000.00 USD ad revenue. Since OGA is completely free for users and free of advertising, the site has ~$6000 anually. which is almost entirely dedicated to servers and hosting.
What is this about "the API" people are referencing? Is there an established drupal API? If not, an API would need to be developed alongside the app or mobile version of the site. I'm for it. Working on getting the site code made available on github. :)
@Joth: Good idea. Basically identical to suggestion #14 above.
@VinnNo.0: well, for the CC0 license it is sufficient, but from what I understand the jam needs credits as if it were essentially CC-BY. That probably doesn't mean you need to do much more than what you've indicated, but I'm guessing it should at least have a URL listed or credits.txt referenced in it so people can find the asset page it came from.
EDIT: maybe I'm overthinking it:
I assume that means props are sufficient(?) for cc0, though I guess you still could include a URL or credits.txt reference "because this is a nice thing to do". :)
Having clickable links in credits is more of a convenience than a requirement of the license. My entry for last year didn't display the URL for the assets at all, which is actually less in-line with the letter of the license requirements than displaying a non-interactive URL.
It's not about making sure you pronounce all the magic words exactly right to summon the legal-compliance-demon. Just give the player some way to see where the asset came from. click to open webpage, or display url text (clickable or not), or reference to credits file, whatever.
If the framework you're using doesn't make an interactive credits screen easy, just put something like "EpicSong5 by Joth, CC-BY. See credits.txt for more information." That's sufficient and perfectly compliant with the license and jam rules. I know that makes Chaser's job a little harder, but if it's the difference between completely reworking existing assets just to avoid a bureaucratic version of the requirements- or worse- not submitting a jam entry altogether, Chaser's suffering is a risk I'm willing to take. :)
past bounties ranged from $30 to $70.
The Bounty system was never formalized, but informally, as the bounty initiator, you would be setting the terms. A few options:
There is no formal payment system in place. Just a paypal transfer, typically. In the past, payment was based on the honor system. If you promise to pay an artist for meeting the requirements, but don't like the result even if it meets the requirements, you're honor-bound to pay the artist anyway. If an artist shows a proof-of-concept or portfolio that implies a certain level of quality and style, the artist is honor-bound to deliver on a quality final product even if it is taking longer than expected and my no longer be worth the bounty offered. These situations are unlikely, but they should be considered when posting or fulfilling a bounty.
If an honor-based system of bounty and trade seems... unappealing to some, I can act as an escrow and arbitrator. Ultimately, you'll be placing your trust in me, though. At the conclusion of the request, I will do my best to weigh the situation fairly and without bias and determine if the artist acted in good faith or if the payment should be returned to the bounty poster.
As for determining price point, there's really no easy way to determine a decent market price other than talking to multiple artists or perhaps a bidding system. different artists have different rates, styles, and levels of quality. I am wondering if it may work to simply post (detailed) requirements for the asset, and encourage artists to post how much they would be willing to take for performing the task.
Does anyone else have some suggestions on how to handle this?
Weird. I'm not sure how I missed this. Was the original under CC0 temporarily? Well, I have to adjust the licensing until we know more. Thanks for pointing that out, Angelee.
@um: consent has already been given for everything on this site :) https://opengameart.org/content/faq#q-how-to-credit
Thanks, MDV.ecb. The previews now include a full spritesheet to better show what's inside the package. New spritesheet w/ transparency and also individual tiles & sprites with descriptive names categorized by folder and type. :)
that's a good idea. I could add a preview sheet if anyone is willing to create one. :)
Pages