I can add a few bits from me.
You can only do one project as gsoc, because the rules say so: https://summerofcode.withgoogle.com/rules See 7.3.b
The rules also say that you can submit up to 3 proposals, but only one of them we can select. In theory, you can write 2 proposals for 2 projects that you like, and submit both, but we will choose only one anyway. In any case writing a proposal is an effort, and writing two of them is double of that effort.
Yes, a project will have a Mentor guiding it, and you will be talking to Mentor regularly. But also, in case you have some generic questions (about the process for example), you can also ask me or Felix, we take care that everything is running.
I have completed a rough draft for my proposal, can someone review it?
I am actually thinking about it, maybe it's ok? Let me think about it and check the rules :) I assume you are talking about a draft for a project proposal (by our template).
Importantly, your actual application you will be submitting *not to us directly*, but to gsoc website. It will go through the system and then come to us, but not from your hands directly. Make sure you read official guidelines on how to submit the application! :)
On Sat, Mar 26, 2022 at 6:36 PM Felix Singer felixsinger@posteo.net wrote:
On Sat, 2022-03-26 at 10:57 +0530, Aarya Chaumal wrote: [...]
As I said before I am interested in "Optimize Erase-Function Selection" and "Fix Endianness Issues" (I still cant decide which one to choose, kinda wanna do both if possible).
Glad you like them! Though, you can't do both during GSoC, since each of them will be a significant time commitment for you. But if you are still motivated after GSoC, you can do the other one later if it is still available :)
I have understood what is the aim of the projects and also have some idea as to how to go about it.
I have read the proposal template and have some questions: In the project info section, do I have to write the same as given in the projects idea list, or do I write what I have understood (in the short and long descriptions)?
That point is more related to the project proposal. Seems like we mixed it up with the application template :)
However, we expect our applicants to describe the project they want to do in their own words to see if they understood it.
Also, what is expected in the project breakdown?
We would like to see that our applicants made realistic and serious thoughts about their projects. So we expect you give an overview about your work schedule. You should define small steps and elaborate them weekly or fortnightly.
For example:
Week 1: First, I will start with reworking thing XY and ... Week 2: When cleaning up thing XY is finished, then I will work on another thing. Week 3: Depending on how the another thing was solved, I will do this or that.
Of course this schedule won't fixed and this doesn't have to be perfect, because new problems can appear or you might get a better idea for something. We just want to see that you made thoughts about the project and that you have a somewhat realistic schedule on how to do it.
Also, this helps you to keep track of your own work and your schedule before and during GSoC. The past showed that people underestimated their projects or the workload per week and then it got stressful for them.
Will I be doing the project alone or the mentor(s) will be guiding me?
You will have at least one mentor on your side guiding you and you will have weekly meetings with them. So if you have any questions, problems or anything you would like to discuss, then they are your contact persons.
I have completed a rough draft for my proposal, can someone review it?
Well, we can answer questions related to the project or help understanding what hasn't been understood yet, but we won't review your application :)
// Felix