Just wanted to post that @maskaravivek 's solution works for me (for the most part). If no issues, we will be pushing a release with this implementation very shortly. :)

I cherry-picked the change onto our 2.8-release branch - should be fine to just release this in 2.8, no need to wait for 2.9. :) Thanks @Nemo_bis !

I saw your mailing list post. Nicely-written, well done! :)

Hi @Tanvidadu1998 , I trust you received Srishti's email? :) I think you can start writing updates about your progress at https://www.mediawiki.org/wiki/Google_Summer_of_Code/2018#Community_bonding_period . So for instance if you subscribed to wikitech-l as we talked about yesterday, you can add that to your updates. Please feel free to carry on with the other community bonding period steps mentioned on that page, as well as the project-specific tasks that Vivek suggested like reading documentation, and update via that page as you go.

Hi @Aklapper , we extended our Outreachy deadline to Mar 29, and I can confirm that I see this proposal in my Outreachy dashboard.

Hi @maskaravivek , @K0x3rr spoke to me about the same thing over email, and I explained to him that this project is eligible for both GSoC and Outreachy, but that T188877 is reserved solely for GSoC. :)

Thanks for submitting your proposal. It looks great to me in general, and the list of bugfixes is impressive! :)

@Gupta-meghna64 thanks for the update! The previous apps that you have worked on look amazing. Well done. :)

Thanks @ayushin78 . :)

Thanks for the update, @harisanker24 !

Happy to see that you have updated your proposal! The new formatting looks great and much more readable. :)

I agree with @maskaravivek - the outcome of the quiz should not affect reputation/points. :)

Thanks for submitting your proposal! :) It looks good to me in general, but I have a few suggestions:

• In the timeline it is good that you have frontloaded your work and allocated time for mockups, testing and debugging, etc. However, I personally think too little time is allocated for implementation. E.g. For Phase 1 I would recommend moving "Decide the information which will be displayed in the stats info page. Improve it through community discussion." up into the mockup week so that you have at least 2 weeks for implementation.
• We appear to be missing 5 days in June? ;) If you are allocating that time for writing your midpoint report, please do mention that.

Nice to see you have submitted a proposal, and the apps you have worked on before look great. :) A few suggestions:

GitHub project link would be great!

Thanks for putting this proposal up. I am guessing that tasks and deliverables are still being worked on? That's totally fine, but I would recommend putting the deliverables next to the tasks in the table (in a 3rd column), that will make it easier for us to view them.

Glad to see that you are working on your proposal. :) I especially like the detailed task breakdowns - it's great that you have suggested documenting the results of various API strategies, and mockups for each UI phase.

Very thorough and well thought-out proposal, nice. :) I am very happy to see time allocated for testing and fixing bugs, and that the task details reflect the discussion we had in the relevant GitHub issues. A few suggestions:

Should be fixed via https://github.com/commons-app/apps-android-commons/pull/1019 , thanks for bringing this to our notice!

Update to all: After some discussion, we have been informed that this requirement has been waived, for the reasons mentioned here. Thank you for your patience and help, everyone. :)

Hi all,

Apologies for reviving this, but it would be very useful for the Commons Android app if we could query this. Several users have requested to be able to see the total number of uploads they have made to Commons, but we are unable to show it to them.

Hi @Tobias1984 and @Rfarrand ,

This issue is currently tracked at https://github.com/commons-app/apps-android-commons/issues/144 , please refer there instead (sorry, @Aklapper , we had to do some housekeeping in our GitHub issues).

Thanks for the suggestion. We do have plans to add more licenses to the app - the task is currently tracked at https://github.com/commons-app/apps-android-commons/issues/254 . Unfortunately I don't have the time currently to implement it, due to other commitments. However, I have outlined the steps needed for implementation on that GitHub thread, and it would make a good starter task for someone wanting to get involved with our codebase, so if any volunteers are interested in picking it up, that would be great. :) Alternatively, I could include it (along with adding explicit license selection, as the current license selection method is less than ideal) in my IEG renewal proposal at the start of next year.

Hi @Qgil , yes I completed this task during the Dec 2015 Outreachy round. :)

Closing this, if anyone disagrees please feel free to reopen.

