Re: KDE and Google Summer of Code 2018

[Thomas Pfeiffer]

> On 22. Jan 2018, at 00:35, David Edmundson  wrote:
> 
> 
> 
> On Sun, Jan 21, 2018 at 7:25 PM, Albert Astals Cid  > wrote:
> El divendres, 19 de gener de 2018, a les 10:42:44 CET, Marco Martin va
> escriure:
> > On Mon, Jan 15, 2018 at 8:15 PM, Nate Graham  > > wrote:
> > > I've submitted an idea for System Settings: Improve handling for touchpads
> > > and mice with Libinput
> >
> > Speaking of systemsettings, would be a good fit porting to qml some
> > medium-to-big kcm?
> 
> What's the actual benefit of that porting?
> 
> 
> Unifying and fixing all our KCMs is the intention, there's new designs from 
> Andy.
> Use of QtQuick is a side effect, but the intended direction if we're 
> rewriting something anyway.

Let’s not forget touch-friendliness as an important benefit!

Re: KDE and Google Summer of Code 2018

[David Edmundson]

On Sun, Jan 21, 2018 at 7:25 PM, Albert Astals Cid  wrote:

> El divendres, 19 de gener de 2018, a les 10:42:44 CET, Marco Martin va
> escriure:
> > On Mon, Jan 15, 2018 at 8:15 PM, Nate Graham 
> wrote:
> > > I've submitted an idea for System Settings: Improve handling for
> touchpads
> > > and mice with Libinput
> >
> > Speaking of systemsettings, would be a good fit porting to qml some
> > medium-to-big kcm?
>
> What's the actual benefit of that porting?
>
>
Unifying and fixing all our KCMs is the intention, there's new designs from
Andy.
Use of QtQuick is a side effect, but the intended direction if we're
rewriting something anyway.

There's multiple threads on plasma-devel if you have something to follow
up. I don't think it's something for the GSOC thread as it's work already
happening. Thread "System Settings KCM Tidying" is probably the best
overview.

David

Re: KDE and Google Summer of Code 2018

[Albert Astals Cid]

El divendres, 19 de gener de 2018, a les 10:42:44 CET, Marco Martin va 
escriure:
> On Mon, Jan 15, 2018 at 8:15 PM, Nate Graham  wrote:
> > I've submitted an idea for System Settings: Improve handling for touchpads
> > and mice with Libinput
> 
> Speaking of systemsettings, would be a good fit porting to qml some
> medium-to-big kcm?

What's the actual benefit of that porting?

Cheers,
  Albert

> --
> Marco Martin

Re: Re: KDE and Google Summer of Code 2018

[Clemens Toennies]

