Both threads discuss text excerpts that do not exist in today's http://www.google.com/intl/en/sketchup/3dwh/tos.html document. Section 8.2. of the document clearly states that re-distribution and modifications outside of 3D Warehouse is prohibited.
With the exception of Content generated by you, you may not modify, rent, lease, loan, sell, distribute or create derivative works based on this Content (either in whole or in part) unless you have been specifically told that you may do so by Google or by the owners of that Content, in a separate agreement.
(1) The "preferred form for making modifications" part of the GPL (with respect to art) is at best vague and at worst completely unenforceable.
"preferred form for making modifications" is also vague for code. Vague is good, because it can include technologies and practices that do not yet exist. Somehow it appears to be clear however, that "preferred form for making modifications" for example means non-obfuscated code. Whether this also means that comments which help understand derivative GPL code may not be stripped and whether having to provide a revision control history of derivative GPL code - when it exists - can be challenged by the owners of the original GPL code and ultimately clarified in court.
For example, let's say someone makes a midi file and uploads it to the site. Someone else (who may not have access to mixing software or even a computer at the time of recording) takes the midi file and records themselves playing an accompaniment to it.
To compare to a code situation: what if you take a compiled GPL program and start making binary modifications to it using a hex editor? The case becomes uncommon and the interpretation of "preferred form for making modifications" becomes unclear to many (including me). I would assume that the source code of the binary and documentation on how the binary was changed might be enough.
Of course modifying 'object code' is much more commen in digital art, which often makes the requirements non-obvious.
So now you have an audio file that's a live instrument with the midi playing in the background. What's the preferred form for making modifications? Can the GPL be construed to prevent this sort of modification?
The preferred form for making modifications would have to be determined. This would most likely make creators of derivative works ask the GPL original owners and/or other creators of such works for clarification what would be considered the preferred form. By that I mean not that they should ask "I want to edit this: how do I have to edit it and what do I need to provide as the preferred form for making modifications" but instead "I edited this art in such and such way. What is considered to be the preferred form for making modifications?"
If the GPL [...] doesn't prevent modifications like this, then the clause about preserving a perferred form for modifications just gives the original rights holder a false sense of security.
The clause does not mean "you may only use methods which leave access to the most preferrable form of making modifications". It means "when providing derivative works, you need to provide the preferrable form of making modifications". What that is, depends on the methods.
In either case, this sort of ambiguity makes the GPL a non-optimal choice as an art license.
The ambiguity allows for works to be used and edited in ways that have not been considered or have not been konwn to the authors of the GPL and to the owners of the GPLed original work.
That being said...
I consider the GPL to be non-marketable to many artists because there is no preamble that speaks to creators of works other than software (because the word "software" is used all over the preamble) and because there is no "How to Apply These Terms to Your New Digital Art" information (there is one for code at the end of the license page).
On the other hand there is no other sophisticated strong copyleft (strong meaning that the preferred form for making modifications has to be provided) alternative, which makes GPL clearly useful to those artists who want this requirement.
To confirmation of the statement "The GPL and LGPL aren't appropriate licenses for art." kind of devalues the licensing choise of the users that pick it.
If OGA's position is that GPL is not a license in the interest of artists, then there should be a warning or the option to chose it even disabled.
"(now covered by CC-BY-SA 3.0)" sounds like in version 2.5 and earlier there was not SA option (I guess just removing the version number will solve that)
(2) That isn't a mistake, just poor phrasing on my part. What I was getting at is that if someone wants to license their work under the MIT license, which isn't an available selection, just select the GPL and then note in the comments that they're also releasing the work under the MIT license.
Please change "GPL" to "MIT". I understand this will make the phrasing clear?
I agree that there is constant resistance against using GPL for art and that its wording is hard to accept to be applicable to non-software.
The statement that CC-BY-SA 3 replaces the spot which GPL fills, is incorrect, as CC-BY-SA 3 has no requirement that the preferred form for making modifications is provided, while GPL does.
2. The statement """under another license (such as the GPL) that's not included among the options. """ is incorrect, as the GPL (v2/v3) is available. Unless GPLv1 is meant.
I have no art education. To me the line between intended concept art and potential story backdrop or potential character portrait varies on the work.
I like this mockup (I hope this term works as a replacement for "mock in game screen shot"?) and OGA needs more mockups. It might get complicated to ensure license and attribution requirements are met when different sources are mixed. But still: yay mockups!
This appears to be a mockup and might be better suited in "documents" as in "this is a graphic to be used in a game design document, not in a game". Concept art to me is either art usable as story images/backdrops or portraits. This one is not, due to the UI elements in it.
It could be used as a static image on an gaming device screen in games, although looking at the description, it doesn't seem to be the intention.
Are all the graphical elements by you? If not, I assume the other authors agreed to sharing this under CC0/PD on OGA? :)
This submission would definitely be more useful with a layered, lossless image provided. Perhaps it would be useful to have the flash source as well, if you don't oppose sharing those.
Thanks, just in case: you can edit your submission and replace files/previews (see tabs top left).
You are absolutely welcome to upload more sounds. Either by extending this submission and updating the preview or uploading new submissions. I personally discourage uploading single sounds when you have many to share, as the OGA search/browse interface is better suited for packs of short sounds.
Both threads discuss text excerpts that do not exist in today's http://www.google.com/intl/en/sketchup/3dwh/tos.html document. Section 8.2. of the document clearly states that re-distribution and modifications outside of 3D Warehouse is prohibited.
I recommend that you carefully read the license.
Please try to use one post per reply.
The terms prohibit re-distribution and modifications outside of 3D Warehouse.
The terms permit re-distribution and modifications only inside of 3D Warehouse.
Incorrect. Please read again.
"[...] on or through, the Services."
Please link to your sources.
"preferred form for making modifications" is also vague for code. Vague is good, because it can include technologies and practices that do not yet exist. Somehow it appears to be clear however, that "preferred form for making modifications" for example means non-obfuscated code. Whether this also means that comments which help understand derivative GPL code may not be stripped and whether having to provide a revision control history of derivative GPL code - when it exists - can be challenged by the owners of the original GPL code and ultimately clarified in court.
To compare to a code situation: what if you take a compiled GPL program and start making binary modifications to it using a hex editor? The case becomes uncommon and the interpretation of "preferred form for making modifications" becomes unclear to many (including me). I would assume that the source code of the binary and documentation on how the binary was changed might be enough.
Of course modifying 'object code' is much more commen in digital art, which often makes the requirements non-obvious.
The preferred form for making modifications would have to be determined. This would most likely make creators of derivative works ask the GPL original owners and/or other creators of such works for clarification what would be considered the preferred form. By that I mean not that they should ask "I want to edit this: how do I have to edit it and what do I need to provide as the preferred form for making modifications" but instead "I edited this art in such and such way. What is considered to be the preferred form for making modifications?"
The clause does not mean "you may only use methods which leave access to the most preferrable form of making modifications". It means "when providing derivative works, you need to provide the preferrable form of making modifications". What that is, depends on the methods.
The ambiguity allows for works to be used and edited in ways that have not been considered or have not been konwn to the authors of the GPL and to the owners of the GPLed original work.
That being said...
I consider the GPL to be non-marketable to many artists because there is no preamble that speaks to creators of works other than software (because the word "software" is used all over the preamble) and because there is no "How to Apply These Terms to Your New Digital Art" information (there is one for code at the end of the license page).
On the other hand there is no other sophisticated strong copyleft (strong meaning that the preferred form for making modifications has to be provided) alternative, which makes GPL clearly useful to those artists who want this requirement.
To confirmation of the statement "The GPL and LGPL aren't appropriate licenses for art." kind of devalues the licensing choise of the users that pick it.
If OGA's position is that GPL is not a license in the interest of artists, then there should be a warning or the option to chose it even disabled.
"(now covered by CC-BY-SA 3.0)" sounds like in version 2.5 and earlier there was not SA option (I guess just removing the version number will solve that)
Please change "GPL" to "MIT". I understand this will make the phrasing clear?
If this is the worng place to initiate this discussion, please delete or tell me to delete this post.
1. I disagree with the GPL/LGPL statement.
FSF approves of GPL for non-software http://www.gnu.org/philosophy/nonsoftware-copyleft.html . DFCW (used as Wikimedia file license guidelines) approves of GPL for works: http://freedomdefined.org/Licenses
I agree that there is constant resistance against using GPL for art and that its wording is hard to accept to be applicable to non-software.
The statement that CC-BY-SA 3 replaces the spot which GPL fills, is incorrect, as CC-BY-SA 3 has no requirement that the preferred form for making modifications is provided, while GPL does.
2. The statement """under another license (such as the GPL) that's not included among the options. """ is incorrect, as the GPL (v2/v3) is available. Unless GPLv1 is meant.
Thank you very much for replying so extensively!
I have no art education. To me the line between intended concept art and potential story backdrop or potential character portrait varies on the work.
I like this mockup (I hope this term works as a replacement for "mock in game screen shot"?) and OGA needs more mockups. It might get complicated to ensure license and attribution requirements are met when different sources are mixed. But still: yay mockups!
To me, the concept of mockups seem more related to game design documents than to concept art. On the other hand, the documents section here http://opengameart.org/art-search-advanced?keys=&field_art_type_tid%5B%5D=11 is chaotic.
I look forward to the individual assets!
This appears to be a mockup and might be better suited in "documents" as in "this is a graphic to be used in a game design document, not in a game". Concept art to me is either art usable as story images/backdrops or portraits. This one is not, due to the UI elements in it.
It could be used as a static image on an gaming device screen in games, although looking at the description, it doesn't seem to be the intention.
Are all the graphical elements by you? If not, I assume the other authors agreed to sharing this under CC0/PD on OGA? :)
This submission would definitely be more useful with a layered, lossless image provided. Perhaps it would be useful to have the flash source as well, if you don't oppose sharing those.
Thanks, just in case: you can edit your submission and replace files/previews (see tabs top left).
You are absolutely welcome to upload more sounds. Either by extending this submission and updating the preview or uploading new submissions. I personally discourage uploading single sounds when you have many to share, as the OGA search/browse interface is better suited for packs of short sounds.
Also yay for 7z!
These sounds are awesome!
This appears to be a .rar inside a .zip. Is there a purpose to this?
Previews need to be freely licensed. As cool as the preview is, unless everything in it is freely licensed, please replace it (you can use this: http://www.mediafire.com/?ca85iri7smxgerh - made with https://github.com/qubodup/ogatools/blob/master/montage-sfx )
Hi,
Please read the licenses or translations of them:
gpl3 http://www.viti.es/gnu/licenses/gpl.html
cc0 http://creativecommons.org/publicdomain/zero/1.0/deed.es_ES (summary, press "Código Legal" to see the license)
ccbysa3 http://creativecommons.org/licenses/by-sa/3.0/es/ (summary, press "Código Legal" to see the license)
ccby3 http://creativecommons.org/licenses/by/3.0/es/ (summary, press "Código Legal" to see the license)
I'd suggest googling translations of gpl2, lgpl3 and lgpl 2.1
Pages