Feature parity with the Android Commons app makes a lot of sense to me. I don't have much iOS experience, but my opinion is that using Swift might make it easier to recruit and on-board new volunteers, compared to a legacy app that is running Objective-C.

My $0.02 as a woman and a first-time participant thinking of applying to attend the Wikimedia Hackathon 2017:

Just to clarify, are you requesting this feature for the web-based Upload Wizard? Commons-App-Android-Upload is for the Commons Android app.

Excellent, happy to hear that!

This would be great. AFAIK there isn't even an 'unofficial' iOS app for this any more, last I checked it had been pulled from the store because the developer's account had expired (see here).

@Aschroet - Ah, I looked into the developer console history to refresh my memory and yes, there was a mixup before. About a year ago, I was new to the app and it was my first release, so I mistakenly titled the release after 1.3 as '1.31'. :) I was informed of the error and fixed it, but that was a while later, so some uploads must have gone through.

I will have to release a hotfix for another bug anyway, so no harm putting this in v1.31 and seeing how it goes. Do let me know. :)

Thanks for the tip, @Aschroet ! Would you like to comment on the changes I intend to make to fix it?

Interesting, I'm not sure in what cases a picture would have a geolocation of (0,0). If the EXIF data did not exist it should be returning null, and thus excluded from appending the location template. I don't think this is as easy a fix as the previous one (unless we're okay with excluding location templates in cases where that value is found as well). Will ask on GitHub.

Thanks @Aschroet . I forgot to clarify: updates do take a while to go through on Google Play, and users don't always update their apps immediately, so it might take a few days for any changes to get to the majority of users. But if the issue persists beyond that time frame, then I will need to look at it again. :)

We have released v1.30 of the app which should hopefully fix the issue. Please do let us know if it persists, thanks!

Thanks for letting us know! We'll work on it (https://github.com/commons-app/apps-android-commons/issues/269)

From memory, if I take photos of a well-known cafe, Google pops up one notification saying something like "Add 5 pictures to Punnet Cafe" or similar. It includes both photos of food etc as well as photos of the location, so I doubt image recognition plays a big part. If I recall correctly, it even includes selfies, which might be an issue in our case. (I know that the pictures displayed on Google Maps don't include selfies, so I'm guessing they filter them out after submission)

@Jane023 it is a built-in functionality that I wrote for the Android app about 6 months ago. I don't think it can be converted to the web uploader per se, different programming language entirely.

The Commons Android app already contains the functionality you are requesting, if I understand correctly. Not sure about the web-based Upload Wizard.

The Android app for this does exist at https://play.google.com/store/apps/details?id=fr.free.nrw.commons . It supports the 'share' option, you can browse through your gallery, click 'share' and select our app from the list of potential apps displayed.

I think this has been settled. Could anyone confirm and close?

Thanks @Qgil ! I glanced at the guidelines which suggested that I email blogteam@wikimedia.org with the blog post idea first before writing a draft, so I've done that. Crossing my fingers.... :)

@Niharika thanks! I had no idea we could speak at conferences about our projects. :)

Final update: Not sure if this is where it should go, but I just wanted folks to know that the internship has been awesome - I've learnt heaps about FOSS, Android development and Wikimedia. And the community has been amazing. :) I'm very much hoping to stick around - I've submitted an IEG proposal for further work on the app, and I'll try to help or share my experiences with the next round of Outreachy applicants as well.

Just letting you know that we haven't forgotten, I have added your bug report to the list of bugfixes planned for the app as part of an IEG proposal. :) Would very much appreciate it if you could take a look at the proposal and review/endorse it if you see fit.

No probs Johan. :)

Thanks @Niharika , that would be great!

Do you mean the features listed in the report? They have been implemented and are available in v1.12 of the app that was released on Feb 18.

Apologies, I would love to but will be unable to make the stipulated time (19:00 UTC, right?). But thanks for asking me, and do let me know if there is a way to work around that. :)

Thanks for asking me. :) What would that involve? Is there a page where I could read more about it?

Woohoo! :)

Sure thing, thanks for the nudge @01tonythomas :)

Thanks everyone, it's been a great ride! @Niharika I definitely plan to. :)