As Google Code-in ends, time to plan for Google Summer of Code
aleixpol at kde.org
Mon Jan 16 16:46:48 UTC 2017
On Mon, Jan 16, 2017 at 2:53 PM, Kevin Funk <kfunk at kde.org> wrote:
> See below, we need ideas for KDevelop!
> I think I'll manage to mentor a GSoC again (if it happens) this year.
> Ideas (party copied from last year's list of ideas which did not happen):
> * KDevelop: Improve QML/JS integration: Module path dialog, proper handling of
> QRC imports, navigation for 'import ...' lines, etc.
+1.5 (0.5 extra because it has on impact on my workflow)
> * KDevelop: Go integration
> * KDevelop: Rust integration
> * KDevelop: Windows debugger integration (CDB)
I'm a bit afraid that this could end up not being used, hence broken.
How usable is lldb on windows? Does it just work on clang binaries?
> ---------- Forwarded Message ----------
> Subject: As Google Code-in ends, time to plan for Google Summer of Code
> Date: Friday, 13 January 2017, 13:38:40 CET
> From: Valorie Zimmerman <valorie.zimmerman at gmail.com>
> To: KDE community <kde-community at kde.org>, Kde Soc Mentor <kde-soc-
> mentor at kde.org>, Frameworks Devel <kde-devel at kde.org>, kde-core-devel <kde-
> core-devel at kde.org>
> I've just finished preparing the new Ideas page for 2017:
> It is basically the same as every other year, and has no previous
> ideas on it. If you or your project plan to present a former idea
> again, click on the 2016 Ideas link, and copy/paste it into the 2017
> page as soon as possible.
> Of course, new ideas are welcome as well, as long as there are mentors
> available. We'll remove ideas with no mentor listed. Please ensure
> that there is contact information for each mentor.
> *Please* do no maintain a separate Ideas page which you present to
> students. We need one central place for Ideas, and rules and
> guidelines as well.
> Speaking of guidelines: please read over
> https://community.kde.org/GSoC and see what you think. We've tried to
> clarify the language and make our general expectations clear, as we
> think being upfront about our standards is one way to get better
> proposals and better students.
> Kevin Funk | kfunk at kde.org | http://kfunk.org
More information about the KDevelop-devel