My feedback as an admin who has seen many proposals is: your timeline is inadequate.
Your timeline should be complete enough that both the mentor(s) and applicant can use it as a roadmap to the summer. That does not mean that it can't be adjusted over the coding period -- some things are easier than expected, others are more difficult and take more time. But that timeline should have *everything* in it for every week, from writing tests, user testing if applicable, documenting the code, writing necessary documentation, meeting with the team/mentors, writing blog posts -- **every** **thing*.* Applicants who create complete timelines such as I just described in general do very well. Those who have skimpy ones, on average, do not do as well. All the best, Valorie, part of the KDE GSoC admin team On Sun, Apr 17, 2022 at 9:03 PM Smit Patil <smit1...@gmail.com> wrote: > Hi, can someone re-review my proposal and let me know what you think so I > can edit it before April 19, 2022 ? > Also I have one complete working kcm at > https://invent.kde.org/smitpatil/kwingamma (which I wish to upstream) > > I think my last message was not sent cause of attached pdf so here is > link:- > https://drive.google.com/file/d/1fU-VL_oQbrV5D1I1y88OFkfB3Bv_naJg/view?usp=sharing > > On Mon, Apr 11, 2022 at 4:50 AM Nate Graham <n...@kde.org> wrote: > >> Cool, I have marked myself as "want to mentor". As long as there is a >> co-mentor with better dev skills than me, I will be happy to proceed. >> >> Nate >> >> >> On 4/10/22 17:15, Smit Patil wrote: >> > I have submitted the proposal on GSoC's WebApp. Please check it out. >> > As David Edmundson suggested, I also rebased and reworked my old MR. >> > It is now waiting for a review about the dbus interface. >> > -- http://about.me/valoriez - pronouns: she/her