[GSoC Draft proposal] Redesign system settings modules by porting them to QtQuick

[Smit Patil]

Hi Valorie, Thanks for your valuable input :)

I don't have much experience in writing proposals. My
presentation/communication skills are somewhat weak

Biggest part of KWinGamma KCM was understanding KWin Code, adding code to
set
gamma and exposing it from DBus in KWin and testing it.
Writing actual KCM was pretty easy. Testing took more time than developing
it.
It's in full working condition

In case of these existing KCMs, DBus interfaces and logic already exists
and I just have to
rewrite them in Qml/Kirigami. I don't have to disconnect-reconnect any
hardware like in KWinGamma for testing.
So on the surface these tasks look pretty easy. That's why my initial list
was so ambitious.
I lack the experience of writing and maintaining these KCMs(only made one
which is not even upstreamed yet),
writing documentation, meeting with other developers and discussing ...etc.
My goal is to get that experience from this event.
So right now I can only approximately guess the timeframe required for
these activities.

Please see:
https://drive.google.com/file/d/1g11icAawvBwp2J4wczi57nA7Dno7ew-E/view?usp=sharing
I have not uploaded this version on GSoC yet cause I still think my
proposal lacks something and would appretiate feedback.
I know it contains repetitive timeline but such is nature of my task



On Mon, Apr 18, 2022 at 9:57 AM Valorie Zimmerman <
valorie.zimmerman at gmail.com> wrote:

> 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 <smit17av at 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 <nate at 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20220418/126aee33/attachment-0001.htm>