@whym:
Apps like Fake GPS allow us to perform tests in places with many pins such as Paris, or places with few pins such as deserts. :-)
I would suggest taking screencasts of Wikishootme and the app for the same area and zoom level, then compare the time until all pins are loaded.

"Maps tiles load slowly" is probably very lengthy to solve.
Maybe investigate it first, then identify what is the issue, then if relevant send a bug report to upstream (for instance OsmDroid or Wikimedia), then possibly work on it after upstream responded (for instance they might give tips).

I see {F44022202} and similar in the proposal above. Is it images? Feel free to post them below using the "Upload file" button, or even upload them on Commons and post the URLs here. Thanks! :-)

On July 12 I see "GSoC contributors start working on their project with guidance from Mentors." ... at that point it is started already, so maybe no need for this sentence?

Hi all,

Yes exactly, thanks!

Ah yes please put a special line for that one. Thanks for all of your hard work! 🙂

Very sorry for the review delays! What PR(s) are you thinking about in particular?

Thanks for pointing this out!
I replaced 3A with a similarly sized task.

As we discussed via email beforehand, to me this seems to be a reasonable project content for a GSoC.

Looks great!

Several tables is fine. Would you mind putting merged PRs first though? Thanks :-)

Great proposal!

@Maryann-Onyinye Added, thanks! :-)

Comparing with the rules listed at https://commons.wikimedia.org/wiki/Commons:Depicts I find the sample analysis above to be too harsh. I would consider these as good:

Actually just changing our Referer HTTP header to https://maps.wikimedia.org did the trick. 🙂

Any blocker for approval?

Upload in the Commons Android app is now much more reliable, huge thanks to Ritika!

Thanks Platonides for the prompt reply!

Thanks a lot Ritika for all of your hard work!

A few things may be polished, but it is generally good enough, and very detailed. 🙂

Looks good, thanks!

Looks good to me, thanks!

@PriyankShankar Both methods are OK.

Looks great, thanks!

Sorry would you mind checking https://github.com/commons-app/apps-android-commons/issues/5129#issuecomment-1491402922? thanks!

Did you mean to include a timeline?

Sorry please check https://github.com/commons-app/apps-android-commons/issues/5129#issuecomment-1491402922 thanks!

No problem at all!
It is perfect now. :-)

Great proposal!

Hi Priyank,
Big apologies for the delay, I was on a trip for 5 days.
Could you please include the word "lossless" for all transformations? Lossless rotation, lossless crop, lossless blur. Please add a sentence to explain the last one as the wording is surprising at first.
Also, please link to your merged pull request(s).
Otherwise the proposal looks good!

@srishakatux This can be closed, thanks always for your support! :-)

@Karankulx I am not sure what you are talking about, but if you want to create a proposal, please create a new task. By the way, color manipulation before upload is not desirable. Thanks!

Are you aware of the document https://github.com/commons-app/commons-app-documentation/blob/master/android/Students.md?

@Aman7531 Would you mind adding links to the pull requests (or at least one link, for the pull request you are most proud of)?
Thank you!

Thank you! Based on your screenshot, I added steps at the 7th bullet of https://github.com/commons-app/commons-app-documentation/blob/master/android/Students.md#how-to-apply

Thank you for asking! Would you mind sending a screenshot of the form so that we can be 100% sure to have the right choice?
At https://www.mediawiki.org/wiki/Google_Summer_of_Code/2022#Improve_the_picture_selector_of_the_Commons_Android_app we wrote Expected size of project: 350 hours, Difficulty rating: mediumbut without seeing the form I am not 100% sure how that translates to.
Thanks in advance!

Great proposal, the work is well explained, there are even screenshots, the schedule makes sense.
Just a few very minor typos:
After marking some images -> After selecting some images
Not for uploaded images -> Not for upload images
Implementaion -> Implementation
Rest work -> Rest of work
Activies -> Activities

Yes, if done losslessly then blur+rotate+crop is well enough for a GSoC.
You can keep "Implement Update Depicts" as a bonus task "if time allows".

Please be aware that AndroidMediaUtil is probably harder to use, and might even need some modifications. Feel free to modify your schedule to allow some buffer, for instance I would suggest not doing contrast change and EXIF, and leaving more time for both unit tests and final code review.

Thank you for the detailed proposal, with screenshots and a timeline.

@srishakatux 350 hours medium sounds like the best choice indeed, thanks!

Aditya implemented everything :-)

With artificial intelligence chips now being embedded directly on devices, and AI-based upscaling becoming routine, our average JPG upload will soon be artistic rather than reliable encyclopedic content.

Implemented and merged into master branch, huge thanks to Aditya!

"none of the main upload tools (Pattypan, url2commons) support SDC"

Thanks!
Would you mind explaining in a few words how you plan to cache API results? You can add this information to the "Implementation Strategy" section.

@Pheonix10 Thanks!

Great proposal, thanks!

Thanks for this very well-written proposal, especially the implementation part is great!
The tasks are rather ambitious, but your technical implementation details and your timeline are convincing.

Looks pretty good!
No need to divide time in durations smaller than a week.
Minor correction: "commons" as the name of the website should always be uppercase: "Commons".

Thanks for applying!

First feedback on this proposal:

Mentor here, I confirm that this GSoC is still open.

Thanks Gabrielchl, perfectly accurate answer!

Yes, it is done, thanks!

@Pavithraes Done, thanks! :-)

@Aklapper Here is an example of a "Wikimedia Commons image page": https://commons.wikimedia.org/wiki/File:Milgram_Experiment_v2.png

T213031 is only about "Wikimedia Commons image pages".
On the opposite, the present issue is for "Wikipedia articles".

In T235936#5588446, @Masumrezarock100 wrote:

This is likely an issue with Facebook problem not Mediawiki.

Implemented and successfully tested, not merged yet because of ongoing work on a library.

Here is my use case, just to illustrate the usefulness of having a SPARQL endpoint.

I stumbled upon this bug on commons.wikimedia.org right now.
I can confirm the bug is fixed on commons.wikimedia.beta.wmflabs.org thanks, looking forward to the release.