There should be no hashmarks in the tags. It makes them unsearchable. They are not related to twitter tags. Additionally, tags like "Game" and "music" are kind of pointless. Everything on the site is for games, and this asset is already categorized as music.
Party_lollipop and Lolipop_chiptune seem like they go well together. Why not have them as one submission with two songs?
The attribution notice you have: "...just don't change the document and obviously don't register it as yours..." What document? The file type? Please know that CC0 allows people to change the song in any way they wish, including the removal or alteration of metadata. That condition is essentially unenforcable. Would you be willing to alter or remove that part to avoid confusion? Until then, I have to disable downloads to prevent people from using this file in a way you may not approve of. The same applies to https://opengameart.org/content/lollipop-chiptune
Ouch! So you definitely are familiar with this pain. I would like to say "come help! We need your skills", but I doubt you want to do more of your day job as hobby volunteer work. Death's Darling (aka ElizaWy) is making some pretty big strides on a replacement OGA framework (PHP, but not Drupal), so if you are interested, we'll meet up and talk about next steps. No pressure though.
What I meant was, the difficulty lies in the entanglement of outdated framework needing outdated PHP. There is nothing I am aware of about the server hardware/OS that prevents modern PHP versions from being used, but this statement...
"it probably wouldn't be too hard to replace Drupal's internal mail functionality with something more up-to-date without fully upgrading Drupal."
... is incorrect, unfortunately. Modern PHP breaks nearly every part of drupal 7 and the modules it uses. It is filled with deprecated functions and now-forbidden datatype uses. Replacing just the mail functionality would still leave every other part of the site busted. We can't tell the mail functionality to use PHP 7+, but tell everything else to keep using PHP 5. Which means all parts of the site have to be overhauled to work with modern PHP, or the whole site has to keep using outdated PHP.
"Your title and preview images must be descriptive of the content you actually uploaded. Specifically, if what you uploaded is a sample of a larger pack, the preview image must describe the art you actually uploaded to OGA, and not the additional art that you are advertising. It is fine to link to the larger pack in your description."
Unfortunately, saying "Not everything appears in images is present on asset pack." is not sufficient. Either the content missing from the preview must be added to the download, or any content not present in the download must be removed from the preview here.
Please use an audio file as the first preview file. People are unable to listen to an image saying "free RPG piano music" to determine if they want to download the music.
Also, if you are requiring attribution, you may want to consider a license other than CC0 as it is the only license that cannot require attribution. OGA-BY is as free as it gets while still requiring attribution.
If attribution is not a requirement for you, then there is no need to change the license, but please add some clarification to the attribution instructions to indicate credit is not mandatory.
That's probably in there as well. Upgrading PHP would enable TSL stuff, but it would also break EVERYTHING else until we get the rest of it updated. Also, yes we're aiming for an OGA that isn't neccessarily Drupal at all. More of a replacement + migrate data than an upgrade.
"...unless you're just using really outdated servers installations..."
Bingo. Well, maybe not outdated server hardware/OS, but the OGA framework is drupal 7. The current drupal version available is 10.2. There is no upgrade path from 7 to current, and certainly no simple update with the massive database and custom modules. TLS 1.3 didn't exist when drupal 7 was built, much less the consideration to incorporate it into drupal's emailing system.
Also, @dejonge2 there isn't really a reason you won't be able to post here again. You can log in with your username and the password you picked. You won't be able to change your password nor get any notifications via email because of the temporary email used, but that doesn't stop you from logging in now that you're registered.
Added a warning on the registration page. See image below. Verbiage suggestions welcome. Hopefully this will serve as a stop-gap for now. I can always rename your nick to the one you really wanted in the event it becomes unaccessible due to this issue.
EDIT: Issue is fixed, warning removed from registration page.
Nice tune. I like it.
A few issues, though:There should be no hashmarks in the tags. It makes them unsearchable. They are not related to twitter tags. Additionally, tags like "Game" and "music" are kind of pointless. Everything on the site is for games, and this asset is already categorized as music.The attribution notice you have: "...just don't change the document and obviously don't register it as yours..." What document? The file type? Please know that CC0 allows people to change the song in any way they wish, including the removal or alteration of metadata. That condition is essentially unenforcable. Would you be willing to alter or remove that part to avoid confusion? Until then, I have to disable downloads to prevent people from using this file in a way you may not approve of. The same applies to https://opengameart.org/content/lollipop-chiptuneEDIT: Fixed, thanks! :)
Bumped for new content.
Ouch! So you definitely are familiar with this pain. I would like to say "come help! We need your skills", but I doubt you want to do more of your day job as hobby volunteer work. Death's Darling (aka ElizaWy) is making some pretty big strides on a replacement OGA framework (PHP, but not Drupal), so if you are interested, we'll meet up and talk about next steps. No pressure though.
What I meant was, the difficulty lies in the entanglement of outdated framework needing outdated PHP. There is nothing I am aware of about the server hardware/OS that prevents modern PHP versions from being used, but this statement...
... is incorrect, unfortunately. Modern PHP breaks nearly every part of drupal 7 and the modules it uses. It is filled with deprecated functions and now-forbidden datatype uses. Replacing just the mail functionality would still leave every other part of the site busted. We can't tell the mail functionality to use PHP 7+, but tell everything else to keep using PHP 5. Which means all parts of the site have to be overhauled to work with modern PHP, or the whole site has to keep using outdated PHP.
Those previews are great,
but I believe what Basto is saying is; the preview needs to accurately reflect what people are downloading here.Per site submission guidelines:Unfortunately, saying "Not everything appears in images is present on asset pack." is not sufficient. Either the content missing from the preview must be added to the download, or any content not present in the download must be removed from the preview here.EDIT: Fixed, thanks! :)
Please use an audio file as the first preview file. People are unable to listen to an image saying "free RPG piano music" to determine if they want to download the music.Also, if you are requiring attribution, you may want to consider a license other than CC0 as it is the only license that cannot require attribution. OGA-BY is as free as it gets while still requiring attribution.If attribution is not a requirement for you, then there is no need to change the license, but please add some clarification to the attribution instructions to indicate credit is not mandatory.EDIT: Fixed, thanks! :)
That's probably in there as well. Upgrading PHP would enable TSL stuff, but it would also break EVERYTHING else until we get the rest of it updated. Also, yes we're aiming for an OGA that isn't neccessarily Drupal at all. More of a replacement + migrate data than an upgrade.
Bingo. Well, maybe not outdated server hardware/OS, but the OGA framework is drupal 7. The current drupal version available is 10.2. There is no upgrade path from 7 to current, and certainly no simple update with the massive database and custom modules. TLS 1.3 didn't exist when drupal 7 was built, much less the consideration to incorporate it into drupal's emailing system.
Also, @dejonge2 there isn't really a reason you won't be able to post here again. You can log in with your username and the password you picked. You won't be able to change your password nor get any notifications via email because of the temporary email used, but that doesn't stop you from logging in now that you're registered.
Added a warning on the registration page. See image below. Verbiage suggestions welcome. Hopefully this will serve as a stop-gap for now. I can always rename your nick to the one you really wanted in the event it becomes unaccessible due to this issue.EDIT: Issue is fixed, warning removed from registration page.
Pages