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

[Smit Patil]

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 and working kcm at
https://invent.kde.org/smitpatil/kwingamma (which I wish to upstream)

On Mon, Apr 11, 2022 at 4:50 AM Nate Graham  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.
>


kcm-redesign-v2.pdf
Description: Adobe PDF document

Re: [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.zimmer...@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  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  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
>
>
>

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

[Valorie Zimmerman]

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  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  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

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

[Smit Patil]

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  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.
>

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

[Nate Graham]

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.

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

[Smit Patil]

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.

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

[Valorie Zimmerman]

If you are interested in mentoring, *now* is the time (I mean today) to
ensure that you are subscribed to the private ML for mentors,
kde-soc-men...@kde.org, and write to kde-soc-managem...@kde.org asking to
be added as a mentor to the GSoC webapp. Please provide your
google-connected email if you don't write from that email account, and
mention what team you are working with.

Time is short; please act on both *now.*

Valorie, for the GSoC admin team

On Thu, Mar 31, 2022 at 10:05 AM Smit Patil  wrote:

> Hello all,
> I'm looking for potentials mentors for GSoC 2022 to review/comment my
> draft proposal
> for this task:-
> https://community.kde.org/GSoC/2022/Ideas#Plasma_modernise_system_settings_modules
>


-- 
http://about.me/valoriez - pronouns: she/her

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

[Smit Patil]

>
>
> Cut it down to 4 and you'll still have an effective GSOC.

Lets try and move forward on the gamma KCM
>

Ok, I'll remove File Association and will start working on gamma tomorrow
evening
So that's down to 5
Thanks for input :)

On Tue, Apr 5, 2022 at 8:35 PM David Edmundson 
wrote:

> >Please checkout new attached proposal
>
> The list of KCMs is ambitious. Everything takes twice as long as you
> expect when you hit roadblocks, review comments and unexpected bugs.
> Cut it down to 4 and you'll still have an effective GSOC.
>
> A big aspect of student selection comes from experience of other
> contributions rather than the proposal itself. I would encourage you
> to submit some merge requests for small tasks. Lets try and move
> forward on the gamma KCM that you have done, it'll be a good way to
> show your skills.
>
> I know that somewhat fell through the cracks due to the timing of the
> MR, so lets get that up-and-running again.
>
> David
>

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

[David Edmundson]

>Please checkout new attached proposal

The list of KCMs is ambitious. Everything takes twice as long as you
expect when you hit roadblocks, review comments and unexpected bugs.
Cut it down to 4 and you'll still have an effective GSOC.

A big aspect of student selection comes from experience of other
contributions rather than the proposal itself. I would encourage you
to submit some merge requests for small tasks. Lets try and move
forward on the gamma KCM that you have done, it'll be a good way to
show your skills.

I know that somewhat fell through the cracks due to the timing of the
MR, so lets get that up-and-running again.

David

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

[Smit Patil]

>
> I think for the Font Management KCM there was a conclusion that we would
> remove that from systemsettings and have it as a standalone application
> instead, so porting to QML isn't strictly necessary.

For the KWin Scripts KCM Alex is already working on a port:
>

I removed those KCMs from my proposal

As for the proposal itself: It's currently a bit superficial, merely
> saying port X in week Y. Maybe you could add a bit more detail about
> what kind of challenges there might be while porting?
>

Smit: I didn't look at the kcms in question at all but imo 1 week per kcm
> can
> be very steep.
>

I have added some extra text and adjusted the timelines.
Coding part seems easy to me. UI/UX will take time I guess

Please checkout new attached proposal
# Redesign system settings modules by porting them to QtQuick

# Goals

Port following KCM modules to QtQuick/Kirigami2

1. File Associations
1. Window Behavior
1. Task Switcher
1. Spell check
1. Screen Edges
1. Compositor
1. Gamma

## Implementation

Porting and redesigning Most of the KCMs will be straightforward 
complete rewrite with similar feature parity with previous ones

Coding part seems easy but I think UI/UX will be the hard part. 
Also I think that if we are rewriting it then it must have better UI/UX than old version 

Some KCMs like Spell Checking and Gamma can get new features such as 
bulk adding words or setting contrast ...etc respectively 

## Timeline

This is my proposed timeline.

 - Week 1
   
   Port **Task Switcher** KCM
   Alternative tab is just duplicate of fist Main tab so this will be very easy

 - Week 2
 
Port **Screen Edges** KCM
Single page. Looks easy

 - Week 3-4

   Port **Window Behavior** KCM
   This one is looks simple but is actually quite big

 - Week 5-6

   Port **Spell check** KCM

   This is also very simple KCM but IMO we should add some additional 
   functionality to it like 'Add bulk words' from a specefic file format,
   and allow searching if word is in list or not ..etc

 - Week 7-9

   Port **File Associations** KCM
   This looks complex KCM in terms of UI/U

 - Week 10
 
   Redesign and Port **Compositor** KCM
   Simple 1 page KCM
   
 - Week 11

   Redesign and Port **Gamma** KCM

   This is also simple 1 page KCM but if my https://invent.kde.org/plasma/kwin/-/merge_requests/1335 
   gets merged, we can just use my half made kcm at https://invent.kde.org/smitpatil/kwingamma