On Jan 19, 2018 6:11 PM, "pointedstick"  wrote:
>
> While we're at it, let's not only re-work existing KCMs, but try to take
the opportunity to simplify and consolidate where possible. For example,
the Launch Feedback KCM consists only of two checkboxes that could easily
be moved elsewhere (the cursor part into the Cursors KCM, and the Task
Manager part into individual Task Manager widgets' settings, perhaps?)

Good points.
The Fx Speed in the compositing kcm could also fit in the Effects kcm.

Greetings, Clemens.

>  On Fri, 19 Jan 2018 09:06:52 -0800 David Edmundson  wrote 
> >
> >
> >On Fri, Jan 19, 2018 at 4:41 PM, Marco Martin  wrote:
> >On venerdì 19 gennaio 2018 13:42:25 CET David Edmundson wrote:
> > > Note that they'll be finishing GSOC around the same time as 5.14, so
that
> > > potentially means GSOC work released in 5.15.
> > > We shouldn't pick high priority ones that we want done before then.
> >
> > basing on the priorities recorded in
https://phabricator.kde.org/project/view/
> > 254/
> >
> > a possible list, among the "medium":
> > * removable devices
> > * printers
> > * spell check
> > * formats
> >
> > among the "high", but we can live if gets delayed a bit:
> > * mouse (can of worms?)
> > * date/time
> > * user manager
> >
> > other suggestions?
> >
> >
> >
> >Mouse is maybe covered by Roman's existing task?
> >Printers isn't part of Plasma, we need to check with the author.
> >
> >
> >
> >But I think all of them are good options.
> >
> >
> >
> >
> >They're not the same size, I don't think working on date and time would
take up 3 months.
> >Maybe we can group a few of the simpler ones together?
> >
> >
> >Go for it.
> >You can put me down in the list of mentors.
> >
> >
> >David
> >
> >
> >
> >
> >
> > --
> > Marco Martin
> >
> >
> >
> >
> >
> >
> >
>
>

Re: Re: KDE and Google Summer of Code 2018

[pointedstick]

While we're at it, let's not only re-work existing KCMs, but try to take the 
opportunity to simplify and consolidate where possible. For example, the Launch 
Feedback KCM consists only of two checkboxes that could easily be moved 
elsewhere (the cursor part into the Cursors KCM, and the Task Manager part into 
individual Task Manager widgets' settings, perhaps?)

Nate


 On Fri, 19 Jan 2018 09:06:52 -0800 David Edmundson  wrote  
>
>
>On Fri, Jan 19, 2018 at 4:41 PM, Marco Martin  wrote:
>On venerdì 19 gennaio 2018 13:42:25 CET David Edmundson wrote:
> > Note that they'll be finishing GSOC around the same time as 5.14, so that
> > potentially means GSOC work released in 5.15.
> > We shouldn't pick high priority ones that we want done before then.
> 
> basing on the priorities recorded in https://phabricator.kde.org/project/view/
> 254/
> 
> a possible list, among the "medium":
> * removable devices
> * printers
> * spell check
> * formats
> 
> among the "high", but we can live if gets delayed a bit:
> * mouse (can of worms?)
> * date/time
> * user manager
> 
> other suggestions?
>
>
>
>Mouse is maybe covered by Roman's existing task?
>Printers isn't part of Plasma, we need to check with the author.
>
>
>
>But I think all of them are good options. 
>
>
>
>
>They're not the same size, I don't think working on date and time would take 
>up 3 months.
>Maybe we can group a few of the simpler ones together?
>
>
>Go for it.
>You can put me down in the list of mentors.
>
>
>David
>
>
>
> 
> 
> --
> Marco Martin
> 
>
>
>
>
> 
>

Re: KDE and Google Summer of Code 2018

[David Edmundson]

On Fri, Jan 19, 2018 at 4:41 PM, Marco Martin  wrote:

> On venerdì 19 gennaio 2018 13:42:25 CET David Edmundson wrote:
> > Note that they'll be finishing GSOC around the same time as 5.14, so that
> > potentially means GSOC work released in 5.15.
> > We shouldn't pick high priority ones that we want done before then.
>
> basing on the priorities recorded in https://phabricator.kde.org/
> project/view/
> 254/
>
> a possible list, among the "medium":
> * removable devices
> * printers
> * spell check
> * formats
>
> among the "high", but we can live if gets delayed a bit:
> * mouse (can of worms?)
> * date/time
> * user manager
>
> other suggestions?
>

Mouse is maybe covered by Roman's existing task?
Printers isn't part of Plasma, we need to check with the author.

But I think all of them are good options.

They're not the same size, I don't think working on date and time would
take up 3 months.
Maybe we can group a few of the simpler ones together?

Go for it.
You can put me down in the list of mentors.

David


>
> --
> Marco Martin
>

Re: KDE and Google Summer of Code 2018

[Marco Martin]

On venerdì 19 gennaio 2018 13:42:25 CET David Edmundson wrote:
> Note that they'll be finishing GSOC around the same time as 5.14, so that
> potentially means GSOC work released in 5.15.
> We shouldn't pick high priority ones that we want done before then.

basing on the priorities recorded in https://phabricator.kde.org/project/view/
254/

a possible list, among the "medium":
* removable devices
* printers
* spell check
* formats

among the "high", but we can live if gets delayed a bit:
* mouse (can of worms?)
* date/time
* user manager

other suggestions?


-- 
Marco Martin

Re: KDE and Google Summer of Code 2018

[David Edmundson]

On Fri, Jan 19, 2018 at 9:42 AM, Marco Martin  wrote:

> On Mon, Jan 15, 2018 at 8:15 PM, Nate Graham 
> wrote:
> > I've submitted an idea for System Settings: Improve handling for
> touchpads
> > and mice with Libinput
>
> Speaking of systemsettings, would be a good fit porting to qml some
> medium-to-big kcm?
>

It's perfect.

Though I'd like us to emphasise that it's not just about doing a simple 1:1
switch of the UI layer but building on Andy's mockups with a UI redesign,
doing a code tidy up, and fixing any relevant open bugs in that module at
the same time.

Note that they'll be finishing GSOC around the same time as 5.14, so that
potentially means GSOC work released in 5.15.
We shouldn't pick high priority ones that we want done before then.

David

Re: KDE and Google Summer of Code 2018

[Marco Martin]

On Mon, Jan 15, 2018 at 8:15 PM, Nate Graham  wrote:
> I've submitted an idea for System Settings: Improve handling for touchpads
> and mice with Libinput

Speaking of systemsettings, would be a good fit porting to qml some
medium-to-big kcm?
--
Marco Martin

Re: KDE and Google Summer of Code 2018

[Nate Graham]

I've submitted an idea for System Settings: Improve handling for 
touchpads and mice with Libinput


https://community.kde.org/GSoC/2018/Ideas#Improve_handling_for_touchpads_and_mice_with_Libinput

This is pretty important going forward since most distros are shipping 
with Libinput now, but our users aren't able to configure their devices 
without resorting to editing xorg config files using a different driver.


Nate


On 01/15/2018 06:13 AM, Dmitry Kazakov wrote:

Hi, Valorie!

I have just edited the list of Krita ideas, now we have 8 ideas, 4 of 
which are low-hanging fruits with localized optimizations of the code. I 
hope that will help people who do not want to learn all half-million 
lines of Krita code.


Speaking truly, I think I understand why there is so little effort from 
people with the ideas. Since the last year Google forbids students to 
apply more than 2 times, it means that most of the applicants will be 
newcomers and, most probably, they will not be able to prepare some 
extensive proposal/design for a project. It is just too difficult to 
prepare a good proposal for a project so big in size. So it might be 
that the quality of last year proposals discouraged people from doing 
this work again.


The only way how we can solve the issue is to prepare very scope-limited 
tasks, such that the students would not need to learn all the code (in 
our case we just added AVX optimizations, which are limited to a scope 
of a couple of classes). But that is not always possible or makes sense 
for the some projects.



On 15.01.2018 03:39, Valorie Zimmerman wrote:
I'm very discouraged to see so little movement on this. After skipping 
GCi this past fall, are we now also considering skipping GSoC? Or 
downsizing the number of students we are mentoring?


Without Ideas we will not get students. More important, we must 
complete the Org application soon, and the Ideas page is the core of 
that application.


This is good for your team and your project, in the long run. It 
brings in new contributors and fresh ideas.


If you need some guidance, please read 
https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list.html


I should have linked to it for the last email.

Valorie

On Wed, Jan 10, 2018 at 3:03 PM, Valorie Zimmerman 
mailto:valorie.zimmer...@gmail.com>> wrote:



Hello GSoC mentors, and teams supporting mentors,

TL;DR: Fill out https://community.kde.org/GSoC/2018/Ideas
; read
https://community.kde.org/GSoC. Now.

Every year, we've asked for more time to get ramped up for GSoC,
and so now is the time for organizations to apply[1]. We have
begun to write our application, and  that means that our Ideas
page needs to be filled NOW, because that is the prime
consideration for the GSoC team once the Org Applications deadline
has passed.

The quality of our ideas and the guidance they give our students
are the most important part of our application. Please begin
filling in your ideas now if you have not already, and ensure that
that page is comprehensive, accurate and attractive. Including
screenshots and other images is allowed, if it enriches the idea
for a project. *Please ensure complete information about how to
contact the team*; this is crucial.

Also, take a look at the landing page
https://community.kde.org/GSoC. Experienced mentors agree that:

1. commits must be made before the student proposal is submitted,
and linked on that proposal, and

2. that regular communication from the student must be initiated
by the student at least weekly, and we expect daily or nearly
daily communication with the team in a more informal way.

Be sure to point students to that information, as this should
lower the number of proposals, while raising the quality.

1. https://developers.google.com/open-source/gsoc/timeline


PS: If your team has an Idea, ensure that you have mentors for it,
and that those mentors are subscribe to KDE-Soc-Mentor list.
Remove any ideas without mentors available, please. Now, before
you forget!

Valorie



--
http://about.me/valoriez


--
Dmitry Kazakov

Re: KDE and Google Summer of Code 2018

[Dmitry Kazakov]

Hi, Valorie!

I have just edited the list of Krita ideas, now we have 8 ideas, 4 of 
which are low-hanging fruits with localized optimizations of the code. I 
hope that will help people who do not want to learn all half-million 
lines of Krita code.


Speaking truly, I think I understand why there is so little effort from 
people with the ideas. Since the last year Google forbids students to 
apply more than 2 times, it means that most of the applicants will be 
newcomers and, most probably, they will not be able to prepare some 
extensive proposal/design for a project. It is just too difficult to 
prepare a good proposal for a project so big in size. So it might be 
that the quality of last year proposals discouraged people from doing 
this work again.


The only way how we can solve the issue is to prepare very scope-limited 
tasks, such that the students would not need to learn all the code (in 
our case we just added AVX optimizations, which are limited to a scope 
of a couple of classes). But that is not always possible or makes sense 
for the some projects.



On 15.01.2018 03:39, Valorie Zimmerman wrote:
I'm very discouraged to see so little movement on this. After skipping 
GCi this past fall, are we now also considering skipping GSoC? Or 
downsizing the number of students we are mentoring?


Without Ideas we will not get students. More important, we must 
complete the Org application soon, and the Ideas page is the core of 
that application.


This is good for your team and your project, in the long run. It 
brings in new contributors and fresh ideas.


If you need some guidance, please read 
https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list.html


I should have linked to it for the last email.

Valorie

On Wed, Jan 10, 2018 at 3:03 PM, Valorie Zimmerman 
mailto:valorie.zimmer...@gmail.com>> wrote:



Hello GSoC mentors, and teams supporting mentors,

TL;DR: Fill out https://community.kde.org/GSoC/2018/Ideas
; read
https://community.kde.org/GSoC. Now.

Every year, we've asked for more time to get ramped up for GSoC,
and so now is the time for organizations to apply[1]. We have
begun to write our application, and  that means that our Ideas
page needs to be filled NOW, because that is the prime
consideration for the GSoC team once the Org Applications deadline
has passed.

The quality of our ideas and the guidance they give our students
are the most important part of our application. Please begin
filling in your ideas now if you have not already, and ensure that
that page is comprehensive, accurate and attractive. Including
screenshots and other images is allowed, if it enriches the idea
for a project. *Please ensure complete information about how to
contact the team*; this is crucial.

Also, take a look at the landing page
https://community.kde.org/GSoC. Experienced mentors agree that:

1. commits must be made before the student proposal is submitted,
and linked on that proposal, and

2. that regular communication from the student must be initiated
by the student at least weekly, and we expect daily or nearly
daily communication with the team in a more informal way.

Be sure to point students to that information, as this should
lower the number of proposals, while raising the quality.

1. https://developers.google.com/open-source/gsoc/timeline


PS: If your team has an Idea, ensure that you have mentors for it,
and that those mentors are subscribe to KDE-Soc-Mentor list.
Remove any ideas without mentors available, please. Now, before
you forget!

Valorie



--
http://about.me/valoriez


--
Dmitry Kazakov

Re: KDE and Google Summer of Code 2018

[Johnny Jazeix]

Hi,

on GCompris side, we hope/plan to mentor 2 students like last year. I
updated the page to add one more task.

Regarding the events: this year, we were planning to skip SoK to focus more
on GCi and GSoC, having the 3 events is too consuming and do not allow us
to progress on our main tasks. There was a bit of change due to the fact
that it was GCi that was skipped but the main point is still there, we
don't have enough time/resource to handle the 3 events.

Johnny


2018-01-15 1:39 GMT+01:00 Valorie Zimmerman :

> I'm very discouraged to see so little movement on this. After skipping GCi
> this past fall, are we now also considering skipping GSoC? Or downsizing
> the number of students we are mentoring?
>
> Without Ideas we will not get students. More important, we must complete
> the Org application soon, and the Ideas page is the core of that
> application.
>
> This is good for your team and your project, in the long run. It brings in
> new contributors and fresh ideas.
>
> If you need some guidance, please read https://google.github.io/
> gsocguides/mentor/defining-a-project-ideas-list.html
>
> I should have linked to it for the last email.
>
> Valorie
>
> On Wed, Jan 10, 2018 at 3:03 PM, Valorie Zimmerman <
> valorie.zimmer...@gmail.com> wrote:
>
>>
>> Hello GSoC mentors, and teams supporting mentors,
>>
>> TL;DR: Fill out https://community.kde.org/GSoC/2018/Ideas; read
>> https://community.kde.org/GSoC. Now.
>>
>> Every year, we've asked for more time to get ramped up for GSoC, and so
>> now is the time for organizations to apply[1]. We have begun to write our
>> application, and  that means that our Ideas page needs to be filled NOW,
>> because that is the prime consideration for the GSoC team once the Org
>> Applications deadline has passed.
>>
>> The quality of our ideas and the guidance they give our students are the
>> most important part of our application. Please begin filling in your ideas
>> now if you have not already, and ensure that that page is comprehensive,
>> accurate and attractive. Including screenshots and other images is allowed,
>> if it enriches the idea for a project. *Please ensure complete information
>> about how to contact the team*; this is crucial.
>>
>> Also, take a look at the landing page https://community.kde.org/GSoC.
>> Experienced mentors agree that:
>>
>> 1. commits must be made before the student proposal is submitted, and
>> linked on that proposal, and
>>
>> 2. that regular communication from the student must be initiated by the
>> student at least weekly, and we expect daily or nearly daily communication
>> with the team in a more informal way.
>>
>> Be sure to point students to that information, as this should lower the
>> number of proposals, while raising the quality.
>>
>> 1. https://developers.google.com/open-source/gsoc/timeline
>>
>> PS: If your team has an Idea, ensure that you have mentors for it, and
>> that those mentors are subscribe to KDE-Soc-Mentor list. Remove any ideas
>> without mentors available, please. Now, before you forget!
>>
>> Valorie
>>
>
>
> --
> http://about.me/valoriez
>

Re: KDE and Google Summer of Code 2018

[Valorie Zimmerman]

I'm very discouraged to see so little movement on this. After skipping GCi
this past fall, are we now also considering skipping GSoC? Or downsizing
the number of students we are mentoring?

Without Ideas we will not get students. More important, we must complete
the Org application soon, and the Ideas page is the core of that
application.

This is good for your team and your project, in the long run. It brings in
new contributors and fresh ideas.

If you need some guidance, please read
https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list.html

I should have linked to it for the last email.

Valorie

On Wed, Jan 10, 2018 at 3:03 PM, Valorie Zimmerman <
valorie.zimmer...@gmail.com> wrote:

>
> Hello GSoC mentors, and teams supporting mentors,
>
> TL;DR: Fill out https://community.kde.org/GSoC/2018/Ideas; read
> https://community.kde.org/GSoC. Now.
>
> Every year, we've asked for more time to get ramped up for GSoC, and so
> now is the time for organizations to apply[1]. We have begun to write our
> application, and  that means that our Ideas page needs to be filled NOW,
> because that is the prime consideration for the GSoC team once the Org
> Applications deadline has passed.
>
> The quality of our ideas and the guidance they give our students are the
> most important part of our application. Please begin filling in your ideas
> now if you have not already, and ensure that that page is comprehensive,
> accurate and attractive. Including screenshots and other images is allowed,
> if it enriches the idea for a project. *Please ensure complete information
> about how to contact the team*; this is crucial.
>
> Also, take a look at the landing page https://community.kde.org/GSoC.
> Experienced mentors agree that:
>
> 1. commits must be made before the student proposal is submitted, and
> linked on that proposal, and
>
> 2. that regular communication from the student must be initiated by the
> student at least weekly, and we expect daily or nearly daily communication
> with the team in a more informal way.
>
> Be sure to point students to that information, as this should lower the
> number of proposals, while raising the quality.
>
> 1. https://developers.google.com/open-source/gsoc/timeline
>
> PS: If your team has an Idea, ensure that you have mentors for it, and
> that those mentors are subscribe to KDE-Soc-Mentor list. Remove any ideas
> without mentors available, please. Now, before you forget!
>
> Valorie
>


-- 
http://about.me/valoriez

KDE and Google Summer of Code 2018

[Valorie Zimmerman]

Hello GSoC mentors, and teams supporting mentors,

TL;DR: Fill out https://community.kde.org/GSoC/2018/Ideas; read
https://community.kde.org/GSoC. Now.

Every year, we've asked for more time to get ramped up for GSoC, and so now
is the time for organizations to apply[1]. We have begun to write our
application, and  that means that our Ideas page needs to be filled NOW,
because that is the prime consideration for the GSoC team once the Org
Applications deadline has passed.

The quality of our ideas and the guidance they give our students are the
most important part of our application. Please begin filling in your ideas
now if you have not already, and ensure that that page is comprehensive,
accurate and attractive. Including screenshots and other images is allowed,
if it enriches the idea for a project. *Please ensure complete information
about how to contact the team*; this is crucial.

Also, take a look at the landing page https://community.kde.org/GSoC.
Experienced mentors agree that:

1. commits must be made before the student proposal is submitted, and
linked on that proposal, and

2. that regular communication from the student must be initiated by the
student at least weekly, and we expect daily or nearly daily communication
with the team in a more informal way.

Be sure to point students to that information, as this should lower the
number of proposals, while raising the quality.

1. https://developers.google.com/open-source/gsoc/timeline

PS: If your team has an Idea, ensure that you have mentors for it, and that
those mentors are subscribe to KDE-Soc-Mentor list. Remove any ideas
without mentors available, please. Now, before you forget!

Valorie
-- 
http://about.me/valoriez