Hey, just wanted to let you guys know that I follow this thread, and I admire your dedication to a frequent release schedule and creating content. Keep it up. :)
The trouble with explicitly stating that the preview images must fall under the same license as the actual files is that that might not be true for some older preview images, and it's impossible to know which ones that doesn't apply to. caeles points to a completely legitimate edge case.
We already have a rule that the preview images have to reflect what's in the actual content, but I prefer that this be kept a judgement call rather than an absolute hard and fast requirement. The key is to avoid misleading previews.
Furthermore, I would actually kind of prefer that the preview images not be freely licensed, unless the author explicitly says they are. When I get around to preserving the pages of deleted content, I want to be able to preserve the preview images so that people can identify what the content was, and if the preview images themselves are freely licensed, then in many cases that's essentially the same as allowing people to download the originals against the artist's wishes. (Note: I also plan to watermark the images on deleted content and perhaps do some other processing so as to make them otherwise impractical to use).
Flagging license issues is something I really hate having to do, particularly since a lot of time if it happens on someone's first post, they just abandon it and never come back. I really would prefer to avoid adding additional situations where it would be necessary to do that. I'd much rather tell people that preview images are all rights reserved unless otherwise noted.
You mentioned in the other thread that you might be willing to rewrite the relevant changes to the FAQ yourself. which is something I'm not going to have time to do this week. If you can do that, I'll look over them and then merge the changes in.
Hi. I don't have enough spare cycles at the moment to come up with my own writing, but if you're willing to rewrite the relevant sections (with the changed bits in bold so that I can revirew them), I'll take a look and try to merge the changes into the FAQ.
Problems are everywhere . try to be honest and respectful to one's own work and that of others . Sorry about the link below. I do not know how to remove it .
@Snabisch: What link are you talking about? I'm not seeing any.
So, a quick note, because we've had issues with this in the past:
OGA will always respect the wishes of artists who want to have their art taken down. However, people need to be aware that those licenses are, in fact, irrevocable, and we cannot and will not assist anyone trying to revoke a license. Furthermore, records of removed art are retained offline in case there's ever a question of whether they were posted. Eventually, we'll be making those records viewable (without the downloads available) so that people can check them on their own. In the rare case where an artist "takes there ball and goes home" and removes all text and previews from their submissions before requesting to have them taken down (this has happened more than once), we willl revert those submissions to the last "good faith" posting before putting up the deletion record.
Regardless of the license on a work, we don't accept art that's obviously not intended to be distributed as game art. We had an individual who cut commercial game art out of a CC-BY-SA screenshot from an indie game and post it here. While that is legal to do, it's incredibly disrespectful of the artist, and we won't archive it here. Likewise, if an artist is selling their own freely-licensed art, OGA isn't going to undermine them by distributing it for free. Note that this is all site policy and not a legal requirement. This is a bannable offense, although we generally issue warnings first, at our discretion.
If an artist doesn't own a piece of art in the first place, they don't have a right to put their own license on it, and the license was never valid. If that's the case, people still need to remove that work from their projects. In the near future, I'm going to add a notification system to let registered users know if art that they have downloaded has been flagged with a licensing issue.
I don't get the impression that anyone here has any misconceptions abouot this stuff, but for people wandering through and seeing this thread, I want to make sure that common misconceptions are cleared up.
Just wanted to say that I'm actually completely on board with archiving submissions with their respective license files; it's just something that will take a big effort to implement and will likely be bug prone for a while, so it's something I can't really touch until I have more time.
Consider this edge case: Someone submits a bunch of art with one license, and a week later, they go back and remove that license and add a different one. There are two ways this could be handled, and both are ugly:
Keep uncompressed copies of every file on the site, along with the compressed ones. This would increase space usage by a good 50% or so, and space is already at a premium.
Uncompress the archive file into a temp directory, remove the license file, add a new license file, and then recompress the archive, which is time-consuming and kind of complicated.
There's also the matter of "I submitted this zip file, so why can't you just put the license in that file, rather than zipping up the license and my zip file inside another zip file?" I mean, yeah, it would make sense to slip the license files into existing archives, but that would add another layer of complexity.
And these are just the issues that I'm anticipating right now when I'm typing this up. :)
Anyway, like I said, I want to address this, but it would open up a host of issues that I don't have time to deal with at the moment. Also note that if you go to your downloads tab, you can download a credits file that lists each and every thing you've downloaded, along with all the files that were contained in the submission, the author, the attribution notice, and the license(s), which I think addresses this to at least some extent.
So, your mention of the burn tool actually brings up an interesting line of discussion. There are a set of "rules" for what makes something pixel art, which can generally be distilled down to "you should know why each and every pixel is the precise color that it is."
Rules like this generally aren't arbitrary (and it's not like there's some Pixel Art Commission out there deciding what is and isn't pixel art), and they often come to be due to the fact that following those rules tends to produce better results or help you avoid issues later on.
That being said, as an artist, your goal is to produce the best possible art for your game in the time that you have. So if the burn tool works for you and it speeds up your process, then there's nothing wrong with continuing to use it, particularly since your use of it so far hasn't caused any visible issues. Your art doesn't have to conform to an exact set of processes in order to be good.
Now, there's a big caveat here for other people who might be reading this: If you're a beginning artist, you should be aware that the rules are there to help you, and to also to help others help you. If you're new to art in general, it's a good idea to follow the "rules" of whatever art form you're working on, because those rules help you avoid making beginner mistakes. When you reach KiEN's skill level, you're probably safe breaking the rules, provided you know why you're doing so. In OP's case, using the burn tool is a shortcut that allows more art to be produced faster with little or no sacrifice in final quality. In general, if "that's my style" is your reason for breaking a rule, then you probably shouldn't be breaking that rule until you've mastered a "style" that involves following the rules.
He looks delightfully evil.
Hey, just wanted to let you guys know that I follow this thread, and I admire your dedication to a frequent release schedule and creating content. Keep it up. :)
The trouble with explicitly stating that the preview images must fall under the same license as the actual files is that that might not be true for some older preview images, and it's impossible to know which ones that doesn't apply to. caeles points to a completely legitimate edge case.
We already have a rule that the preview images have to reflect what's in the actual content, but I prefer that this be kept a judgement call rather than an absolute hard and fast requirement. The key is to avoid misleading previews.
Furthermore, I would actually kind of prefer that the preview images not be freely licensed, unless the author explicitly says they are. When I get around to preserving the pages of deleted content, I want to be able to preserve the preview images so that people can identify what the content was, and if the preview images themselves are freely licensed, then in many cases that's essentially the same as allowing people to download the originals against the artist's wishes. (Note: I also plan to watermark the images on deleted content and perhaps do some other processing so as to make them otherwise impractical to use).
Flagging license issues is something I really hate having to do, particularly since a lot of time if it happens on someone's first post, they just abandon it and never come back. I really would prefer to avoid adding additional situations where it would be necessary to do that. I'd much rather tell people that preview images are all rights reserved unless otherwise noted.
You mentioned in the other thread that you might be willing to rewrite the relevant changes to the FAQ yourself. which is something I'm not going to have time to do this week. If you can do that, I'll look over them and then merge the changes in.
Hi. I don't have enough spare cycles at the moment to come up with my own writing, but if you're willing to rewrite the relevant sections (with the changed bits in bold so that I can revirew them), I'll take a look and try to merge the changes into the FAQ.
Translated:
Problems are everywhere . try to be honest and respectful to one's own work and that of others . Sorry about the link below. I do not know how to remove it .
@Snabisch: What link are you talking about? I'm not seeing any.
So, a quick note, because we've had issues with this in the past:
I don't get the impression that anyone here has any misconceptions abouot this stuff, but for people wandering through and seeing this thread, I want to make sure that common misconceptions are cleared up.
Just wanted to say that I'm actually completely on board with archiving submissions with their respective license files; it's just something that will take a big effort to implement and will likely be bug prone for a while, so it's something I can't really touch until I have more time.
Consider this edge case: Someone submits a bunch of art with one license, and a week later, they go back and remove that license and add a different one. There are two ways this could be handled, and both are ugly:
There's also the matter of "I submitted this zip file, so why can't you just put the license in that file, rather than zipping up the license and my zip file inside another zip file?" I mean, yeah, it would make sense to slip the license files into existing archives, but that would add another layer of complexity.
And these are just the issues that I'm anticipating right now when I'm typing this up. :)
Anyway, like I said, I want to address this, but it would open up a host of issues that I don't have time to deal with at the moment. Also note that if you go to your downloads tab, you can download a credits file that lists each and every thing you've downloaded, along with all the files that were contained in the submission, the author, the attribution notice, and the license(s), which I think addresses this to at least some extent.
Are you using references?
So, your mention of the burn tool actually brings up an interesting line of discussion. There are a set of "rules" for what makes something pixel art, which can generally be distilled down to "you should know why each and every pixel is the precise color that it is."
Rules like this generally aren't arbitrary (and it's not like there's some Pixel Art Commission out there deciding what is and isn't pixel art), and they often come to be due to the fact that following those rules tends to produce better results or help you avoid issues later on.
That being said, as an artist, your goal is to produce the best possible art for your game in the time that you have. So if the burn tool works for you and it speeds up your process, then there's nothing wrong with continuing to use it, particularly since your use of it so far hasn't caused any visible issues. Your art doesn't have to conform to an exact set of processes in order to be good.
Now, there's a big caveat here for other people who might be reading this: If you're a beginning artist, you should be aware that the rules are there to help you, and to also to help others help you. If you're new to art in general, it's a good idea to follow the "rules" of whatever art form you're working on, because those rules help you avoid making beginner mistakes. When you reach KiEN's skill level, you're probably safe breaking the rules, provided you know why you're doing so. In OP's case, using the burn tool is a shortcut that allows more art to be produced faster with little or no sacrifice in final quality. In general, if "that's my style" is your reason for breaking a rule, then you probably shouldn't be breaking that rule until you've mastered a "style" that involves following the rules.
Pages