You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no stated licence in the gallery, so users have to ask to use them (if they have any notion of copyright), i think it should be better to state a cc licence on those, not sure how to handle that, since those images come from various people, i guess we should list them there, and check every author for an useful licence (cc-by for such thing?), and (sadly) get ride of the ones we can't get a permission for (unable to contact people or so).
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1377037-gallery-image-licences?utm_campaign=plugin&utm_content=tracker%2F43807&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F43807&utm_medium=issues&utm_source=github).
The text was updated successfully, but these errors were encountered:
We could have a notice in the footer or somewhere that all content on this site is MIT licensed unless stated otherwise, and only add license mentions for content that has a different license, like in the case of a screenshot from a proprietary app.
There is no stated licence in the gallery, so users have to ask to use them (if they have any notion of copyright), i think it should be better to state a cc licence on those, not sure how to handle that, since those images come from various people, i guess we should list them there, and check every author for an useful licence (cc-by for such thing?), and (sadly) get ride of the ones we can't get a permission for (unable to contact people or so).
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1377037-gallery-image-licences?utm_campaign=plugin&utm_content=tracker%2F43807&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F43807&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: