minetest / minetest.github.io

Official Minetest website hosted by Github Pages
https://www.minetest.net/
MIT License
120 stars 63 forks source link

Fix issues with gallery + readd MTG + add figcaptions #255

Closed rubenwardy closed 2 years ago

rubenwardy commented 2 years ago

image

sfan5 commented 2 years ago

This breaks the URLs in the appdata file: https://github.com/minetest/minetest/blob/master/misc/net.minetest.minetest.appdata.xml#L55-L63

sfan5 commented 2 years ago

Also look at image compression, mineclone2.jpg is way too big.

rubenwardy commented 2 years ago

Gallery file determines order

appgurueu commented 2 years ago

Gallery file determines order

Right, then why not rename images 1, 2 & 3 to sensible names as well?

sfan5 commented 2 years ago

So, what about the licenses? Either a screenshot is licensed according to all of its parts or showing off the broad parts of engine functionality is fair use regardless of licenses. If we believe the first to be right then the following should be figured out:

Personally I agree with the fair use interpretation, though the person who took the screenshot still has a right to it (or do they?).

For the old MTG screenshots it looks like texture licenses were briefly checked: https://github.com/minetest/minetest.github.io/pull/143#issuecomment-424419075


By the way, soothing32.jpg has a row of black pixels at the top. Should be fixed or re-done.

Right, then why not rename images 1, 2 & 3 to sensible names as well?

The 1, 3 and 5.jpg URLs need to stay valid because they're linked from the appdata file. So I'd rather have them all numbered.

kilbith commented 2 years ago

so does i3.jpg

This is RPG16 used there, which applies for all item textures.

Are you mad because we don’t show off bare MTG enough for you ? 🤔

appgurueu commented 2 years ago

Either a screenshot is licensed according to all of its parts

This would be the safest approach: When rigorously following this you can't possibly get into any license issues. Technically a screenshot might be considered a derivative work of the texture pack & mod textures seen within it and thus would have to abide by their respective licenses. It's quite tedious though to track down all the licenses.

showing off the broad parts of engine functionality is fair use regardless of licenses

According to this site we're probably good to go:

If screenshots of these materials are transformative, or if they depict a small part of an overall work, and don’t act as a substitute for the original, there’s a good chance your screenshot is legal. However, if the law determines your screenshot to be outside of fair use, you may face legal ramifications.

If following this, don't include any false licenses, but rather provide attribution by pointing to the source - fair use doesn't provide a right to relicense content.

sfan5 commented 2 years ago

The black row of pixels in 2.jpg is still there, cropping works but might be better to re-do the screenshot in 1080p anyway.