My speed may slow down during mid August and November due
my in-sem and end-sem examinations which are are likely 
going to be held in that time

I believe that I can manage both university and GSoC at the same time as 
my college is flexible about attendance
   

## About Me

I'm Smit S. Patil. I'm a student at Sinhgad College of Engineering in Pune 
currently studying Information Technology in 3rd year.
I've been using desktop Linux since 2017 as my primary operating system 
and KDE as my primary Desktop Environment since 2018. 

I've first started programming with C and GTK and self-taught myself since 2017

In 2018, I was selected as runner-up in Google CodeIn 2018 for KDE and PostgreSQL
organization. I sent patches to GCompris software.

Since then, I've also tried to contribute to core KDE by creating a few merge requests
(which you can check out on my [invent profile](https://invent.kde.org/smitpatil))
to kwin, plasma-sdk, and kirigami2 and wish to do more in future 

I'm also known as violetghoul on matrix with username @smit:matrix.org

I'm also submitting a proposal to LLVM and when given a choice
I'll choose KDE because I want to contribute to the amazing desktop 
environment I use daily

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

[David Redondo]

Am Freitag, 1. April 2022, 19:09:07 CEST schrieb Nate Graham:
> I would be willing to co-mentor alongside someone else with more dev
> experience.
I am happy to be co-mentor. As I was never a mentor before you can also mentor 
my mentoring ;)

-


>I'm looking for potentials mentors for GSoC 2022 to review/comment my draft
>proposal
Smit: I didn't look at the kcms in question at all but imo 1 week per kcm can 
be very steep.

David 

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

[Nicolas Fella]

Hi,

On 3/31/22 19:04, Smit Patil wrote:

Hello all,
I'm looking for potentials mentors for GSoC 2022 to review/comment my
draft proposal
for this task:-
https://community.kde.org/GSoC/2022/Ideas#Plasma_modernise_system_settings_modules


I think for the Font Management KCM there was a conclusion that we would
remove that from systemsettings and have it as a standalone application
instead, so porting to QML isn't strictly necessary.

For the KWin Scripts KCM Alex is already working on a port:
https://invent.kde.org/plasma/kwin/-/commits/work/alex/scripts_qml_tmp

As for the proposal itself: It's currently a bit superficial, merely
saying port X in week Y. Maybe you could add a bit more detail about
what kind of challenges there might be while porting?

Cheers

Nico

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

[Nate Graham]

Hello Smit,

I would be willing to co-mentor alongside someone else with more dev 
experience.


The project looks like a good one to me.

Nate


On 3/31/22 11:04, Smit Patil wrote:

Hello all,
I'm looking for potentials mentors for GSoC 2022 to review/comment my 
draft proposal
for this task:- 
https://community.kde.org/GSoC/2022/Ideas#Plasma_modernise_system_settings_modules 

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

[Smit Patil]

Hello all,
I'm looking for potentials mentors for GSoC 2022 to review/comment my draft
proposal
for this task:-
https://community.kde.org/GSoC/2022/Ideas#Plasma_modernise_system_settings_modules
# Redesign system settings modules by porting them to QtQuick

# Goals

Port following KCM modules to QtQuick/Kirigami2

1. Font Management
1. File Associations
1. Window Behavior
1. Task Switcher
1. Kwin Script
1. Spell check
1. Screen Edges
1. Gamma
1. Compositor

## Implementation

Porting and redesigning Most of the KCMs will be straightforward 
complete rewrite with similar feature parity with previous ones


## Timeline

This is my proposed timeline.

 - Week 1-2
 
   Port Font Management KCM
   
 - Week 3-4
 
   Port File Associations KCM
   
 - Week 5
 
   Port Window Behavior KCM
   
 - Week 6
 
   Port Task Switcher KCM
   
 - Week 7
 
   Port Kwin Script KCM
   
 - Week 8
 
   Port Spell check KCM

 - Week 9
 
   Redesign and Port Compositor KCM
   
 - Week 10

   Try to get https://invent.kde.org/plasma/kwin/-/merge_requests/1335 merged
   and then Redesign and Port Gamma KCM


My speed may slow down during mid August and November due
my in-sem and end-sem examinations which are are likely 
going to be held in that time

I believe that I can manage both university and GSoC at the same time as 
my college is flexible about attendance
   

## About Me

I'm Smit S. Patil. I'm a student at Sinhgad College of Engineering in Pune 
currently studying Information Technology in 3rd year.
I've been using desktop Linux since 2017 as my primary operating system 
and KDE as my primary Desktop Environment since 2018. 

I've first started programming with C and GTK and self-taught myself since 2017

In 2018, I was selected as runner-up in Google CodeIn 2018 for KDE and PostgreSQL
organization. I sent patches to GCompris software.

Since then, I've also tried to contribute to core KDE by creating a few merge requests
(which you can check out on my [invent profile](https://invent.kde.org/smitpatil))
to kwin, plasma-sdk, and kirigami2 and wish to do more in future 

I'm also known as violetghoul on matrix with username @smit:matrix.org

I'm also submitting a proposal to LLVM and when given a choice
I'll choose KDE because I want to contribute to the amazing desktop 
environment I use daily