@hernandack: yes, I'm also not terribly familiar with drupal. We could switch to another framework, but we definitely need a robust CMS framework at the very least. OGA is big and complicated; lots of file types, lots of widgets to get images and thumbnails auto-converted, etc. Drupal is such a CMS framework, and switching to another CMS has no guarantee of being any more familiar to more users. We also know that the current data is organized in such a way that migrating from Drupal to Drupal is going to be easier than migrating from, say, Drupal to Joomla or something. I'm not saying we won't be changing to some other framework. Just that I don't know of a superior alternative at this time, despite my own unfamiliarity with it. I am looking forward to exploring drupal 8 though! :)
We are certainly looking for interested people who would like to help out with both coding as well as UI design and even sql data migration. If you're interested in helping out, drop us a line!
@bonsaiheldin: agreed. more transparency = more understanding. I can't speak to the patreon stuff since I don't have any dealings with that, but I like the code being openly available as a start. The current OGA2 code being available is definitely useful since it allows coders to see how the code currently operates, which informs how the code could operate (or should be fixed) in OGA3 code.
OGA does currently have a code of conduct already: No discussion of religion. No discussion of politics, except relating directly to copyright, the Creative Commons, and/or FOSS. Don't be racist, homophobic, or otherwise hateful. More details on the FAQ, but this is intentionally very simple. Bart feels (and I agree) that adding a bunch of specificity doesn't actually prevent additional offense and often serves to promote people trying to find edge-case loopholes where they push the envelope to see just how far they can go without getting banned. While enforcing the rule "Don't be racist, homophobic, or otherwise hateful" makes more specific rules superfluous. (like "don't be ableist, don't use covert anti-semitic hatespeech signals, don't use microagressions to make backhanded insults" which are far more difficult to accurately define) Most users violating the CoC do not do so because we didn't have one or because they weren't aware of its existence, so I am not sure if a more formalized CoC would prevent much. However, it may be worth exploring a way to make this CoC more prominent to new users in the new verstion of the site. :)
Having more people manage the various social presentations of OGA as well as the day-to-day administration of the site is a good idea, and we're well on our way toward that end: OGA's social media accounts are being extended to a few select volunteers. For starters, the OGA GitHub is now official and active (Thanks AntumDeluge and Botanic!)
This is more of a tileset ("2D art") than it is a texture, though. Also, I am not the author of the superpowers assets. I am just the gal who shared it here on OGA. Sparklin Labs is the author as indicated in the description and attribution notice of the submission you've linked to. :)
Some of the tags you've used are redundant though and may actually hinder people finding these assets. There is no need to tag this as "sound", "effect", "sound effects", "sfx", "sfx pack", "pack", or "collection". Such tags are routinely deleted. It is already in the "sound effect" category. See https://opengameart.org/content/art-tags for effective tagging tips.
@hernandack: yes, I'm also not terribly familiar with drupal. We could switch to another framework, but we definitely need a robust CMS framework at the very least. OGA is big and complicated; lots of file types, lots of widgets to get images and thumbnails auto-converted, etc. Drupal is such a CMS framework, and switching to another CMS has no guarantee of being any more familiar to more users. We also know that the current data is organized in such a way that migrating from Drupal to Drupal is going to be easier than migrating from, say, Drupal to Joomla or something. I'm not saying we won't be changing to some other framework. Just that I don't know of a superior alternative at this time, despite my own unfamiliarity with it. I am looking forward to exploring drupal 8 though! :)
We are certainly looking for interested people who would like to help out with both coding as well as UI design and even sql data migration. If you're interested in helping out, drop us a line!
@bonsaiheldin: agreed. more transparency = more understanding. I can't speak to the patreon stuff since I don't have any dealings with that, but I like the code being openly available as a start. The current OGA2 code being available is definitely useful since it allows coders to see how the code currently operates, which informs how the code could operate (or should be fixed) in OGA3 code.
OGA does currently have a code of conduct already: No discussion of religion. No discussion of politics, except relating directly to copyright, the Creative Commons, and/or FOSS. Don't be racist, homophobic, or otherwise hateful. More details on the FAQ, but this is intentionally very simple. Bart feels (and I agree) that adding a bunch of specificity doesn't actually prevent additional offense and often serves to promote people trying to find edge-case loopholes where they push the envelope to see just how far they can go without getting banned. While enforcing the rule "Don't be racist, homophobic, or otherwise hateful" makes more specific rules superfluous. (like "don't be ableist, don't use covert anti-semitic hatespeech signals, don't use microagressions to make backhanded insults" which are far more difficult to accurately define) Most users violating the CoC do not do so because we didn't have one or because they weren't aware of its existence, so I am not sure if a more formalized CoC would prevent much. However, it may be worth exploring a way to make this CoC more prominent to new users in the new verstion of the site. :)
Having more people manage the various social presentations of OGA as well as the day-to-day administration of the site is a good idea, and we're well on our way toward that end: OGA's social media accounts are being extended to a few select volunteers. For starters, the OGA GitHub is now official and active (Thanks AntumDeluge and Botanic!)
Nice!
This is more of a tileset ("2D art") than it is a texture, though. Also, I am not the author of the superpowers assets. I am just the gal who shared it here on OGA. Sparklin Labs is the author as indicated in the description and attribution notice of the submission you've linked to. :)thanks. :)
Nice. I would like to verify its origin, if I may. Where can the original texture be found on the web?
The preview is nice, but why haven't you included the song itself for download? I can't listen to a jpg. :P
This is more music than sound effect, isn't it? It should be in the "Music" art type.
This is more music than sound effect, isn't it? It should be in the "Music" art type.
This is more music than sound effect, isn't it? It should be in the "Music" art type.
Why is this in the 2D art category?:)
not bad. :)
Some of the tags you've used are redundant though and may actually hinder people finding these assets. There is no need to tag this as "sound", "effect", "sound effects", "sfx", "sfx pack", "pack", or "collection". Such tags are routinely deleted. It is already in the "sound effect" category.See https://opengameart.org/content/art-tags for effective tagging tips.Pages