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.
I figured it might be better to keep this in the same thread?
Correct. Thread necromancy is impossible here: if there is more content to share on a given topic, then the topic isn't actually dead. Sharing the new content isn't resurrecting it.
If a topic is locked, it's dead, but then resurrecting it by making another post isn't possible.
The first question is: what are your players using the screenshots/footage for?
In all likelihood, those screenshots are covered by fair-use, but that's assuming they're not planning to make their own game from the screenshots. Blogs and let's-play videos (even commercial ones) are generally considered fair use, but it's still up to the blogger/twitch-streamer/YouTuber to make that determination, not you. I will say that CC-BY et al is almost certainly less risky for such 3rd party content creators than ANY proprietary licensed content such as the stuff in AAA commercial games. So if they are making content from Minecraft gameplay footage, making the same or similar content from your game that uses CC-BY(-SA) is even safer for them.
Fair-Use aside, yes your players would have to give proper attribution to all the appropriate artists for any screenshots or footage they use in a non-fair-use context. However, it is not your responsibility to patrol what other people do with assets you also happen to use. If you follow the terms of the license, but your players violate copyright, you won't get in trouble for it. They will. You aren't encouraging them to violate copyright just by (properly) using assets.
I can't speak about proprietary licenses. They're all different so no generalized information provided here would apply to such licenses or EULAs.
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.
Correct. Thread necromancy is impossible here: if there is more content to share on a given topic, then the topic isn't actually dead. Sharing the new content isn't resurrecting it.
If a topic is locked, it's dead, but then resurrecting it by making another post isn't possible.
Thanks for the update!
The first question is: what are your players using the screenshots/footage for?
In all likelihood, those screenshots are covered by fair-use, but that's assuming they're not planning to make their own game from the screenshots. Blogs and let's-play videos (even commercial ones) are generally considered fair use, but it's still up to the blogger/twitch-streamer/YouTuber to make that determination, not you. I will say that CC-BY et al is almost certainly less risky for such 3rd party content creators than ANY proprietary licensed content such as the stuff in AAA commercial games. So if they are making content from Minecraft gameplay footage, making the same or similar content from your game that uses CC-BY(-SA) is even safer for them.
Fair-Use aside, yes your players would have to give proper attribution to all the appropriate artists for any screenshots or footage they use in a non-fair-use context. However, it is not your responsibility to patrol what other people do with assets you also happen to use. If you follow the terms of the license, but your players violate copyright, you won't get in trouble for it. They will. You aren't encouraging them to violate copyright just by (properly) using assets.
I can't speak about proprietary licenses. They're all different so no generalized information provided here would apply to such licenses or EULAs.
@JORAX: Credited where?
Pages