Fri, Oct 12
Vicuna does this, and it is vital.
It should absolutely be implemented in the upload wizard too.
Sep 13 2018
Aug 22 2018
Thanks everyone! :-)
Aug 9 2018
Jul 20 2018
Jul 3 2018
Jun 15 2018
Jun 13 2018
Pull request merged, thanks! It should be released in 2.9
Jun 12 2018
May 31 2018
May 22 2018
May 14 2018
May 8 2018
Here is a long list of images that are often used as stub/portal/etc icons, and can thus be considered as unrelated to the topic of the article: https://www.wikidata.org/w/index.php?title=User:Magnus_Manske/FIST_icons&action=raw
It is kept up-to-date by FIST/WDFIST users, including me :-)
May 2 2018
@Edgars2007: Yes, looks great! The only problem is that its data has not been updated since May 2017.
May 1 2018
Apr 3 2018
Mar 28 2018
Mar 27 2018
Any microtask you performed on the Commons mobile app maybe?
Or if not, on other Wikimedia software?
Mar 26 2018
I don't think "Add and implement option download metadata to a separate .txt, .xml or .json file" is really needed on mobile.
it's sub-categories -> its sub-categories
Mar 22 2018
Is there any difference between "Improvements based on the feedback received from mentors, other community members, Testing, Bug fixes, Writing documentation. Release app in Google play (at least in alpha)" and "Phase I evaluation"?
Is there a reason why Phase II is in the opposite order?
Mar 21 2018
@Diddypod I don't think anonymous users can upload pictures?
Mar 20 2018
The UI sounds reasonable.
Mar 15 2018
Familiarising featured images scrollable activity -> Familiarizing myself with the featured images scrollable activity
There are two "Review 1"
The link "Pull down gesture removal for Map View" seems broken.
Mar 13 2018
Mar 6 2018
Feb 28 2018
Feb 16 2018
Me: It would be very convenient if we had a tool to cut paper.
A: We could use a thermonuclear quantum laser for that. Closing as duplicate.
B: Sorry guys, we cannot have a thermonuclear quantum laser.
Me: Wait, closing as duplicate was a mistake in the first place, I don't need a thermonuclear quantum laser... How about plain old scissors?
Feb 15 2018
Feb 14 2018
Feb 6 2018
It was for another account, newly created.
Jan 31 2018
Nice job with the caption field!
Captions totally make sense, as it is important to have a sort of multilingual label that described the file and can be edited.
It makes the uneditable and untranslatable filename/title field redundant, so I removed it in this wireframe:
Jan 27 2018
Jan 23 2018
Jan 17 2018
Dec 29 2017
Oct 20 2017
@Etonkovidova A notification appeared, I clicked on it and it lead me to a page saying "There is nothing".
Oct 19 2017
It is not obvious indeed. My little story:
Oct 18 2017
From the user's point of view, it is not a complex problem, and only the UI makes it complex.
If the UI was 1. Select "century" 2. Select the century from a dropdown list, then there would be zero chance for mistake.
The dropdown list would need "More..." buttons to go arbitrarily far in the past and future, so implementation sounds a bit complex, though.
Oct 10 2017
Sep 7 2017
Aug 18 2017
Aug 15 2017
Jun 7 2017
@Nemo_bis Many of our users created their account via the app, and have no idea what MediaWiki is. As a consequence, for them creating a Github account is probably easier than figuring out how log into Phabricator:
@Nemo_bis Yes, being user-friendly to new translators is one of our top priorities.
Especially those who have never heard about issue tracking/XML/WMF/etc. (people who only know Wikipedia, Commons, and the Android app, as users)
Jun 6 2017
As a community-maintained app, we use what we deem to be the most convenient platform, and right now this is Github, by a very large margin.
Nov 25 2016
Nov 14 2016
Personally I don't see banner is not a big issue on diff pages.
If we have them, the beginning of the "Revision" section would probably be the most sensible place, though.
Not happening anymore, thanks!
Now the shadow is only like a pixel too long:
Nov 4 2016
[...] reasons why the Commons uploaders were [...]
Oct 28 2016
I suggest you create a new issue at https://github.com/lyrk/Commons detailing your offer.
Oct 7 2016
Just some thoughts:
Sep 20 2016
Sep 6 2016
Magnus Manske just suggested it for the Commons app too: https://github.com/commons-app/apps-android-commons/issues/259
Jul 27 2016
Fixed, thanks all :-)
Jul 13 2016
@Bawolff It is a joke right? Our app launches a category search and gives the results to the user as category suggestions. Because of the present bug the server gives us trash categories, which means the server needs fixing.
Jul 12 2016
This is an urgent issue.
Jul 5 2016
I am such a wiki editor who adds and maintains lists.
Mar 16 2016
Mar 2 2016
As a conclusion, I just noticed this comment on the talk page of https://commons.wikimedia.org/wiki/Commons:Mobile_app :
Feb 29 2016
@Niedzielski as per my email last week all seems complete, so let's close it :-)
Feb 23 2016
It should be moved to the Commons page, and merged into the similar list that exists there already.
Maybe leave a link "For the list of features, see here"
Mostly the features list. The "Reports" paragraph can be removed too, I guess, we are not fond of user spying.
I think they serve different purposes, the mediawiki.org page being about the development project, while the commons page is a user guide. Much of the information would need to be moved around indeed: Removing "user guide" stuff from the first one, which is out of date anyway. The Commons page can keep a short history paragraph, but most of it should go to mediawiki.org I guess. Also, each one should link to the other.
You can let #3 as is indeed.
@Nemo_bis Actually we have a separate issue about how we would like to revert to using the Wikimedia Commons logo instead of the current ugly logo (that I drew as a replacement to avoid the kind of legal problems that caused another of my apps to get banned from Play Store): https://github.com/nicolas-raoul/apps-android-commons/issues/68
So yes, access to the logo would be great. Request created per your suggestion: https://phabricator.wikimedia.org/T127791
Feb 22 2016
On that wiki page, I see the following:
I did not know it was possible. Done now, thanks! https://phabricator.wikimedia.org/T127678
Feb 21 2016
@Krenair: After the WMF announced they would no longer support the app, forking it was the obvious thing to do.
I have no control over gerrit (I think). On Github I was able to fix bugs, push releases, write wiki documentation, without having to bother anyone.
Feb 16 2016
Writing dev documentation for developers would be great, I guess it could be either a .md file in the app source code, or a page in Github wiki.
It would describe the rationale of the categorization suggestion strategy, and the API calls with sample request/response for each API used.
Feb 3 2016
getLastKnownLocation sounds like it might not get the correct location.
Feb 2 2016
Jan 29 2016
Fixing 'repeat categories' is higher priority I would say.