Everyone, welcome to our GitHub repository! Thanks for showing interest in the Commons Android app.
I am posting this information as some of you have messaged me asking where to get started.
Check the volunteer guide and contributing guidelines for more details.
The number of contributions you make will not be the primary criterion for choosing the intern. So please don't feel pressured to make the biggest number of contributions.
Please avoid creating a pull request for an issue until the issue has been assigned to you.
In the proposal, we want to see the timeline and understand how you have broken down the main task into small sub-tasks. Please make sure that you are able to clearly mention the sub tasks and provide a good estimate of the time you think it might take. Also, factor in time for documentation and unit test cases.
Things to note:
You can find sample proposals here:
https://phabricator.wikimedia.org/project/board/3795/query/all/
@maskaravivek I have multiple possible project ideas for Commons Mobile App, should I message you directly or will it be discussed here?
This is the project that we have proposed for this year's GSoC/Outreachy. https://phabricator.wikimedia.org/T244197
If you wish to discuss other ideas, you can send an mail about it.
hey @maskaravivek
The view to this link is restricted
hey @maskaravivek
The view to this link is restricted
Have you created an account?
@misaochan The issue still persists after creating an account.

Have the same issue too after creating an account.
I created the account. Still getting the same issue.
Ah yes, we need @maskaravivek to edit the task then. :)
I have updated the task link. It should work now.
it just works now :)
Important Note:
The number of contributions you make won't be the primary criteria for choosing the intern. So please don't feel pressurized to make the most number of contributions.
Please avoid creating a pull request for an issue until the issue has been discussed and assigned to you.
@maskaravivek Wouldn't it be better to also mention the note in the description of the issue to ensure it isn't missed? :thinking:
I modified the desc with Vivek's note.
@misaochan maybe it is also a good idea to add the following to the description:
That student should first request a code review from the person who assigned the issue or who created the issue, instead of tagging every maintainer on each and every PR.
That student should first request a code review from the person who assigned the issue or who created the issue, instead of tagging every maintainer on each and every PR.
Haha. I think it is okay that new contributors are tagging lots of people as its understandable that they are excited about getting their first PRs merged. :)
I used to tag @misaochan and then also ping her on the issue thread 🤣
But yes IMO there's no need to initially tag anyone for code reviews. One of the collaborators will check it out in 1-2 days. If no one checks it then feel free to tag relevant folks.
Hi all, this was written for the 2020 GSoC programme, but I just wanted to re-pin this because it contains extremely good advice for anyone aiming to apply for the 2021 round. In particular, please note this section:
The number of contributions you make will not be the primary criterion for choosing the intern. So please don't feel pressured to make the biggest number of contributions.
Please avoid creating a pull request for an issue until the issue has been assigned to you.
Speaking of GSoC 2021, I wonder if we are aware of the upcoming changes to the programme? 🤔
With the pandemic straining folks’ time we are changing the size of the projects and time commitment students are expected to spend on their projects. Starting in 2021, students will be focused on a 175-hour project over a 10-week coding period.
What was the requirement for the last GSoC, does anyone remember?
Pinging also @madhurgupta10 for this. :)
With the pandemic straining folks’ time we are changing the size of the projects and time commitment students are expected to spend on their projects. Starting in 2021, students will be focused on a 175-hour project over a 10-week coding period.
What was the requirement for the last GSoC, does anyone remember?
Pinging also @madhurgupta10 for this. :)
These changes are for GSoC 2021, for last year the pattern was the same as all previous years with 10 weeks of coding and 3 evaluations. Check out this article
What was the requirement for the last GSoC, does anyone remember?
Pinging also @madhurgupta10 for this. :)These changes are for GSoC 2021, for last year the pattern was the same as all previous years with 10 weeks of coding and 3 evaluations.
I believe it is 12 weeks the previous year. Also, the 350 hour time requirement of previous years is being reduced to 175 in 2021 (that's 1/2 the time requirement of previous years). Here's concise piece about the changes:
Google Summer of Code 2021 has been announced with significant changes compared to previous editions. Notably coding hours and period will be reduced from 350 hours and 12 weeks to 175 hours and 10 weeks; there would be 2 evaluations (instead of 3). Additionally, eligibility requirements will be relaxed, among others allowing people participating in a variety of different licensed academic programs, not just students of accredited university programs.
@nicolas-raoul @misaochan what this year this organization participate in gsoc 2021
The information for GSoC 2021 is at https://github.com/commons-app/commons-app-documentation/blob/master/android/Students.md
Thanks! :-)
Most helpful comment
Haha. I think it is okay that new contributors are tagging lots of people as its understandable that they are excited about getting their first PRs merged. :)
I used to tag @misaochan and then also ping her on the issue thread 🤣
But yes IMO there's no need to initially tag anyone for code reviews. One of the collaborators will check it out in 1-2 days. If no one checks it then feel free to tag relevant folks.