-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Introducing a brief explanation of image license #1316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
How about a (?) link at the right of the selection gadget, that opens a page on our Wiki or https://commons.wikimedia.org/wiki/Commons:First_steps/License_selection in the user's language? |
@nicolas-raoul that sounds great! I'll start working on it :) |
@gupta-meghna64 I am already working on a class that would fetch a token for a url based on the language selected by the user. You can continue from there. It will save time. |
@nicolas-raoul how do I retrieve the user's language? Should there be an option of selecting the language from a list on clicking info icon or some other way? |
@gupta-meghna64 How about just something like Locale.getDefault().getLanguage();? |
That sounds like a great idea @nicolas-raoul |
I will start working on this issue as a part of #274 |
@tanvidadu Sounds good. :) |
After thinking more about this, I believe that license choice is important enough to have its own activity, which would explain each license with proper sentences. I believe the best would be to do like OpenArchive's app which, rather than asking for a license, asks the user what permissions they agree to let: The scale is much bigger so it could be a phase 2 in a different issue, though. |
Summary
There should be a brief explanation of the licenses of images in the application to prevent the user from randomly choosing any license.
For example-
There should be an explanation about:
Commons app version
Commons 2.6.7
Would you like to work on the issue?
Yes!
It would be great if everyone could give their suggestions on how to go about this and what all can be done to make the best fix :)
The text was updated successfully, but these errors were encountered: