<div dir="ltr">Yes, Jan 23 is the deadline for the Org application. Of course we can continue to add, edit and tinker around the edges until the students begin to apply. But we want a lovely list by the 23rd. -v<br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 17, 2018 at 9:18 AM, Roman Gilg <span dir="ltr"><<a href="mailto:subdiff@gmail.com" target="_blank">subdiff@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>Valorie, do we have until 23rd with project ideas? I didn't want to mentor this year because I only was a GSoC student last year, but since there are not yet many ideas from Plasma/KWin I might do it anyway.</div><div><br></div><div>Nate, I want to get a rework of the Wayland Mouse KCM already into Plasma 5.13. But the final GSoC submission is way after the release. Libinput configuration on X might be still a valuable addition (although I would like to see these resources better spent on some other part of the Wayland session, in particular when you factor in the late final submission next summer).</div><div><br></div><div>Cheers</div><span class="HOEnZb"><font color="#888888"><div>Roman</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 15, 2018 at 8:15 PM, Nate Graham <span dir="ltr"><<a href="mailto:pointedstick@zoho.com" target="_blank">pointedstick@zoho.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've submitted an idea for System Settings: Improve handling for touchpads and mice with Libinput<br>
<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_f<wbr>or_touchpads_and_mice_with_Lib<wbr>input</a><br>
<br>
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.<br>
<br>
Nate<span><br>
<br>
<br>
On 01/15/2018 06:13 AM, Dmitry Kazakov wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
Hi, Valorie!<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
<br>
On 15.01.2018 03:39, Valorie Zimmerman wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
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?<br>
<br>
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.<br>
<br>
This is good for your team and your project, in the long run. It brings in new contributors and fresh ideas.<br>
<br>
If you need some guidance, please read <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>
<br>
I should have linked to it for the last email.<br>
<br>
Valorie<br>
<br></span><div><div class="m_-1351826326959781313h5">
On Wed, Jan 10, 2018 at 3:03 PM, Valorie Zimmerman <<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>>> wrote:<br>
<br>
<br>
Hello GSoC mentors, and teams supporting mentors,<br>
<br>
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><br>
<<a href="https://community.kde.org/GSoC/2018/Ideas" rel="noreferrer" target="_blank">https://community.kde.org/GSo<wbr>C/2018/Ideas</a>>; read<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 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 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 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>
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><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>><br>
<br>
PS: If your team has an Idea, ensure that you have mentors for 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>
<br>
-- <br>
<a href="http://about.me/valoriez" rel="noreferrer" target="_blank">http://about.me/valoriez</a><br>
</div></div></blockquote>
<br><span class="m_-1351826326959781313HOEnZb"><font color="#888888">
-- <br>
Dmitry Kazakov<br>
<br>
</font></span></blockquote>
<br>
</blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><a href="http://about.me/valoriez" target="_blank">http://about.me/valoriez</a><br><br><br></div>
</div></div>