Thanks @VoidRaven-18 for such a detailed proposal, I hope you're contributions are sorted based on the impact, with the best ones at the top :)

Thanks @PriyankShankar for a detailed proposal. Could you add specific details about your working hours, given that you've a full time job? Also, please add the answers to these questions to your proposal:

• Are you eligible for Google Summer of Code? Eligibility criteria: https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation
• What are your expectations from the mentors and this beginner-friendly mentorship program?
• Do you plan to submit any other proposal apart from this one?

Hi all,

Hi @Mtiwari479, welcome to the community! :)

Hi all,

Hi @LGoto, I'm actively mentoring only this project. I authored the other task on Phabricator as I'm the current maintainer, but Sivaraam and Neel will be mentoring it.

Also the "Tasks" section links to one declined task and one discussion threat which does not seem to be an actual task.

@LGoto we've made our microtask selection flexible and this is how we've been doing for all the previous GSoC editions. My personal observation with selected microtasks is that contributors end up fighting for the tasks. Double effort doesn't help us and do not want anyone's effort to go in vain. Moreover, we don't want to set wrong expectations in terms of selections. We can link good first issues to get newcomers started, but that might not guarantee a selection. They might think "we did the given task but still did not get selected". Slightly complex tasks makes it challenging for the newcomers.

@LGoto we have defined how to choose a microtask here: https://github.com/commons-app/commons-app-documentation/blob/master/android/gsoc.md. It has been added to the description. Is there anything else that you would like us to add?

Please note that you must have at least 2 mentors for a project; be sure to include their Phab usernames. Also you must include microtasks, ideally linked to this task.

Hi @Pppery and @LGoto, I understand the community's concern about AI usage, but I’d like to clarify the specific nature of these tasks to see if it eases some of those worries. I respect your priority to ensure a safe and productive learning environment for the student; we certainly wouldn't want to place a participant in the middle of a contentious community debate.

Hi @LGoto, thank you for checking the proposal. I have reached out to the mentors to get their Phabricator handles and had created this ticket to share it with them. Is there a way to convert this proposal into draft until I get the details?

when the user reconnects with the internet we can start reuploading (but that will be done from the start)

Great proposal! I've a few observations to share.

Nice proposal! By "implement the new UI" in the timeline, do you mean you'll be making any changes to the code as well? Apart from minor code changes, doing preliminary research and brainstorming during this period might be helpful. Last year, Nicolas had suggested to upload a few pictures via the app, the task helped me make some super crucial observations! Since this year's idea partly extends the one that we had last year, it might help this year as well.

Thank you @Nicolas_Raoul for the last-minute review. Also, I have submitted my proposal on the GSoC website already, and will move it to the "Proposals Submitted" column too. Thank you @Gopavasanth for the reminder.

I have modified the first task and added a few more details asked in the pre-populated template. I have also added another section for post-GSoC involvement, discussing my future plans about my involvement with the community. Would like to hear any feedback/suggestions one last time before the deadline. Thank you! :)

Thank you @Nicolas_Raoul for suggesting a new issue. I will make the necessary changes.

Thank you @Nicolas_Raoul for checking my proposal again after I modified the strategy for the first issue. Since this issue has now got resolved, I will look for another issue and change the strategy accordingly.

@Nicolas_Raoul, I have modified the strategy for the first issue and chosen a general implementation for now. I apologise again for missing out on key observations; will ensure this does not happen again.

Thank you @Nicolas_Raoul for your valuable feedback, and for confirming that the General Strategy image is accessible to you as well. I am sorry; I think I missed @Kaartic's comment about the regular selector on GitHub, probably because most of the users reported it to be working fine on Android 12. I will research more about the restricted access to the EXIF location and have a general implementation strategy for both the selectors then.

I am sorry, I just realised uploaded files are not visible to everyone. These are the handles mentioned in the mail:

Thank you @Aklapper. I just got a little worried seeing a lot of handles being CC'd together and wanted to clarify that this is not ready for review as of now.
List of CC'd handles:
{F36912841}

From the mail that I received today, it seems like this task has been CC'd to a number of handles. We can edit the tasks and mail them for review when ready is what I interpreted from the Commons GitHub repo. I was expecting a "Save Draft" option so that I could save my progress and continue later. But I could find only the "Create Task" option and did that, without tagging anyone. Did I miss anything? I am sorry for any confusion or trouble this task may have caused.