<div dir="ltr">Yea, I thought that we could find maybe some intermediate state/goal for the parallel rendering to which we can fallback when the overall goal can't be achieved. I would add a line about the difficulty of this project to the idea list. What do you think about this plan? But if you still think that it's not a good idea, I'll remove it.<div><br></div><div>Your project ideas sound great. I will add these to the ideas list. Also maybe David could mentor one of them.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 18, 2018 at 7:54 PM, Martin Flöser <span dir="ltr"><<a href="mailto:mgraesslin@kde.org" target="_blank">mgraesslin@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Am 2018-01-18 15:23, schrieb Roman Gilg:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I added two KWin project ideas:<br>
<a href="https://community.kde.org/GSoC/2018/Ideas#KWin" rel="noreferrer" target="_blank">https://community.kde.org/GSoC<wbr>/2018/Ideas#KWin</a><br>
</blockquote>
<br></span>
The first idea (parallel rendering) is IMHO too difficult for a GSoC. The other idea sounds reasonable from scope.<br>
<br>
Cheers<br>
Martin<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
On Wed, Jan 17, 2018 at 6:18 PM, Roman Gilg <<a href="mailto:subdiff@gmail.com" target="_blank">subdiff@gmail.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
Valorie, do we have until 23rd with project ideas? I didn't want to<br>
mentor this year because I only was a GSoC student last year, but<br>
since there are not yet many ideas from Plasma/KWin I might do it<br>
anyway.<br>
<br>
Nate, I want to get a rework of the Wayland Mouse KCM already into<br>
Plasma 5.13. But the final GSoC submission is way after the release.<br>
Libinput configuration on X might be still a valuable addition<br>
(although I would like to see these resources better spent on some<br>
other part of the Wayland session, in particular when you factor in<br>
the late final submission next summer).<br>
<br>
Cheers<br>
Roman<br>
<br>
On Mon, Jan 15, 2018 at 8:15 PM, Nate Graham <<a href="mailto:pointedstick@zoho.com" target="_blank">pointedstick@zoho.com</a>><br>
wrote:<br>
I've submitted an idea for System Settings: Improve handling for<br>
touchpads and mice with Libinput<br>
<br>
<br>
</blockquote>
<a href="https://community.kde.org/GSoC/2018/Ideas#Improve_handling_for_touchpads_and_mice_with_Libinput" rel="noreferrer" target="_blank">https://community.kde.org/GSoC<wbr>/2018/Ideas#Improve_handling_<wbr>for_touchpads_and_mice_with_<wbr>Libinput</a><br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[1]<div><div class="h5"><br>
<br>
This is pretty important going forward since most distros are<br>
shipping with Libinput now, but our users aren't able to configure<br>
their devices without resorting to editing xorg config files using a<br>
different driver.<br>
<br>
Nate<br>
<br>
On 01/15/2018 06:13 AM, Dmitry Kazakov wrote:<br>
Hi, Valorie!<br>
<br>
I have just edited the list of Krita ideas, now we have 8 ideas, 4<br>
of which are low-hanging fruits with localized optimizations of the<br>
code. I hope that will help people who do not want to learn all<br>
half-million lines of Krita code.<br>
<br>
Speaking truly, I think I understand why there is so little effort<br>
from people with the ideas. Since the last year Google forbids<br>
students to apply more than 2 times, it means that most of the<br>
applicants will be newcomers and, most probably, they will not be<br>
able to prepare some extensive proposal/design for a project. It is<br>
just too difficult to prepare a good proposal for a project so big<br>
in size. So it might be that the quality of last year proposals<br>
discouraged people from doing this work again.<br>
<br>
The only way how we can solve the issue is to prepare very<br>
scope-limited tasks, such that the students would not need to learn<br>
all the code (in our case we just added AVX optimizations, which are<br>
limited to a scope of a couple of classes). But that is not always<br>
possible or makes sense for the some projects.<br>
<br>
On 15.01.2018 03:39, Valorie Zimmerman wrote:<br>
I'm very discouraged to see so little movement on this. After<br>
skipping GCi this past fall, are we now also considering skipping<br>
GSoC? Or downsizing the number of students we are mentoring?<br>
<br>
Without Ideas we will not get students. More important, we must<br>
complete the Org application soon, and the Ideas page is the core of<br>
that application.<br>
<br>
This is good for your team and your project, in the long run. It<br>
brings in new contributors and fresh ideas.<br>
<br>
If you need some guidance, please read<br>
<br>
</div></div></blockquote>
<a href="https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list.html" rel="noreferrer" target="_blank">https://google.github.io/gsocg<wbr>uides/mentor/defining-a-projec<wbr>t-ideas-list.html</a><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[2]<span class=""><br>
<br>
I should have linked to it for the last email.<br>
<br>
Valorie<br>
<br>
On Wed, Jan 10, 2018 at 3:03 PM, Valorie Zimmerman<br>
<<a href="mailto:valorie.zimmerman@gmail.com" target="_blank">valorie.zimmerman@gmail.com</a> <mailto:<a href="mailto:valorie.zimmerman@gmail.com" target="_blank">valorie.zimmerman@gmai<wbr>l.com</a>>><br>
wrote:<br>
<br>
Hello GSoC mentors, and teams supporting mentors,<br>
<br></span>
TL;DR: Fill out <a href="https://community.kde.org/GSoC/2018/Ideas" rel="noreferrer" target="_blank">https://community.kde.org/GSoC<wbr>/2018/Ideas</a> [3]<br>
<<a href="https://community.kde.org/GSoC/2018/Ideas" rel="noreferrer" target="_blank">https://community.kde.org/GSo<wbr>C/2018/Ideas</a> [3]>; read<div><div class="h5"><br>
<a href="https://community.kde.org/GSoC" rel="noreferrer" target="_blank">https://community.kde.org/GSoC</a><wbr>. Now.<br>
<br>
Every year, we've asked for more time to get ramped up for GSoC,<br>
and so now is the time for organizations to apply[1]. We have<br>
begun to write our application, and that means that our Ideas<br>
page needs to be filled NOW, because that is the prime<br>
consideration for the GSoC team once the Org Applications<br>
deadline<br>
has passed.<br>
<br>
The quality of our ideas and the guidance they give our students<br>
are the most important part of our application. Please begin<br>
filling in your ideas now if you have not already, and ensure<br>
that<br>
that page is comprehensive, accurate and attractive. Including<br>
screenshots and other images is allowed, if it enriches the idea<br>
for a project. *Please ensure complete information about how to<br>
contact the team*; this is crucial.<br>
<br>
Also, take a look at the landing page<br>
<a href="https://community.kde.org/GSoC" rel="noreferrer" target="_blank">https://community.kde.org/GSoC</a><wbr>. Experienced mentors agree that:<br>
<br>
1. commits must be made before the student proposal is<br>
submitted,<br>
and linked on that proposal, and<br>
<br>
2. that regular communication from the student must be initiated<br>
by the student at least weekly, and we expect daily or nearly<br>
daily communication with the team in a more informal way.<br>
<br>
Be sure to point students to that information, as this should<br>
lower the number of proposals, while raising the quality.<br>
<br></div></div>
1. <a href="https://developers.google.com/open-source/gsoc/timeline" rel="noreferrer" target="_blank">https://developers.google.com/<wbr>open-source/gsoc/timeline</a> [4]<br>
<<a href="https://developers.google.com/open-source/gsoc/timeline" rel="noreferrer" target="_blank">https://developers.google.com<wbr>/open-source/gsoc/timeline</a> [4]><span class=""><br>
<br>
PS: If your team has an Idea, ensure that you have mentors for<br>
it,<br>
and that those mentors are subscribe to KDE-Soc-Mentor list.<br>
Remove any ideas without mentors available, please. Now, before<br>
you forget!<br>
<br>
Valorie<br>
<br>
--<br>
<a href="http://about.me/valoriez" rel="noreferrer" target="_blank">http://about.me/valoriez</a><br>
<br>
--<br>
Dmitry Kazakov<br>
</span></blockquote>
<br>
<br>
<br><span class="">
Links:<br>
------<br>
[1]<br>
<a href="https://community.kde.org/GSoC/2018/Ideas#Improve_handling_for_touchpads_and_mice_with_Libinput" rel="noreferrer" target="_blank">https://community.kde.org/GSoC<wbr>/2018/Ideas#Improve_handling_<wbr>for_touchpads_and_mice_with_<wbr>Libinput</a><br>
[2]<br>
<a href="https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list.html" rel="noreferrer" target="_blank">https://google.github.io/gsocg<wbr>uides/mentor/defining-a-projec<wbr>t-ideas-list.html</a><br>
[3] <a href="https://community.kde.org/GSoC/2018/Ideas" rel="noreferrer" target="_blank">https://community.kde.org/GSoC<wbr>/2018/Ideas</a><br>
[4] <a href="https://developers.google.com/open-source/gsoc/timeline" rel="noreferrer" target="_blank">https://developers.google.com/<wbr>open-source/gsoc/timeline</a><br>
</span></blockquote>
</blockquote></div><br></div>