https://community.kde.org/api.php?action=feedcontributions&user=Leinir&feedformat=atomKDE Community Wiki - User contributions [en]2024-03-28T09:54:25ZUser contributionsMediaWiki 1.40.2https://community.kde.org/index.php?title=Akademy/2022/Workshop:_Making_Zynthbox_Playground_Modules&diff=94726Akademy/2022/Workshop: Making Zynthbox Playground Modules2022-09-28T09:29:03Z<p>Leinir: </p>
<hr />
<div>== When, Where, and What? ==<br />
<br />
Room 3 – 4th October 17:00<br />
<br />
'''First things first:''' Zynthbox is a free software music noodling platform, or workshop if you will, for easily experimenting with and capturing musical ideas. One of the things the platform has is a kind of free-form part-logic, part-visual plugin system called Playground Modules. These modules can provide anything from, say, a couple of buttons that throw some midi notes into the ether to make the synths make a noise, through visually dense keyboard systems (like the included notes grid), chord generation tools, to full blown sequencer editors (like the included step sequencer), to automatic note generators which interact with Zynthbox' playback system in real-time while playing.<br />
<br />
== Plan of Approach ==<br />
<br />
At this workshop, we will first do a quick introduction to Zynthbox itself, so you can more easily see where the playground modules fit in, followed by a short introduction to how to actually build the things, and distribute them to people via Zynthbox' sharing site (which lives alongside the KDE Store).<br />
<br />
=== What should you know before we start? ===<br />
<br />
I'm not going to be teaching anybody QML here, so you'll need to come prepared for that (sorry, we don't have time, but i'm told it's easy enough if you have a working understanding of react and similar web frameworks). Outside of that, i am going to try and show you what you need to do, but if you want to prepare ahead of time, and of course i would certainly recommend that you at least skim through it, you can take a look at the Playground Modules wiki page here: https://wiki.zynthbox.io/index.php?title=Playground_Modules<br />
<br />
If you want something to actually run the thing on, you're going to need a Raspberry Pi 4, and optimally a touch screen (we target a 1024x600 one, so that'd be your best bet). I will have one with me, but of course that's only one, so plan accordingly ;)<br />
<br />
PS: "Why is this at a KDE Conference, when it's not a KDE project?" you ask very sensibly. Zynthbox' UI stack is based heavily on a pile of KDE technologies, primarily but not limited to Kirigami, KWin, and KNewStuff, and i am just really keen to show it to people :)<br />
<br />
== Notes for the wrapup ==<br />
<br />
TBW, obviously ;)</div>Leinirhttps://community.kde.org/index.php?title=Akademy/2022/Workshop:_Making_Zynthbox_Playground_Modules&diff=94725Akademy/2022/Workshop: Making Zynthbox Playground Modules2022-09-28T09:08:15Z<p>Leinir: </p>
<hr />
<div>== When, Where, and What? ==<br />
<br />
Room 3 – 4th October 17:00<br />
<br />
'''First things first:''' Zynthbox is a free software music noodling platform, or workshop if you will, for easily experimenting with and capturing musical ideas. One of the things the platform has is a kind of free-form part-logic, part-visual plugin system called Playground Modules. These modules can provide anything from, say, a couple of buttons that throw some midi notes into the ether to make the synths make a noise, through visually dense keyboard systems (like the included notes grid), chord generation tools, to full blown sequencer editors (like the included step sequencer), to automatic note generators which interact with Zynthbox' playback system in real-time while playing.<br />
<br />
== Plan of Approach ==<br />
<br />
At this workshop, we will first do a quick introduction to Zynthbox itself, so you can more easily see where the playground modules fit in, followed by a short introduction to how to actually build the things, and distribute them to people via Zynthbox' sharing site (which lives alongside the KDE Store).<br />
<br />
=== What should you know before we start? ===<br />
<br />
I'm not going to be teaching anybody QML here, so you'll need to come prepared for that (sorry, we don't have time, but i'm told it's easy enough if you have a working understanding of react and similar web frameworks). Outside of that, i am going to try and show you what you need to do, but if you want to prepare ahead of time, and of course i would certainly recommend that you at least skim through it, you can take a look at the Playground Modules wiki page here: https://wiki.zynthbox.io/index.php?title=Playground_Modules<br />
<br />
PS: "Why is this at a KDE Conference, when it's not a KDE project?" you ask very sensibly. Zynthbox' UI stack is based heavily on a pile of KDE technologies, primarily but not limited to Kirigami, KWin, and KNewStuff, and i am just really keen to show it to people :)<br />
<br />
== Notes for the wrapup ==<br />
<br />
TBW, obviously ;)</div>Leinirhttps://community.kde.org/index.php?title=Akademy/2022/Tuesday&diff=94724Akademy/2022/Tuesday2022-09-28T09:05:22Z<p>Leinir: /* Room 3 – 4th October */</p>
<hr />
<div>= BoF sessions on Tuesday, 4th October 2022 =<br />
<br />
''All rooms are in *tbd* and have *tbd infrastructure*.''<br />
<br />
If you need any other equipment, please send an email to akademy-team@kde.org.<br />Please put your name and email address in the Host/Notes section. There is no length limitation; text will wrap. <br />
<br />
'''BoF Wrap-up at 18:00'''<br /><br />
Please join the BoF wrap-up session this evening. Another opportunity for communication. Share outcomes and plans, cross-pollinate, attract attention to your project.<br />
Please select someone from your BoF to give a summary—topic, what was discussed and decided, what's next, resources desired.<br />
<br />
The Akademy team might reassign BoFs based on operational needs<br />
<br />
=== Room 1 – 4th October ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 1<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:00<br />
| KDE Free Qt Foundation/Working Group<br />
| Albert Astals Cid<br />
|-<br />
| 11:00<br />
| Plasma Ink<br />
| Niccolò Vé/Aleix Pol<br />
|-<br />
| 12:00<br />
| Embedded KWin<br />
| Kai Uwe Broulik<br />
|-<br />
| 13:00 <br />
| ''Lunch''<br />
| <br />
|-<br />
| 15:00<br />
| KDE e.V. Office Hours<br />
| Aleix, KDE e.V. Board<br />
|-<br />
| 16:00<br />
| Hardware platforms for KDE to flourish<br />
| Aleix<br />
|-<br />
| 17:00<br />
| The KDE Qt5 Patch Collection<br />
| Albert Astals Cid<br />
|-<br />
| 18:00<br />
| BoF Wrap Up<br />
| Go to Room tbd<br />
|}<br />
<br />
=== Room 2 – 4th October ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 2<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00<br />
| width="200pt" | <br />
| width="400pt" | <br />
|-<br />
| 10:00<br />
| KDE PIM<br />
| Carl Schwan<br />
|-<br />
| 11:00<br />
| <br />
| <br />
|-<br />
| 12:00<br />
| KDE Eco<br />
| Joseph<br />
|-<br />
| 13:00 <br />
| ''Lunch''<br />
| <br />
|-<br />
| 15:00<br />
| <br />
| <br />
|-<br />
| 16:00<br />
| Let's chat about Fundraising<br />
| Lays Rodrigues<br />
|-<br />
| 17:00<br />
|<br />
|<br />
|-<br />
| 18:00<br />
| BoF Wrap Up<br />
| Go to Room tbd<br />
|}<br />
<br />
=== Room 3 – 4th October ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 3<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00<br />
| width="200pt" | Yocto<br />
| width="400pt" | Andreas CoLa: adding meta-kde/meta-kf5 to CI, migration to Qt6, Yocto upstream compatibility, branch/merge strategy,...<br />
|-<br />
| 10:00<br />
| Plasma<br />
| Marco<br />
|-<br />
| 11:00<br />
| <br />
| <br />
|-<br />
| 12:00<br />
|<br />
| <br />
|-<br />
| 13:00 <br />
| ''Lunch''<br />
| <br />
|-<br />
| 15:00<br />
| [https://invent.kde.org/system/dolphin/-/issues/35 Dolphin 🐬]<br />
| Felix Ernst<br />
|-<br />
| 16:00<br />
| <br />
| <br />
|-<br />
| 17:00<br />
| [[Akademy/2022/Workshop: Making Zynthbox Playground Modules|Workshop: Making Zynthbox Playground Modules]]<br />
| Dan Leinir Turthra Jensen<br />
|-<br />
| 18:00<br />
| BoF Wrap Up<br />
| Go to Room tbd<br />
|}<br />
<br />
=== Room 4 – 4th October ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 4<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:00<br />
| <br />
| <br />
|-<br />
| 11:00<br />
| <br />
| <br />
|-<br />
| 12:00<br />
|<br />
| <br />
|-<br />
| 13:00 <br />
| ''Lunch''<br />
| <br />
|-<br />
| 15:00<br />
| <br />
| <br />
|-<br />
| 16:00<br />
| <br />
| <br />
|-<br />
| 17:00<br />
|<br />
|<br />
|-<br />
| 18:00<br />
| BoF Wrap Up<br />
| Go to Room tbd<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Akademy/2022/Workshop:_Making_Zynthbox_Playground_Modules&diff=94723Akademy/2022/Workshop: Making Zynthbox Playground Modules2022-09-28T09:03:24Z<p>Leinir: Created page with "'''First things first:''' Zynthbox is a free software music noodling platform, or workshop if you will, for easily experimenting with and capturing musical ideas. One of the t..."</p>
<hr />
<div>'''First things first:''' Zynthbox is a free software music noodling platform, or workshop if you will, for easily experimenting with and capturing musical ideas. One of the things the platform has is a kind of free-form part-logic, part-visual plugin system called Playground Modules. These modules can provide anything from, say, a couple of buttons that throw some midi notes into the ether to make the synths make a noise, through visually dense keyboard systems (like the included notes grid), chord generation tools, to full blown sequencer editors (like the included step sequencer), to automatic note generators which interact with Zynthbox' playback system in real-time while playing.<br />
<br />
== Plan of Approach ==<br />
<br />
At this workshop, we will first do a quick introduction to Zynthbox itself, so you can more easily see where the playground modules fit in, followed by a short introduction to how to actually build the things, and distribute them to people via Zynthbox' sharing site (which lives alongside the KDE Store).<br />
<br />
=== What should you know before we start? ===<br />
<br />
I'm not going to be teaching anybody QML here, so you'll need to come prepared for that (sorry, we don't have time, but i'm told it's easy enough if you have a working understanding of react and similar web frameworks). Outside of that, i am going to try and show you what you need to do, but if you want to prepare ahead of time, and of course i would certainly recommend that you at least skim through it, you can take a look at the Playground Modules wiki page here: https://wiki.zynthbox.io/index.php?title=Playground_Modules<br />
<br />
PS: "Why is this at a KDE Conference, when it's not a KDE project?" you ask very sensibly. Zynthbox' UI stack is based heavily on a pile of KDE technologies, primarily but not limited to Kirigami, KWin, and KNewStuff, and i am just really keen to show it to people :)<br />
<br />
== Notes for the wrapup ==<br />
<br />
TBW, obviously ;)</div>Leinirhttps://community.kde.org/index.php?title=Akademy/2022/Tuesday&diff=94722Akademy/2022/Tuesday2022-09-28T08:44:35Z<p>Leinir: /* Room 3 – 4th October */</p>
<hr />
<div>= BoF sessions on Tuesday, 4th October 2022 =<br />
<br />
''All rooms are in *tbd* and have *tbd infrastructure*.''<br />
<br />
If you need any other equipment, please send an email to akademy-team@kde.org.<br />Please put your name and email address in the Host/Notes section. There is no length limitation; text will wrap. <br />
<br />
'''BoF Wrap-up at 18:00'''<br /><br />
Please join the BoF wrap-up session this evening. Another opportunity for communication. Share outcomes and plans, cross-pollinate, attract attention to your project.<br />
Please select someone from your BoF to give a summary—topic, what was discussed and decided, what's next, resources desired.<br />
<br />
The Akademy team might reassign BoFs based on operational needs<br />
<br />
=== Room 1 – 4th October ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 1<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:00<br />
| KDE Free Qt Foundation/Working Group<br />
| Albert Astals Cid<br />
|-<br />
| 11:00<br />
| Plasma Ink<br />
| Niccolò Vé/Aleix Pol<br />
|-<br />
| 12:00<br />
| Embedded KWin<br />
| Kai Uwe Broulik<br />
|-<br />
| 13:00 <br />
| ''Lunch''<br />
| <br />
|-<br />
| 15:00<br />
| KDE e.V. Office Hours<br />
| Aleix, KDE e.V. Board<br />
|-<br />
| 16:00<br />
| Hardware platforms for KDE to flourish<br />
| Aleix<br />
|-<br />
| 17:00<br />
| The KDE Qt5 Patch Collection<br />
| Albert Astals Cid<br />
|-<br />
| 18:00<br />
| BoF Wrap Up<br />
| Go to Room tbd<br />
|}<br />
<br />
=== Room 2 – 4th October ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 2<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00<br />
| width="200pt" | <br />
| width="400pt" | <br />
|-<br />
| 10:00<br />
| KDE PIM<br />
| Carl Schwan<br />
|-<br />
| 11:00<br />
| <br />
| <br />
|-<br />
| 12:00<br />
| KDE Eco<br />
| Joseph<br />
|-<br />
| 13:00 <br />
| ''Lunch''<br />
| <br />
|-<br />
| 15:00<br />
| <br />
| <br />
|-<br />
| 16:00<br />
| Let's chat about Fundraising<br />
| Lays Rodrigues<br />
|-<br />
| 17:00<br />
|<br />
|<br />
|-<br />
| 18:00<br />
| BoF Wrap Up<br />
| Go to Room tbd<br />
|}<br />
<br />
=== Room 3 – 4th October ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 3<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00<br />
| width="200pt" | Yocto<br />
| width="400pt" | Andreas CoLa: adding meta-kde/meta-kf5 to CI, migration to Qt6, Yocto upstream compatibility, branch/merge strategy,...<br />
|-<br />
| 10:00<br />
| Plasma<br />
| Marco<br />
|-<br />
| 11:00<br />
| <br />
| <br />
|-<br />
| 12:00<br />
|<br />
| <br />
|-<br />
| 13:00 <br />
| ''Lunch''<br />
| <br />
|-<br />
| 15:00<br />
| [https://invent.kde.org/system/dolphin/-/issues/35 Dolphin 🐬]<br />
| Felix Ernst<br />
|-<br />
| 16:00<br />
| <br />
| <br />
|-<br />
| 17:00<br />
| Workshop: Making Zynthbox Playground Modules<br />
| Dan Leinir Turthra Jensen - [[Akademy/2022/Workshop: Making Zynthbox Playground Modules|notes/description]]<br />
|-<br />
| 18:00<br />
| BoF Wrap Up<br />
| Go to Room tbd<br />
|}<br />
<br />
=== Room 4 – 4th October ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 4<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:00<br />
| <br />
| <br />
|-<br />
| 11:00<br />
| <br />
| <br />
|-<br />
| 12:00<br />
|<br />
| <br />
|-<br />
| 13:00 <br />
| ''Lunch''<br />
| <br />
|-<br />
| 15:00<br />
| <br />
| <br />
|-<br />
| 16:00<br />
| <br />
| <br />
|-<br />
| 17:00<br />
|<br />
|<br />
|-<br />
| 18:00<br />
| BoF Wrap Up<br />
| Go to Room tbd<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Craft/Blueprints&diff=92274Craft/Blueprints2021-06-24T11:21:09Z<p>Leinir: /* Structure */ Fill out the sample blueprint a bunch</p>
<hr />
<div>{{Note|This page is work in progress. Please help to make it more useful!}}<br />
<br />
== Adding New Blueprints ==<br />
<br />
Blueprints are stored in separate repositories. At the moment there are these repositories:<br />
* git@invent.kde.org:packaging/craft-blueprints-kde.git (enabled by default)<br />
<br/><br />
To navigate to this repository on your local file system:<br />
cs craft-blueprints-kde<br />
<br />
If you want to add a new blueprint first of all you have to choose the right location (e.g. kde apps are located in the <tt>kde</tt> folder.<br />
<br />
{{Warning|The name of the package folder needs to match the blueprint name. An example would be <code>kdegraphics-mobipocket\kdegraphics-mobipocket.py</code>}}<br />
<br />
== Structure ==<br />
<br />
The following shows an example blueprint file. Outside of the information in the various fields which define the software package itself, and that there is one file missing (blocklist.txt, which you can see the description of in the comment above the line which references that file), this is what a blueprint looks like. Since there is no project named category/projectname.git on KDE's Invent, the blueprint won't just build, but apart from that, this is what they look like.<br />
<br />
<syntaxhighlight lang="python"><br />
<br />
import info<br />
<br />
class subinfo(info.infoclass):<br />
# This defines the basic information about your software package (both the basic<br />
# metainformation like human readable names, where the source comes from, and<br />
# what other blueprints it depends on).<br />
def setTargets(self):<br />
# The human-readable name of the main binary<br />
self.displayName = "Your Project"<br />
# A description of the entire package<br />
self.description = "A really solid software package that does nifty things"<br />
# The project's webpage (if you're unsure for a KDE project, just use this one)<br />
self.webpage = "https://kde.org"<br />
# You can set various targets. By convention, call your primary one "master"<br />
# and then give the git URL for the project. If you need to specify a branch,<br />
# you can do so by adding a pipe and the name of the branch (or indeed tag)<br />
# to the line<br />
self.svnTargets["master"] = "https://invent.kde.org/category/projectname.git|branch"<br />
# The default target is what Craft will use to build your package if it is not<br />
# told anything else (by either the command line, or another blueprint which<br />
# depends on yours).<br />
self.defaultTarget = "master"<br />
def setDependencies( self ):<br />
# Defines the blueprints this blueprint depends on, and which target (default is what<br />
# was defined above, and is usually what you would write, except in highly specific<br />
# cases). These are the directories inside the blueprints directory which contain<br />
# the blueprint for the thing this blueprint depends on.<br />
# A buildDependencies entry is something required for actually building the<br />
# software in this blueprint<br />
self.buildDependencies["dev-utils/pkg-config"] = "default"<br />
# a runtimeDependencies entry is something which must also be installed for the<br />
# software to function (and which will also then be included in any package you<br />
# build using Craft)<br />
self.runtimeDependencies["libs/qt5/qtbase"] = "default"<br />
# If there are compiler specific things to consider, either a library you need<br />
# for a specific compiler and not for others, you can use CraftCore.compiler to<br />
# make such checks.<br />
if CraftCore.compiler.isMinGW():<br />
self.runtimeDependencies["libs/runtime"] = None #mingw-based builds need this<br />
<br />
from Package.CMakePackageBase import * # The package base<br />
<br />
class Package(CMakePackageBase):<br />
# This defines which build system your blueprint should use. In this case, we are<br />
# using the CMake package base, but there are a lot of options for specific use cases,<br />
# such as Meson, Perl, QMake, and Binary ones. See <br />
# https://invent.kde.org/packaging/craft/-/tree/master/bin/Package<br />
# for details on which package base options are available. For KDE projects, however<br />
# you will almost certainly be using CMake, and the others are commonly more useful<br />
# for when you are creating blueprints for new dependencies.<br />
def __init__( self ):<br />
# Always remember to just initialize the package base like so<br />
CMakePackageBase.__init__( self )<br />
# If you have tests set up to build by default, for example, you might want to<br />
# disable those for Craft builds (usually, in KDE, those tests are more useful<br />
# for the CI system, and less useful for Craft, which is more useful for creating<br />
# installer packages and the like, not for automated testing purposes). You can<br />
# do this by setting the following option.<br />
CMakePackageBase.buildTests = False<br />
<br />
def createPackage(self):<br />
# Usually you will not need this entry, but in case your main executable is<br />
# called something else than the blueprint's name, you can set that here.<br />
# This allows Craft to pass this information to tools which build packages,<br />
# such as the one which builds appimages, which will then be able to work<br />
# on the correct executable.<br />
self.defines["appname"] = "mainexecutable"<br />
# For Windows, similarly to above, if your application is called something<br />
# other than your blueprint's name, you can explicitly pass in an icon from<br />
# somewhere on the Craft filesystem. Here we pick out an ico file from inside<br />
# the <br />
self.defines["icon"] = os.path.join(self.sourceDir(), "gemini", "calligragemini.ico")<br />
# For Windows, you can define a set of shortcuts by setting the shortcuts define with<br />
# multiple values, such as below:<br />
self.defines["shortcuts"] = [{"name" : self.subinfo.displayName, "target":"bin/mainexecutable.exe"},<br />
{"name" : "The Other Application", "target" : "bin/differentexecutable.exe"},<br />
{"name" : "A Bonus Tool", "target" : "bin/anotherexecutable.exe"}]<br />
# If you have files that get installed automatically, but which you know are<br />
# in fact not needed for the application to run (this will sometimes be the<br />
# case for example for building Windows packages, where you don't need some<br />
# of the things installed by some dependencies), you can list those files<br />
# in a list in some file, which is a list of regular expressions which will<br />
# be interpreted on a per-line basis, and any file which is matched by any line<br />
# will not be included in the package.<br />
self.blacklist_file.append(os.path.join(self.packageDir(), "blocklist.txt"))<br />
# Alternatively, you can add a direct filter on specific files by adding<br />
# lines like this one (which will cause Craft to not package any executable<br />
# file that is outside the two directories at the start, and is not named<br />
# one of the four names in the second paranthesis).<br />
self.addExecutableFilter(r"(bin|libexec)/(?!(mainexecutable|differentexecutable|anotherexecutable|update-mime-database)).*")<br />
<br />
# You can add packages that should be ignored for packaging purposes. This is<br />
# in many ways similar to adding a buildDependencies entry, but only ignores<br />
# this specific package (which can be handy if other things pull in a package<br />
# that your software doesn't need when publishing).<br />
self.ignoredPackages.append("dev-utils/sed")<br />
<br />
# In some cases, you need to do things depending on specific conditions,<br />
# such as building on anything that is not Linus, where you might wish to<br />
# not ship dbus. You can do this like so:<br />
if not CraftCore.compiler.isLinux:<br />
self.ignoredPackages.append("libs/dbus")<br />
<br />
# Finally, just call the packager itself to get the package actually created.<br />
return super().createPackage()<br />
</syntaxhighlight><br />
<br />
=== Dependencies ===<br />
The various things you can list as dependencies (and indeed reference in places which reference other blueprints) are the directory names in which you can find the python files which define other blueprints in this repository: https://invent.kde.org/packaging/craft-blueprints-kde/<br />
<br />
=== Package Base ===<br />
See https://invent.kde.org/packaging/craft/-/tree/master/bin/Package for available package bases<br />
<br />
== Howto ==<br />
<br />
=== Apply Patches ===<br />
Apply a simple patch<br />
<syntaxhighlight lang="python"><br />
# ...<br />
def setTargets(self):<br />
# ...<br />
# "5.81.0" is the version the patch should be applied<br />
self.patchToApply["5.81.0"] = [("patch-file.diff", 1)] # patch file, patch depth (= git apply -p<n> option)<br />
self.patchLevel["5.81.0"] = 1<br />
</syntaxhighlight><br />
<br />
It is also possible to do fancy stuff like<br />
<syntaxhighlight lang="python"><br />
# ...<br />
def setTargets(self):<br />
# ...<br />
for ver in ["master"] + self.versionInfo.tarballs():<br />
self.patchToApply[ver] = [("patch-file.diff", 1)]<br />
self.patchLevel[ver] = 1<br />
</syntaxhighlight><br />
<br />
=== Check for Compiler/OS ===<br />
If you want to run a command based on the current environment you can use <code>CraftCore.compiler</code><br />
<syntaxhighlight lang="python"><br />
if CraftCore.compiler.isWindows:<br />
# do something only on windows<br />
if not CraftCore.compiler.isGCC:<br />
# don't do something with GCC<br />
</syntaxhighlight><br />
<br />
Take a look at https://invent.kde.org/packaging/craft/-/blob/master/bin/CraftCompiler.py to see all available options</div>Leinirhttps://community.kde.org/index.php?title=Akademy/2021/Friday&diff=92123Akademy/2021/Friday2021-06-15T08:55:41Z<p>Leinir: /* Room 01 - 25th June */</p>
<hr />
<div>= BoF sessions on Friday, 25 June 2021 =<br />
<br />
[https://community.kde.org/Akademy/2021/AllBoF Back to all BoFs]<br />
<br />
=== Room 01 - 25th June ===<br />
{| class="table table-striped"<br />
|-<br />
! [https://meet.kde.org/b/ Link to Room 1]<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00 UTC<br />
| width="200pt" | KDE Goal: All about the apps - Automation<br />
| width="400pt" | Aleix Pol<br />
|-<br />
| 10:00 UTC<br />
| KDE Goal: All about the apps - Distribution<br />
| Dan Leinir Turthra Jensen (ties into the previous topic)<br />
|-<br />
| 11:00 UTC<br />
|<br />
|<br />
|-<br />
| 12:00 - 17:00 UTC <br />
| Break<br />
| <br />
|}<br />
<br />
=== Room 02 - 25th June ===<br />
{| class="table table-striped"<br />
|-<br />
! [https://meet.kde.org/b/ Link to Room 2]<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00 UTC<br />
| width="200pt" | <br />
| width="400pt" | <br />
|-<br />
| 10:00 UTC<br />
|<br />
|<br />
|-<br />
| 11:00 UTC<br />
|<br />
|<br />
|-<br />
| 12:00 - 17:00 UTC<br />
| Break<br />
| <br />
|}<br />
<br />
=== Room 03 - 25th June ===<br />
{| class="table table-striped"<br />
|-<br />
! [https://meet.kde.org/b/ Link to Room 3]<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:00 UTC<br />
| width="200pt" | <br />
| width="400pt" | <br />
|-<br />
| 10:00 UTC<br />
|<br />
|<br />
|-<br />
| 11:00 UTC<br />
|<br />
|<br />
|-<br />
| 12:00 - 17:00 UTC<br />
| Break<br />
| <br />
|}</div>Leinirhttps://community.kde.org/index.php?title=ReleasingSoftware&diff=91567ReleasingSoftware2021-04-16T13:02:06Z<p>Leinir: /* Branching */ Fix incorrect link to old repo-metadata location</p>
<hr />
<div>This page documents the steps to release software packages developed by the KDE community. This guide applies to all software which is '''not''' part of a bigger bundle like Frameworks, Plasma and KDE Gear, which have specific release cycles and release managers.<br />
<br />
== Sanity Checklist ==<br />
<br />
Stuff your project should have before beta or final release:<br />
* Have completed (or at least be going through) [https://community.kde.org/Policies/Application_Lifecycle review in kdereview] or [https://community.kde.org/Incubator Incubator]<br />
* The [https://reuse.software/spec/ REUSE Specification - Version 3.0] shall be applied when stating licenses and when adding license files to a project.<br />
* Each source file either must contain SPDX identifiers or licence headers to state under which terms the software may be used, modified and redistributed.<br />
* A [https://techbase.kde.org/Development/Tutorials/Localization/i18n_Build_Systems#Writing_a_Messages.sh_script Messages.sh file] which extracts all the i18n() translations<br />
* An appinfo.xml or metainfo.xml file with AppStream data [https://community.kde.org/Guidelines_and_HOWTOs/AppStream AppStream Guidelines]<br />
* A screenshot in [https://invent.kde.org/websites/product-screenshots product-screenshots]<br />
* Check [https://build.kde.org/ KDE CI] and other CIs such as [http://build.neon.kde.org/ KDE neon] that it compiles successfully<br />
* Check the code with some sanity tools like [https://kde.org/applications/development/org.kde.clazy clazy] or [https://clang.llvm.org/extra/clang-tidy/ clang-tidy], if not already done as part of CI runs.<br />
* Documentation appropriate to the project: API documentation, user documentation (including docbook or other format documented by the Documentation team)<br />
* A bugzilla product<br />
<br />
== Branching ==<br />
<br />
Before you create a release, if you plan to maintain a stable branch and release bugfix version from it, branch it off of master. The name should be "$MAJOR.$MINOR" or similar, i.e. "1.2". This branch will be called "stable branch" in the text below. Push the branch to the remote repository.<br />
<br />
<source lang="bash"><br />
git checkout -b 1.2<br />
git push --set-upstream origin 1.2<br />
</source><br />
<br />
You can also branch after making a tar using releaseme's branchme.rb script<br />
<br />
Whenever you make a new stable branch you must e-mail [https://mail.kde.org/mailman/listinfo/kde-i18n-doc kde-i18n-doc] to ask for translations to also be branched and repo-metadata to be updated. Make sure you get a confirmation that your request has been handled.<br />
<br />
For people using kdesrc-build and [https://build.kde.org/ KDE's CI build.kde.org], once you have created and pushed a new stable branch you need to update also [https://invent.kde.org/sysadmin/repo-metadata repo-metadata]:<br />
* Change the branch name for "stable-kf5-qt5" in the the file "logical-module-structure"<br />
* Update dependencies listed in the file "dependency-data-stable-kf5-qt5" if needed (wildcard rules might keep you covered, explicit listing done only for non-basic needs)<br />
<br />
When your product is covered on build.kde.org, after that you also need to trigger some jobs, so build.kde.org can catch up. For that follow this [[Infrastructure/Continuous_Integration_System#Updating_builds_on_switching_the_.22stable.22_branch|workflow]].<br />
<br />
When your product is covered on [https://binary-factory.kde.org/ KDE's package/installer generator binary-factory.kde.org], after you created and pushed a new stable branch you will also need to update the configuration of [https://invent.kde.org/packaging/craft-blueprints-kde/ craft-blueprints-kde] and possibly [https://invent.kde.org/sysadmin/binary-factory-tooling.git/ binary-factory-tooling]. The actual changes depend on the project and should be documented with them.<br />
<br />
== Freezing ==<br />
<br />
To prevent regressions early before a release, it is suggested to announce and enforce a "feature-freeze". From this point on, no new features should be introduced to the stable branch.<br />
<br />
Before a release, you'll need to give translators a notification about the upcoming new version. If you created a stable branch, update kde:sysadmin/repo-metadata (read the README.md first), set the "stable i18n branch" to the stable branch. Then write an email about one month before the release or so to the translators at on KDE i18n-doc <kde-i18n-doc@kde.org> . At this point, do not do any changes to translated strings, i.e. consider your branch (or master, if you didn't create a separate branch) to be "string-frozen". If you do need a string changed, ask the translators for a string-freeze exception.<br />
<br />
Note: Other feature branches will always be unfrozen, and any kind of strings or features can be changed/added. If you created a separate release branch, also the master branch is not frozen.<br />
<br />
== Versioning in source code and libraries ==<br />
<br />
When you are ready to do a release, make sure the current HEAD in the stable branch has the correct version string set in its source code as well as the SOVERSION etc., to reflect what you want to release.<br />
<br />
A good suggestion is to have something like this in your top-level CMakeLists.txt:<br />
<br />
<source lang="cmake"><br />
cmake_policy(SET CMP0048 NEW)<br />
project(kgraphviewer VERSION "2.4.0")<br />
<br />
ecm_setup_version(${PROJECT_VERSION}<br />
VARIABLE_PREFIX KGRAPHVIEWER<br />
SOVERSION ${PROJECT_VERSION_MAJOR}<br />
VERSION_HEADER "${CMAKE_CURRENT_BINARY_DIR}/config-kgraphviewer.h"<br />
)<br />
<br />
#usage somewhere in cmake for a library:<br />
set_target_properties(kgraphviewerlib PROPERTIES VERSION ${PROJECT_VERSION} SOVERSION ${KGRAPHVIEWER_SOVERSION} OUTPUT_NAME kgraphviewer )<br />
</source><br />
<br />
The config-kgraphviewer.h looks like this:<br />
<br />
<source lang="cpp"><br />
/* config-kgraphviewer.h. Generated by cmake from config.-kgraphviewer.h.cmake */<br />
<br />
#ifndef CONFIG_KGRAPHVIEWER_H<br />
#define CONFIG_KGRAPHVIEWER_H<br />
<br />
#include <kdeversion.h><br />
<br />
#define KGRAPHVIEWER_MAJOR_VERSION @KGRAPHVIEWER_VERSION_MAJOR@<br />
#define KGRAPHVIEWER_MINOR_VERSION @KGRAPHVIEWER_VERSION_MINOR@<br />
#define KGRAPHVIEWER_PATCH_VERSION @KGRAPHVIEWER_VERSION_PATCH@<br />
<br />
#define KGRAPHVIEWER_VERSION_STR "@KGRAPHVIEWER_VERSION_MAJOR@.@KGRAPHVIEWER_VERSION_MINOR@.@KGRAPHVIEWER_VERSION_PATCH@"<br />
<br />
#define KGRAPHVIEWER_VERSION KDE_MAKE_VERSION(@KGRAPHVIEWER_VERSION_MAJOR@, @KGRAPHVIEWER_VERSION_MINOR@, @KGRAPHVIEWER_VERSION_PATCH@)<br />
<br />
#endif // CONFIG_KGRAPHVIEWER_H<br />
</source><br />
<br />
Then you can include the generated config-kgraphviewer.h in e.g. your main.cpp and use the KGRAPHVIEWER_VERSION_STR define and similar. You can also install this file (useful for libraries to do feature-detection based on the version number).<br />
<br />
NOTE: Don't forget to also increase the version number in master, after you branched off. I.e. as soon as you created a "1.2" branch, ensure master's source code uses a version string such as "1.2.80" which is analogous to 1.3 Alpha 1. "1.2.90" would be 1.3 Beta 1.<br />
<br />
== Versioning in AppStream files ==<br />
<br />
The AppStream appdata.xml and metainfo.xml file should include the release version and date, this info will be shown in package managers such as Discover and app stores such as Flathub.<br />
<br />
You can use the script in https://invent.kde.org/sysadmin/appstream-metainfo-release-update to add and update the release info.<br />
<br />
== Creating a Tarball ==<br />
<br />
The [https://invent.kde.org/sdk/releaseme releaseme] scripts help with that.<br />
<br />
First check you have a working gpg2 install and a key set up which can do the digital signature:<br />
<source lang="bash"><br />
echo test > test.text; gpg2 --armor --detach-sign -o test.text.sig test.text<br />
</source><br />
<br />
If that works create the tar:<br />
<br />
<source lang="bash"><br />
./tarme.rb --version 0.1 --origin stable myapp<br />
</source><br />
<br />
This will create myapp-0.1.tar.xz and its digital signature myapp-0.1.tar.xz.sig<br />
<br />
--origin can also be trunk. It will use the Git branch set in trunk_kf5 or stable_kf5 in the i18n.json file in your project's [https://invent.kde.org/sysadmin/repo-metadata/ repo_metadata]<br />
<br />
== Uploading the Tar ==<br />
<br />
Read readme: ftp://upload.kde.org/README<br />
<br />
Upload to ftp://upload.kde.org/, for example via ''curl''<br />
curl -T "myapp-0.1.tar.xz{,.sig}" ftp://upload.kde.org/incoming/<br />
<br />
or via the traditional ''ftp'' command line program:<br />
echo put myapp-0.1.tar.xz | ftp ftp://upload.kde.org/incoming/<br />
echo put myapp-0.1.tar.xz.sig | ftp ftp://upload.kde.org/incoming/<br />
<br />
Then, file a sysadmin ticket to notify about the upload and to provide the checksums for verification: https://go.kde.org/u/systickets<br />
<br />
== Tagging ==<br />
<br />
When you publish your tar you should also push the signed tag to the Git repo.<br />
<source lang="bash"><br />
./tagme.rb --version 0.1<br />
</source><br />
This uses git running gpg to tag, you may need to set with (see https://help.github.com/articles/telling-git-about-your-gpg-key/)<br />
<source lang="bash"><br />
git config --global user.signingkey<br />
</source><br />
<br />
test with<br />
<source lang="bash"><br />
git init; echo asdf > asdf; git add asdf; git commit -a -m 'commit'; git tag -s -m 'Tagging #{options[:version]}' v123 HEAD<br />
</source><br />
<br />
== Updating bugzilla ==<br />
The new version should be added to the list of available versions to the component/product.<br />
If you don't have enough permissions, create a sysadmin ticket for that, or ask this a part of the ticket created for the tarballs (see [[#Uploading_the_Tar]])<br />
<br />
== Announcing the Release ==<br />
<br />
Once the sysadmins moved the tarball, you can announce the release. First send a mail to kde-announce-apps@kde.org and your project's mailing list(s). The mail can be short and link to a longer announcement blog post or news item. If you write a detailed blog post, make sure that that your blog/site is aggregated on planet.kde.org.<br />
<br />
You should include the full fingerprint to the GPG key used to sign the tar and tags in your announce e-mail. (Don't put it on a wiki.) Upload your key to openPGP key servers using <code>gpg2 --send-keys <fingerprint></code><br />
<br />
Ideally you also want to sign your email with the key in question to proof that you have control over the key.</div>Leinirhttps://community.kde.org/index.php?title=KDEReview&diff=90428KDEReview2020-10-23T14:20:15Z<p>Leinir: Moved Peruse out of KDEReview into extragear/graphics</p>
<hr />
<div>What is KDE Review: [[Policies/Application_Lifecycle#kdereview]]<br />
<br />
Current projects in KDE Review:<br />
<br />
{|class="wikitable"<br />
! Name<br />
! Contact<br />
! Date Review Requested<br />
! Status<br />
|-<br />
|kup<br />
|Simon Persson<br />
|April 2020<br />
|<br />
|}<br />
<br />
Moved projects<br />
{|class="wikitable"<br />
! Name<br />
! Contact<br />
! Date Review Requested<br />
! Status<br />
|-<br />
|Peruse<br />
|Dan Leinir Turthra Jensen<br />
|September 2020<br />
|Moved to extragear/graphics on 2020/10/23<br />
|-<br />
|kid3<br />
|Urs Fleisch<br />
|Feb 2020<br />
|<br />
|-<br />
|cutehmi<br />
|Michal Policht<br />
|Feb 2020<br />
|I've moved cuteHMI back to playaround pending review of build system, translation integration and getting some more readable introduction to the project.<br />
|-<br />
|ruqola<br />
|Laurent Montel<br />
|Sep 2019<br />
|https://marc.info/?t=156827303600001&r=1&w=3 Moved to extra network 13 Feb 2020<br />
|-<br />
|rkward<br />
|Thomas Friedrichsmeier<br />
|Nov 2018 but several issues outstanding<br />
|e-mailed 2019-03-07 for status, he says he'll prioritise the highlighted issues. Moved back to playground/edu 2019-04-22 as issues had not yet been dealt with.<br />
|-<br />
|liquidshell<br />
|Martin<br />
|Nov 2017. e-mailed asking to resubmit 2019-03-07<br />
|political issues as well as technical. re-submitting for review Sun 10 March 2019. Moved to extragear Apr 22 2019 as no further political complaints and only minor technical issues.<br />
|-<br />
|atlantik<br />
|pino<br />
|none yet, pinged 2019-03-07<br />
|moved to playground/games as no response 2019-04-12<br />
|-<br />
|symmy<br />
|Elvis Angelaccio<br />
|Nov 2017. some issues brought up. moved to extra/utils Apr 2019.<br />
|e-mailed asked for update. people said it could be a kgpg feature but that's not a reason to block it. checking if he wants it in playground or extragear. Bumped again to kde-core-devel 2019-03-19.<br />
|-<br />
|plasma-redshift-control<br />
|Martin Kostolný<br />
|Jan 2018<br />
|moved to extra/base<br />
|-<br />
|kdots<br />
|MInh<br />
|ages ago<br />
|moved to unmaintained as Minh said he can not maintain it and nobody else has picked it up<br />
|-<br />
|kpeg<br />
|Ronny<br />
|ages ago<br />
|moved to unmaintained https://marc.info/?l=kde-games-devel&m=150369367617478&w=2<br />
|-<br />
|plasma-simplemenu<br />
|Eike<br />
|Nov 2017, all good<br />
|moved to extra/base<br />
|-<br />
|pulseaudio-qt<br />
|Nicolas Fella<br />
|Nov 2018<br />
|moved to extra/libs<br />
|-<br />
|rust-qt-binding-generator<br />
|Jos VDO<br />
|Sep 2017<br />
|Moved to extragear/sdk<br />
|-<br />
|atelier<br />
|Lays and KDE Atelier Telegram group<br />
|none yet, pinged 2019-03-07<br />
|moved back to playground<br />
|-<br />
|plasma-active-window-control<br />
|Martin Kostolný<br />
|Jan 2018<br />
|pinged on what to do 2019-03-07. chris holland replied saying he's interested in release. moved to extra/base March 16.<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=SoK/Ideas/2021&diff=90303SoK/Ideas/20212020-09-25T10:49:46Z<p>Leinir: /* Peruse: Expand Peruse or Creator's featureset */</p>
<hr />
<div>[[File:Mascot konqi-app-presentation.png|thumbnail|right|[[Konqi]] is giving a lesson!]]<br />
<br />
==Ideas==<br />
<br />
=== Information for students ===<br />
<br />
These ideas were contributed by our developers and users. They are sometimes vague or incomplete. If you wish to submit a proposal based on these ideas, contact the developers and find out more about the particular suggestion you're interested in.<br />
<br />
When writing your proposal or asking for help from the general KDE community don't assume people are familiar with the ideas here. KDE is really big!<br />
<br />
If there is no specific contact given in the idea, you can ask questions on the general KDE development list kde-devel@kde.org. See [http://www.kde.org/mailinglists/ the KDE mailing lists page] for information on available mailing lists and how to subscribe.<br />
<br />
=== Sample project ===<br />
<br />
'''Project type:''' Coding / Web Development / Promo / Translation<br />
<br />
'''Brief explanation:'''<br />
<br />
'''Expected results:'''<br />
<br />
'''Knowledge Prerequisite:'''<br />
<br />
'''Mentor:'''<br />
<br />
When adding an idea to this section, please try to include the following data:<br />
<br />
:*if the application is not widely known, a description of what it does and where its code lives<br />
:*a brief explanation<br />
:*the expected results<br />
:*pre-requisites for working on your project<br />
:*if applicable, links to more information or discussions<br />
:*mailing list or IRC channel for your application/library/module<br />
:*your name and email address for contact (if you're willing to be a mentor)<br />
<br />
If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first.<br />
<br />
==Ideas==<br />
===Your Own Idea ===<br />
<br />
==== Project: Something that you're totally excited about ====<br />
<br />
'''Project type:''' Coding / Web Development / Promo / Translation<br />
<br />
'''Brief explanation:''' Do you have an awesome idea you want to work on with KDE but that is not among the ideas below? That's cool. We love that! But please do us a favor: Get in touch with a mentor early on and make sure your project is realistic and within the scope of KDE. That will spare you and us a lot of frustration.<br />
<br />
'''Expected results:''' Something you and KDE loves<br />
<br />
'''Knowledge Prerequisite:''' Probably C++ and Qt but depends on your project<br />
<br />
'''Mentor:''' Try to see who in KDE is interested in what you want to work on and approach them. If you are unsure you can always ask in #kde-soc on Freenode IRC.<br />
<br />
<br />
=== Promo: tips and tricks videos for social networks ===<br />
<br />
'''Project type:''' Promo<br />
<br />
'''Brief explanation:''' The goal of this task is to create promo videos showing off tips and tricks from the list maintained here: [https://phabricator.kde.org/T13465 T13465]. You will be able to choose a few of them and create short videos with some effects applied to them. The amount of videos you will need to do depends on how much time you have.<br />
<br />
'''Expected results:''' Your short videos will be displayed on social media and viewed by many people. This will help with the promotion of KDE's software as powerful applications.<br />
<br />
'''Knowledge Prerequisite:''' Knowledge of KDenlive is recommended but not required, but you will need to learn and use KDenlive. The promo team has some KDenlive experts and it is a good occasion to learn how to use it. <br />
<br />
'''Mentor:''' Paul Brown and rest of the KDE Promo team. Join us IRC: #kde-promo, Matrix: #kde-promo:kde.org or Telegram: https://t.me/joinchat/AEyx-0O8HKlHV7Cg7ZoSyA<br />
<br />
=== Documentation: Improve documentation about how to write Plasma widgets ===<br />
<br />
'''Project type:''' Documentation<br />
<br />
'''Brief explanation:''' The goal of this task is to improve the existing Plasma widgets documentation and move it to [https://develop.kde.org/docs develop.kde.org/docs].<br />
<br />
'''Expected results:''' It will be easier for people to write their own plasmoids :D<br />
<br />
'''Knowledge Prerequisite:''' A bit of QML and English writing skills :)<br />
<br />
'''Mentor:''' Carl Schwan, you can join our matrix room in [https://webchat.kde.org/#/room/#developer-doc:kde.org #developer-doc:kde.org]<br />
<br />
<br />
<br />
=== [http://edu.kde.org/kstars KStars], Coding: Make custom catalogs fast by putting them on a special data structure ===<br />
<br />
'''Project type:''' Code<br />
<br />
'''Brief explanation:''' The goal of this project is to improve the speed at which large custom (user-created / internet-downloaded) catalogs of sky objects (e.g. galaxies etc.) are rendered by KStars. KStars already has adaptations of a space-partitioning data structure (kind of like a k-D tree), the Hierarchical Triangular Mesh, which can be used to create an index based on the region of the sky in which an object lies, which are used elsewhere in KStars. The project would adapt this data structure to work with custom catalogs.<br />
<br />
'''Expected results:'''<br />
1. Optimize the rendering by only rendering those objects that are in the regions displayed on the screen<br />
2. Optimize the computations by only computing positions for those objects that are in the regions displayed on the screen<br />
3. Stretch Goal: Optimize the loading to only load into memory (from the database) those objects that are in regions displayed on the screen<br />
<br />
A merge request with proper code review validation is expected at each step of this project.<br />
<br />
The final win for KStars is that we will be able to render catalogs of hundreds of thousands of galaxies (such as the Principal Galaxies Catalog) without impact in performance.<br />
<br />
'''Knowledge Prerequisite:''' C++, Basic understanding of Object Oriented Programming, Rudimentary familiarity with Qt<br />
<br />
'''Mentor:''' TBD<br />
<br />
=== [https://peruse.kde.org/ Peruse]: Expand Peruse or Creator's featureset ===<br />
<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:''' Peruse and Peruse Creator are both basic, capable applications, but as all applications, there is more to do to make them really sing. Maybe we want Peruse to be able to make use of the ACBF Jump system to make interactive fiction possible, and for Peruse Creator to be able to create that. Maybe we want Peruse Creator to have more creative management tools to support the creation of books, like a timeline of events, language descriptions. Maybe we want Peruse Creator's translation tools to be more capable, and Peruse itself to be able to display the rich text areas found in ACBF and other advanced formats. In short, have a play, and pitch your ideas.<br />
<br />
'''Expected results:''' A more capable Peruse and/or Peruse Creator<br />
<br />
'''Knowledge Prerequisite:''' You should be comfortable with C++, Qt, and QML based application development, as both applications depend heavily on this combination.<br />
<br />
'''Mentor:''' Dan Leinir Turthra Jensen (catch the person with the screen name leinir anywhere on KDE's infrastructure, and indeed most other places)</div>Leinirhttps://community.kde.org/index.php?title=SoK/Ideas/2021&diff=90302SoK/Ideas/20212020-09-25T10:04:58Z<p>Leinir: /* Ideas */ Add Peruse pitch-an-idea idea</p>
<hr />
<div>[[File:Mascot konqi-app-presentation.png|thumbnail|right|[[Konqi]] is giving a lesson!]]<br />
<br />
==Ideas==<br />
<br />
=== Information for students ===<br />
<br />
These ideas were contributed by our developers and users. They are sometimes vague or incomplete. If you wish to submit a proposal based on these ideas, contact the developers and find out more about the particular suggestion you're interested in.<br />
<br />
When writing your proposal or asking for help from the general KDE community don't assume people are familiar with the ideas here. KDE is really big!<br />
<br />
If there is no specific contact given in the idea, you can ask questions on the general KDE development list kde-devel@kde.org. See [http://www.kde.org/mailinglists/ the KDE mailing lists page] for information on available mailing lists and how to subscribe.<br />
<br />
=== Sample project ===<br />
<br />
'''Project type:''' Coding / Web Development / Promo / Translation<br />
<br />
'''Brief explanation:'''<br />
<br />
'''Expected results:'''<br />
<br />
'''Knowledge Prerequisite:'''<br />
<br />
'''Mentor:'''<br />
<br />
When adding an idea to this section, please try to include the following data:<br />
<br />
:*if the application is not widely known, a description of what it does and where its code lives<br />
:*a brief explanation<br />
:*the expected results<br />
:*pre-requisites for working on your project<br />
:*if applicable, links to more information or discussions<br />
:*mailing list or IRC channel for your application/library/module<br />
:*your name and email address for contact (if you're willing to be a mentor)<br />
<br />
If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first.<br />
<br />
==Ideas==<br />
===Your Own Idea ===<br />
<br />
==== Project: Something that you're totally excited about ====<br />
<br />
'''Project type:''' Coding / Web Development / Promo / Translation<br />
<br />
'''Brief explanation:''' Do you have an awesome idea you want to work on with KDE but that is not among the ideas below? That's cool. We love that! But please do us a favor: Get in touch with a mentor early on and make sure your project is realistic and within the scope of KDE. That will spare you and us a lot of frustration.<br />
<br />
'''Expected results:''' Something you and KDE loves<br />
<br />
'''Knowledge Prerequisite:''' Probably C++ and Qt but depends on your project<br />
<br />
'''Mentor:''' Try to see who in KDE is interested in what you want to work on and approach them. If you are unsure you can always ask in #kde-soc on Freenode IRC.<br />
<br />
<br />
=== Promo: tips and tricks videos for social networks ===<br />
<br />
'''Project type:''' Promo<br />
<br />
'''Brief explanation:''' The goal of this task is to create promo videos showing off tips and tricks from the list maintained here: [https://phabricator.kde.org/T13465 T13465]. You will be able to choose a few of them and create short videos with some effects applied to them. The amount of videos you will need to do depends on how much time you have.<br />
<br />
'''Expected results:''' Your short videos will be displayed on social media and viewed by many people. This will help with the promotion of KDE's software as powerful applications.<br />
<br />
'''Knowledge Prerequisite:''' Knowledge of KDenlive is recommended but not required, but you will need to learn and use KDenlive. The promo team has some KDenlive experts and it is a good occasion to learn how to use it. <br />
<br />
'''Mentor:''' Paul Brown and rest of the KDE Promo team. Join us IRC: #kde-promo, Matrix: #kde-promo:kde.org or Telegram: https://t.me/joinchat/AEyx-0O8HKlHV7Cg7ZoSyA<br />
<br />
=== Documentation: Improve documentation about how to write Plasma widgets ===<br />
<br />
'''Project type:''' Documentation<br />
<br />
'''Brief explanation:''' The goal of this task is to improve the existing Plasma widgets documentation and move it to [https://develop.kde.org/docs develop.kde.org/docs].<br />
<br />
'''Expected results:''' It will be easier for people to write their own plasmoids :D<br />
<br />
'''Knowledge Prerequisite:''' A bit of QML and English writing skills :)<br />
<br />
'''Mentor:''' Carl Schwan, you can join our matrix room in [https://webchat.kde.org/#/room/#developer-doc:kde.org #developer-doc:kde.org]<br />
<br />
<br />
<br />
=== [http://edu.kde.org/kstars KStars], Coding: Make custom catalogs fast by putting them on a special data structure ===<br />
<br />
'''Project type:''' Code<br />
<br />
'''Brief explanation:''' The goal of this project is to improve the speed at which large custom (user-created / internet-downloaded) catalogs of sky objects (e.g. galaxies etc.) are rendered by KStars. KStars already has adaptations of a space-partitioning data structure (kind of like a k-D tree), the Hierarchical Triangular Mesh, which can be used to create an index based on the region of the sky in which an object lies, which are used elsewhere in KStars. The project would adapt this data structure to work with custom catalogs.<br />
<br />
'''Expected results:'''<br />
1. Optimize the rendering by only rendering those objects that are in the regions displayed on the screen<br />
2. Optimize the computations by only computing positions for those objects that are in the regions displayed on the screen<br />
3. Stretch Goal: Optimize the loading to only load into memory (from the database) those objects that are in regions displayed on the screen<br />
<br />
A merge request with proper code review validation is expected at each step of this project.<br />
<br />
The final win for KStars is that we will be able to render catalogs of hundreds of thousands of galaxies (such as the Principal Galaxies Catalog) without impact in performance.<br />
<br />
'''Knowledge Prerequisite:''' C++, Basic understanding of Object Oriented Programming, Rudimentary familiarity with Qt<br />
<br />
'''Mentor:''' TBD<br />
<br />
=== [https://peruse.kde.org/ Peruse]: Expand Peruse or Creator's featureset ===<br />
<br />
'''Project type:''' Coding<br />
<br />
'''Brief explanation:''' Peruse and Peruse Creator are both basic, capable applications, but as all applications, there is more to do to make them really sing. Maybe we want Peruse to be able to make use of the ACBF Jump system to make interactive fiction possible, and for Peruse Creator to be able to create that. Maybe we want Peruse Creator to have more creative management tools to support the creation of books, like a timeline of events, language descriptions. Maybe we want Peruse Creator's translation tools to be more capable, and Peruse itself to be able to display the rich text areas found in ACBF and other advanced formats. In short, have a play, and pitch your ideas.<br />
<br />
'''Expected results:''' A more capable Peruse and/or Peruse Creator<br />
<br />
'''Knowledge Prerequisite:''' You should be comfortable with C++, Qt, and QML based application development, as both applications depend heavily on this combination.<br />
<br />
'''Mentor:''' Dan Leinir Turthra Jensen</div>Leinirhttps://community.kde.org/index.php?title=KDEReview&diff=90201KDEReview2020-09-15T13:15:07Z<p>Leinir: Added Peruse to KDEReview</p>
<hr />
<div>What is KDE Review: [[Policies/Application_Lifecycle#kdereview]]<br />
<br />
Current projects in KDE Review:<br />
<br />
{|class="wikitable"<br />
! Name<br />
! Contact<br />
! Date Review Requested<br />
! Status<br />
|-<br />
|kup<br />
|Simon Persson<br />
|April 2020<br />
|<br />
|-<br />
|Peruse<br />
|Dan Leinir Turthra Jensen<br />
|September 2020<br />
|<br />
|}<br />
<br />
Moved projects<br />
{|class="wikitable"<br />
! Name<br />
! Contact<br />
! Date Review Requested<br />
! Status<br />
|-<br />
|kid3<br />
|Urs Fleisch<br />
|Feb 2020<br />
|<br />
|-<br />
|cutehmi<br />
|Michal Policht<br />
|Feb 2020<br />
|I've moved cuteHMI back to playaround pending review of build system, translation integration and getting some more readable introduction to the project.<br />
|-<br />
|ruqola<br />
|Laurent Montel<br />
|Sep 2019<br />
|https://marc.info/?t=156827303600001&r=1&w=3 Moved to extra network 13 Feb 2020<br />
|-<br />
|rkward<br />
|Thomas Friedrichsmeier<br />
|Nov 2018 but several issues outstanding<br />
|e-mailed 2019-03-07 for status, he says he'll prioritise the highlighted issues. Moved back to playground/edu 2019-04-22 as issues had not yet been dealt with.<br />
|-<br />
|liquidshell<br />
|Martin<br />
|Nov 2017. e-mailed asking to resubmit 2019-03-07<br />
|political issues as well as technical. re-submitting for review Sun 10 March 2019. Moved to extragear Apr 22 2019 as no further political complaints and only minor technical issues.<br />
|-<br />
|atlantik<br />
|pino<br />
|none yet, pinged 2019-03-07<br />
|moved to playground/games as no response 2019-04-12<br />
|-<br />
|symmy<br />
|Elvis Angelaccio<br />
|Nov 2017. some issues brought up. moved to extra/utils Apr 2019.<br />
|e-mailed asked for update. people said it could be a kgpg feature but that's not a reason to block it. checking if he wants it in playground or extragear. Bumped again to kde-core-devel 2019-03-19.<br />
|-<br />
|plasma-redshift-control<br />
|Martin Kostolný<br />
|Jan 2018<br />
|moved to extra/base<br />
|-<br />
|kdots<br />
|MInh<br />
|ages ago<br />
|moved to unmaintained as Minh said he can not maintain it and nobody else has picked it up<br />
|-<br />
|kpeg<br />
|Ronny<br />
|ages ago<br />
|moved to unmaintained https://marc.info/?l=kde-games-devel&m=150369367617478&w=2<br />
|-<br />
|plasma-simplemenu<br />
|Eike<br />
|Nov 2017, all good<br />
|moved to extra/base<br />
|-<br />
|pulseaudio-qt<br />
|Nicolas Fella<br />
|Nov 2018<br />
|moved to extra/libs<br />
|-<br />
|rust-qt-binding-generator<br />
|Jos VDO<br />
|Sep 2017<br />
|Moved to extragear/sdk<br />
|-<br />
|atelier<br />
|Lays and KDE Atelier Telegram group<br />
|none yet, pinged 2019-03-07<br />
|moved back to playground<br />
|-<br />
|plasma-active-window-control<br />
|Martin Kostolný<br />
|Jan 2018<br />
|pinged on what to do 2019-03-07. chris holland replied saying he's interested in release. moved to extra/base March 16.<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Plasma/2020Virtual&diff=88244Sprints/Plasma/2020Virtual2020-05-14T08:14:13Z<p>Leinir: /* Attendance */</p>
<hr />
<div>==Plasma Virtual Sprint 2020==<br />
<br />
Where: 🏡<br />
<br />
==Attendance==<br />
<br />
Please put your name below if you're interested in attending. Cutoff date for deciding the sprint dates is 23rd May 2020, please fill-in your availability for dates in between 1-15 June before deadline.<br />
<br />
Keep list alphabetically sorted.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Name<br />
! Availability dates<br />
! Timezone<br />
|-<br />
| Bhushan Shah<br />
| 1-14 June<br />
| UTC +5.30<br />
|-<br />
| Dan Leinir Turthra Jensen<br />
| 1-14 June<br />
| UTC +1<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=GSoC/2018/Ideas&diff=79024GSoC/2018/Ideas2018-01-16T19:17:39Z<p>Leinir: /* KGpg */</p>
<hr />
<div>[[File:Mascot konqi-app-presentation.png|thumbnail|right|[[Konqi]] is giving a lesson!]]<br />
See also: [[../../|GSoc Instructions]], [[../../2016/Ideas|Last year ideas]]<br />
<br />
== Guidelines ==<br />
<br />
=== Information for Students ===<br />
<br />
These ideas were contributed by our developers and users. They are sometimes vague or incomplete. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at.<br />
<br />
Being accepted as a Google Summer of Code student is quite competitive. Accepted students typically have thoroughly researched the technologies of their proposed project and have been in frequent contact with potential mentors. '''Simply copying and pasting an idea here will not work.''' On the other hand, creating a completely new idea without first consulting potential mentors is unlikely to work out.<br />
<br />
When writing your proposal or asking for help from the general KDE community don't assume people are familiar with the ideas here. KDE is really big!<br />
<br />
If there is no specific contact given you can ask questions on the general KDE development list kde-devel@kde.org. See [http://www.kde.org/mailinglists/ the KDE mailing lists page] for information on available mailing lists and how to subscribe.<br />
<br />
{{Note|'''These are all proposals! We are open to new ideas you might have!!''' Do you have an awesome idea you want to work on with KDE but that is not among the ideas below? That's cool. We love that! But please do us a favor: Get in touch with a mentor early on and make sure your project is realistic and within the scope of KDE.}}<br />
<br />
__TOC__<br />
<br />
=== Adding a Proposal ===<br />
<br />
{{Note|Follow the template of other proposals!}}<br />
<br />
==== Project: ====<br />
<br />
'''If appropriate, screenshot or other image'''<br />
<br />
'''Brief explanation:'''<br />
<br />
'''Expected results:'''<br />
<br />
'''Knowledge Prerequisite:'''<br />
<br />
'''Mentor:'''<br />
<br />
When adding an idea to this section, please try to include the following data:<br />
<br />
:*if the application is not widely known, a description of what it does and where its code lives<br />
:*a brief explanation<br />
:*the expected results<br />
:*pre-requisites for working on your project<br />
:*if applicable, links to more information or discussions<br />
:*mailing list or IRC channel for your application/library/module<br />
:*your name and email address for contact (if you're willing to be a mentor)<br />
<br />
If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first.<br />
<br />
==Ideas==<br />
===Your Own Idea ===<br />
<br />
==== Project: Something that you're totally excited about ====<br />
<br />
'''Brief explanation:''' Do you have an awesome idea you want to work on with KDE but that is not among the ideas below? That's cool. We love that! But please do us a favor: Get in touch with a mentor early on and make sure your project is realistic and within the scope of KDE. That will spare you and us a lot of frustration.<br />
<br />
'''Expected results:''' Something you and KDE loves<br />
<br />
'''Knowledge Prerequisite:''' Probably C++ and Qt but depends on your project<br />
<br />
'''Mentor:''' Try to see who in KDE is interested in what you want to work on and approach them. If you are unsure you can always ask in #kde-soc on Freenode IRC.<br />
<br />
=== Krita ===<br />
[http://www.krita.org Krita]: digital painting for artists. It support creating images from scratch from begin to end. Krita is a complex application and developers need to have a fair amount of experience in order to be able to do something.<br />
<br />
Krita is a widely used digital painting application for professional artists. Last year, Krita gained the ability to create hand-drawn 2D animations, among other new features. For this year, projects that the Krita team would be interested in include the following ideas.<br />
<br />
Note that we're always open to ideas you bring in yourself: if you're passionate about something you've come up with yourself, that you want for Krita, that's a big plus for us.<br />
<br />
We also expect prospective students to submit at least three patchs for bugs or wishes or small features. We want to know how good you are! See https://phabricator.kde.org/T7724 for some smaller tasks that you could work on that are not bugs.<br />
<br />
==== Project: Optimize multithreading in Krita's Tile Manager (make the hash table lockfree) ====<br />
<br />
'''Brief explanation''': This is a hard-core project, only suitable for someone with deep knowledge of the problems of designing multi-threaded software. It involves Krita's core datamodel, where the tiles that compose image data are managed. The main problem is that at the moment the core utilizes QReadWriteLock and QMutex a lot, which means that Krita painting performance stops scaling well, when the number of CPU cores becomes larger than 8. The goal of this project is to locate all the bottlenecks (there are at least 4 of them) and resolve them in a lock-free. One of the bottlenecks involves KisTileHashTable which is used to access the tiles. Since this touches the very core of Krita, a thorough test plan is essential.<br />
<br />
'''Steps to apply''':<br />
The topic of the project is quite advanced, so we recommend you to do the following steps before writing a proposal:<br />
# Build Krita with unittests enabled<br />
# Install GNU Perf or VTune<br />
# Run FreehandStrokeBenchmark in a profiler and try to locate all the places where most of the locking/waits happen. The main one will be the hash table, but there are at least three more (your task is to locate them and add into your proposal!)<br />
# (optional) To test your coding abilities you can try to port one of the hash tables code from [https://github.com/preshing/junction Junction] library to Qt's primitives. If you don't feel overwhelmed with such code, you are perfectly fit for the project!<br />
# And feel free to contact Krita developers, if you have any question during these steps!<br />
<br />
'''Expected results''': No bottlenecks anymore! <br />
<br />
'''Knowledge Prerequisite''': C++, Qt, threads, locks.<br />
<br />
'''Mentor''': Dmitry Kazakov (dmkitryK|log on irc)<br />
<br />
==== Project: Extending Animation Support for curves ====<br />
<br />
'''Brief Explanation''': In Krita, you can already add curves that could be applied to some properties of a layer, like opactity, animating those properties. We want the animation support extended by allowing users to place masks (filter masks, transformation masks, transparency masks) on the timeline and animate their properties using curves. Every property of a layer or mask placed on the timeline should be animatable.<br />
<br />
'''Expected results''':<br />
* Implementation of a gui for applying the curve settings to one or more properties of a mask or layer<br />
* Implementation of the actual rendering of the properties in the frames<br />
* Saving of these settings<br />
<br />
'''Knowledge Prerequisite''':<br />
* C++ and Qt<br />
<br />
'''Mentor''': Boudewijn Rempt (IRC: boud) or Dmitry Kazakov (IRC: dmitryk_log)<br />
<br />
==== Project: Taking the Shape Brush to the next level ====<br />
'''Brief Explanation''': Krita has a number of interesting brush engines. One of them is the Shape Brush engine. Inspired by Alchemy, the shape brush "throws" shapes on the canvas. The current implementation is limited to geometric shapes. We want the brush engine to be extended to make it possible to load vector shapes defined as PDF or SVG and use those to draw on the canvas as well. Other improvements are the addition of Feathering, an outline mode, edge sharpening and background textures.<br />
<br />
'''Expected Results''': A revampted and exciting shapes brush<br />
<br />
'''Knowledge Prerequisite''':<br />
* C++, Qt, Krita<br />
<br />
'''Mentor''': Boudewijn Rempt (IRC: boud) or Lukas Tvrdy (IRC: LukasT)<br />
<br />
==== Project: Analysis of thoroughput of Krita Blending Modes and porting them to AVX2 ====<br />
<br />
'''Brief Explanation''': Blending modes is the hottest piece of code in Krita. It should process gigabytes of data per second, therefore it should be extremely optimized. Some of its parts are already optimized to use AVX instructions, but some (float16 color spaces) are not. We need to port the rest of the color spaces to AVX and make a research into the possibilities of using AXV2 instructions directly (int16 instructions). [https://github.com/VcDevel/Vc Vc library] supports AXV2 instructions, though we don't know to what extent, it might happen that you would need to extent the library itself to get the needed functionality. This is another hard-core project only suitable if you have a good deal of experience.<br />
<br />
'''Steps to apply''': The topic of the project is quite advanced, so we recommend you to do the following steps before writing a proposal:<br />
<br />
# Build Krita with unittests enabled<br />
# Install GNU Perf or VTune<br />
# Run KisCompositionBenchmark under a profiler and see the hottest places of blending modes code<br />
# Check the code of "Normal" blending mode for float32 color spaces (KoOptimizedCompositeOpOver128), copy the file and try to create you own blending mode for float16 color space. Hint: the only thing you should do is to implement correct unpacking/packing code that would convert the values to 32-bit float and back.<br />
# If you don't feel overwhelmed with such code, you are perfectly fit for the project!<br />
# And feel free to contact Krita developers, if you have any question during these steps!<br />
<br />
'''Expected Results''': Float16 color spaces are ported to AVX, Integer8 and Integer16 colorspaces are ported to AVX2<br />
<br />
'''Knowledge Prerequisite''': C++, SEE/AVX (read [http://www.intel.eu/content/www/eu/en/architecture-and-technology/64-ia-32-architectures-optimization-manual.html Intel's manual])<br />
<br />
'''Mentor''': Dmitry Kazakov (IRC: dmitryk|log)<br />
<br />
==== Project: Port generic code for not-so-popular blending modes to AVX ====<br />
<br />
'''Brief Explanation''': In Krita we have a lot of blending modes, but only Normal and Alpha Darken are optimized and ported to AVX instructions. The reason for that is obvious, these two blending modes are the hottest and are used in every single image produced in Krita. But it doesn't mean that the other blending modes are less important for painters: they still use Multiply for painting shadows, and Linear Dodge for painting highlights, so they should also be fast! <br />
<br />
The good piece of news is that all these "non-popular" blending modes are implemented in Krita by means of a single class KoCompositeOpGenericSC, so, basically, as a result of your project you should provide one class only! The bad piece of news is that this single class implements about a hundred of blending modes using C++ templates... so be prepared! :)<br />
<br />
'''Steps to apply''': The topic of the project is quite advanced, so we recommend you to do the following steps before writing a proposal:<br />
<br />
# Build Krita with unittests enabled<br />
# Install GNU Perf or VTune<br />
# Run KisCompositionBenchmark under a profiler and see the hottest places of blending modes code<br />
# Check the code of "Copy" blending mode in KoCompositeOpCopy2 and try to port it into AVX for RGB8 colorspace. Use KoOptimizedCompositeOpOver32 as an example.<br />
# If you don't feel overwhelmed with such code, you are perfectly fit for the project!<br />
# And feel free to contact Krita developers, if you have any question during these steps!<br />
<br />
'''Expected Results''': "Copy" blending mode is ported to AVX, all the "gereric" blending modes are ported to AVX<br />
<br />
'''Knowledge Prerequisite''': C++, SEE/AVX (read [http://www.intel.eu/content/www/eu/en/architecture-and-technology/64-ia-32-architectures-optimization-manual.html Intel's manual])<br />
<br />
'''Mentor''': Dmitry Kazakov (IRC: dmitryk|log)<br />
<br />
==== Project: Optimize Soft, Gaussian and Stamp brushes to use AVX ====<br />
<br />
'''Brief Explanation''': When the user draws a line in Krita, this line consists of thousands of small rectangular images (dabs) that are painted one over another. For each dab Krita generates its own mask (depending on the stylus pressure and tilt) and uses this mask for filling the layer. It happens thousands of times per second, which makes mask generation code one of the hottest places in Krita. We already have AVX optimization for Default brush mask engine and it works 5(!) times faster than Gaussian engine and 3(!) times faster than the Soft engine. The goal of this project is to port the rest of non-optimized engines to use AVX via [https://github.com/VcDevel/Vc Vc library] and make them faster.<br />
<br />
'''Steps to apply''': The topic of the project is quite advanced, so we recommend you to do the following steps before writing a proposal:<br />
<br />
# Build Krita with unittests enabled<br />
# Install GNU Perf or VTune<br />
# Run FreehandStrokeBenchmark under a profiler and compare the results for different types of brushes. You can see how faster Default brush tip is.<br />
# Check the code in kis_brush_mask_applicator_factories.cpp and try to implement your own version of FastRowProcessor for KisGaussCircleMaskGenerator '''without''' using any AVX. Even without any vector instruction the brush will become much faster, just because it will use less virtual calls.<br />
# If you don't feel overwhelmed with the amount of C++ templates in your code, you are perfectly fit for the project!<br />
# And feel free to contact Krita developers, if you have any question during these steps!<br />
<br />
'''Expected Results''': Circular Soft, Gaussian and Stamp brush masks are ported to AVX-optimized code. Optionally, if there is enough time, rectangular brush masks are posted as well.<br />
<br />
'''Knowledge Prerequisite''': C++, SEE/AVX (read [http://www.intel.eu/content/www/eu/en/architecture-and-technology/64-ia-32-architectures-optimization-manual.html Intel's manual])<br />
<br />
'''Mentor''': Dmitry Kazakov (IRC: dmitryk|log)<br />
<br />
<br />
==== Project: Partial canvas updates and region of interest (performance optimization for huge (20k+) canvases) ====<br />
<br />
'''Brief Explanation''': We already have an optimization for huge canvases, which is called Instant Preview. But it woks only when the user has the canvas zoomed out to fit the screen. There are some usecases, when the user wants to work with a small "working area" of a huge image and he doesn't care what happens with the rest of the image. This project is targeted to optimize this case.<br />
<br />
'''Expected Results''': By the end of the summer we expect these features to be implemented:<br />
* Partial updates in openGL canvas. Right now we redraw all the image textures in every frame, which is not needed after porting to Qt5.<br />
* Region of Intereset (ROI) in KisImage. Updates should be reordered and the priority should be given to the areas that are currently visible to the user<br />
* Work Area Tool. The user is be able to define the area, where he would like to work in. The updates for other parts of the image are skipped until the user exits this special mode.<br />
* (if there is time) Optimize textures loading to use RIO as well. Theoretically, we can just skip uploading of the tiles that are not visible on the screen at the moment.<br />
<br />
'''Steps to apply''': The topic of the project is quite advanced, so we recommend you to do the following steps before writing a proposal:<br />
<br />
# Build Krita<br />
# Check the code in KisImage, pay attention to 'cropRect' parameter of the update calls. That is exactly what you need for limiting the updates in the work area tool<br />
# Try to write Work Area Tool: copy the code of KisToolCrop, connect it to Krita and make it override the cropRect paramenter in KisImage.<br />
# If you manage to make a draft of Work Area Tool, most probably, you will manage to complete the whole project successfully!<br />
# And feel free to contact Krita developers, if you have any question during these steps!<br />
<br />
'''Knowledge Prerequisite''': C++, OpenGL<br />
<br />
'''Mentor''': Dmitry Kazakov (IRC: dmitryk|log), Julian Thijssen (IRC: Nimmy)<br />
<br />
==== Project: Add 3D Painting Assistants ====<br />
<br />
'''Brief explanation''': One of the more innovative features in Krita are the painting assistants. These are shapes overlaid on the canvas that the artist can use to help him achieve perspective, straight lines and other shapes freehand. For complex drawings it would be useful to be able to place 3D models on the canvas, position and scale them and use those as guides for drawing.<br />
<br />
'''Expected results''': by the end of the summer, 3D models should be shown on canvas as canvas decorations, using OpenGL in hidden-line wireframe mode. The models should be manipulated using on-canvas controls like other assistants. Magnetic snapping is an optional extra.<br />
<br />
'''Knowledge Prerequisite''': C++, Qt, OpenGL, Assimp<br />
<br />
'''Mentor''': Julian Thijssen (IRC: Nimmy)<br />
<br />
=== KDE Student Programs ===<br />
<br />
KDE Student Programs is the working group responsible for running Season of KDE and managing KDE's participation in Google Summer of Code, Google Code-In, and other mentorship programmes.<br />
<br />
==== Project: A new Season of KDE Website ====<br />
<br />
'''Brief explanation''': Season of KDE will need a new website to make managing the project easier for us. The core feature set that we're looking to have comprises:<br />
<br />
* Student applications on the website<br />
* Mentors can mark themselves interested in projects during the application phase<br />
* Org admins will create slots and assign projects and mentors to slots<br />
* Manage mid-term evaluations and results<br />
* Bulk data export and import<br />
<br />
For maintainability by the rest of KDE we'd like the app to be in Python (Tornado or a WSGI framework). It would also be nice if the app was an SPA riding on top of a REST API server so we can have command-line tools interacting with the server as well.<br />
<br />
'''Expected results''': Easier project administration for KDE.<br />
<br />
'''Knowledge Prerequisite''': Python, Tornado/WSGI, LDAP, full-stack web development, Single-Page applications.<br />
<br />
'''Mentor''': Boudhayan Gupta <bgupta@kde.org>, BaloneyGeek on IRC<br />
<br />
=== GCompris ===<br />
==== Project: finishing started activities ====<br />
'''Brief explanation''': GCompris is a an educational software suite comprising of numerous activities for children aged 2 to 10. Originally written in Gtk+ it's development team started to rewrite it from scratch in Qt Quick.<br />
<br />
'''Expected results''':<br />
The aim of this year is to complete and getting merged activities that were started but have not been finished. You can find a list of tasks that you can work on at https://phabricator.kde.org/T7498. First phase is to check what is missing to be integrated (on code and graphic side) and then to complete them. You can find at https://cgit.kde.org/gcompris.git/refs/heads the list of the current branches (some of them need to be dropped, so contact us before starting working on one of them).<br />
<br />
'''Knowledge Prerequisite''':<br />
<br />
Be interested in children’s education<br />
<br />
Be familiar with GCompris concept and content<br />
<br />
Basic knowledge in a programming language (a 1 year school course is enough)<br />
<br />
Be able to build the Qt Quick version of GCompris<br />
<br />
'''Application guide''':<br />
Continuing an activity already started or rewriting from scratch is something you have to check before writing your application. Provide a timeline in your application. If you haven't contributed yet please read http://gcompris.net/wiki/An_exercise_for_new_contributors and http://gcompris.net/wiki/Reviewing_an_activity<br />
<br />
There are several info in the wiki: http://gcompris.net/wiki/Developer%27s_corner.<br />
<br />
''Feel free to contact us either on irc or by mail (gcompris-devel@kde.org)''<br />
<br />
'''Mentors''': Divyam Madaan (IRC: dmadaan), Johnny Jazeix (IRC: JohnnyJ), Rudra Nil Basu (IRC: rudra), Timothée Giet (IRC: Animtim)<br />
<br />
==== Project: Unit test framework ====<br />
<br />
'''Expected results''':<br />
The aim of this project is to build the base for unit testing for GCompris. The student will have to think on what we can test (qml, js...) and how we can put this in place.<br />
More information can be found in https://phabricator.kde.org/T7668.<br />
<br />
'''Knowledge Prerequisite''':<br />
<br />
Be interested in children’s education<br />
<br />
Be familiar with GCompris concept and content<br />
<br />
Basic knowledge in a programming language and CMake use (a 1 year school course is enough)<br />
<br />
Be able to build the Qt Quick version of GCompris<br />
<br />
Technologies used are CMake, C++, Qt.<br />
<br />
''Feel free to contact us either on irc or by mail (gcompris-devel@kde.org)''<br />
<br />
'''Mentors''': Divyam Madaan (IRC: dmadaan), Johnny Jazeix (IRC: JohnnyJ), Rudra Nil Basu (IRC: rudra), Timothée Giet (IRC: Animtim)<br />
<br />
=== KDE Partition Manager ===<br />
==== Project: finishing KAuth support [Season of KDE]====<br />
'''Brief explanation''': KDE Partition Manager is a utility program to help you manage the disk devices, partitions and file systems on your computer. It allows you to easily create, copy, move, delete, resize without losing data, backup and restore partitions.<br />
<br />
'''Expected results''':<br />
Last year a lot of work was done to make KDE Partition Manager not to start as root and use KAuth to elevate privileges. The aim of this project is to finish required refactoring and make sure everything still works.<br />
<br />
The two main issues are:<br />
<br />
* SMART support needs to be ported from (unmaitained) libatasmart library to calling smartctl command. This task is likely to be fairly easy.<br />
<br />
* KDE Partition Manager operation runner should be refactored, instead of calling KAuth helper multiple times to run a single command it has to prepare a list of all commands and their inputs and call KAuth helper once. This needs some refactoring in how partition manager reads and writes disk data (e.g. when moving/copying/backing up or restoring partition). In particular we don't want to transfer all the disk data back from the helper to the main application and back to the helper as DBus transport is fairly slow.<br />
<br />
'''Knowledge Prerequisite''':<br />
<br />
* Be able to build the KPMcore and KDE Partition Manager from source.<br />
<br />
* Knowledge of C++ / Qt (No knowledge of KDE Frameworks is required).<br />
<br />
'''Application guide''':<br />
Get in touch on IRC (#kde-devel or #calamares).<br />
<br />
'''Mentors''': Andrius Štikonas (IRC:stikonas)<br />
<br />
=== Kopete ===<br />
<br />
==== Project: Write tests and Improve protocol support ====<br />
<br />
'''Brief explanation''': Kopete is an instant messaging client that has the modular architecture and supports many messaging services with useful plugins to complement them. <br />
<br />
'''Expected results''':<br />
The aim of this project is to fix the bugs due to porting and improve the frontend and the test coverage.<br />
<br />
'''Knowledge Prerequisite''':<br />
<br />
* Be interested in test-driven development.<br />
<br />
* Be familiar with the codebase of KDE in general.<br />
<br />
* Knowledge of C++ / Qt.<br />
<br />
'''Application guide''':<br />
<br />
Get in touch with us on mailing-list and start hacking KDE and fix bugs. Teams of two people is preferred for this project as it is a lot of work :)<br />
<br />
You can contact on IRC also but it is better to discuss over mailing list as not many people are in IRC on #kopete channel.<br />
<br />
'''Mentors''': Vijay <vijaykrishnavanshi@gmail.com> (vijay_ on IRC), Kopete Mailing List <kopete-devel@kde.org><br />
<br />
=== Documentation ===<br />
<br />
==== Project [for Season of KDE only]: Verify and update the various documentation ====<br />
<br />
'''Brief explanation:''' If you have been in and around KDE for some time you might have noticed some changes in the documentation, well here is your chance is to improve them. Documentation can always use some iterations and revisits. Your task is to understand the challenges that a beginner might and write advice for them. Your speed will depend on your familiarity with KDE infrastructure.<br />
<br />
'''Expected results:''' Better documentation. <br />
<br />
'''Knowledge Prerequisite:''' C++ and Qt, and good writing skills :)<br />
<br />
'''Mentor:''' Vijay <vijaykrishnavanshi@gmail.com> (vijay_ on IRC)<br />
<br />
=== LabPlot ===<br />
[http://www.labplot.kde.org LabPlot] is a KDE-application for interactive graphing and analysis of scientific data. LabPlot provides an easy way to create, manage and edit plots and to perform data analysis.<br />
<br />
==== Project: Plotting of live MQTT data ====<br />
'''Brief explanation''': LabPlot has already some support for plotting of live-data (http://krajszgsoc.blogspot.de/2017/09/in-finish-line-but-not-in-end.html). To cover more use-cases we want to also support MQTT sources. We need to investigate the available MQTT libraries for Qt:<br />
* https://blog.qt.io/blog/2017/08/14/introducing-qtmqtt-protocol/<br />
* https://github.com/emqtt/qmqtt<br />
and to add some support for MQTT to LabPlot.<br />
<br />
'''Expected results''': Similar to the currently supported data sources (files, sockets, serial port, SQL databases) we want to support the subscription to MQTT brockers and plotting of their data. <br />
<br />
'''Knowledge Prerequisite''': C++, Qt, (optional) knowledge and experience with MQTT<br />
<br />
'''Mentor''': Fábián Kristóf - Szabolcs (mailto:fkristofszabolcs@gmail.com)<br />
<br />
==== Project: Import of educational data sets available on the internet ====<br />
'''Brief explanation''': There are many internet pages providing data sets for educational and study purposes for many different areas (astrophysics, statistics, medicine, etc.). Some tools used in the scientific area provide some "wrappers" for such online sources and allow the user to easily play around with those data sets in the applications whereas the technical details like fetching of data from the server and parsing are done completely transparent for the user. The goal of this project is to add similar functionality to LabPlot. There will be a wizard where the user can select from a thematically grouped list of data sets available online. The internal description of such an online data set should contain the URL with the actual file that needs to be downloaded and the settings for LabPlot's data parser (separator, column names and data types, etc.). The data fetched once should be cached so there is no need to fetch from the web again. Here we can have a look maybe at KStars for how to implement such a caching strategy and maybe even re-use some code from KStars.<br />
In addition to the list of pre-defined online sources, we need to elaborate how the user can add new online data sets (together with all the required parametrization) and publish the settings to make them available for everybody.<br />
<br />
'''Expected results''': We want to be able to easily import the educational data sets available on the internet.<br />
<br />
'''Knowledge Prerequisite''': C++, Qt<br />
<br />
'''Mentor''': Stefan Gerlach<br />
<br />
==== Project: Import of data from web-services ====<br />
'''Brief explanation''': Brief explanation: This goal of this project is to extend the number of supported data sources by adding the possibility to import the data from web services (live and historical financial data, weather, etc.). Most web services expose their data via JSON. We need to add a "JSON filter" to LabPlot capable to connect to a web service, to fetch the data, to parse it and to import into LabPlot's internal data containers. In the GUI the user should be guided through the entry of the service URL, additional services parameters like API token, etc. and through the settings for the actual parsing (which JSON fields to consume and how). Also, it should be possible to refresh the data periodically like it is already possible for the live data (http://krajszgsoc.blogspot.de/2017/09/in-finish-line-but-not-in-end.html). The goal is also to provide a set of widely known web services so the user can select and import the data from a list of pre-defined services. In addition to this, we need to elaborate the possibility to "publish" the settings for a web-service done by the user and make them publicly available to every LabPlot user.<br />
<br />
<br />
'''Expected results''': Similar to the currently supported data sources (files, sockets, serial port, SQL databases) we want to import the data from web services and visualize it.<br />
<br />
'''Knowledge Prerequisite''': C++, Qt, (optional) JSON support in Qt<br />
<br />
'''Mentor''': Alexander Semke<br />
<br />
=== Kdenlive ===<br />
[https://kdenlive.org Kdenlive] is a KDE-application for professionnal video editors. It supports hundreds of video formats, and all the features you can expect from a non-linear video editor, including some advanced features like timeline preview rendering, proxy clips and more. <br />
<br />
==== Project [for Season of KDE only]: Improve audio workflow: mixer ====<br />
<br />
'''Brief explanation''': Kdenlive already allows you adjust audio levels for each clip or for an entire track by adding effects. The idea of an audio mixer is to create a new widget that easily allows to control volume and balance for each track without having to search for effects. The core audio components should already be available through our video framework MLT. So this job will require to understand how Kdenlive interacts with MLT. Some details about the audio mixer features can be found in our [https://kdenlive.org/video-editing-applications-handbook/#audio documentation]<br />
<br />
'''Expected results''': Better control of the audio output for users <br />
<br />
'''Knowledge Prerequisite''': C++, Qt, requires some preliminary studies to understand how Kdenlive/MLT work<br />
<br />
'''Mentor''': Jean-Baptiste Mardelle<br />
<br />
==== Project [for Season of KDE only]: Improve on monitor controls for image transformation ====<br />
<br />
'''Brief explanation''': When adding a "Transform" effect to a clip in Kdenlive, you can then resize and move the image directly on the monitor through a Qml overlay. The idea is to also add the possibility to adjust rotation directly on the monitor screen, and improve the general UI of this Qml overlay.<br />
<br />
'''Expected results''': Fluent control of size, position and rotation inside the monitor<br />
<br />
'''Knowledge Prerequisite''': C++, Qt, Qml - this does not require much knowledge of Kdenlive, and is mostly a Qml work<br />
<br />
'''Mentor''': Jean-Baptiste Mardelle<br />
<br />
=== Choqok ===<br />
==== Project: Port Choqok to Kirigami ====<br />
<br />
'''Brief explanation:''' Current Choqok UI doesn't make use of QML and creates interfaces in C++ files. The idea is to rewrite the interface in QML. At this point is better doing it with Kirigami since this means it will work on Plasma Mobile too.<br />
<br />
'''Expected results:''' Choqok UI makes use of Kirigami.<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt, Qml<br />
<br />
'''Mentor:''' Andrea Scarpino (IRC: ilpianista)<br />
<br />
'''Application guide''':<br />
Get in touch on IRC (#choqok).<br />
<br />
=== KStars ===<br />
<br />
[https://edu.kde.org/kstars KStars] is free, open source, cross-platform Astronomy Software. It provides an accurate graphical simulation of the night sky, from any location on Earth, at any date and time. <br />
<br />
==== Project: Deep Sky Object Overhaul ====<br />
'''Brief explanation''': KStars supports many deep sky objects (DSOs) including galaxies, nebulae, supernovae, clusters and more. Currently, some deep sky catalogs are stored in simple space separated text format where they are parsed into KStars directly or into KStars Deep Sky Component SQLite3 database which is then loaded in KStars. However, since all DSOs are loaded at once into memory, this limits the size of catalogs within KStars. A solution similar to how dynamic stars are cached in and out of memory must be developed for DSOs. Furthermore, all catalog entries should have their trixels indexed so that they can be efficiently drawn unto the sky map. Another issue is that catalogs can overlap since there is no cross-identification of various catalogs. For example, Andromeda galaxy exists in Messier catalog as M31, and exists in NGC catalog as NGC 224. The database should support ability to cross-identify objects from all supported and future catalogs.<br />
<br />
'''Expected results''': <br />
* Convert all text-format catalogs to SQLite3 database.<br />
* Develop master DSO database where cross-identification of objects is supported. Master database can supported addon downloadable catalogs where they can be merged once downloaded by the user.<br />
* Import of The Principal Galaxy Catalog, 2003 Version (PGC2003) which contains ~1 million galaxies into KStars as a downloadable addon.<br />
* Caching and drawing optimizations for large catalogs.<br />
* Cross-identification for all supported DSO catalogs including, but not limited too: NGC/IC/Messier/Arp/PGC/LDN<br />
* Trixel indexation for all DSOs. Implementation of improved drawing cached routine in KStars for DSOs similar to stars.<br />
* All necessary updates within KStars maps, tools and dialogs to reflect the above changes.<br />
<br />
'''Knowledge Prerequisite''': C++, Qt, Data Structures<br />
<br />
'''Mentor''': Jasem Mutlaq ([https://riot.im/app/#/room/#kstars:matrix.org Matrix]: Jasem)<br />
<br />
==== Project: Ekos Web Client ====<br />
'''Brief explanation''': Ekos is KStars premier tool for observatory control and automation. A web client port of Ekos is desired where it communicates with the underlying INDI servers and drivers without a direct dependency on thick desktop clients. Ekos includes many modules including setup, capture, focus, guide, align, and mount. All functionalities of the desktop Ekos client are expected in the web client version using Python+Ajax or similar framework technologies suitable for online dynamic driven clients.<br />
<br />
'''Expected results''': <br />
* Online Ekos web client with all the thick client feature set.<br />
* Authentication and Registration framework.<br />
* Support for notifications similar to desktop client.<br />
* Ajax dynamic driven interface with near real time updates for framing and captures.<br />
* Multi-user support with granular permissions.<br />
* Web based INDI Control Panel with all the driver controls as in the desktop version.<br />
<br />
'''Knowledge Prerequisite''': C++, Qt, Django/Ajax or similar technology framework.<br />
<br />
'''Mentor''': Jasem Mutlaq ([https://riot.im/app/#/room/#kstars:matrix.org Matrix]: Jasem)<br />
<br />
==== Project: Implement Qt3D backend for KStars ====<br />
'''Brief explanation''': The Skymap in KStars desktop version is currently built using QPainter and 2D drawing primitives. In order to take advantage of advances in modern GPU hardware and to present a stunning visual view of the night sky, a 3D backend is desired. Qt 3D provides functionality for near-realtime simulation systems with support for 2D and 3D rendering in both Qt C++ and Qt Quick applications. Within KStars, SkyPainter provides a backend-agnostic class for drawing object unto the skymap regardless of the backend. Previously, an experimental OpenGL backend was developed but was later deprecated due to drawing issues. Since Qt3D provides an abstraction to the backend framework (OpenGL/Vulkan/DirectX), it presents a very flexible framework for building future-proof 3D applications.<br />
<br />
'''Expected results''': <br />
* Create Qt3D based backend to draw all objects currently implemented by QPainter backend.<br />
* Create realistic colors, shares, textures, meshes, lighting for all stars, solar system, and deep sky objects.<br />
* Create animations for meteor shows, comet tails, stars twinkle..etc<br />
'''Knowledge Prerequisite''': C++, Qt, Prior experience working with 3D applications/games.<br />
<br />
'''Mentor''': Akarsh Simha ([https://riot.im/app/#/room/#kstars:matrix.org Matrix]: kstar)<br />
<br />
=== Peruse ===<br />
<br />
Peruse is a comic book reader application by KDE, which is designed to work both on touch based devices, and on the traditional desktop. Additionally, it has a tool called Peruse Creator which is designed to create comic books for use with Peruse and any other CBZ capable comic book reader. It has rudimentary support for the [http://acbf.wikia.com/wiki/Specifications Advanced Comic Book Format], which is a metadata container for comic book archives (CBR, CBZ and so on).<br />
<br />
See also the Peruse website for more detailed information: https://peruse.kde.org/<br />
<br />
==== Project: Expand Creator's Abilities ====<br />
<br />
'''Brief explanation:''' Peruse Creator is currently very simple, and will allow the user to create a CBZ comic book archive annotated with a subset of the [http://acbf.wikia.com/wiki/Specifications Advanced Comic Book Format] (ACBF) metainfo, such as authors, publisher information, characters and so on. It does not allow for the creation or editing of the viewport based navigation that ACBF describes, nor does it support the text layers system ACBF proposes for comic book translation. It also lacks editor components for a variety of the general metainformation ACBF suggests.<br />
<br />
Your project proposal should include explicit descriptions of which of these you wish to build support for, and how you propose to do so. It should further include timeframes for each.<br />
<br />
'''Expected results:''' A more capable Peruse Creator.<br />
<br />
'''Knowledge Prerequisite:''' C++ and Qt required, additionally QML/QtQuick knowledge is preferred<br />
<br />
'''Mentor:''' Dan Leinir Turthra Jensen (admin@leinir.dk, IRC: leinir, Telegram and twitter: @leinir)<br />
<br />
==== Project: New Viewer Component ====<br />
<br />
'''Brief explanation:''' The current viewer component for Comic Book Archives (CBR) in Peruse is a simple full-page viewer, which only supports page-by-page navigation. The [http://acbf.wikia.com/wiki/Specifications Advanced Comic Book Format] (ACBF) metadata container brings with it support for a viewport system, which describes how the application should present [http://acbf.wikia.com/wiki/Body_Section_Definition#Frame specific sub-sections of each page], as well as a system for [http://acbf.wikia.com/wiki/Body_Section_Definition#Jump navigating between arbitrary pages in the comic].<br />
<br />
Your project proposal should include explicit descriptions of how you would suggest to implement this, as well as a schedule for the work.<br />
<br />
'''Expected results:''' A viewer component which is able to consume and display the viewport based navigation metadata from the ACBF container, as well as present the general metainformation to the user.<br />
<br />
'''Knowledge Prerequisite:''' C++ and Qt required, additionally QML/QtQuick knowledge is preferred<br />
<br />
'''Mentor:''' Dan Leinir Turthra Jensen (admin@leinir.dk, IRC: leinir, Telegram and twitter: @leinir)<br />
<br />
=== KGpg ===<br />
<br />
[https://utils.kde.org/projects/kgpg KGpg] is a frontend for GnuPG key management.<br />
<br />
'''Brief explanation:''' KGpg currently consists of one application with a very narrow external interface, which is available via DBus. The goal is to split out parts of the code into a static library that is used both by the KGpg binary as well as to-be-written unit tests, which should also cover at least all of the "[https://cgit.kde.org/kgpg.git/tree/transactions transaction]" classes.<br />
<br />
'''Expected results:''' unit tests that can be called via CTest, and are integrated into the KDE CI jobs<br />
<br />
'''Knowledge Prerequisite:''' basic C++, CMake, and GnuPG usage<br />
<br />
'''Mentor:''' Rolf Eike Beer (kde@opensource.sf-tec.de, IRC: Dakon)<br />
<br />
=== Plasma ===<br />
==== Improve handling for touchpads and mice with Libinput ====<br />
<br />
'''Brief explanation:''' [https://www.freedesktop.org/wiki/Software/libinput/ Libinput] is now used as the driver for input devices in most distros. However, System Settings does not present the user with good interfaces for configuring input devices with libinput. Currently the only well-supported use case is for [https://bugsfiles.kde.org/attachment.cgi?id=108954 touchpads in a Wayland session]. For touchpads on X11, and mice on both X11 and Wayland, the user experience is sub-optimal or non-existent.<br />
<br />
'''Expected results:''' System Settings should expose good user interfaces for configuring both touchpads and mice when using Libinput, and for both Wayland and X11.<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt<br />
<br />
'''Mentor:''' Nate Graham (Email: pointedstick@zoho.com; Telegram: @nggraham)<br />
<br />
'''Application guide''':<br />
* https://wayland.freedesktop.org/libinput/doc/latest/developers.html<br />
* https://bugs.kde.org/show_bug.cgi?id=383379<br />
<br />
==== Discover: fwupd integration ====<br />
<br />
'''Brief explanation:''' Discover Software Center is in charge of offering different kinds of assets at the moment. Applications, Add-ons, etc as well as serving updates. At the moment it's still not able to update our devices' firmwares. There's a tool for GNU/Linux called FWUPD to do so: https://fwupd.org/developers<br />
<br />
Despite the description specifying plasma, the end goal is to provide a seamless solution to have your hardware's firmware up to date.<br />
If the proposal is too short, other improvements suggested to add to the idea will be welcome.<br />
<br />
'''Expected results:''' Plasma being great at having an up to date system, also with hardware.<br />
<br />
'''Knowledge Prerequisite:''' C++ and Qt, also notions of how glib works, to understand upstream FWUPD.<br />
<br />
'''Mentor:''' Aleix Pol: apol, @AleixPol, aleixpol@kde.org</div>Leinirhttps://community.kde.org/index.php?title=GSoC/2018/Ideas&diff=79007GSoC/2018/Ideas2018-01-15T12:28:03Z<p>Leinir: /* Ideas */</p>
<hr />
<div>[[File:Mascot konqi-app-presentation.png|thumbnail|right|[[Konqi]] is giving a lesson!]]<br />
See also: [[../../|GSoc Instructions]], [[../../2016/Ideas|Last year ideas]]<br />
<br />
== Guidelines ==<br />
<br />
=== Information for Students ===<br />
<br />
These ideas were contributed by our developers and users. They are sometimes vague or incomplete. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at.<br />
<br />
Being accepted as a Google Summer of Code student is quite competitive. Accepted students typically have thoroughly researched the technologies of their proposed project and have been in frequent contact with potential mentors. '''Simply copying and pasting an idea here will not work.''' On the other hand, creating a completely new idea without first consulting potential mentors is unlikely to work out.<br />
<br />
When writing your proposal or asking for help from the general KDE community don't assume people are familiar with the ideas here. KDE is really big!<br />
<br />
If there is no specific contact given you can ask questions on the general KDE development list kde-devel@kde.org. See [http://www.kde.org/mailinglists/ the KDE mailing lists page] for information on available mailing lists and how to subscribe.<br />
<br />
{{Note|'''These are all proposals! We are open to new ideas you might have!!''' Do you have an awesome idea you want to work on with KDE but that is not among the ideas below? That's cool. We love that! But please do us a favor: Get in touch with a mentor early on and make sure your project is realistic and within the scope of KDE.}}<br />
<br />
__TOC__<br />
<br />
=== Adding a Proposal ===<br />
<br />
{{Note|Follow the template of other proposals!}}<br />
<br />
==== Project: ====<br />
<br />
'''If appropriate, screenshot or other image'''<br />
<br />
'''Brief explanation:'''<br />
<br />
'''Expected results:'''<br />
<br />
'''Knowledge Prerequisite:'''<br />
<br />
'''Mentor:'''<br />
<br />
When adding an idea to this section, please try to include the following data:<br />
<br />
:*if the application is not widely known, a description of what it does and where its code lives<br />
:*a brief explanation<br />
:*the expected results<br />
:*pre-requisites for working on your project<br />
:*if applicable, links to more information or discussions<br />
:*mailing list or IRC channel for your application/library/module<br />
:*your name and email address for contact (if you're willing to be a mentor)<br />
<br />
If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first.<br />
<br />
==Ideas==<br />
===Your Own Idea ===<br />
<br />
==== Project: Something that you're totally excited about ====<br />
<br />
'''Brief explanation:''' Do you have an awesome idea you want to work on with KDE but that is not among the ideas below? That's cool. We love that! But please do us a favor: Get in touch with a mentor early on and make sure your project is realistic and within the scope of KDE. That will spare you and us a lot of frustration.<br />
<br />
'''Expected results:''' Something you and KDE loves<br />
<br />
'''Knowledge Prerequisite:''' Probably C++ and Qt but depends on your project<br />
<br />
'''Mentor:''' Try to see who in KDE is interested in what you want to work on and approach them. If you are unsure you can always ask in #kde-soc on Freenode IRC.<br />
<br />
=== Krita ===<br />
[http://www.krita.org Krita]: digital painting for artists. It support creating images from scratch from begin to end. Krita is a complex application and developers need to have a fair amount of experience in order to be able to do something.<br />
<br />
Krita is a widely used digital painting application for professional artists. Last year, Krita gained the ability to create hand-drawn 2D animations, among other new features. For this year, projects that the Krita team would be interested in include the following ideas.<br />
<br />
Note that we're always open to ideas you bring in yourself: if you're passionate about something you've come up with yourself, that you want for Krita, that's a big plus for us.<br />
<br />
We also expect prospective students to submit at least three patchs for bugs or wishes or small features. We want to know how good you are! See https://phabricator.kde.org/T7724 for some smaller tasks that you could work on that are not bugs.<br />
<br />
==== Project: Optimize multithreading in Krita's Tile Manager (make the hash table lockfree) ====<br />
<br />
'''Brief explanation''': This is a hard-core project, only suitable for someone with deep knowledge of the problems of designing multi-threaded software. It involves Krita's core datamodel, where the tiles that compose image data are managed. The main problem is that at the moment the core utilizes QReadWriteLock and QMutex a lot, which means that Krita painting performance stops scaling well, when the number of CPU cores becomes larger than 8. The goal of this project is to locate all the bottlenecks (there are at least 4 of them) and resolve them in a lock-free. One of the bottlenecks involves KisTileHashTable which is used to access the tiles. Since this touches the very core of Krita, a thorough test plan is essential.<br />
<br />
'''Steps to apply''':<br />
The topic of the project is quite advanced, so we recommend you to do the following steps before writing a proposal:<br />
# Build Krita with unittests enabled<br />
# Install GNU Perf or VTune<br />
# Run FreehandStrokeBenchmark in a profiler and try to locate all the places where most of the locking/waits happen. The main one will be the hash table, but there are at least three more (your task is to locate them and add into your proposal!)<br />
# (optional) To test your coding abilities you can try to port one of the hash tables code from [https://github.com/preshing/junction Junction] library to Qt's primitives. If you don't feel overwhelmed with such code, you are perfectly fit for the project!<br />
# And feel free to contact Krita developers, if you have any question during these steps!<br />
<br />
'''Expected results''': No bottlenecks anymore! <br />
<br />
'''Knowledge Prerequisite''': C++, Qt, threads, locks.<br />
<br />
'''Mentor''': Dmitry Kazakov (dmkitryK|log on irc)<br />
<br />
==== Project: Extending Animation Support for curves ====<br />
<br />
'''Brief Explanation''': In Krita, you can already add curves that could be applied to some properties of a layer, like opactity, animating those properties. We want the animation support extended by allowing users to place masks (filter masks, transformation masks, transparency masks) on the timeline and animate their properties using curves. Every property of a layer or mask placed on the timeline should be animatable.<br />
<br />
'''Expected results''':<br />
* Implementation of a gui for applying the curve settings to one or more properties of a mask or layer<br />
* Implementation of the actual rendering of the properties in the frames<br />
* Saving of these settings<br />
<br />
'''Knowledge Prerequisite''':<br />
* C++ and Qt<br />
<br />
'''Mentor''': Boudewijn Rempt (IRC: boud) or Dmitry Kazakov (IRC: dmitryk_log)<br />
<br />
==== Project: Taking the Shape Brush to the next level ====<br />
'''Brief Explanation''': Krita has a number of interesting brush engines. One of them is the Shape Brush engine. Inspired by Alchemy, the shape brush "throws" shapes on the canvas. The current implementation is limited to geometric shapes. We want the brush engine to be extended to make it possible to load vector shapes defined as PDF or SVG and use those to draw on the canvas as well. Other improvements are the addition of Feathering, an outline mode, edge sharpening and background textures.<br />
<br />
'''Expected Results''': A revampted and exciting shapes brush<br />
<br />
'''Knowledge Prerequisite''':<br />
* C++, Qt, Krita<br />
<br />
'''Mentor''': Boudewijn Rempt (IRC: boud) or Lukas Tvrdy (IRC: LukasT)<br />
<br />
==== Project: Analysis of thoroughput of Krita Blending Modes and porting them to AVX2 ====<br />
<br />
'''Brief Explanation''': Blending modes is the hottest piece of code in Krita. It should process gigabytes of data per second, therefore it should be extremely optimized. Some of its parts are already optimized to use AVX instructions, but some (float16 color spaces) are not. We need to port the rest of the color spaces to AVX and make a research into the possibilities of using AXV2 instructions directly (int16 instructions). [https://github.com/VcDevel/Vc Vc library] supports AXV2 instructions, though we don't know to what extent, it might happen that you would need to extent the library itself to get the needed functionality. This is another hard-core project only suitable if you have a good deal of experience.<br />
<br />
'''Steps to apply''': The topic of the project is quite advanced, so we recommend you to do the following steps before writing a proposal:<br />
<br />
# Build Krita with unittests enabled<br />
# Install GNU Perf or VTune<br />
# Run KisCompositionBenchmark under a profiler and see the hottest places of blending modes code<br />
# Check the code of "Normal" blending mode for float32 color spaces (KoOptimizedCompositeOpOver128), copy the file and try to create you own blending mode for float16 color space. Hint: the only thing you should do is to implement correct unpacking/packing code that would convert the values to 32-bit float and back.<br />
# If you don't feel overwhelmed with such code, you are perfectly fit for the project!<br />
# And feel free to contact Krita developers, if you have any question during these steps!<br />
<br />
'''Expected Results''': Float16 color spaces are ported to AVX, Integer8 and Integer16 colorspaces are ported to AVX2<br />
<br />
'''Knowledge Prerequisite''': C++, SEE/AVX (read [http://www.intel.eu/content/www/eu/en/architecture-and-technology/64-ia-32-architectures-optimization-manual.html Intel's manual])<br />
<br />
'''Mentor''': Dmitry Kazakov (IRC: dmitryk|log)<br />
<br />
==== Project: Port generic code for not-so-popular blending modes to AVX ====<br />
<br />
'''Brief Explanation''': In Krita we have a lot of blending modes, but only Normal and Alpha Darken are optimized and ported to AVX instructions. The reason for that is obvious, these two blending modes are the hottest and are used in every single image produced in Krita. But it doesn't mean that the other blending modes are less important for painters: they still use Multiply for painting shadows, and Linear Dodge for painting highlights, so they should also be fast! <br />
<br />
The good piece of news is that all these "non-popular" blending modes are implemented in Krita by means of a single class KoCompositeOpGenericSC, so, basically, as a result of your project you should provide one class only! The bad piece of news is that this single class implements about a hundred of blending modes using C++ templates... so be prepared! :)<br />
<br />
'''Steps to apply''': The topic of the project is quite advanced, so we recommend you to do the following steps before writing a proposal:<br />
<br />
# Build Krita with unittests enabled<br />
# Install GNU Perf or VTune<br />
# Run KisCompositionBenchmark under a profiler and see the hottest places of blending modes code<br />
# Check the code of "Copy" blending mode in KoCompositeOpCopy2 and try to port it into AVX for RGB8 colorspace. Use KoOptimizedCompositeOpOver32 as an example.<br />
# If you don't feel overwhelmed with such code, you are perfectly fit for the project!<br />
# And feel free to contact Krita developers, if you have any question during these steps!<br />
<br />
'''Expected Results''': "Copy" blending mode is ported to AVX, all the "gereric" blending modes are ported to AVX<br />
<br />
'''Knowledge Prerequisite''': C++, SEE/AVX (read [http://www.intel.eu/content/www/eu/en/architecture-and-technology/64-ia-32-architectures-optimization-manual.html Intel's manual])<br />
<br />
'''Mentor''': Dmitry Kazakov (IRC: dmitryk|log)<br />
<br />
==== Project: Partial canvas updates and region of interest (performance optimization for huge (20k+) canvases) ====<br />
<br />
'''Brief Explanation''': We already have an optimization for huge canvases, which is called Instant Preview. But it woks only when the user has the canvas zoomed out to fit the screen. There are some usecases, when the user wants to work with a small "working area" of a huge image and he doesn't care what happens with the rest of the image. This project is targeted to optimize this case.<br />
<br />
'''Expected Results''': By the end of the summer we expect these features to be implemented:<br />
* Partial updates in openGL canvas. Right now we redraw all the image textures in every frame, which is not needed after porting to Qt5.<br />
* Region of Intereset (ROI) in KisImage. Updates should be reordered and the priority should be given to the areas that are currently visible to the user<br />
* Work Area Tool. The user is be able to define the area, where he would like to work in. The updates for other parts of the image are skipped until the user exits this special mode.<br />
* (if there is time) Optimize textures loading to use RIO as well. Theoretically, we can just skip uploading of the tiles that are not visible on the screen at the moment.<br />
<br />
'''Steps to apply''': The topic of the project is quite advanced, so we recommend you to do the following steps before writing a proposal:<br />
<br />
# Build Krita<br />
# Check the code in KisImage, pay attention to 'cropRect' parameter of the update calls. That is exactly what you need for limiting the updates in the work area tool<br />
# Try to write Work Area Tool: copy the code of KisToolCrop, connect it to Krita and make it override the cropRect paramenter in KisImage.<br />
# If you manage to make a draft of Work Area Tool, most probably, you will manage to complete the whole project successfully!<br />
# And feel free to contact Krita developers, if you have any question during these steps!<br />
<br />
'''Knowledge Prerequisite''': C++, OpenGL<br />
<br />
'''Mentor''': Dmitry Kazakov (IRC: dmitryk|log), Julian Thijssen (IRC: Nimmy)<br />
<br />
==== Project: Add 3D Painting Assistants ====<br />
<br />
'''Brief explanation''': One of the more innovative features in Krita are the painting assistants. These are shapes overlaid on the canvas that the artist can use to help him achieve perspective, straight lines and other shapes freehand. For complex drawings it would be useful to be able to place 3D models on the canvas, position and scale them and use those as guides for drawing.<br />
<br />
'''Expected results''': by the end of the summer, 3D models should be shown on canvas as canvas decorations, using OpenGL in hidden-line wireframe mode. The models should be manipulated using on-canvas controls like other assistants. Magnetic snapping is an optional extra.<br />
<br />
'''Knowledge Prerequisite''': C++, Qt, OpenGL, Assimp<br />
<br />
'''Mentor''': Julian Thijssen (IRC: Nimmy)<br />
<br />
=== KDE Student Programs ===<br />
<br />
KDE Student Programs is the working group responsible for running Season of KDE and managing KDE's participation in Google Summer of Code, Google Code-In, and other mentorship programmes.<br />
<br />
==== Project: A new Season of KDE Website ====<br />
<br />
'''Brief explanation''': Season of KDE will need a new website to make managing the project easier for us. The core feature set that we're looking to have comprises:<br />
<br />
* Student applications on the website<br />
* Mentors can mark themselves interested in projects during the application phase<br />
* Org admins will create slots and assign projects and mentors to slots<br />
* Manage mid-term evaluations and results<br />
* Bulk data export and import<br />
<br />
For maintainability by the rest of KDE we'd like the app to be in Python (Tornado or a WSGI framework). It would also be nice if the app was an SPA riding on top of a REST API server so we can have command-line tools interacting with the server as well.<br />
<br />
'''Expected results''': Easier project administration for KDE.<br />
<br />
'''Knowledge Prerequisite''': Python, Tornado/WSGI, LDAP, full-stack web development, Single-Page applications.<br />
<br />
'''Mentor''': Boudhayan Gupta <bgupta@kde.org>, BaloneyGeek on IRC<br />
<br />
=== GCompris ===<br />
==== Project: finishing started activities ====<br />
'''Brief explanation''': GCompris is a an educational software suite comprising of numerous activities for children aged 2 to 10. Originally written in Gtk+ it's development team started to rewrite it from scratch in Qt Quick.<br />
<br />
'''Expected results''':<br />
The aim of this year is to complete and getting merged activities that were started but have not been finished. You can find a list of tasks that you can work on at https://phabricator.kde.org/T7498. First phase is to check what is missing to be integrated (on code and graphic side) and then to complete them. You can find at https://cgit.kde.org/gcompris.git/refs/heads the list of the current branches (some of them need to be dropped, so contact us before starting working on one of them).<br />
<br />
'''Knowledge Prerequisite''':<br />
<br />
Be interested in children’s education<br />
<br />
Be familiar with GCompris concept and content<br />
<br />
Basic knowledge in a programming language (a 1 year school course is enough)<br />
<br />
Be able to build the Qt Quick version of GCompris<br />
<br />
'''Application guide''':<br />
Continuing an activity already started or rewriting from scratch is something you have to check before writing your application. Provide a timeline in your application. If you haven't contributed yet please read http://gcompris.net/wiki/An_exercise_for_new_contributors and http://gcompris.net/wiki/Reviewing_an_activity<br />
<br />
There are several info in the wiki: http://gcompris.net/wiki/Developer%27s_corner.<br />
<br />
''Feel free to contact us either on irc or by mail (gcompris-devel@kde.org)''<br />
<br />
'''Mentors''': Divyam Madaan (IRC: dmadaan), Johnny Jazeix (IRC: JohnnyJ), Rudra Nil Basu (IRC: rudra), Timothée Giet (IRC: Animtim)<br />
<br />
==== Project: Unit test framework ====<br />
<br />
'''Expected results''':<br />
The aim of this project is to build the base for unit testing for GCompris. The student will have to think on what we can test (qml, js...) and how we can put this in place.<br />
More information can be found in https://phabricator.kde.org/T7668.<br />
<br />
'''Knowledge Prerequisite''':<br />
<br />
Be interested in children’s education<br />
<br />
Be familiar with GCompris concept and content<br />
<br />
Basic knowledge in a programming language and CMake use (a 1 year school course is enough)<br />
<br />
Be able to build the Qt Quick version of GCompris<br />
<br />
Technologies used are CMake, C++, Qt.<br />
<br />
''Feel free to contact us either on irc or by mail (gcompris-devel@kde.org)''<br />
<br />
'''Mentors''': Divyam Madaan (IRC: dmadaan), Johnny Jazeix (IRC: JohnnyJ), Rudra Nil Basu (IRC: rudra), Timothée Giet (IRC: Animtim)<br />
<br />
=== KDE Partition Manager ===<br />
==== Project: finishing KAuth support [Season of KDE]====<br />
'''Brief explanation''': KDE Partition Manager is a utility program to help you manage the disk devices, partitions and file systems on your computer. It allows you to easily create, copy, move, delete, resize without losing data, backup and restore partitions.<br />
<br />
'''Expected results''':<br />
Last year a lot of work was done to make KDE Partition Manager not to start as root and use KAuth to elevate privileges. The aim of this project is to finish required refactoring and make sure everything still works.<br />
<br />
The two main issues are:<br />
<br />
* SMART support needs to be ported from (unmaitained) libatasmart library to calling smartctl command. This task is likely to be fairly easy.<br />
<br />
* KDE Partition Manager operation runner should be refactored, instead of calling KAuth helper multiple times to run a single command it has to prepare a list of all commands and their inputs and call KAuth helper once. This needs some refactoring in how partition manager reads and writes disk data (e.g. when moving/copying/backing up or restoring partition). In particular we don't want to transfer all the disk data back from the helper to the main application and back to the helper as DBus transport is fairly slow.<br />
<br />
'''Knowledge Prerequisite''':<br />
<br />
* Be able to build the KPMcore and KDE Partition Manager from source.<br />
<br />
* Knowledge of C++ / Qt (No knowledge of KDE Frameworks is required).<br />
<br />
'''Application guide''':<br />
Get in touch on IRC (#kde-devel or #calamares).<br />
<br />
'''Mentors''': Andrius Štikonas (IRC:stikonas)<br />
<br />
=== Kopete ===<br />
<br />
==== Project: Write tests and Improve protocol support ====<br />
<br />
'''Brief explanation''': Kopete is an instant messaging client that has the modular architecture and supports many messaging services with useful plugins to complement them. <br />
<br />
'''Expected results''':<br />
The aim of this project is to fix the bugs due to porting and improve the frontend and the test coverage.<br />
<br />
'''Knowledge Prerequisite''':<br />
<br />
* Be interested in test-driven development.<br />
<br />
* Be familiar with the codebase of KDE in general.<br />
<br />
* Knowledge of C++ / Qt.<br />
<br />
'''Application guide''':<br />
<br />
Get in touch with us on mailing-list and start hacking KDE and fix bugs. Teams of two people is preferred for this project as it is a lot of work :)<br />
<br />
You can contact on IRC also but it is better to discuss over mailing list as not many people are in IRC on #kopete channel.<br />
<br />
'''Mentors''': Vijay <vijaykrishnavanshi@gmail.com> (vijay_ on IRC), Kopete Mailing List <kopete-devel@kde.org><br />
<br />
=== Documentation ===<br />
<br />
==== Project [for Season of KDE only]: Verify and update the various documentation ====<br />
<br />
'''Brief explanation:''' If you have been in and around KDE for some time you might have noticed some changes in the documentation, well here is your chance is to improve them. Documentation can always use some iterations and revisits. Your task is to understand the challenges that a beginner might and write advice for them. Your speed will depend on your familiarity with KDE infrastructure.<br />
<br />
'''Expected results:''' Better documentation. <br />
<br />
'''Knowledge Prerequisite:''' C++ and Qt, and good writing skills :)<br />
<br />
'''Mentor:''' Vijay <vijaykrishnavanshi@gmail.com> (vijay_ on IRC)<br />
<br />
=== LabPlot ===<br />
[http://www.labplot.kde.org LabPlot] is a KDE-application for interactive graphing and analysis of scientific data. LabPlot provides an easy way to create, manage and edit plots and to perform data analysis.<br />
<br />
==== Project [for Season of KDE only]: Additional documentation for supported functions and constants ====<br />
<br />
'''Brief explanation''': LabPlot allows the user to generate and plot data based on mathematical expressions parameterizing the data. The internal mathematical parser supports the user with syntax highlighting and text completion. In addition to this there is a dialog where the user can navigate through all supported functions (standard mathematical functions, Bessel functions, Fermi-Dirac functions, zeta functions, etc.) and constants (mathematical constants, constants from astrophysics, nuclear physics, etc.) and select the desired expression. To improve the user experience and to further help the selection of the proper mathematical expression, additional documentation in form of the corresponding article on Wikipedia or on mathworld.com should be provided. The idea is to provide a web view in the dialog where the selection of the supported expressions is done and to load their the corresponding web page providing further information. E.g., by selecting the Gegenbauer polynomials, the user can optionally open the additional documentation showing the wiki page in the local language https://de.wikipedia.org/wiki/Gegenbauer-Polynom (maybe the mobile version) with the option to switch to mathworld docu on http://mathworld.wolfram.com/GegenbauerPolynomial.html.<br />
<br />
The task is to systematically go through all supported expressions and to collect the links to the web pages and to implement the optional web view loading those web pages in the dialog mentioned above.<br />
<br />
'''Expected results''': Increased user experience during for the input of mathematical expressions <br />
<br />
'''Knowledge Prerequisite''': C++, Qt<br />
<br />
'''Mentor''': Fabian Kristof - Szabolcs<br />
<br />
==== Project: Plotting of live MQTT data ====<br />
'''Brief explanation''': LabPlot has already some support for plotting of live-data (http://krajszgsoc.blogspot.de/2017/09/in-finish-line-but-not-in-end.html). To cover more use-cases we want to also support MQTT sources. We need to investigate the available MQTT libraries for Qt:<br />
* https://blog.qt.io/blog/2017/08/14/introducing-qtmqtt-protocol/<br />
* https://github.com/emqtt/qmqtt<br />
and to add some support for MQTT to LabPlot.<br />
<br />
'''Expected results''': Similar to the currently supported data sources (files, sockets, serial port, SQL databases) we want to support the subscription to MQTT brockers and plotting of their data. <br />
<br />
'''Knowledge Prerequisite''': C++, Qt, (optional) knowledge and experience with MQTT<br />
<br />
'''Mentor''': Fábián Kristóf - Szabolcs (mailto:fkristofszabolcs@gmail.com)<br />
<br />
==== Project: Import of educational data sets available on the internet ====<br />
'''Brief explanation''': There are many internet pages providing data sets for educational and study purposes for many different areas (astrophysics, statistics, medicine, etc.). Some tools used in the scientific area provide some "wrappers" for such online sources and allow the user to easily play around with those data sets in the applications whereas the technical details like fetching of data from the server and parsing are done completely transparent for the user. The goal of this project is to add similar functionality to LabPlot. There will be a wizard where the user can select from a thematically grouped list of data sets available online. The internal description of such an online data set should contain the URL with the actual file that needs to be downloaded and the settings for LabPlot's data parser (separator, column names and data types, etc.). The data fetched once should be cached so there is no need to fetch from the web again. Here we can have a look maybe at KStars for how to implement such a caching strategy and maybe even re-use some code from KStars.<br />
In addition to the list of pre-defined online sources, we need to elaborate how the user can add new online data sets (together with all the required parametrization) and publish the settings to make them available for everybody.<br />
<br />
'''Expected results''': We want to be able to easily import the educational data sets available on the internet.<br />
<br />
'''Knowledge Prerequisite''': C++, Qt<br />
<br />
'''Mentor''': tbd<br />
<br />
==== Project: Import of data from web-services ====<br />
'''Brief explanation''': Brief explanation: This goal of this project is to extend the number of supported data sources by adding the possibility to import the data from web services (live and historical financial data, weather, etc.). Most web services expose their data via JSON. We need to add a "JSON filter" to LabPlot capable to connect to a web service, to fetch the data, to parse it and to import into LabPlot's internal data containers. In the GUI the user should be guided through the entry of the service URL, additional services parameters like API token, etc. and through the settings for the actual parsing (which JSON fields to consume and how). Also, it should be possible to refresh the data periodically like it is already possibile for the live data (http://krajszgsoc.blogspot.de/2017/09/in-finish-line-but-not-in-end.html). The goal is also to provide a set of widely known web services so the user can select and import the data from a list of pre-defined services. In addition to this, we need to elaborate the possibility to "publish" the settings for a web-service done by the user and make them publicaly available to every LabPlot user.<br />
<br />
<br />
'''Expected results''': Similar to the currently supported data sources (files, sockets, serial port, SQL databases) we want to import the data from web services and visualize it.<br />
<br />
'''Knowledge Prerequisite''': C++, Qt, (optional) JSON support in Qt<br />
<br />
'''Mentor''': tbd<br />
<br />
=== Kdenlive ===<br />
[https://kdenlive.org Kdenlive] is a KDE-application for professionnal video editors. It supports hundreds of video formats, and all the features you can expect from a non-linear video editor, including some advanced features like timeline preview rendering, proxy clips and more. <br />
<br />
==== Project [for Season of KDE only]: Improve audio workflow: mixer ====<br />
<br />
'''Brief explanation''': Kdenlive already allows you adjust audio levels for each clip or for an entire track by adding effects. The idea of an audio mixer is to create a new widget that easily allows to control volume and balance for each track without having to search for effects. The core audio components should already be available through our video framework MLT. So this job will require to understand how Kdenlive interacts with MLT. Some details about the audio mixer features can be found in our [https://kdenlive.org/video-editing-applications-handbook/#audio documentation]<br />
<br />
'''Expected results''': Better control of the audio output for users <br />
<br />
'''Knowledge Prerequisite''': C++, Qt, requires some preliminary studies to understand how Kdenlive/MLT work<br />
<br />
'''Mentor''': Jean-Baptiste Mardelle<br />
<br />
==== Project [for Season of KDE only]: Improve on monitor controls for image transformation ====<br />
<br />
'''Brief explanation''': When adding a "Transform" effect to a clip in Kdenlive, you can then resize and move the image directly on the monitor through a Qml overlay. The idea is to also add the possibility to adjust rotation directly on the monitor screen, and improve the general UI of this Qml overlay.<br />
<br />
'''Expected results''': Fluent control of size, position and rotation inside the monitor<br />
<br />
'''Knowledge Prerequisite''': C++, Qt, Qml - this does not require much knowledge of Kdenlive, and is mostly a Qml work<br />
<br />
'''Mentor''': Jean-Baptiste Mardelle<br />
<br />
=== Choqok ===<br />
==== Project: Port Choqok to Kirigami ====<br />
<br />
'''Brief explanation:''' Current Choqok UI doesn't make use of QML and creates interfaces in C++ files. The idea is to rewrite the interface in QML. At this point is better doing it with Kirigami since this means it will work on Plasma Mobile too.<br />
<br />
'''Expected results:''' Choqok UI makes use of Kirigami.<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt, Qml<br />
<br />
'''Mentor:''' Andrea Scarpino (IRC: ilpianista)<br />
<br />
'''Application guide''':<br />
Get in touch on IRC (#choqok).<br />
<br />
=== KStars ===<br />
<br />
[https://edu.kde.org/kstars KStars] is free, open source, cross-platform Astronomy Software. It provides an accurate graphical simulation of the night sky, from any location on Earth, at any date and time. <br />
<br />
==== Project: Deep Sky Object Overhaul ====<br />
'''Brief explanation''': KStars supports many deep sky objects (DSOs) including galaxies, nebulae, supernovae, clusters and more. Currently, some deep sky catalogs are stored in simple space separated text format where they are parsed into KStars directly or into KStars Deep Sky Component SQLite3 database which is then loaded in KStars. However, since all DSOs are loaded at once into memory, this limits the size of catalogs within KStars. A solution similar to how dynamic stars are cached in and out of memory must be developed for DSOs. Furthermore, all catalog entries should have their trixels indexed so that they can be efficiently drawn unto the sky map. Another issue is that catalogs can overlap since there is no cross-identification of various catalogs. For example, Andromeda galaxy exists in Messier catalog as M31, and exists in NGC catalog as NGC 224. The database should support ability to cross-identify objects from all supported and future catalogs.<br />
<br />
'''Expected results''': <br />
* Convert all text-format catalogs to SQLite3 database.<br />
* Develop master DSO database where cross-identification of objects is supported. Master database can supported addon downloadable catalogs where they can be merged once downloaded by the user.<br />
* Import of The Principal Galaxy Catalog, 2003 Version (PGC2003) which contains ~1 million galaxies into KStars as a downloadable addon.<br />
* Caching and drawing optimizations for large catalogs.<br />
* Cross-identification for all supported DSO catalogs including, but not limited too: NGC/IC/Messier/Arp/PGC/LDN<br />
* Trixel indexation for all DSOs. Implementation of improved drawing cached routine in KStars for DSOs similar to stars.<br />
* All necessary updates within KStars maps, tools and dialogs to reflect the above changes.<br />
<br />
'''Knowledge Prerequisite''': C++, Qt, Data Structures<br />
<br />
'''Mentor''': Jasem Mutlaq ([https://riot.im/app/#/room/#kstars:matrix.org Matrix]: Jasem)<br />
<br />
==== Project: Ekos Web Client ====<br />
'''Brief explanation''': Ekos is KStars premier tool for observatory control and automation. A web client port of Ekos is desired where it communicates with the underlying INDI servers and drivers without a direct dependency on thick desktop clients. Ekos includes many modules including setup, capture, focus, guide, align, and mount. All functionalities of the desktop Ekos client are expected in the web client version using Python+Ajax or similar framework technologies suitable for online dynamic driven clients.<br />
<br />
'''Expected results''': <br />
* Online Ekos web client with all the thick client feature set.<br />
* Authentication and Registration framework.<br />
* Support for notifications similar to desktop client.<br />
* Ajax dynamic driven interface with near real time updates for framing and captures.<br />
* Multi-user support with granular permissions.<br />
* Web based INDI Control Panel with all the driver controls as in the desktop version.<br />
<br />
'''Knowledge Prerequisite''': C++, Qt, Django/Ajax or similar technology framework.<br />
<br />
'''Mentor''': Jasem Mutlaq ([https://riot.im/app/#/room/#kstars:matrix.org Matrix]: Jasem)<br />
<br />
==== Project: Implement Qt3D backend for KStars ====<br />
'''Brief explanation''': The Skymap in KStars desktop version is currently built using QPainter and 2D drawing primitives. In order to take advantage of advances in modern GPU hardware and to present a stunning visual view of the night sky, a 3D backend is desired. Qt 3D provides functionality for near-realtime simulation systems with support for 2D and 3D rendering in both Qt C++ and Qt Quick applications. Within KStars, SkyPainter provides a backend-agnostic class for drawing object unto the skymap regardless of the backend. Previously, an experimental OpenGL backend was developed but was later deprecated due to drawing issues. Since Qt3D provides an abstraction to the backend framework (OpenGL/Vulkan/DirectX), it presents a very flexible framework for building future-proof 3D applications.<br />
<br />
'''Expected results''': <br />
* Create Qt3D based backend to draw all objects currently implemented by QPainter backend.<br />
* Create realistic colors, shares, textures, meshes, lighting for all stars, solar system, and deep sky objects.<br />
* Create animations for meteor shows, comet tails, stars twinkle..etc<br />
'''Knowledge Prerequisite''': C++, Qt, Prior experience working with 3D applications/games.<br />
<br />
'''Mentor''': Akarsh Simha ([https://riot.im/app/#/room/#kstars:matrix.org Matrix]: kstar)<br />
<br />
=== Peruse ===<br />
<br />
Peruse is a comic book reader application by KDE, which is designed to work both on touch based devices, and on the traditional desktop. Additionally, it has a tool called Peruse Creator which is designed to create comic books for use with Peruse and any other CBZ capable comic book reader. It has rudimentary support for the [http://acbf.wikia.com/wiki/Specifications Advanced Comic Book Format], which is a metadata container for comic book archives (CBR, CBZ and so on).<br />
<br />
See also the Peruse website for more detailed information: https://peruse.kde.org/<br />
<br />
==== Project: Expand Creator's Abilities ====<br />
<br />
'''Brief explanation:''' Peruse Creator is currently very simple, and will allow the user to create a CBZ comic book archive annotated with a subset of the [http://acbf.wikia.com/wiki/Specifications Advanced Comic Book Format] (ACBF) metainfo, such as authors, publisher information, characters and so on. It does not allow for the creation or editing of the viewport based navigation that ACBF describes, nor does it support the text layers system ACBF proposes for comic book translation. It also lacks editor components for a variety of the general metainformation ACBF suggests.<br />
<br />
Your project proposal should include explicit descriptions of which of these you wish to build support for, and how you propose to do so. It should further include timeframes for each.<br />
<br />
'''Expected results:''' A more capable Peruse Creator.<br />
<br />
'''Knowledge Prerequisite:''' C++ and Qt required, additionally QML/QtQuick knowledge is preferred<br />
<br />
'''Mentor:''' Dan Leinir Turthra Jensen (admin@leinir.dk, IRC: leinir, Telegram and twitter: @leinir)<br />
<br />
==== Project: New Viewer Component ====<br />
<br />
'''Brief explanation:''' The current viewer component for Comic Book Archives (CBR) in Peruse is a simple full-page viewer, which only supports page-by-page navigation. The [http://acbf.wikia.com/wiki/Specifications Advanced Comic Book Format] (ACBF) metadata container brings with it support for a viewport system, which describes how the application should present [http://acbf.wikia.com/wiki/Body_Section_Definition#Frame specific sub-sections of each page], as well as a system for [http://acbf.wikia.com/wiki/Body_Section_Definition#Jump navigating between arbitrary pages in the comic].<br />
<br />
Your project proposal should include explicit descriptions of how you would suggest to implement this, as well as a schedule for the work.<br />
<br />
'''Expected results:''' A viewer component which is able to consume and display the viewport based navigation metadata from the ACBF container, as well as present the general metainformation to the user.<br />
<br />
'''Knowledge Prerequisite:''' C++ and Qt required, additionally QML/QtQuick knowledge is preferred<br />
<br />
'''Mentor:''' Dan Leinir Turthra Jensen (admin@leinir.dk, IRC: leinir, Telegram and twitter: @leinir)</div>Leinirhttps://community.kde.org/index.php?title=Akademy/2017/Wednesday&diff=77683Akademy/2017/Wednesday2017-07-26T08:40:46Z<p>Leinir: /* Room 2.4 - 26th July */</p>
<hr />
<div>= BoF sessions on Wednesday, July 26th 2017 =<br />
<br />
''All rooms are on Aulario IV and have either a blackboard or a whiteboard.'' If you need any other equipment, please send an email to akademy-team@kde.org.<br />Please put your name and email address in the Host/Notes section. There is no length limitation; text will wrap. <br />
<br />
'''BoF Wrap-up at 18:00'''<br /><br />
Please join the BoF wrap-up session this evening. Another opportunity for communication. Share outcomes and plans, cross-pollinate, attract attention to your project.<br />
Please select someone from your BoF to give a summary—topic, what was discussed and decided, what's next, resources desired.<br />
<br />
The Akademy team might reasign BoFs based on operational needs<br />
<br />
=== Room 2.2 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.2<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30 <br />
| Lunch and Daytrip<br />
|<br />
|}<br />
<br />
=== Room 2.4 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.4<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" | Open Collaboration Services 1.7 Proposal Preparation<br />
| width="400pt" | Dan Leinir Turthra Jensen (admin@leinir.dk) - https://notes.kde.org/p/akademy-2017-ocs-1.7-bof<br />
|-<br />
| 10:30<br />
| Munich city KDE requirements<br />
| https://notes.kde.org/p/akademy-2017-limux-bof<br />
|-<br />
| 11:30 <br />
|KDE Applications Lifecycle update https://community.kde.org/Policies/Application_Lifecycle/Draft<br />
| jriddell<br />
|-<br />
| 12:30<br />
| Lunch and Daytrip<br />
|<br />
|}<br />
<br />
=== Room 2.5 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.5<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |UserBase wiki <br />
| width="400pt" |Claus_chr - UserBase is serioulsy out of date, and very little work is being done. What should we do? Drop it? Try to revive it? Total revive: https://notes.kde.org/p/UserbaseWiki<br />
|-<br />
| 10:30<br />
| Build your own Flatpak workshop<br />
| Aleix<br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
| Lunch and Daytrip<br />
| <br />
|}<br />
<br />
=== Room 2.6 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.6<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
| Lunch and Daytrip<br />
|<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Akademy/2017/Wednesday&diff=77680Akademy/2017/Wednesday2017-07-26T06:09:01Z<p>Leinir: /* Room 2.4 - 26th July */</p>
<hr />
<div>= BoF sessions on Wednesday, July 26th 2017 =<br />
<br />
''All rooms are on Aulario IV and have either a blackboard or a whiteboard.'' If you need any other equipment, please send an email to akademy-team@kde.org.<br />Please put your name and email address in the Host/Notes section. There is no length limitation; text will wrap. <br />
<br />
'''BoF Wrap-up at 18:00'''<br /><br />
Please join the BoF wrap-up session this evening. Another opportunity for communication. Share outcomes and plans, cross-pollinate, attract attention to your project.<br />
Please select someone from your BoF to give a summary—topic, what was discussed and decided, what's next, resources desired.<br />
<br />
The Akademy team might reasign BoFs based on operational needs<br />
<br />
=== Room 2.2 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.2<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30 <br />
| Lunch and Daytrip<br />
|<br />
|}<br />
<br />
=== Room 2.4 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.4<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" | Open Collaboration Services 1.7 Proposal Preparation<br />
| width="400pt" | Dan Leinir Turthra Jensen (admin@leinir.dk)<br />
|-<br />
| 10:30<br />
| Munich city KDE requirements<br />
| <br />
|-<br />
| 11:30 <br />
|KDE Applications Lifecycle update https://community.kde.org/Policies/Application_Lifecycle/Draft<br />
| jriddell<br />
|-<br />
| 12:30<br />
| Lunch and Daytrip<br />
|<br />
|}<br />
<br />
=== Room 2.5 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.5<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |UserBase wiki <br />
| width="400pt" |Claus_chr - UserBase is serioulsy out of date, and very little work is being done. What should we do? Drop it? Try to revive it?<br />
|-<br />
| 10:30<br />
| Build your own Flatpak workshop<br />
| Aleix<br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
| Lunch and Daytrip<br />
| <br />
|}<br />
<br />
=== Room 2.6 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.6<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
| Lunch and Daytrip<br />
|<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Akademy/2017/Wednesday&diff=77679Akademy/2017/Wednesday2017-07-26T06:07:53Z<p>Leinir: /* Room 2.2 - 26th July */</p>
<hr />
<div>= BoF sessions on Wednesday, July 26th 2017 =<br />
<br />
''All rooms are on Aulario IV and have either a blackboard or a whiteboard.'' If you need any other equipment, please send an email to akademy-team@kde.org.<br />Please put your name and email address in the Host/Notes section. There is no length limitation; text will wrap. <br />
<br />
'''BoF Wrap-up at 18:00'''<br /><br />
Please join the BoF wrap-up session this evening. Another opportunity for communication. Share outcomes and plans, cross-pollinate, attract attention to your project.<br />
Please select someone from your BoF to give a summary—topic, what was discussed and decided, what's next, resources desired.<br />
<br />
The Akademy team might reasign BoFs based on operational needs<br />
<br />
=== Room 2.2 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.2<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30 <br />
| Lunch and Daytrip<br />
|<br />
|}<br />
<br />
=== Room 2.4 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.4<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| Munich city KDE requirements<br />
| <br />
|-<br />
| 11:30 <br />
|KDE Applications Lifecycle update https://community.kde.org/Policies/Application_Lifecycle/Draft<br />
| jriddell<br />
|-<br />
| 12:30<br />
| Lunch and Daytrip<br />
|<br />
|}<br />
<br />
=== Room 2.5 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.5<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |UserBase wiki <br />
| width="400pt" |Claus_chr - UserBase is serioulsy out of date, and very little work is being done. What should we do? Drop it? Try to revive it?<br />
|-<br />
| 10:30<br />
| Build your own Flatpak workshop<br />
| Aleix<br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
| Lunch and Daytrip<br />
| <br />
|}<br />
<br />
=== Room 2.6 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.6<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
| Lunch and Daytrip<br />
|<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Akademy/2017/daytrip/registration&diff=77535Akademy/2017/daytrip/registration2017-07-23T10:59:57Z<p>Leinir: /* Wednesday daytrip registration */</p>
<hr />
<div><br />
= Wednesday daytrip registration =<br />
<br />
This is the registration page for the [[Akademy/2017/daytrip | Wednesday daytrip]]. If you are sure to attend please add your name. Remember there are exactly '''49 seats''' available:<br />
<br />
# Jos van den Oever<br />
# Jure Repinc<br />
# Ivan Čukić<br />
# David Edmundson<br />
# Francis Herne<br />
# Helio Castro<br />
# Lia Silva<br />
# Sven Brauch<br />
# Albert Astals Cid <br />
# Ingo Klöcker <br />
# Dominik Haumann<br />
# Christoph Cullmann<br />
# José Millán Soto <br />
# Luigi Toscano <br />
# Luciano Montanaro<br />
# Silvia Montanaro <br />
# Dan Leinir Turthra Jensen<br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
#<br />
# <br />
# <br />
#</div>Leinirhttps://community.kde.org/index.php?title=Akademy/2017/Wednesday&diff=77410Akademy/2017/Wednesday2017-07-19T08:22:50Z<p>Leinir: /* Room 2.2 - 26th July */</p>
<hr />
<div>= BoF sessions on Wednesday, July 26th 2017 =<br />
<br />
''All rooms have either a blackboard or a whiteboard.'' If you need any other equipment, please send an email to akademy-team@kde.org.<br />Please put your name and email address in the Host/Notes section. There is no length limitation; text will wrap. <br />
<br />
'''BoF Wrap-up at 18:00'''<br /><br />
Please join the BoF wrap-up session this evening. Another opportunity for communication. Share outcomes and plans, cross-pollinate, attract attention to your project.<br />
Please select someone from your BoF to give a summary—topic, what was discussed and decided, what's next, resources desired.<br />
<br />
The Akademy team might reasign BoFs based on operational needs<br />
<br />
=== Room 2.2 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.2<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| Open Collaboration Services 1.7 Proposal Preparation<br />
| Dan Leinir Turthra Jensen (admin@leinir.dk)<br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30 <br />
| Lunch and Daytrip<br />
|<br />
|}<br />
<br />
=== Room 2.4 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.4<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
| Lunch and Daytrip<br />
|<br />
|}<br />
<br />
=== Room 2.5 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.5<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
| Lunch and Daytrip<br />
| <br />
|}<br />
<br />
=== Room 2.6 - 26th July ===<br />
{| class="wikitable" border="1"<br />
|-<br />
! 2.6<br />
!<br />
! <br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
| Lunch and Daytrip<br />
|<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Plasma/Affenfels&diff=75814Plasma/Affenfels2017-01-05T16:13:48Z<p>Leinir: /* People */</p>
<hr />
<div>Plasma's 2017 Sprint, Stuttgart<br />
<br />
https://reimbursements.kde.org/events/25<br />
<br />
This Plasma sprint will be hosted at [http://www.vonaffenfels.de von Affenfels GmbH], Kronenstraße 40, 70174 Stuttgart, Germany. <br />
<br />
Monday 6 February 2017 - Sunday 12 February 2017<br />
== Directions ==<br />
From Stuttgart Hauptbahnhof (main station) it is a less than 10 minutes walk to get there. <br />
<br />
The airport Flughafen Stuttgart (STR) has train connections to the main station (S2 and S3, look for the green circle with a white S in it), running roughly every 15 minutes.<br />
<br />
You can find public transport information here: http://en.vvs.de/home/ (they also have an app for Android (runs on BB10 just find and should on Sailfish too), iOS, Windows Phone)<br />
<br />
Ticket from airport to main station is 4 € (3 zones)<br />
Ticket from the ibis budget hotel is 2,80 € (2 zones) - you could buy a "4er Ticket" which allows to stamp for four rides. (10,60 € ie. 2,65 € per ride)<br />
<br />
Unfortunately, week pass is subscription-only, i.e. you can't just buy it at a ticket machine.<br />
<br />
Regional and long-distance trains arrive at Stuttgart Hauptbahnhof (oben) which is at the surface.<br />
U Stadtbahn (blue square with a "U") arrives Hauptbahnhof "Arnulf-Klett-Platz" which is one level underground<br />
S-Bahn (green circle with an "S") arrives Hauptbahnhof (tief) which is two levels underground<br />
<br />
== Accommodation ==<br />
Recommended accommodation I guess is [http://www.ibis.com/de/hotel-5441-ibis-budget-stuttgart-city-nord/index.shtml ibis budget Hotel Stuttgart Nord], roughly 350 € for a double room Monday through Sunday.<br />
<br />
There's a frequent Stadtbahn ("U Stadtbahn", look for the blue square with a white U in it) connection at "Maybachstraße" (line U6) going to Hauptbahnhof (main station) main station, taking less than 10 minutes.<br />
<br />
== Communications ==<br />
<br />
[https://telegram.me/joinchat/A36wiAoJgD9Tz9mP_9Q4LA Telegram Group]<br />
<br />
== People ==<br />
<br />
{| border="1"<br />
|-<br />
! Name <br />
! When?<br />
! Accommodation<br />
! Mobile<br />
! Transport<br />
! Dietary needs<br />
|-<br />
| Kai Uwe Broulik (host)<br />
| Mon, 6 Feb – Sun, 12 Feb<br />
| At Home ;)<br />
| +49 173 184 3 987<br />
| Car / Train<br />
| None<br />
|-<br />
| Jonathan Riddell<br />
| Sun 5 Feb – Sun, 12 Feb<br />
| Ibis Budget Nord<br />
| +44 7941 938912<br />
| Doing a road trip from FOSDEM with David E, arriving Sunday 5 late, leaving Sunday 12 early<br />
| <br />
|-<br />
| David Edmundson<br />
| Sun 5 Feb – Sun, 12 Feb<br />
| Ibis Budget Nord<br />
| +44 7481923182<br />
| Doing a road trip from FOSDEM with Jonathan R, arriving Sunday 5 late, leaving Sunday 12 early<br />
| <br />
|-<br />
| Marco Martin<br />
| Mon 6 Feb – Sun, 12 Feb<br />
| Ibis Budget Nord<br />
| +39 3492547165<br />
| Plane/Train<br />
| None<br />
|-<br />
| Sebastian Kügler<br />
| Mon 6 Feb – Sun, 12 Feb<br />
| Ibis Budget Nord<br />
| +31 48370928<br />
| Train<br />
| None<br />
|-<br />
| Aleix Pol<br />
| Mon 6 Feb – Fri, 10 Feb<br />
| Wherever you tell me<br />
| <br />
| Will be coming from FOSDEM, leaving by plane<br />
| None<br />
|-<br />
| Bhushan Shah<br />
| Mon 6 Feb - Sun 12 Feb<br />
| ibis Budget Nord<br />
|<br />
| Arrival train/Depart flight<br />
| Vegetarian<br />
|-<br />
| Roman Gilg<br />
| Mon 6 Feb - Sun 12 Feb<br />
| ibis Budget Nord<br />
|<br />
| Train or car (probably from Munich if someone is interested in ride sharing )<br />
| None<br />
|-<br />
| Ken Vermette<br />
| Mon 5-6 Feb - Sun 12 Feb<br />
| Wherever you put me<br />
| +1-613-483-0556<br />
| Train, Plane, Pair of shoes<br />
| None<br />
|-<br />
| Dan Leinir Turthra Jensen<br />
| Mon 6 Feb - Sun 12 Feb<br />
| ibis Budget Nord<br />
| +44 7402 160 469<br />
| Plane<br />
| None<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2016&diff=72342Sprints/Randa/20162016-06-16T15:52:58Z<p>Leinir: /* Blogs */</p>
<hr />
<div>Here you find information which is important for the duration of the meetings (Sunday, 12th to Sunday, 19th of June 2016).<br />
<br />
= Important general information =<br />
<br />
Here you'll find imporant information for the time during the meeting. Such as e.g. the departure time for the trip to Zermatt. So take a look here from time to time. For general information about the Randa meetings (how to reach, grocery nearby, etc.) go [[Sprints/Randa|one page up]].<br />
<br />
* Personal information about [http://community.kde.org/Sprints/Randa/2016/Travel dates and times of arrival and departure].<br />
* Please add a short note about what you did on the [http://community.kde.org/Sprints/Randa/2016/Work work page].<br />
* [https://sprints.kde.org/sprint/301 Registration page]<br />
* Fundraiser TBD<br />
* [http://survey.kde.org/index.php Feedback questionnaire]: Randa Meetings participants, please fill in!<br />
<br />
== Topic this year ==<br />
Bring KDE software to more platforms<br />
<br />
== Bank account information ==<br />
<br />
For the people who need to send us the food and other money:<br/><br />
''It seems that from the Euro zone you need to do an international transfer instead of the standard Euro IBAN.''<br />
* IBAN: CH91 8049 6000 0097 0223 2<br />
* Address: Verein Randa Meetings, Mario Fux, Uferweg 20, 3400 Burgdorf BE, Switzerland<br />
* Currency: CHF<br />
* Make sure to select ''Cost payed by sender'' or you'll have to buy Mario a drink ;)<br />
* Bank information:<br />
** '''name:''' Raiffeisen Mischable-Matterhorn<br />
** '''SWIFT/BIC Code:''' RAIFCH22<br />
** See [http://www.swissiban.com/bdesc.php?id=3581 this website] for more.<br />
<br />
== Opening time local grocery ==<br />
<br />
* Monday to Wednesday, Friday: 7:30 to 10:00 and 16:00 to 18:00 (closed on Tuesday and Thursday afternoon)<br />
* Saturday: 7:30 to 10:00 and 14:00 to 16:00 (NEEDS TO BE VERIFIED)<br />
<br />
== Remember to bring ==<br />
This is a not-exhaustive list by going thru various emails sent<br />
* Towel<br />
* Clothes fitting the weather<br />
* Indoor shoes<br />
* Squirrel<br />
* Sleeping bag or 30 CHF for renting a thick blanket.<br />
* 15CHF per day for food (plus 5 CHF for the week: chef fee ;-)<br />
* Swiss power adapter<br />
* Hiking shoes<br />
Remember, Randa House is closer to camping than to a 5 star hotel. <br />
<br />
= Hardware to use and try =<br />
* 2 ExoPC (1:?, 1: frinring)<br />
* 1 WeTab<br />
* 1 Touch monitor 27''<br />
* 1 Projector<br />
* 1 extra laptop running Windows + complete SDK setup (emerge/Qt5+deps/KF5/MSVC2015) [kfunk]<br />
* 1x [https://support.lenovo.com/en/documents/pd100258 ThinkVision 28 - Touch 28-inch 4K2K Tegra K1 Entertainment Center]<br />
<br />
Enter your group below:<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%"<br />
|-<br />
! scope="col" | Date<br />
! scope="col" | Device 1<br />
! scope="col" | Device 2<br />
|-<br />
| Monday<br />
|<br />
|<br />
|-<br />
| Tuesday<br />
|<br />
|<br />
|-<br />
| Wednesday<br />
|<br />
|<br />
|-<br />
| Thursday<br />
|<br />
|<br />
|-<br />
| Friday<br />
|<br />
|<br />
|-<br />
| Saturday<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
= Room/Group reservations =<br />
<br />
Please add you group name to a room and time in the table below to schedule a meeting or BoF. For the room names (Africa, America, Asia, Australia & Europe) and sizes see [http://community.kde.org/File:Grundriss-new2.gif the ground plan of the building]<br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%"<br />
|-<br />
! scope="col" | Date<br />
! scope="col" | Africa<br />
! scope="col" | America<br />
! scope="col" | Asia<br />
! scope="col" | Australia<br />
! scope="col" | Europe<br />
|-<br />
| Monday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Monday: 14:00-18:00<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Monday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Tuesday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|Android Session<br />
|-<br />
| Tuesday: 14:00-18:00<br />
|KMyMoney QML<br />
|<br />
| <br />
|<br />
|2pm Windows Session, 4pm OS X<br />
|-<br />
| Tuesday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Wednesday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|10am Linux Deployment Session<br />
|-<br />
| Wednesday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|14:00 KNewStuff Session<br />
|-<br />
| Wednesday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Saturday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Saturday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|14:00 KNewStuffCore session<br />
|-<br />
| Saturday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
|}<br />
<br />
= OpenDay =<br />
<br />
None this year. Please get in contact with us if you're interested to visit us. We'll find a day that fits best.<br />
<br />
<br />
= Trip - TBD =<br />
<br />
If the weather is good enough (there is no definition at this point in time ;-) we'll do a short trip to Zermatt and (for the more sporty ones) do a short (there is a definition: 3 hours and around 15 km) hike back to Randa.<br />
<br />
<br />
= Menu plan =<br />
<br />
Everyday a new meal.<br />
*Breakfast: 7.30-9.30<br />
*Lunch: 13.00 (1pm) <br />
*Dinner: 19.00 (7pm)<br />
<br />
= Blog posts and other news about the meeting =<br />
<br />
Please add here the URLs to the blog posts about the meeting (newest on the top of the list!).<br />
<br />
== Blogs ==<br />
<br />
When writing a blog entry, please add something like the thing below to your blog, so we can get a bit of exposure to the fundraiser. Modify the text as you see fit ;)<br />
<br />
<nowiki><div class="separator" style="clear: both; text-align: center;"><br />
<a href="https://www.kde.org/fundraisers/randameetings2016/"><img border="0" height="55" src="https://www.kde.org/fundraisers/randameetings2016/images/banner-fundraising2016.png" width="400" /><br /><br />
Help us keep going, at this and many other sprints, clickety-click! :D</a></div></nowiki><br />
<br />
=== June 16 ===<br />
* Dan Leinir Turthra Jensen (leinir) [http://kath-leinir.blogspot.ch/2016/06/perusing-progress-at-randa-meetings-2016.html Perusing Progress at Randa Meetings 2016]<br />
* David Faure (dfaure) [https://blogs.kde.org/2016/06/16/icon-theme-deployment-windows-mac-os-and-mobile-platforms Icon theme deployment on Windows, Mac OS and mobile platforms]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/16/new-katekwrite-bundles-for-mac/ New Kate/KWrite Bundles for Mac]<br />
* Adriaan de Groot (adridg) [http://euroquis.nl/bobulate/?p=1482 Randa in General]<br />
<br />
=== June 15 ===<br />
* Kai Uwe Broulik (kbroulik) [http://blog.broulik.de/2016/06/plasma-in-randa/ Plasma in Randa]<br />
* Dennis Nienhüser (Earthwings) [http://nienhueser.de/blog/?p=658 Marble 1.14.1 for Windows]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/15/kate-co-on-tour/ Kate & Co. on Tour]<br />
* Dominik Haumann (dhaumann) [https://kate-editor.org/2016/06/15/kates-tabbar-gets-movable-tabs/ Kate's Tabbar gets Movable Tabs]<br />
* Joseph W. Joshua (joejoshw) [https://kdenlive.org/node/9468 Moving towards a working Windows Build]<br />
* Adriaan de Groot (adridg) [http://euroquis.nl/bobulate/?p=1480 Zanshin 0.4 on FreeBSD]<br />
<br />
=== June 14 ===<br />
* Lays Rodrigues (BR-Print3D) [https://laysrodriguesdev.wordpress.com/2016/06/14/randa-meetings-day-3/ Randa Meetings – Day 3]<br />
* Andreas Cord-Landwehr (CoLa) [https://cordlandwehr.wordpress.com/2016/06/14/adding-android-to-the-ci-and-many-nit-picks/ Adding Android to the CI and Many Nit-Picks]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/14/new-mac-os-x-build-documentation/ New Mac OS X Build Documentation]<br />
* Adriaan de Groot (adridg) [http://euroquis.nl/bobulate/?p=1478 Reconciling Packaging Data (2)]<br />
* Dominik Haumann (dhaumann) [https://kate-editor.org/2016/06/14/minimap-fine-tuning/ MiniMap Fine-Tuning]<br />
* Adriaan de Groot (adridg) [http://euroquis.nl/bobulate/?p=1473 Reconciling Packaging Data]<br />
* Jean-Baptiste Mardelle (j-b-m) [https://kdenlive.org/node/9467 Kdenlive in Randa]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/14/updated-bundles-now-release-builds-and-less-frameworks/ Updated Bundles, now Release Builds and less Frameworks]<br />
<br />
=== June 13 ===<br />
* Lays Rodrigues (lays147) [https://laysrodriguesdev.wordpress.com/2016/06/13/randa-meetings-day-2/ Randa Meetings Day 2]<br />
* Kevin Funk (kfunk) [http://kfunk.org/2016/06/13/working-on-kdevelop-and-kde-on-windows-in-randa/ Working on KDevelop and KDE on Windows in Randa]<br />
* Scarlett Clark (sgclark) [http://scarlettgatelyclark.com/2016/debian-kde-reproducible-builds-week-3-randa-platforms-equals-busy-times/ Debian: KDE: Reproducible Builds week 3, Randa Platforms Equals Busy times!]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/13/new-get-it-page-build-it-split-out/ New “Get It” Page & “Build It” split out]<br />
* Dominik Haumann (dhaumann) [https://kate-editor.org/2016/06/13/working-on-kate-in-randa/ Working on Kate in Randa]<br />
* Dan Leinir Turthra Jensen (leinir) [http://kath-leinir.blogspot.ch/2016/06/randa-meetings-2016-is-go.html Randa Meetings 2016 is go!]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/13/katekwrite-application-bundle-update/ Kate/KWrite Application Bundle Update]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/13/first-day-in-randa/ First Day in Randa]<br />
<br />
=== June 12 ===<br />
*Lays Rodrigues (lays147) [https://laysrodriguesdev.wordpress.com/2016/06/12/randa-meetings-first-day/ Randa Meetings First Day]<br />
<br />
=== Pre Sprint ===<br />
* Aleix Pol [http://www.proli.net/2016/06/10/kde-on-flatpak-in-randa/ KDE on Flatpak]<br />
* Christoph Cullmann (cullmann) (June 11) [https://kate-editor.org/2016/06/11/randa-meeting-2016-tomorrow-on-tour/ Randa Meeting 2016 – Tomorrow on Tour ;=)]<br />
* Lays Rodriguezs (BR-Print3D) (May 28) [https://laysrodriguesdev.wordpress.com/2016/05/28/coding-at-lakademy/ Coding at Lakademy]<br />
* Scarlett Clark (sgclark) (March 4) [http://scarlettgatelyclark.com/2016/kubuntu-kde-where-oh-where-have-i-been-busy-i-say/ Kubuntu: KDE: Where oh where have I been? Busy I say.]<br />
* Randa-Meetings.ch (February 23) [http://randa-meetings.ch/2016/02/23/spread-to-more-platforms-registrations-for-randa-meetings-2016-open/ Spread to more platforms – Registrations for Randa Meetings 2016 open]<br />
<br />
== Other news ==<br />
* pro-linux.de (June 16) [http://www.pro-linux.de/news/1/23662/kde-startet-spendenkampagne.html KDE startet Spendenkampagne]<br />
* Golem.de (June 13) [http://www.golem.de/news/softwareverteilung-kde-arbeitet-an-app-bundels-mit-snappy-und-flatpak-1606-121473.html KDE arbeitet an App-Bundels mit Snappy und Flatpak]<br />
<br />
= Picture collections about the meeting =<br />
<br />
* [http://www.example.org Link to pictures]<br />
<br />
= [http://en.wikipedia.org/wiki/Table_football Table Football] Tournament =<br />
Date not yet known<br/></div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2016/Work&diff=72282Sprints/Randa/2016/Work2016-06-16T12:54:14Z<p>Leinir: /* Wednesday, 15th of June */</p>
<hr />
<div>At the end of every day everybody should take some minutes to write what she or he has done or learned this day at the Randa Meetings. Just some words or a sentence or a link to his or her blog post ;-).<br />
<br />
== Sunday, 12th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Lays Rodrigues<br />
|Worked in Umbrello(GSoC) - Make UI's files to dialogs to better manage/organize the widgets<br />
|- <br />
|Kevin Funk<br />
|Discussions about KDevelop, fixing GCC 4.8 bugs in the KDevelop code base<br />
|-<br />
|Marble<br />
|Discuss open topics and decide what to focus on, new MS Windows installer for Marble 1.14.1<br />
|-<br />
|Scarlett Clark (CI)<br />
|Debug new CI yaml files.<br />
|-<br />
|Group or person<br />
|One sentence of what you've done<br />
|}<br />
<br />
== Monday, 13th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Scarlett Clark (CI)<br />
|http://scarlettgatelyclark.com/2016/debian-kde-reproducible-builds-week-3-randa-platforms-equals-busy-times/<br />
|- <br />
|Kevin Funk<br />
|Reviving KDevelop on Windows build, test-building & running Okteta for Friedrich, updating Qt Windows build to 5.6<br />
|-<br />
|Lays Rodrigues<br />
|More work on Umbrello - Creating Ui files to better manage widgets of dialogs<br />
|-<br />
|Joseph Joshua<br />
|Continued work on porting Kdenlive to Windows. Working on cross compiling MLT with all of its dependencies <br />
|-<br />
|Alexander Potashev<br />
|Porting of Kross Ruby plugin to Qt5 and Ruby 1.9+; cleanups and a bugfix in kross.git.<br />
|-<br />
|Dan Leinir Turthra Jensen<br />
|Peruse: Series support improvements, and make the application translatable<br />
|-<br />
|Group or person<br />
|One sentence of what you've done<br />
|}<br />
<br />
== Tuesday, 14th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Scarlett Clark<br />
|Deathly ill! But still managed to get several platform changes into CI DSL code.<br />
|-<br />
|Kevin Funk<br />
|Platform discussions: Hosting the KDE on Windows session + participating in the OS X one. Helping out people on Windows.<br />
|-<br />
|Group or person<br />
|One sentence of what you've done<br />
|}<br />
<br />
== Wednesday, 15th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|-<br />
|KNewStuff<br />
|Discussion about potential path ahead for KNewStuff. Path decided, details to be worked out on Saturday, but Phabricator project to organise all sorted<br />
|-<br />
|Group or person<br />
|One sentence of what you've done<br />
|}<br />
<br />
== Thursday, 16th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Group or person<br />
|One sentence of what you've done<br />
|}<br />
<br />
== Friday, 17th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Group or person<br />
|One sentence of what you've done<br />
|}<br />
<br />
== Saturday, 18th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Group or person<br />
|One sentence of what you've done<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2016&diff=72258Sprints/Randa/20162016-06-15T13:09:26Z<p>Leinir: /* Room/Group reservations */</p>
<hr />
<div>Here you find information which is important for the duration of the meetings (Sunday, 12th to Sunday, 19th of June 2016).<br />
<br />
= Important general information =<br />
<br />
Here you'll find imporant information for the time during the meeting. Such as e.g. the departure time for the trip to Zermatt. So take a look here from time to time. For general information about the Randa meetings (how to reach, grocery nearby, etc.) go [[Sprints/Randa|one page up]].<br />
<br />
* Personal information about [http://community.kde.org/Sprints/Randa/2016/Travel dates and times of arrival and departure].<br />
* Please add a short note about what you did on the [http://community.kde.org/Sprints/Randa/2016/Work work page].<br />
* [https://sprints.kde.org/sprint/301 Registration page]<br />
* Fundraiser TBD<br />
* [http://survey.kde.org/index.php Feedback questionnaire]: Randa Meetings participants, please fill in!<br />
<br />
== Topic this year ==<br />
Bring KDE software to more platforms<br />
<br />
== Bank account information ==<br />
<br />
For the people who need to send us the food and other money:<br/><br />
''It seems that from the Euro zone you need to do an international transfer instead of the standard Euro IBAN.''<br />
* IBAN: CH91 8049 6000 0097 0223 2<br />
* Address: Verein Randa Meetings, Mario Fux, Uferweg 20, 3400 Burgdorf BE, Switzerland<br />
* Currency: CHF<br />
* Make sure to select ''Cost payed by sender'' or you'll have to buy Mario a drink ;)<br />
* Bank information:<br />
** '''name:''' Raiffeisen Mischable-Matterhorn<br />
** '''SWIFT/BIC Code:''' RAIFCH22<br />
** See [http://www.swissiban.com/bdesc.php?id=3581 this website] for more.<br />
<br />
== Opening time local grocery ==<br />
<br />
* Monday to Wednesday, Friday: 7:30 to 10:00 and 16:00 to 18:00 (closed on Tuesday and Thursday afternoon)<br />
* Saturday: 7:30 to 10:00 and 14:00 to 16:00 (NEEDS TO BE VERIFIED)<br />
<br />
== Remember to bring ==<br />
This is a not-exhaustive list by going thru various emails sent<br />
* Towel<br />
* Clothes fitting the weather<br />
* Indoor shoes<br />
* Squirrel<br />
* Sleeping bag or 30 CHF for renting a thick blanket.<br />
* 15CHF per day for food (plus 5 CHF for the week: chef fee ;-)<br />
* Swiss power adapter<br />
* Hiking shoes<br />
Remember, Randa House is closer to camping than to a 5 star hotel. <br />
<br />
= Hardware to use and try =<br />
* 2 ExoPC (1:?, 1: frinring)<br />
* 1 WeTab<br />
* 1 Touch monitor 27''<br />
* 1 Projector<br />
* 1 extra laptop running Windows + complete SDK setup (emerge/Qt5+deps/KF5/MSVC2015) [kfunk]<br />
* 1x [https://support.lenovo.com/en/documents/pd100258 ThinkVision 28 - Touch 28-inch 4K2K Tegra K1 Entertainment Center]<br />
<br />
Enter your group below:<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%"<br />
|-<br />
! scope="col" | Date<br />
! scope="col" | Device 1<br />
! scope="col" | Device 2<br />
|-<br />
| Monday<br />
|<br />
|<br />
|-<br />
| Tuesday<br />
|<br />
|<br />
|-<br />
| Wednesday<br />
|<br />
|<br />
|-<br />
| Thursday<br />
|<br />
|<br />
|-<br />
| Friday<br />
|<br />
|<br />
|-<br />
| Saturday<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
= Room/Group reservations =<br />
<br />
Please add you group name to a room and time in the table below to schedule a meeting or BoF. For the room names (Africa, America, Asia, Australia & Europe) and sizes see [http://community.kde.org/File:Grundriss-new2.gif the ground plan of the building]<br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%"<br />
|-<br />
! scope="col" | Date<br />
! scope="col" | Africa<br />
! scope="col" | America<br />
! scope="col" | Asia<br />
! scope="col" | Australia<br />
! scope="col" | Europe<br />
|-<br />
| Monday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Monday: 14:00-18:00<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Monday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Tuesday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|Android Session<br />
|-<br />
| Tuesday: 14:00-18:00<br />
|KMyMoney QML<br />
|<br />
| <br />
|<br />
|2pm Windows Session, 4pm OS X<br />
|-<br />
| Tuesday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Wednesday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|10am Linux Deployment Session<br />
|-<br />
| Wednesday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|14:00 KNewStuff Session<br />
|-<br />
| Wednesday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Saturday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Saturday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|14:00 KNewStuffCore session<br />
|-<br />
| Saturday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
|}<br />
<br />
= OpenDay =<br />
<br />
None this year. Please get in contact with us if you're interested to visit us. We'll find a day that fits best.<br />
<br />
<br />
= Trip - TBD =<br />
<br />
If the weather is good enough (there is no definition at this point in time ;-) we'll do a short trip to Zermatt and (for the more sporty ones) do a short (there is a definition: 3 hours and around 15 km) hike back to Randa.<br />
<br />
<br />
= Menu plan =<br />
<br />
Everyday a new meal.<br />
*Breakfast: 7.30-9.30<br />
*Lunch: 13.00 (1pm) <br />
*Dinner: 19.00 (7pm)<br />
<br />
= Blog posts and other news about the meeting =<br />
<br />
Please add here the URLs to the blog posts about the meeting (newest on the top of the list!).<br />
<br />
== Blogs ==<br />
<br />
=== June 15 ===<br />
* Adriaan de Groot (adridg) [http://euroquis.nl/bobulate/?p=1480 Zanshin 0.4 on FreeBSD]<br />
* Dominik Haumann (dhaumann) [https://kate-editor.org/2016/06/15/kates-tabbar-gets-movable-tabs/ Kate's Tabbar gets Movable Tabs]<br />
<br />
=== June 14 ===<br />
* Lays Rodrigues (BR-Print3D) [https://laysrodriguesdev.wordpress.com/2016/06/14/randa-meetings-day-3/ Randa Meetings – Day 3]<br />
* Andreas Cord-Landwehr (CoLa) [https://cordlandwehr.wordpress.com/2016/06/14/adding-android-to-the-ci-and-many-nit-picks/ Adding Android to the CI and Many Nit-Picks]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/14/new-mac-os-x-build-documentation/ NEW MAC OS X BUILD DOCUMENTATION]<br />
* Adriaan de Groot (adridg) [http://euroquis.nl/bobulate/?p=1478 Reconciling Packaging Data (2)]<br />
* Dominik Haumann (dhaumann) [https://kate-editor.org/2016/06/14/minimap-fine-tuning/ MiniMap Fine-Tuning]<br />
* Adriaan de Groot (adridg) [http://euroquis.nl/bobulate/?p=1473 Reconciling Packaging Data]<br />
* Jean-Baptiste Mardelle (j-b-m) [https://kdenlive.org/node/9467 Kdenlive in Randa]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/14/updated-bundles-now-release-builds-and-less-frameworks/ UPDATED BUNDLES, NOW RELEASE BUILDS AND LESS FRAMEWORKS]<br />
<br />
=== June 13 ===<br />
* Lays Rodrigues (lays147) [https://laysrodriguesdev.wordpress.com/2016/06/13/randa-meetings-day-2/ Randa Meetings Day 2]<br />
* Kevin Funk (kfunk) [http://kfunk.org/2016/06/13/working-on-kdevelop-and-kde-on-windows-in-randa/ Working on KDevelop and KDE on Windows in Randa]<br />
* Scarlett Clark (sgclark) [http://scarlettgatelyclark.com/2016/debian-kde-reproducible-builds-week-3-randa-platforms-equals-busy-times/ Debian: KDE: Reproducible Builds week 3, Randa Platforms Equals Busy times!]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/13/new-get-it-page-build-it-split-out/ NEW “GET IT” PAGE & “BUILD IT” SPLIT OUT]<br />
* Dominik Haumann (dhaumann) [https://kate-editor.org/2016/06/13/working-on-kate-in-randa/ WORKING ON KATE IN RANDA]<br />
* Dan Leinir Turthra Jensen (leinir) [http://kath-leinir.blogspot.ch/2016/06/randa-meetings-2016-is-go.html Randa Meetings 2016 is go!]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/13/katekwrite-application-bundle-update/ KATE/KWRITE APPLICATION BUNDLE UPDATE]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/13/first-day-in-randa/ FIRST DAY IN RANDA]<br />
<br />
=== June 12 ===<br />
*Lays Rodrigues (lays147) [https://laysrodriguesdev.wordpress.com/2016/06/12/randa-meetings-first-day/ Randa Meetings First Day]<br />
<br />
=== Pre Sprint ===<br />
* Aleix Pol [http://www.proli.net/2016/06/10/kde-on-flatpak-in-randa/ KDE on Flatpak]<br />
* Christoph Cullmann (cullmann) (June 11) [https://kate-editor.org/2016/06/11/randa-meeting-2016-tomorrow-on-tour/ RANDA MEETING 2016 – TOMORROW ON TOUR ;=)]<br />
* Lays Rodriguezs (BR-Print3D) (May 28) [https://laysrodriguesdev.wordpress.com/2016/05/28/coding-at-lakademy/ Coding at Lakademy]<br />
* Scarlett Clark (sgclark) (March 4) [http://scarlettgatelyclark.com/2016/kubuntu-kde-where-oh-where-have-i-been-busy-i-say/ Kubuntu: KDE: Where oh where have I been? Busy I say.]<br />
* Randa-Meetings.ch (February 23) [http://randa-meetings.ch/2016/02/23/spread-to-more-platforms-registrations-for-randa-meetings-2016-open/ Spread to more platforms – Registrations for Randa Meetings 2016 open]<br />
<br />
== Other news ==<br />
<br />
* Golem.de (June 13) [http://www.golem.de/news/softwareverteilung-kde-arbeitet-an-app-bundels-mit-snappy-und-flatpak-1606-121473.html KDE arbeitet an App-Bundels mit Snappy und Flatpak]<br />
<br />
= Picture collections about the meeting =<br />
<br />
* [http://www.example.org Link to pictures]<br />
<br />
= [http://en.wikipedia.org/wiki/Table_football Table Football] Tournament =<br />
Date not yet known<br/></div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2016&diff=72238Sprints/Randa/20162016-06-14T18:21:28Z<p>Leinir: /* Room/Group reservations */</p>
<hr />
<div>Here you find information which is important for the duration of the meetings (Sunday, 12th to Sunday, 19th of June 2016).<br />
<br />
= Important general information =<br />
<br />
Here you'll find imporant information for the time during the meeting. Such as e.g. the departure time for the trip to Zermatt. So take a look here from time to time. For general information about the Randa meetings (how to reach, grocery nearby, etc.) go [[Sprints/Randa|one page up]].<br />
<br />
* Personal information about [http://community.kde.org/Sprints/Randa/2016/Travel dates and times of arrival and departure].<br />
* Please add a short note about what you did on the [http://community.kde.org/Sprints/Randa/2016/Work work page].<br />
* [https://sprints.kde.org/sprint/301 Registration page]<br />
* Fundraiser TBD<br />
* [http://survey.kde.org/index.php Feedback questionnaire]: Randa Meetings participants, please fill in!<br />
<br />
== Topic this year ==<br />
Bring KDE software to more platforms<br />
<br />
== Bank account information ==<br />
<br />
For the people who need to send us the food and other money:<br/><br />
''It seems that from the Euro zone you need to do an international transfer instead of the standard Euro IBAN.''<br />
* IBAN: CH91 8049 6000 0097 0223 2<br />
* Address: Verein Randa Meetings, Mario Fux, Uferweg 20, 3400 Burgdorf BE, Switzerland<br />
* Currency: CHF<br />
* Make sure to select ''Cost payed by sender'' or you'll have to buy Mario a drink ;)<br />
* Bank information:<br />
** '''name:''' Raiffeisen Mischable-Matterhorn<br />
** '''SWIFT/BIC Code:''' RAIFCH22<br />
** See [http://www.swissiban.com/bdesc.php?id=3581 this website] for more.<br />
<br />
== Opening time local grocery ==<br />
<br />
* Monday to Wednesday, Friday: 7:30 to 10:00 and 16:00 to 18:00 (closed on Tuesday and Thursday afternoon)<br />
* Saturday: 7:30 to 10:00 and 14:00 to 16:00 (NEEDS TO BE VERIFIED)<br />
<br />
== Remember to bring ==<br />
This is a not-exhaustive list by going thru various emails sent<br />
* Towel<br />
* Clothes fitting the weather<br />
* Indoor shoes<br />
* Squirrel<br />
* Sleeping bag or 30 CHF for renting a thick blanket.<br />
* 15CHF per day for food (plus 5 CHF for the week: chef fee ;-)<br />
* Swiss power adapter<br />
* Hiking shoes<br />
Remember, Randa House is closer to camping than to a 5 star hotel. <br />
<br />
= Hardware to use and try =<br />
* 2 ExoPC (1:?, 1: frinring)<br />
* 1 WeTab<br />
* 1 Touch monitor 27''<br />
* 1 Projector<br />
* 1 extra laptop running Windows + complete SDK setup (emerge/Qt5+deps/KF5/MSVC2015) [kfunk]<br />
* 1x [https://support.lenovo.com/en/documents/pd100258 ThinkVision 28 - Touch 28-inch 4K2K Tegra K1 Entertainment Center]<br />
<br />
Enter your group below:<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%"<br />
|-<br />
! scope="col" | Date<br />
! scope="col" | Device 1<br />
! scope="col" | Device 2<br />
|-<br />
| Monday<br />
|<br />
|<br />
|-<br />
| Tuesday<br />
|<br />
|<br />
|-<br />
| Wednesday<br />
|<br />
|<br />
|-<br />
| Thursday<br />
|<br />
|<br />
|-<br />
| Friday<br />
|<br />
|<br />
|-<br />
| Saturday<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
= Room/Group reservations =<br />
<br />
Please add you group name to a room and time in the table below to schedule a meeting or BoF. For the room names (Africa, America, Asia, Australia & Europe) and sizes see [http://community.kde.org/File:Grundriss-new2.gif the ground plan of the building]<br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%"<br />
|-<br />
! scope="col" | Date<br />
! scope="col" | Africa<br />
! scope="col" | America<br />
! scope="col" | Asia<br />
! scope="col" | Australia<br />
! scope="col" | Europe<br />
|-<br />
| Monday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Monday: 14:00-18:00<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Monday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Tuesday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|Android Session<br />
|-<br />
| Tuesday: 14:00-18:00<br />
|KMyMoney QML<br />
|<br />
| <br />
|<br />
|2pm Windows Session, 4pm OS X<br />
|-<br />
| Tuesday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Wednesday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|10am Linux Deployment Session<br />
|-<br />
| Wednesday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|14:00 KNewStuff Session<br />
|-<br />
| Wednesday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Saturday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Saturday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Saturday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
|}<br />
<br />
= OpenDay =<br />
<br />
None this year. Please get in contact with us if you're interested to visit us. We'll find a day that fits best.<br />
<br />
<br />
= Trip - TBD =<br />
<br />
If the weather is good enough (there is no definition at this point in time ;-) we'll do a short trip to Zermatt and (for the more sporty ones) do a short (there is a definition: 3 hours and around 15 km) hike back to Randa.<br />
<br />
<br />
= Menu plan =<br />
<br />
Everyday a new meal.<br />
*Breakfast: 7.30-9.30<br />
*Lunch: 13.00 (1pm) <br />
*Dinner: 19.00 (7pm)<br />
<br />
= Blog posts and other news about the meeting =<br />
<br />
Please add here the URLs to the blog posts about the meeting (newest on the top of the list!).<br />
<br />
== Blogs ==<br />
<br />
=== June 14 ===<br />
* Adriaan de Groot (adridg) [http://euroquis.nl/bobulate/?p=1473 Reconciling Packaging Data]<br />
* Jean-Baptiste Mardelle (j-b-m) [https://kdenlive.org/node/9467 Kdenlive in Randa]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/14/updated-bundles-now-release-builds-and-less-frameworks/ UPDATED BUNDLES, NOW RELEASE BUILDS AND LESS FRAMEWORKS]<br />
* Dominik Haumann (dhaumann) [https://kate-editor.org/2016/06/14/minimap-fine-tuning/ MiniMap Fine-Tuning]<br />
<br />
=== June 13 ===<br />
* Lays Rodrigues (lays147) [https://laysrodriguesdev.wordpress.com/2016/06/13/randa-meetings-day-2/ Randa Meetings Day 2]<br />
* Kevin Funk (kfunk) [http://kfunk.org/2016/06/13/working-on-kdevelop-and-kde-on-windows-in-randa/ Working on KDevelop and KDE on Windows in Randa]<br />
* Scarlett Clark (sgclark) [http://scarlettgatelyclark.com/2016/debian-kde-reproducible-builds-week-3-randa-platforms-equals-busy-times/ Debian: KDE: Reproducible Builds week 3, Randa Platforms Equals Busy times!]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/13/new-get-it-page-build-it-split-out/ NEW “GET IT” PAGE & “BUILD IT” SPLIT OUT]<br />
* Dominik Haumann (dhaumann) [https://kate-editor.org/2016/06/13/working-on-kate-in-randa/ WORKING ON KATE IN RANDA]<br />
* Dan Leinir Turthra Jensen (leinir) [http://kath-leinir.blogspot.ch/2016/06/randa-meetings-2016-is-go.html Randa Meetings 2016 is go!]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/13/katekwrite-application-bundle-update/ KATE/KWRITE APPLICATION BUNDLE UPDATE]<br />
* Christoph Cullmann (cullmann) [https://kate-editor.org/2016/06/13/first-day-in-randa/ FIRST DAY IN RANDA]<br />
<br />
=== June 12 ===<br />
*Lays Rodrigues (lays147) [https://laysrodriguesdev.wordpress.com/2016/06/12/randa-meetings-first-day/ Randa Meetings First Day]<br />
<br />
=== Pre Sprint ===<br />
* Aleix Pol [http://www.proli.net/2016/06/10/kde-on-flatpak-in-randa/ KDE on Flatpak]<br />
* Christoph Cullmann (cullmann) (June 11) [https://kate-editor.org/2016/06/11/randa-meeting-2016-tomorrow-on-tour/ RANDA MEETING 2016 – TOMORROW ON TOUR ;=)]<br />
* Lays Rodriguezs (BR-Print3D) (May 28) [https://laysrodriguesdev.wordpress.com/2016/05/28/coding-at-lakademy/ Coding at Lakademy]<br />
* Scarlett Clark (sgclark) (March 4) [http://scarlettgatelyclark.com/2016/kubuntu-kde-where-oh-where-have-i-been-busy-i-say/ Kubuntu: KDE: Where oh where have I been? Busy I say.]<br />
* Randa-Meetings.ch (February 23) [http://randa-meetings.ch/2016/02/23/spread-to-more-platforms-registrations-for-randa-meetings-2016-open/ Spread to more platforms – Registrations for Randa Meetings 2016 open]<br />
<br />
== Other news ==<br />
<br />
* Golem.de (June 13) [http://www.golem.de/news/softwareverteilung-kde-arbeitet-an-app-bundels-mit-snappy-und-flatpak-1606-121473.html KDE arbeitet an App-Bundels mit Snappy und Flatpak]<br />
<br />
= Picture collections about the meeting =<br />
<br />
* [http://www.example.org Link to pictures]<br />
<br />
= [http://en.wikipedia.org/wiki/Table_football Table Football] Tournament =<br />
Date not yet known<br/></div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2016/Work&diff=72215Sprints/Randa/2016/Work2016-06-14T08:11:41Z<p>Leinir: /* Monday, 13th of June */</p>
<hr />
<div>At the end of every day everybody should take some minutes to write what she or he has done or learned this day at the Randa Meetings. Just some words or a sentence or a link to his or her blog post ;-).<br />
<br />
== Sunday, 12th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Lays Rodrigues<br />
|Worked in Umbrello(GSoC) - Make UI's files to dialogs to better manage/organize the widgets<br />
|- <br />
|Kevin Funk<br />
|Discussions about KDevelop, fixing GCC 4.8 bugs in the KDevelop code base<br />
|-<br />
|Marble<br />
|Discuss open topics and decide what to focus on, new MS Windows installer for Marble 1.14.1<br />
|-<br />
|Scarlett Clark (CI)<br />
|Debug new CI yaml files.<br />
|-<br />
|Group or person<br />
|One sentence of what you've done<br />
|}<br />
<br />
== Monday, 13th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Scarlett Clark (CI)<br />
|http://scarlettgatelyclark.com/2016/debian-kde-reproducible-builds-week-3-randa-platforms-equals-busy-times/<br />
|- <br />
|Lays Rodrigues<br />
|More work on Umbrello - Creating Ui files to better manage widgets of dialogs<br />
|-<br />
|Alexander Potashev<br />
|Porting of Kross Ruby plugin to Qt5 and Ruby 1.9+; cleanups and a bugfix in kross.git.<br />
|-<br />
|Dan Leinir Turthra Jensen<br />
|Peruse: Series support improvements, and make the application translatable<br />
|-<br />
|Group or person<br />
|One sentence of what you've done<br />
|}<br />
<br />
== Tuesday, 14th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Group or person<br />
|One sentence of what you've done<br />
|}<br />
<br />
== Wednesday, 15th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Group or person<br />
|One sentence of what you've done<br />
|}<br />
<br />
== Thursday, 16th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Group or person<br />
|One sentence of what you've done<br />
|}<br />
<br />
== Friday, 17th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Group or person<br />
|One sentence of what you've done<br />
|}<br />
<br />
== Saturday, 18th of June ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Group or person<br />
|One sentence of what you've done<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2016&diff=72196Sprints/Randa/20162016-06-13T12:10:31Z<p>Leinir: /* Blogs */</p>
<hr />
<div>Here you find information which is important for the duration of the meetings (Sunday, 12th to Sunday, 19th of June 2016).<br />
<br />
= Important general information =<br />
<br />
Here you'll find imporant information for the time during the meeting. Such as e.g. the departure time for the trip to Zermatt. So take a look here from time to time. For general information about the Randa meetings (how to reach, grocery nearby, etc.) go [[Sprints/Randa|one page up]].<br />
<br />
* Personal information about [http://community.kde.org/Sprints/Randa/2016/Travel dates and times of arrival and departure].<br />
* Please add a short note about what you did on the [http://community.kde.org/Sprints/Randa/2016/Work work page].<br />
* [https://sprints.kde.org/sprint/301 Registration page]<br />
* Fundraiser TBD<br />
* [http://survey.kde.org/index.php Feedback questionnaire]: Randa Meetings participants, please fill in!<br />
<br />
== Topic this year ==<br />
Bring KDE software to more platforms<br />
<br />
== Bank account information ==<br />
<br />
For the people who need to send us the food and other money:<br/><br />
''It seems that from the Euro zone you need to do an international transfer instead of the standard Euro IBAN.''<br />
* IBAN: CH91 8049 6000 0097 0223 2<br />
* Address: Verein Randa Meetings, Mario Fux, Uferweg 20, 3400 Burgdorf BE, Switzerland<br />
* Currency: CHF<br />
* Make sure to select ''Cost payed by sender'' or you'll have to buy Mario a drink ;)<br />
* Bank information:<br />
** '''name:''' Raiffeisen Mischable-Matterhorn<br />
** '''SWIFT/BIC Code:''' RAIFCH22<br />
** See [http://www.swissiban.com/bdesc.php?id=3581 this website] for more.<br />
<br />
== Opening time local grocery ==<br />
<br />
* Monday to Wednesday, Friday: 7:30 to 10:00 and 16:00 to 18:00 (closed on Tuesday and Thursday afternoon)<br />
* Saturday: 7:30 to 10:00 and 14:00 to 16:00 (NEEDS TO BE VERIFIED)<br />
<br />
== Remember to bring ==<br />
This is a not-exhaustive list by going thru various emails sent<br />
* Towel<br />
* Clothes fitting the weather<br />
* Indoor shoes<br />
* Squirrel<br />
* Sleeping bag or 30 CHF for renting a thick blanket.<br />
* 15 CHF per day for food (plus 5 CHF for the week: chef fee ;-)<br />
* Swiss power adapter<br />
* Hiking shoes<br />
Remember, Randa House is closer to camping than to a 5 star hotel. <br />
<br />
= Hardware to use and try =<br />
* 2 ExoPC (1:?, 1: frinring)<br />
* 1 WeTab<br />
* 1 Touch monitor 27''<br />
* 1 Projector<br />
* 1 extra laptop running Windows + complete SDK setup (emerge/Qt5+deps/KF5/MSVC2015) [kfunk]<br />
* 1x [https://support.lenovo.com/en/documents/pd100258 ThinkVision 28 - Touch 28-inch 4K2K Tegra K1 Entertainment Center]<br />
<br />
Enter your group below:<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%"<br />
|-<br />
! scope="col" | Date<br />
! scope="col" | Device 1<br />
! scope="col" | Device 2<br />
|-<br />
| Monday<br />
|<br />
|<br />
|-<br />
| Tuesday<br />
|<br />
|<br />
|-<br />
| Wednesday<br />
|<br />
|<br />
|-<br />
| Thursday<br />
|<br />
|<br />
|-<br />
| Friday<br />
|<br />
|<br />
|-<br />
| Saturday<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
= Room/Group reservations =<br />
<br />
Please add you group name to a room and time in the table below to schedule a meeting or BoF. For the room names (Africa, America, Asia, Australia & Europe) and sizes see [http://community.kde.org/File:Grundriss-new2.gif the ground plan of the building]<br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%"<br />
|-<br />
! scope="col" | Date<br />
! scope="col" | Africa<br />
! scope="col" | America<br />
! scope="col" | Asia<br />
! scope="col" | Australia<br />
! scope="col" | Europe<br />
|-<br />
| Monday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Monday: 14:00-18:00<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
| Monday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Tuesday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Tuesday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Tuesday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Wednesday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Wednesday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Wednesday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Saturday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Saturday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Saturday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
|}<br />
<br />
= OpenDay =<br />
<br />
None this year. Please get in contact with us if you're interested to visit us. We'll find a day that fits best.<br />
<br />
<br />
= Trip - TBD =<br />
<br />
If the weather is good enough (there is no definition at this point in time ;-) we'll do a short trip to Zermatt and (for the more sporty ones) do a short (there is a definition: 3 hours and around 15 km) hike back to Randa.<br />
<br />
<br />
= Menu plan =<br />
<br />
Everyday a new meal.<br />
*Breakfast: 7.30-9.30<br />
*Lunch: 13.00 (1pm) <br />
*Dinner: 19.00 (7pm)<br />
<br />
= Blog posts and other news about the meeting =<br />
<br />
Please add here the URLs to the blog posts about the meeting (newest on the top of the list!).<br />
<br />
== Blogs ==<br />
<br />
* Dan Leinir Turthra Jensen (leinir) (June 13) [http://kath-leinir.blogspot.ch/2016/06/randa-meetings-2016-is-go.html Randa Meetings 2016 is go!]<br />
* Christoph Cullmann (cullmann) (June 13) [https://kate-editor.org/2016/06/13/katekwrite-application-bundle-update/ KATE/KWRITE APPLICATION BUNDLE UPDATE]<br />
* Christoph Cullmann (cullmann) (June 13) [https://kate-editor.org/2016/06/13/first-day-in-randa/ FIRST DAY IN RANDA]<br />
*Lays Rodrigues(Umbrello)(June 12)[https://laysrodriguesdev.wordpress.com/2016/06/12/randa-meetings-first-day/ Randa Meetings First Day]<br />
* Christoph Cullmann (cullmann) (June 11) [https://kate-editor.org/2016/06/11/randa-meeting-2016-tomorrow-on-tour/ RANDA MEETING 2016 – TOMORROW ON TOUR ;=)]<br />
* Lays Rodriguezs(BR-Print3D) (May 28) [https://laysrodriguesdev.wordpress.com/2016/05/28/coding-at-lakademy/ <br />
Coding at Lakademy]<br />
* Scarlett Clark (sgclark) (March 4) [http://scarlettgatelyclark.com/2016/kubuntu-kde-where-oh-where-have-i-been-busy-i-say/ Kubuntu: KDE: Where oh where have I been? Busy I say.]<br />
* Randa-Meetings.ch (February 23) [http://randa-meetings.ch/2016/02/23/spread-to-more-platforms-registrations-for-randa-meetings-2016-open/ Spread to more platforms – Registrations for Randa Meetings 2016 open]<br />
* Firstname Lastname (nickname) (date) [http://www.example.org Title of blog post]<br />
<br />
== Other news ==<br />
<br />
* Webpage (date) [http://www.example.org Title of the story]<br />
<br />
= Picture collections about the meeting =<br />
<br />
* [http://www.example.org Link to pictures]<br />
<br />
= [http://en.wikipedia.org/wiki/Table_football Table Football] Tournament =<br />
Date not yet known<br/></div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2015/Work&diff=44251Sprints/Randa/2015/Work2015-09-12T14:13:23Z<p>Leinir: /* Friday, 11th of September */</p>
<hr />
<div>At the end of every day everybody should take some minutes to write what she or he has done or learned this day at the Randa Meetings. Just some words or a sentence or a link to his or her blog post ;-).<br />
<br />
== Sunday, 6th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Worked on capabilities, reviewed some patches from the community in the backlog, bug fixing and unit testing.<br />
|}<br />
<br />
== Monday, 7th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Worked on capabilities, reviewed some patches from the community in the backlog, bug fixing and unit testing.<br />
|-<br />
|Gemini<br />
|Ported the QtQuick2 components for Calligra and added to the KF5 based master branch<br />
|}<br />
<br />
== Tuesday, 8th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|More work on capabilities, so they are seamless. Optimized the TCP usage as we were accused of bringing down the network. Vastly improved Remote Keyboard on Android.<br />
|-<br />
|Gemini<br />
|Initial port of Calligra Gemini to Qt5 and QtQuick2<br />
|}<br />
<br />
== Wednesday, 9th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
| Implemented SMS answering plugin. Made improvements to the network usage in Android as well. Finished the Material design KDE Connect app for Android.<br />
|- <br />
|digiKam<br />
| Review of existing problems. Plan tasks to be done during the Randa Meeting to get ready for the digikam-5.0.0-beta1 release. Work towards removal of KDELibs4Support from KIPI Plugins.<br />
|-<br />
|Gemini<br />
|Further porting work and cleanup of Calligra Gemini and QtQuick2 components port<br />
|}<br />
<br />
== Thursday, 10th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Public Beta of the new Android app released ( https://albertvaka.wordpress.com/2015/09/10/kde-connect-2nd-anniversary-and-beta-program ) plus started the review proces to move KDE Connect out of Playground, into Extragear. Added Telepathy integration, for sending and receiving SMS from the KTP desktop client. Some integration work to run KDE Connect on Windows, more work is needed.<br />
|- <br />
|digiKam<br />
| Work towards removal of KDELibs4Support from KIPI Plugins. Move some code from KIPI Plugins (metadataedit and acquireimages) into digiKam core. Factorization of KIPI plugins' source code.<br />
|-<br />
|Gemini<br />
|Achieve first switches and restore basic functionality for Calligra Gemini port (after working out a hard to fix issue with QQuickView)<br />
|}<br />
<br />
== Friday, 11th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Closed lots of bugs reported in the open beta. (Thanks for the quick turnaround! :) Implemented "Find my phone" plugin. Implemented a proof of concept to open tel:// links in KDE Connect, that will end up in libpurpose. Got KDE Connect core and some of the plugins working on Windows.<br />
|- <br />
|digiKam<br />
| Work towards removal of KDELibs4Support from KIPI Plugins. Factorization of KIPI plugins' source code: login dialogs. Fixed Imageshack authentication.<br />
|-<br />
|Gemini<br />
|Initial work on pulling out Gemini functionality into a separate library, to allow for others to make use of this<br />
|}<br />
<br />
== Saturday, 12th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Implemented Run Command plugin, for people to be able to create their own commands activated via KDE Connect. Released stable version of the Android app to the stores and created tarball for the desktop app. <br />
|- <br />
|digiKam<br />
| KDELibs4Support completely removed from KIPI Plugins. (To be continued...)<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2015/Work&diff=44250Sprints/Randa/2015/Work2015-09-12T14:12:13Z<p>Leinir: /* Thursday, 10th of September */</p>
<hr />
<div>At the end of every day everybody should take some minutes to write what she or he has done or learned this day at the Randa Meetings. Just some words or a sentence or a link to his or her blog post ;-).<br />
<br />
== Sunday, 6th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Worked on capabilities, reviewed some patches from the community in the backlog, bug fixing and unit testing.<br />
|}<br />
<br />
== Monday, 7th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Worked on capabilities, reviewed some patches from the community in the backlog, bug fixing and unit testing.<br />
|-<br />
|Gemini<br />
|Ported the QtQuick2 components for Calligra and added to the KF5 based master branch<br />
|}<br />
<br />
== Tuesday, 8th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|More work on capabilities, so they are seamless. Optimized the TCP usage as we were accused of bringing down the network. Vastly improved Remote Keyboard on Android.<br />
|-<br />
|Gemini<br />
|Initial port of Calligra Gemini to Qt5 and QtQuick2<br />
|}<br />
<br />
== Wednesday, 9th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
| Implemented SMS answering plugin. Made improvements to the network usage in Android as well. Finished the Material design KDE Connect app for Android.<br />
|- <br />
|digiKam<br />
| Review of existing problems. Plan tasks to be done during the Randa Meeting to get ready for the digikam-5.0.0-beta1 release. Work towards removal of KDELibs4Support from KIPI Plugins.<br />
|-<br />
|Gemini<br />
|Further porting work and cleanup of Calligra Gemini and QtQuick2 components port<br />
|}<br />
<br />
== Thursday, 10th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Public Beta of the new Android app released ( https://albertvaka.wordpress.com/2015/09/10/kde-connect-2nd-anniversary-and-beta-program ) plus started the review proces to move KDE Connect out of Playground, into Extragear. Added Telepathy integration, for sending and receiving SMS from the KTP desktop client. Some integration work to run KDE Connect on Windows, more work is needed.<br />
|- <br />
|digiKam<br />
| Work towards removal of KDELibs4Support from KIPI Plugins. Move some code from KIPI Plugins (metadataedit and acquireimages) into digiKam core. Factorization of KIPI plugins' source code.<br />
|-<br />
|Gemini<br />
|Achieve first switches and restore basic functionality for Calligra Gemini port (after working out a hard to fix issue with QQuickView)<br />
|}<br />
<br />
== Friday, 11th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Closed lots of bugs reported in the open beta. (Thanks for the quick turnaround! :) Implemented "Find my phone" plugin. Implemented a proof of concept to open tel:// links in KDE Connect, that will end up in libpurpose. Got KDE Connect core and some of the plugins working on Windows.<br />
|- <br />
|digiKam<br />
| Work towards removal of KDELibs4Support from KIPI Plugins. Factorization of KIPI plugins' source code: login dialogs. Fixed Imageshack authentication.<br />
|}<br />
<br />
== Saturday, 12th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Implemented Run Command plugin, for people to be able to create their own commands activated via KDE Connect. Released stable version of the Android app to the stores and created tarball for the desktop app. <br />
|- <br />
|digiKam<br />
| KDELibs4Support completely removed from KIPI Plugins. (To be continued...)<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2015/Work&diff=44247Sprints/Randa/2015/Work2015-09-12T14:09:55Z<p>Leinir: /* Wednesday, 9th of September */</p>
<hr />
<div>At the end of every day everybody should take some minutes to write what she or he has done or learned this day at the Randa Meetings. Just some words or a sentence or a link to his or her blog post ;-).<br />
<br />
== Sunday, 6th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Worked on capabilities, reviewed some patches from the community in the backlog, bug fixing and unit testing.<br />
|}<br />
<br />
== Monday, 7th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Worked on capabilities, reviewed some patches from the community in the backlog, bug fixing and unit testing.<br />
|-<br />
|Gemini<br />
|Ported the QtQuick2 components for Calligra and added to the KF5 based master branch<br />
|}<br />
<br />
== Tuesday, 8th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|More work on capabilities, so they are seamless. Optimized the TCP usage as we were accused of bringing down the network. Vastly improved Remote Keyboard on Android.<br />
|-<br />
|Gemini<br />
|Initial port of Calligra Gemini to Qt5 and QtQuick2<br />
|}<br />
<br />
== Wednesday, 9th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
| Implemented SMS answering plugin. Made improvements to the network usage in Android as well. Finished the Material design KDE Connect app for Android.<br />
|- <br />
|digiKam<br />
| Review of existing problems. Plan tasks to be done during the Randa Meeting to get ready for the digikam-5.0.0-beta1 release. Work on removal of dependency on KDELibs4Support.<br />
|-<br />
|Gemini<br />
|Further porting work and cleanup of Calligra Gemini and QtQuick2 components port<br />
|}<br />
<br />
== Thursday, 10th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Public Beta of the new Android app released ( https://albertvaka.wordpress.com/2015/09/10/kde-connect-2nd-anniversary-and-beta-program ) plus started the review proces to move KDE Connect out of Playground, into Extragear. Added Telepathy integration, for sending and receiving SMS from the KTP desktop client. Some integration work to run KDE Connect on Windows, more work is needed.<br />
|- <br />
|digiKam<br />
| Work towards removal of KDELibs4Support from KIPI Plugins. Move some code from KIPI Plugins (metadataedit and acquireimages) into digiKam core. Factorization of KIPI plugins' source code.<br />
|}<br />
<br />
== Friday, 11th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Closed lots of bugs reported in the open beta. (Thanks for the quick turnaround! :) Implemented "Find my phone" plugin. Implemented a proof of concept to open tel:// links in KDE Connect, that will end up in libpurpose. Got KDE Connect core and some of the plugins working on Windows.<br />
|- <br />
|digiKam<br />
| Work towards removal of KDELibs4Support from KIPI Plugins. Factorization of KIPI plugins' source code: login dialogs. Fixed Imageshack authentication.<br />
|}<br />
<br />
== Saturday, 12th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Implemented Run Command plugin, for people to be able to create their own commands activated via KDE Connect. Released stable version of the Android app to the stores and created tarball for the desktop app. <br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2015/Work&diff=44246Sprints/Randa/2015/Work2015-09-12T14:09:24Z<p>Leinir: /* Tuesday, 8th of September */</p>
<hr />
<div>At the end of every day everybody should take some minutes to write what she or he has done or learned this day at the Randa Meetings. Just some words or a sentence or a link to his or her blog post ;-).<br />
<br />
== Sunday, 6th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Worked on capabilities, reviewed some patches from the community in the backlog, bug fixing and unit testing.<br />
|}<br />
<br />
== Monday, 7th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Worked on capabilities, reviewed some patches from the community in the backlog, bug fixing and unit testing.<br />
|-<br />
|Gemini<br />
|Ported the QtQuick2 components for Calligra and added to the KF5 based master branch<br />
|}<br />
<br />
== Tuesday, 8th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|More work on capabilities, so they are seamless. Optimized the TCP usage as we were accused of bringing down the network. Vastly improved Remote Keyboard on Android.<br />
|-<br />
|Gemini<br />
|Initial port of Calligra Gemini to Qt5 and QtQuick2<br />
|}<br />
<br />
== Wednesday, 9th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
| Implemented SMS answering plugin. Made improvements to the network usage in Android as well. Finished the Material design KDE Connect app for Android.<br />
|- <br />
|digiKam<br />
| Review of existing problems. Plan tasks to be done during the Randa Meeting to get ready for the digikam-5.0.0-beta1 release. Work on removal of dependency on KDELibs4Support.<br />
|}<br />
<br />
== Thursday, 10th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Public Beta of the new Android app released ( https://albertvaka.wordpress.com/2015/09/10/kde-connect-2nd-anniversary-and-beta-program ) plus started the review proces to move KDE Connect out of Playground, into Extragear. Added Telepathy integration, for sending and receiving SMS from the KTP desktop client. Some integration work to run KDE Connect on Windows, more work is needed.<br />
|- <br />
|digiKam<br />
| Work towards removal of KDELibs4Support from KIPI Plugins. Move some code from KIPI Plugins (metadataedit and acquireimages) into digiKam core. Factorization of KIPI plugins' source code.<br />
|}<br />
<br />
== Friday, 11th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Closed lots of bugs reported in the open beta. (Thanks for the quick turnaround! :) Implemented "Find my phone" plugin. Implemented a proof of concept to open tel:// links in KDE Connect, that will end up in libpurpose. Got KDE Connect core and some of the plugins working on Windows.<br />
|- <br />
|digiKam<br />
| Work towards removal of KDELibs4Support from KIPI Plugins. Factorization of KIPI plugins' source code: login dialogs. Fixed Imageshack authentication.<br />
|}<br />
<br />
== Saturday, 12th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Implemented Run Command plugin, for people to be able to create their own commands activated via KDE Connect. Released stable version of the Android app to the stores and created tarball for the desktop app. <br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2015/Work&diff=44245Sprints/Randa/2015/Work2015-09-12T14:07:59Z<p>Leinir: /* Monday, 7th of September */</p>
<hr />
<div>At the end of every day everybody should take some minutes to write what she or he has done or learned this day at the Randa Meetings. Just some words or a sentence or a link to his or her blog post ;-).<br />
<br />
== Sunday, 6th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Worked on capabilities, reviewed some patches from the community in the backlog, bug fixing and unit testing.<br />
|}<br />
<br />
== Monday, 7th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Worked on capabilities, reviewed some patches from the community in the backlog, bug fixing and unit testing.<br />
|-<br />
|Gemini<br />
|Ported the QtQuick2 components for Calligra and added to the KF5 based master branch<br />
|}<br />
<br />
== Tuesday, 8th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|More work on capabilities, so they are seamless. Optimized the TCP usage as we were accused of bringing down the network. Vastly improved Remote Keyboard on Android.<br />
|}<br />
<br />
== Wednesday, 9th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
| Implemented SMS answering plugin. Made improvements to the network usage in Android as well. Finished the Material design KDE Connect app for Android.<br />
|- <br />
|digiKam<br />
| Review of existing problems. Plan tasks to be done during the Randa Meeting to get ready for the digikam-5.0.0-beta1 release. Work on removal of dependency on KDELibs4Support.<br />
|}<br />
<br />
== Thursday, 10th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Public Beta of the new Android app released ( https://albertvaka.wordpress.com/2015/09/10/kde-connect-2nd-anniversary-and-beta-program ) plus started the review proces to move KDE Connect out of Playground, into Extragear. Added Telepathy integration, for sending and receiving SMS from the KTP desktop client. Some integration work to run KDE Connect on Windows, more work is needed.<br />
|- <br />
|digiKam<br />
| Work towards removal of KDELibs4Support from KIPI Plugins. Move some code from KIPI Plugins (metadataedit and acquireimages) into digiKam core. Factorization of KIPI plugins' source code.<br />
|}<br />
<br />
== Friday, 11th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Closed lots of bugs reported in the open beta. (Thanks for the quick turnaround! :) Implemented "Find my phone" plugin. Implemented a proof of concept to open tel:// links in KDE Connect, that will end up in libpurpose. Got KDE Connect core and some of the plugins working on Windows.<br />
|- <br />
|digiKam<br />
| Work towards removal of KDELibs4Support from KIPI Plugins. Factorization of KIPI plugins' source code: login dialogs. Fixed Imageshack authentication.<br />
|}<br />
<br />
== Saturday, 12th of September ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|KDE Connect<br />
|Implemented Run Command plugin, for people to be able to create their own commands activated via KDE Connect. Released stable version of the Android app to the stores and created tarball for the desktop app. <br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2015&diff=44051Sprints/Randa/20152015-08-26T11:48:16Z<p>Leinir: /* Blogs */ Add my blog entry</p>
<hr />
<div>Here you find information which is important for the duration of the meetings (Sunday, 6th to Sunday, 13th of September 2015).<br />
<br />
= Important general information =<br />
<br />
Here you'll find imporant information for the time during the meeting. Such as e.g. the departure time for the trip to Zermatt. So take a look here from time to time. For general information about the Randa meetings (how to reach, grocery nearby, etc.) go [[Sprints/Randa|one page up]].<br />
<br />
* Personal information about [http://community.kde.org/Sprints/Randa/2015/Travel dates and times of arrival and departure].<br />
* Please add a short note about what you did on the [http://community.kde.org/Sprints/Randa/2015/Work work page].<br />
* [https://www.kde.org/fundraisers/kdesprints2015 Fundraiser] for the meetings this year<br />
* [http://survey.kde.org/index.php Feedback questionnaire]: Randa Meetings participants, please fill in!<br />
<br />
== Groups this year ==<br />
* Multimedia<br />
* PIM<br />
* Touch&Mobile<br />
* KDE Connect<br />
* QMLweb<br />
* digiKam<br />
<br />
== Bank account information ==<br />
<br />
For the people who need to send us the food and other money:<br/><br />
''It seems that from the Euro zone you need to do an international transfer instead of the standard Euro IBAN.''<br />
* IBAN: CH91 8049 6000 0097 0223 2<br />
* Address: Verein Randa Meetings, Mario Fux, Uferweg 20, 3400 Burgdorf BE, Switzerland<br />
* Currency: CHF<br />
* Make sure to select ''Cost payed by sender'' or you'll have to buy Mario a drink ;)<br />
* Bank information:<br />
** '''name:''' Raiffeisen Mischable-Matterhorn<br />
** '''SWIFT/BIC Code:''' RAIFCH22<br />
** See [http://www.swissiban.com/bdesc.php?id=3581 this website] for more.<br />
<br />
== Opening time local grocery ==<br />
<br />
* Monday to Wednesday, Friday: 7:30 to 10:00 and 16:00 to 18:00 (closed on Tuesday and Thursday afternoon)<br />
* Saturday: 7:30 to 10:00 and 14:00 to 16:00<br />
<br />
= Hardware to use and try =<br />
* 1 ExoPC<br />
* 1 WeTab<br />
* 1 Touch monitor 27''<br />
* 1 Projector<br />
* and more TBD<br />
<br />
= Room/Group reservations =<br />
<br />
Please add you group name to a room and time in the table below to schedule a meeting or BoF. For the room names (Africa, America, Asia, Australia & Europe) and sizes see [http://community.kde.org/File:Grundriss-new2.gif the ground plan of the building]<br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%"<br />
|-<br />
! scope="col" | Date<br />
! scope="col" | Africa<br />
! scope="col" | America<br />
! scope="col" | Asia<br />
! scope="col" | Australia<br />
! scope="col" | Europe<br />
|-<br />
| Monday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Monday: 14:00-18:00<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
| Monday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Tuesday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Tuesday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Tuesday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Wednesday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Wednesday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Wednesday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Thursday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Friday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Saturday: 08:00-12:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Saturday: 14:00-18:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
| Saturday: 20:00-24:00<br />
|<br />
|<br />
| <br />
|<br />
|<br />
|-<br />
|}<br />
<br />
= OpenDay =<br />
<br />
None this year. Please get in contact with us if you're interested to visit us. We'll find a day that fits best.<br />
<br />
<br />
= Trip - Date not yet known =<br />
<br />
If the weather is good enough (there is no definition at this point in time ;-) we'll do a short trip to Zermatt and (for the more sporty ones) do a short (there is a definition: 3 hours and around 15 km) hike back to Randa.<br />
<br />
<br />
= Menu plan =<br />
<br />
Menu of last year. Needs to be changed.<br />
<br />
{| cellspacing="1" cellpadding="1" border="1" width="100%"<br />
|-<br />
! scope="col" | Date<br />
! scope="col" | Breakfast (8:30-10:30)<br />
! scope="col" | Lunch (13:00-14:00)<br />
! scope="col" | Dinner (19:00-20:00)<br />
|-<br />
| Saturday, 9th of August<br />
| Day of Arrival<br />
| Day of Arrival<br />
| Penne Bolognese or Napoli (V); Dessert: "Chocolaty Welcome"<br />
|-<br />
| Sunday, 10th of August<br />
| Breakfast buffet<br />
| Chicken-breast or Tofu (V), creamy risotto; Dessert: "Cold Surprise"<br />
| Salad buffet with garlic bread<br />
|-<br />
| Monday, 11th of August<br />
| Breakfast buffet<br />
| Meatloaf or Corn slices "Walliser Art" (V), pasta & vegetables; Dessert: "Beaten Chocolate" <br />
| Cholera*<br />
|-<br />
| Tuesday, 12th of August<br />
| Breakfast buffet<br />
| Loin of pork or Quorn (V), mashed potatoes & vegetables; Dessert: "Crashed Sweets"<br />
| Bündner Barley Soup with sausages or with cheese (V); Dessert: fruit slices<br />
|-<br />
| Wednesday, 13th of August (OpenDay)<br />
| Breakfast buffet<br />
| Beef Goulash or filled tomatoes (V), Spätzle & vegetables; Dessert: "Hidden Apples"<br />
| Raclette - suisse classics - a must<br />
|-<br />
| Thursday, 14th of August<br />
| Breakfast buffet<br />
| Lasagne with meat or vegetables (V); Dessert: "All in One"<br />
| Buffet potpourri<br />
|-<br />
| Friday, 15th of August<br />
| Breakfast buffet<br />
| Day of departure<br />
| Day of departure<br />
|-<br />
|}<br />
<br />
Vegetarian dishes are daily regarded and marked with "(V)"!<br />
(*No, this is not a dangerous disease but [http://www.myswitzerland.com/en/interests/food-and-wine/typically-swiss-recipes/recipes-betty-bossi/cholera.html something tasty].)<br />
<br />
= Blog posts and other news about the meeting =<br />
<br />
Please add here the URLs to the blog posts about the meeting (newest on the top of the list!).<br />
<br />
== Blogs ==<br />
<br />
* Dan Leinir Turthra Jensen (leinir) (August 26th) [http://kath-leinir.blogspot.co.uk/2015/08/gemini-at-randa-2015.html Gemini at Randa 2015]<br />
* Mohamed Anwer (tootis) (August 22) [https://mohamedanwer.wordpress.com/2015/08/22/digikam-gsoc-15-the-summary/ digiKam | GSoC 15 the summary]<br />
* Shourya Singh Gupta (shouryasgupta) (August 22) [http://support-kde-randa.blogspot.ch/2015/08/support-randa-meetings-2015.html Support Randa Meetings 2015]<br />
* Martin Gräßlin (August 21) [http://blog.martin-graesslin.com/blog/2015/08/thoughts-on-vulkan-in-kwin/ Thoughts on Vulkan in KWin]<br />
* Valorie Zimmerman (valorie) (August 21) [http://linuxgrandma.blogspot.com/2015/08/upon-returning-home-from-akademy.html Upon returning home from Akademy: thoughts]<br />
* Martin Gräßlin (August 20) [http://blog.martin-graesslin.com/blog/2015/08/layered-compositing/ Layered compositing]<br />
* Harald Sitter (apachelogger) (August 20) [https://apachelog.wordpress.com/2015/08/20/a-touch-of-plasma-in-the-mountains/ A Touch of Plasma in the Mountains]<br />
* Valorie Zimmerman (valorie) (August 20) [http://linuxgrandma.blogspot.com/2015/08/weeeee-kde-is-sponsoring-randa-meetings.html Support Randa 2015]<br />
* Martin Gräßlin (August 19) [http://blog.martin-graesslin.com/blog/2015/08/a-qt-platform-abstraction-plugin-for-kwin/ A Qt Platform Abstraction plugin for KWin]<br />
* Heiko Tietze (August 18) [http://user-prompt.com/usability-at-the-kde-sprint-in-randa/ Usability at the KDE Sprint in Randa]<br />
* Vincent Pinon (vpinon) (August 18) [https://kdenlive.org/node/9442 Kdenlive 15.08: 4 years of maturation, and how to help Free Software to live ]<br />
* Aleix Pol (apol) (August 17) [http://www.proli.net/2015/08/17/sprinting-kde-connect/ Sprinting KDE Connect]<br />
* David Edmundson (d_ed) (August 16) [http://blog.davidedmundson.co.uk/node/100 Powered By Swiss Cheese - My Plans For Randa]<br />
* Bruno Coudoin (bdoin) (August 14) [http://gcompris.net/news-en.html#2015-08-12 GCompris goes to KDE Randa Meeting 2015]<br />
* Mario Fux (unormal) (August 14) [http://blogs.fsfe.org/mario/?p=336 A (or the) secret about the Randa Meetings]<br />
* Daniel Vrátil (dvratil) (August 13) [http://www.dvratil.cz/2015/08/kde-pim-in-randa/ KDE PIM in Randa]<br />
* Patrick von Reth (TheOneRing) (August 13) [http://the2ring.blogspot.com/2015/08/incubating-snorenotify.html Incubating Snorenotify]<br />
* Gilles Caulier (cgilles) (August 11) [https://www.digikam.org/node/742 digiKam at Randa Meeting 2015]<br />
* Michael Bohlender (mbohlender) (August 7) [https://mbohlender.wordpress.com/2015/08/07/mobile-pim-at-randa/ Mobile PIM at Randa]<br />
* Valentin Rusu (valir) (August 6) [https://barlog.rusu.info/valentin/blog/?p=442 Goodbye Akademy 2015, see you Randa 2015]<br />
* Mario Fux (unormal) (August 4) [http://randa-meetings.ch/2015/08/04/randa-meetings-2015-the-countdown-begins/ Randa Meetings 2015 – The countdown begins]<br />
* Bruno Coudoin (bdoin) (August 3) [https://gcompris.wordpress.com/2015/08/03/gcompris-at-akademy-2015/ GCompris at Akademy 2015]<br />
* Firstname Lastname (nickname) (date) [http://www.example.org Title of blog post]<br />
<br />
== Other news ==<br />
<br />
* Dot story (August 22): [https://dot.kde.org/2015/08/22/another-kde-success-story-incubator-part-3 Another KDE success story - the Incubator - Part 3]<br />
* Krita News (August 22): [https://krita.org/item/2015-kde-sprints-fundraiser/ 2015 KDE Sprints Fundraiser]<br />
* Dot story (August 20): [https://dot.kde.org/2015/08/20/another-kde-success-story-incubator-part-2 Another KDE success story - the Incubator - Part 2]<br />
* Linuxfr.org (August 18): [http://linuxfr.org/news/kde-organise-son-sprint-annuel-dans-les-alpes-et-a-besoin-d-un-coup-de-pouce KDE organise son Sprint annuel dans les Alpes... et a besoin d’un coup de pouce !]<br />
* Dot story (August 17): [https://dot.kde.org/2015/08/17/another-kde-success-story-incubator-part-1 Another KDE success story - the Incubator - Part 1]<br />
* KDE-Brasil (August 16): [https://br.kde.org/node/305 Você pode ajudar a melhorar ainda mais as tecnologias do KDE!]<br />
* Dot story (August 16): [https://dot.kde.org/2015/08/16/you-can-help-making-kde-technologies-even-better You can help making KDE technologies even better!]<br />
* Golem.de (August 12): [http://www.golem.de/news/open-source-kde-sammelt-spenden-fuer-plasma-mobile-1508-115716.html KDE sammelt Spenden für Plasma Mobile]<br />
* Pro-Linux.de (August 11): [http://www.pro-linux.de/news/1/22620/kde-startet-spendenkampagne.html KDE startet Spendenkampagne]<br />
* Dot story (August 4): [https://dot.kde.org/2015/08/04/randa-bring-touch-kde Randa - Bring Touch to KDE]<br />
<br />
= Picture collections about the meeting =<br />
<br />
* [http://www.example.org Link to pictures]<br />
<br />
= [http://en.wikipedia.org/wiki/Table_football Table Football] Tournament =<br />
Date not yet known<br/> <br />
<br />
=== Teams ===<br />
Only room for 8 teams of 2 people, sign up fast!.<br/><br />
(add a phone number and IRC nickname and join the #randa channel)<br />
<br />
# Team 1<br />
# Team 2<br />
# Team 3<br />
# Team n<br />
<br />
=== Rules ===<br />
* KO: you lose, you're out.<br />
* First to 5 points win<br />
* Always use the same ball<br />
* Toss for ball at start<br />
* On score losers get ball</div>Leinirhttps://community.kde.org/index.php?title=Akademy/2015/Photos&diff=43430Akademy/2015/Photos2015-07-27T07:57:27Z<p>Leinir: Adding leinir's photo album</p>
<hr />
<div>*Jonathan Riddell: https://www.flickr.com/photos/jriddell/sets/72157655875336760<br />
* Ovidiu-FLorin BOGDAN: https://apollo.geekaliens.com:8001/index.php/apps/gallery/public/C1bHu2SfBNEzbXp<br />
* Alex Merry: https://www.flickr.com/photos/40864317@N08/sets/72157655913592459<br />
* Dan Leinir Turthra Jensen: https://www.flickr.com/gp/49031477@N00/256eW8</div>Leinirhttps://community.kde.org/index.php?title=Akademy/2015/Monday&diff=43234Akademy/2015/Monday2015-07-20T19:05:14Z<p>Leinir: /* Lab 1.3w - 27 July */</p>
<hr />
<div>= BoF sessions on Monday, July 27th 2015 =<br />
<br />
'''All rooms have either a blackboard or a whiteboard, wireless network availability and projectors.''' If you need any other equipment, please send an email to akademy-team@kde.org.<br />Please put your name and email address in the Host/Notes section. There is no length limitation; text will wrap. <br />
<br />
<br />
'''BoF Wrap-up at 18:00'''<br /><br />
Please join the BoF wrap-up session this evening. Another opportunity for communication. Share outcomes and plans, cross-pollinate, attract attention to your project.<br />
Please select someone from your BoF to give a summary—topic, what was discussed and decided, what's next, resources desired.<br />
<br />
The Akademy team might reasign BoFs based on operational needs<br />
=== Lab 0.1w - 27 July ===<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Lab 0.1w <br />
!<br />
! Capacity: 36 people<br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| Plasma General Topics<br />
| Sebastian Kügler<br />
|-<br />
| 11:30 <br />
|Plasma General Topics<br />
|<br />
|-<br />
| 12:30<br />
|Plasma General Topics<br />
|<br />
|-<br />
| 13:30<br />
| Lunch<br />
| <br />
|-<br />
| 15:00 <br />
| Plasma Mobile Design<br />
| Jens Reuterberg<br />
|-<br />
| 16:00<br />
| Plasma Mobile Design<br />
| <br />
|-<br />
| 17:00 <br />
| Plasma Mobile Design<br />
| <br />
|}<br />
<br />
=== Lab 0.5w - 27 July ===<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Lab 0.5w <br />
!<br />
! Capacity: 20 people<br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
|[[Akademy/2015/AllBoF/KanbanGame|Kanban Game]]<br />
| ervin<br />
|-<br />
| 11:30 <br />
| [[Akademy/2015/AllBoF/KanbanGame|Kanban Game]]<br />
| ervin<br />
|-<br />
| 12:30<br />
|FLA signing and future planning<br />
|silverhook<br />
|-<br />
| 13:30<br />
| Lunch<br />
| <br />
|-<br />
| 15:00 <br />
| KDE France BoF<br />
| ervin<br />
|-<br />
| 16:00<br />
| Future Frameworks Releases BoF<br />
| ervin<br />
|-<br />
| 17:00 <br />
| <br />
| <br />
|}<br />
<br />
=== Lab 1.3w - 27 July ===<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Lab 1.3w <br />
!<br />
! Capacity: 32 people<br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" | [[Akademy/2015/Monday/KDE_l10n_and_i18n|KDE l10n and i18n]]<br />
| width="400pt" | tsdgeos<br />
|-<br />
| 10:30<br />
| Teaching Qt with KDE<br />
| Franklin <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
| Shashlik Progression<br />
| leinir<br />
|-<br />
| 13:30<br />
| Lunch<br />
| <br />
|-<br />
| 15:00 <br />
| <br />
| <br />
|-<br />
| 16:00<br />
| <br />
| <br />
|-<br />
| 17:00 <br />
| <br />
| <br />
|}<br />
<br />
=== Lab 1.5w - 27 July ===<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Lab 1.5w <br />
!<br />
! Capacity: 32 people<br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |VDG UI Design Open Session<br />
| width="400pt" |Jens Reuterberg, Thomas Pfeiffer, Andrew Lake. Stop by with any UI design questions, help out with Plasma 5.4 design tasks, or just to learn about UI design. <br />
|-<br />
| 10:30<br />
|VDG UI Design Open Session<br />
| Jens Reuterberg, Thomas Pfeiffer, Andrew Lake. Stop by with any UI design questions, help out with Plasma 5.4 design tasks, or just to learn about UI design. <br />
|-<br />
| 11:30 <br />
|VDG UI Design Open Session<br />
|Jens Reuterberg, Thomas Pfeiffer, Andrew Lake. Stop by with any UI design questions, help out with Plasma 5.4 design tasks, or just to learn about UI design. <br />
|-<br />
| 12:30<br />
|VDG UI Design Open Session<br />
|Jens Reuterberg, Thomas Pfeiffer, Andrew Lake. Stop by with any UI design questions, help out with Plasma 5.4 design tasks, or just to learn about UI design. <br />
|-<br />
| 13:30<br />
| Lunch<br />
| <br />
|-<br />
| 15:00 <br />
| VDG UI Design Open Session<br />
| Jens Reuterberg, Thomas Pfeiffer, Andrew Lake. Stop by with any UI design questions, help out with Plasma 5.4 design tasks, or just to learn about UI design. <br />
|-<br />
| 16:00<br />
| VDG UI Design Open Session<br />
| Jens Reuterberg, Thomas Pfeiffer, Andrew Lake. Stop by with any UI design questions, help out with Plasma 5.4 design tasks, or just to learn about UI design. <br />
|-<br />
| 17:00 <br />
| VDG UI Design Open Session<br />
| Jens Reuterberg, Thomas Pfeiffer, Andrew Lake. Stop by with any UI design questions, help out with Plasma 5.4 design tasks, or just to learn about UI design. <br />
|}<br />
<br />
=== Room 2.0a - 27 July ===<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 2.0a <br />
!<br />
! Capacity: 60 people<br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
|<br />
|<br />
|-<br />
| 13:30<br />
| Lunch<br />
| <br />
|-<br />
| 15:00 <br />
| Evolving KDE<br />
| Lydia Pintscher<br />
|-<br />
| 16:00<br />
| Evolving KDE<br />
| Lydia Pintscher<br />
|-<br />
| 17:00 <br />
| Evolving KDE<br />
| Lydia Pintscher<br />
|}<br />
<br />
=== Room 2.0b - 27 July ===<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 2.0b <br />
!<br />
! Capacity: 60 people<br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
|<br />
|<br />
|-<br />
| 13:30<br />
| Lunch<br />
| <br />
|-<br />
| 15:00 <br />
| <br />
| <br />
|-<br />
| 16:00<br />
| <br />
| <br />
|-<br />
| 17:00 <br />
| <br />
| <br />
|}<br />
=== Room 2.5w - 27 July ===<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 2.5w <br />
!<br />
! Capacity: 40 people<br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
|<br />
|<br />
|-<br />
| 13:30<br />
| Lunch<br />
| <br />
|-<br />
| 15:00 <br />
| <br />
| <br />
|-<br />
| 16:00<br />
| <br />
| <br />
|-<br />
| 17:00 <br />
| <br />
| <br />
|}<br />
=== Room 2.6w - 27 July ===<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 2.6w <br />
!<br />
! Capacity: 40 people<br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
|<br />
|<br />
|-<br />
| 13:30<br />
| Lunch<br />
| <br />
|-<br />
| 15:00 <br />
| <br />
| <br />
|-<br />
| 16:00<br />
| <br />
| <br />
|-<br />
| 17:00 <br />
| <br />
| <br />
|}<br />
=== Room 2.7w - 27 July ===<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 2.7w <br />
!<br />
! Capacity: 57 people<br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 9:30<br />
| width="200pt" |<br />
| width="400pt" |<br />
|-<br />
| 10:30<br />
| <br />
| <br />
|-<br />
| 11:30 <br />
|<br />
|<br />
|-<br />
| 12:30<br />
|<br />
|<br />
|-<br />
| 13:30<br />
| Lunch<br />
| <br />
|-<br />
| 15:00 <br />
| <br />
| <br />
|-<br />
| 16:00<br />
| <br />
| <br />
|-<br />
| 17:00 <br />
| <br />
| <br />
|}<br />
<br />
=== Room 3.2 - 27 July ===<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Room 3.2<br />
!<br />
! Capacity: 132 people<br />
|-<br />
! Time <br />
! Subject <br />
! Host/Notes<br />
|-<br />
| width="100pt" | 12:30<br />
| width="200pt" | Workshop: Integrating native features with your Qt mobile app<br />
| width="400pt" | Kai Uwe Broulik<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=GSoC/2015/Ideas&diff=41653GSoC/2015/Ideas2015-02-19T11:31:56Z<p>Leinir: /* Plasma and Gluon */</p>
<hr />
<div>{{Note|Work in progress, proposals here are often copied from the GSoC 2014 list}}<br />
[[File:GoogleSummer 2015logo.jpg |200px|thumb|right|GSoC 2015 logo]]<br />
See also: [[../../|GSoc Instructions]], [[../../2014/Ideas|Last year ideas]]<br />
<br />
== Guidelines ==<br />
<br />
=== Information for Students ===<br />
<br />
These ideas were contributed by our developers and users. They are sometimes vague or incomplete. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at.<br />
<br />
Being accepted as a Google Summer of Code student is quite competitive. Accepted students typically have thoroughly researched the technologies of their proposed project and have been in frequent contact with potential mentors. Simply copying and pasting an idea here will not work. On the other hand, creating a completely new idea without first consulting potential mentors is unlikely to work out.<br />
<br />
When writing your proposal or asking for help from the general KDE community don't assume people are familiar with the ideas here. KDE is really big!<br />
<br />
If there is no specific contact given you can ask questions on the general KDE development list kde-devel@kde.org. See [http://www.kde.org/mailinglists/ the KDE mailing lists page] for information on available mailing lists and how to subscribe.<br />
<br />
=== Adding a Proposal ===<br />
<br />
{{Note|Follow the template of other proposals!}}<br />
<br />
==== Project: ====<br />
<br />
'''Brief explanation:'''<br />
<br />
'''Expected results:'''<br />
<br />
'''Knowledge Prerequisite:'''<br />
<br />
'''Mentor:'''<br />
<br />
When adding an idea to this section, please try to include the following data:<br />
<br />
:*if the application is not widely known, a description of what it does and where its code lives<br />
:*a brief explanation<br />
:*the expected results<br />
:*pre-requisites for working on your project<br />
:*if applicable, links to more information or discussions<br />
:*mailing list or IRC channel for your application/library/module<br />
:*your name and email address for contact (if you're willing to be a mentor)<br />
<br />
If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first.<br />
<br />
<br />
==Ideas==<br />
<br />
===Your Own Idea ===<br />
<br />
==== Project: Something that you're totally excited about ====<br />
<br />
'''Brief explanation:''' Do you have an awesome idea you want to work on with KDE but that is not among the ideas below? That's cool. We love that! But please do us a favor: Get in touch with a mentor early on and make sure your project is realistic and within the scope of KDE. That will spare you and us a lot of frustration.<br />
<br />
'''Expected results:''' Something you and KDE loves<br />
<br />
'''Knowledge Prerequisite:''' Probably C++ and Qt but depends on your project<br />
<br />
'''Mentor:''' Try to see who in KDE is interested in what you want to work on and approach them. If you are unsure you can always ask in #kde-soc on Freenode IRC.<br />
<br />
===Plasma===<br />
<br />
==== Project: Port various KDE4 Plasmoids to Plasma 5 ====<br />
<br />
'''Brief explanation:''' When we ported from Plasma 4 to Plasma 5 some useful Plasmoids ended up not being initially ported. We want the more important existing applets to continue to run which . Students should select a few Plasmoids which they deem useful for their proposal along with some innovative ideas for improvements. Students should show knowledge of the level of work related. <br />
<br />
'''Expected results:''' A few fully working plasmoids, polished and better than before.<br />
<br />
'''Knowledge Prerequisite:''' QML skills. Ideally some Plasmoid experience<br />
<br />
'''Mentor:''' Sebastian Kugler with help of the Plasma team.<br />
<br />
==== Project: Port KSystemLog to use journald as a backend ====<br />
<br />
'''Brief explanation:''' KSystemLog is a tool for viewing log files. This has slowly started to fail as log files moved in various distributions. Journald provides a common interface to query programatically system and user logs which will fix the main issue. Applications should impress me with their ideas utilising the available features. <br />
<br />
'''Expected results:''' A ported to frameworks journald powered log viewer. <br />
<br />
'''Knowledge Prerequisite:''' C++, Qt. <br />
<br />
'''Mentor:''' David Edmundson with help of the Plasma team.<br />
<br />
=== Plasma and Gluon ===<br />
<br />
==== Project: Extend gamingFreedom.org framework to be more generic ====<br />
<br />
'''Brief explanation:''' Over the last couple of years, the gamingFreedom.org website and server side components have been created, which implement Open Collaboration Services (OCS) in a generic and reusable form. We are now at a point where it would make sense to attempt to use this for further purposes, rather than only for gamingFreedom.org. Specifically, a new implementation of the server component employed for hosting Plasma related content is needed, and a website for presenting this content on the web.<br />
<br />
'''Expected results:''' A new website based on gamingFreedom.org's OCS client libraries, and a server implementation for hosting Plasma content.<br />
<br />
'''Knowledge Prerequisite:''' PHP for the client and server code<br />
<br />
'''Mentor:''' Claudio Desideri and Dan Leinir Turthra Jensen with help of the Plasma team.<br />
<br />
=== Kdenlive ===<br />
<br />
Kdenlive is an intuitive and powerful multi-track video editor, including most recent video technologies. Our software is completely free, as defined by the GNU foundation. Using Kdenlive is investing in a community driven project, which aims to establish relationships between people in order to built the best video tools.<br />
<br />
* [http://www.kdenlive.org Kdenlive project web site]<br />
* [http://community.kde.org/Kdenlive Kdenlive wiki]<br />
* [https://mail.kde.org/mailman/listinfo/kdenlive Mailinglist]<br />
* [http://webchat.freenode.net/?channels=kdenlive #kdenlive IRC channel on Freenode]<br />
<br />
==== Project: Add support for new Animation capabilities ====<br />
<br />
'''Brief explanation:''' MLT, the media frameworks we use for rendering, has recently added a new [http://mltframework.blogspot.com/2013/06/v090-released-with-new-property.html property animation] to its objects. This allows much simpler, smoother and more general animations than the traditional keyframes technology. We then need new widgets to edit these properties, and eventually evolve our on-monitor interactions.<br />
<br />
'''Expected results:''' At the end of the project, we should be able to add and graphically adjust these animation parameters through controls in the effects stack panel, and bonus on the monitor.<br />
<br />
'''Knowledge Prerequisite:''' In the end you will assemble QtWidgets and interact with MLT data through C++. So you should be at ease with C++ and Qt (no need to be an expert), and have a look to the MLT manual page about animation.<br />
<br />
'''Mentor:''' Vincent Pinon with help of the Kdenlive team.<br />
<br />
==== Project: Redesign titler using WebVFX ====<br />
<br />
'''Brief explanation:''' Our titler, the tool we use to add text and drawing objects over the video, relies on a home made module added to the MLT framework. Our module is limited in features, quite slow to render, and demands work to maintain. MLT has since then been plugged into WebVFX engine, which provides infinite possibilities through web technologies, and it is certainly more robust. The goal is then to port our titler to this engine, then maybe evolve the interface to offer new possibilities.<br />
<br />
'''Expected results:''' At the end of the project, the titler should rely only on MLT WebVFX module. Bonus we should be able to add and easily edit more objects types.<br />
<br />
'''Knowledge Prerequisite:''' First step is to translate our XML to Web formats inside the C++ code, so you should understand those dialects. For the UI rework, you would then work with Qt, in either C++ or QML.<br />
<br />
'''Mentor:''' Vincent Pinon with help of the Kdenlive team.<br />
<br />
==== Project: add import/export filters for video editors exchange formats ====<br />
<br />
'''Brief explanation:''' To reduce the barrier to switch to Kdenlive, users should be able to import and export with commercial editing softwares (at least partially). Some scripts already exist to crudely parse EDL or AAF formats, the goal is to do it cleanly integrated in Kdenlive.<br />
<br />
'''Expected results:''' At the end of the project, we should be able to exchange projects with one or more commercial tools. Effects and transitions will probably be limited, but timeline construction should be transferable.<br />
<br />
'''Knowledge Prerequisite:''' The work will consist in manipulating XML data with Qt (C++), so you should understand those dialects.<br />
<br />
'''Mentor:''' Vincent Pinon with help of the Kdenlive team.<br />
<br />
==== Project: make Kdenlive work on Windows and OSX ====<br />
<br />
'''Brief explanation:''' All the frameworks Kdenlive relies on are working on other platforms, and Kdenlive used run on those long time ago. The goal here is to setup build environments on one or two other OS's, and fix the things that prevent Kdenlive to work.<br />
<br />
'''Expected results:''' At the end of the project, Kdenlive should work reliably on one or two commercial OS's.<br />
<br />
'''Knowledge Prerequisite:''' Setting up and running builds, fixing things in C++, CMake, dependencies.<br />
<br />
'''Mentor:''' Vincent Pinon with help of the Kdenlive and KDE porting teams.<br />
<br />
=== Amarok ===<br />
<br />
Amarok is a Music player that helps you organize and rediscover your music. <br />
<br />
* [http://amarok.kde.org Amarok project web site]<br />
* [http://community.kde.org/Amarok Amarok wiki]<br />
* [https://mail.kde.org/mailman/listinfo/amarok-devel Mailinglist]<br />
* [https://plus.google.com/+amarok Google+ page]<br />
* [http://webchat.freenode.net/?channels=amarok #amarok IRC channel on Freenode]<br />
<br />
==== Project: Port Amarok to Qt5/Kf5/Plasma5 ====<br />
<br />
'''Brief explanation:''' Currently Amarok still depends on kdelibs 4.x and Qt4.<br />
<br />
'''Expected results:''' Amarok should compile with Qt 5.x, kdelibs4 dependencies should be replaced with kf5. Port most existing plasma widgets of the Context View to Plasma 5 (at least the most important should be ported). The default system themes should apply to Amarok flawlessly. A very important part of this project is testing the port and adapting the unit tests.<br />
<br />
'''Knowledge Prerequisite:''' good knowledge of C++/Qt, ideally being familiar with kf 5 and Plasma 5. The student should have some basic knowledge of the Amarok project and its functions as well as its architecture. All relevant information about Amarok, Qt5, kf5 and Plasma 5 can be found online, every suitable applicant should be able to find this documentation on their own.<br />
<br />
'''Mentor:''' To be determined. All discussions about the project should be held on the mailinglist and/or on IRC<br />
<br />
===digiKam===<br />
<br />
digiKam is an advanced digital photo management application for Linux, Windows, and Mac-OSX.<br />
<br />
* [http://www.digikam.org digiKam project web site]<br />
* [http://www.exiv2.org Exiv2 project web site]<br />
* [https://techbase.kde.org/Projects/Digikam/CodingSprint2014 digiKam port to KF5 status]<br />
* [https://mail.kde.org/mailman/listinfo/digikam-devel Mailinglist]<br />
* [https://plus.google.com/+digikam Google+ page]<br />
* [http://webchat.freenode.net/?channels=digikam #digikam IRC channel on Freenode]<br />
<br />
==== Project: Re-write database KIO-slaves as pure Qt5 using multithreading ====<br />
<br />
'''Brief explanation:''' Originally, KIO-Slaves have been implemented to run database queries in a separated process to prevent problem with SQlite. Since SQlite support re-entrancy and queries from separated threads, digiKam KIO-slaves used to process complex and long database queries can be re-written as core implementation using Qt thread API. This will improve digiKam availability in time when system is updated in low-level, and permit to adjust finely CPU cores assigned to database process.<br />
<br />
'''Dependencies:''' : digiKam core from "framework" branch (KF5) <br />
<br />
'''Links:''' [https://www.sqlite.org/threadsafe.html Using Sqlite in multi-threaded application], [https://bugs.kde.org/show_bug.cgi?id=146557 Bug #146557]<br />
<br />
'''Knowledge Prerequisite:''' C/C++, Qt, database, multi-threading<br />
<br />
'''Expected results:''' Identify all parts of digiKam core which query database through KIO-slaves mechanism, factorize code in same interface and write a multi-threaded wrapper to run SQlite queries. Write test code to check quickly if database core implementation changes don't affect wrapper functionality. Note : digiKam use internally URL + XML formating to pass data to KIO-slaves and this not be changed.<br />
<br />
'''Difficulty:''' high<br />
<br />
'''Lead Mentor:''' Gilles Caulier <caulier dot gilles at gmail dot com><br />
<br />
==== Project: Advanced Metadata HUB ====<br />
<br />
'''Brief explanation:''' digiKam has already some options to manage workflow between image metadata and database, through the setup/metadata configuration panel. The goal of this project is to write a more advance setup to control finely the most important metadata field in order to read from image and populate database and vis versa. The list of metadata to drive must be easily extensible and configurable. Also, the metadata workflow to synchronize image with database must be more flexible and must provide a way to synchronize files at end of digiKam session and not only in real time (typical case : editing image tags to write in images). <br />
<br />
'''Dependencies:''' : digiKam core and libkexiv2 from "framework" branch (KF5) <br />
<br />
'''Links:''' [https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&component=Metadata&list_id=1205997&product=digikam&query_format=advanced&short_desc=HUB&short_desc_type=allwordssubstr Bugs list from bugzilla]<br />
<br />
'''Knowledge Prerequisite:''' C/C++, Qt, database, multi-threading<br />
<br />
'''Expected results:''' Create metadata hub widget for settings panel, adjust current hub and image scanner implementations, add test code.<br />
<br />
'''Difficulty:''' high<br />
<br />
'''Lead Mentor:''' Gilles Caulier <caulier dot gilles at gmail dot com><br />
<br />
==== Project: Add WebP and WebM support ====<br />
<br />
'''Brief explanation:''' WebP/WebM is new wavelets based image/video format from Google, based on RIFF/MKV container. This format become more popular on the Web and both can be used through an open-source library. We need to support these formats as editable in digiKam (WebP) and manageable by database mechanism through metadata (WebP and WebM).<br />
<br />
'''Dependencies:''' : digiKam core and libkexiv2 from "framework" branch (KF5), Exiv2 library<br />
<br />
'''Links:''' [http://en.wikipedia.org/wiki/WebM WebM format], [http://en.wikipedia.org/wiki/WebP WebP format]<br />
<br />
'''Knowledge Prerequisite:''' C/C++, Qt, Metadata<br />
<br />
'''Expected results:''' Patch Exiv2 library to support both formats in read/write meta-data mode and add optional WebP support in digiKam core to be able to edit images (read/write image contents in 16 bits color depth). Write test code to check new functionality in time.<br />
<br />
'''Difficulty:''' high<br />
<br />
'''Mentors:''' Gilles Caulier <caulier dot gilles at gmail dot com> + Someone from Exiv2 team<br />
<br />
==== Project: Factorize and port to KF5 all web service Import/Export KIPI tools ====<br />
<br />
'''Brief explanation:''' All tools dedicated to import or export items from KIPI host applications to web services as Flickr, GDrive, Dropbox, Facebook, Picasa, etc... need to be factored and ported to KF5/Qt5. Factorization include to make common widgets (settings, GUI layout, rules, etc), and background processing to prevents duplicate code. Also, in order to reduce KIPI host application time loading, the number of tools must be limited. Tools must be grouped by categories, as Social Networks, Cloud Service, Photo Hosting, etc...<br />
<br />
'''Dependencies:''' : digiKam KIPI interface, KIPI Plugins <br />
<br />
'''Bugzilla entries:''' [https://bugs.kde.org/show_bug.cgi?id=221704 221704]<br />
<br />
'''Knowledge Prerequisite:''' C/C++, Qt/KDE, GUI<br />
<br />
'''Expected results:''' KIPI web services tools ported to KF5 and running with digiKam 5.0.0.<br />
<br />
'''Difficulty:''' high<br />
<br />
'''Lead Mentor:''' Gilles Caulier <caulier dot gilles at gmail dot com><br />
<br />
===Marble===<br />
Marble is a virtual globe and world atlas — your swiss army knife for maps. Find your way and explore the world!<br />
<br />
* [http://marble.kde.org/ Marble project website]<br />
* [https://mail.kde.org/mailman/listinfo/marble-devel Mailinglist]<br />
* [Marble Google+ page]<br />
* [http://webchat.freenode.net/?channels=marble #marble IRC channel on Freenode]<br />
<br />
(projects to appear here. Please ask in [http://webchat.freenode.net/?channels=marble #marble] in the meantime)<br />
<br />
=== KStars ===<br />
<br />
KStars is a very powerful tool for anyone interested in astronomy. It is part of the KDE Edu suite.<br />
<br />
==== Project: Ekos Scheduler ====<br />
<br />
'''Brief explanation:''' [http://www.indilib.org/about/ekos.html Ekos] is an advanced astrophotography tool for Linux. It utilizes [http://www.indilib.org INDI] for device control. With Ekos, the user can use the telescope, CCD, and other equipment to perform Astrophotography tasks. However, the user has to be present to configure the options and to command the actions to perform all the astrophotography related tasks, and hence a scheduler is required to automate observations to be constrained within certain limitations such as required minimum angular separation from the moon, whether conditions...etc. Furthermore, the observations should be triggered when certain conditions are met such as observation time, object's altitude...etc. The prospective student is expected to develop a ''Simple'' [http://indilib.org/forum/general/560-simple-ekos-schedular.html Ekos scheduler] to trigger observation runs when certain conditions are met and when the limitations are required.<br />
<br />
'''Expected results:''' Simple scheduler to automate astrophotography runs based on some conditions and within user-configurable limitations.<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt, INDI<br />
<br />
'''Mentors:''' Jasem Mutlaq (IRC: knro)<br />
<br />
The student will need to:<br />
<br />
* Look at the relevant code, and propose a tractable plan for implementing some of the improvements within the GSoC timeframe.<br />
* Implement some of the improvements, producing production-ready code that can be included in the next release of KStars after GSoC 2015.<br />
<br />
==== Project: Constellation art ====<br />
<br />
'''Brief explanation:''' KStars currently draws constellation lines, names, and boundaries, but constellation art is missing. The student is expected to study KStars API and develop a new SkyComponent to superimpose the constellation artwork unto the sky map while re-working other components in KStars to support this. The structure must support multiple sky cultures. The artwork itself must be available under a permissible license. New constellation artwork should be available for download using the KNewStuff framework. The user should be able to select the sky culture.<br />
<br />
'''Expected results:''' High quality artwork for Western constellations in addition to one non-western constellation artwork that can be switched on/off in the sky map.<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt<br />
<br />
'''Mentors:''' Jasem Mutlaq (IRC: knro)<br />
<br />
The student will need to:<br />
<br />
* Look at the relevant code, and propose a tractable plan for implementing some of the improvements within the GSoC timeframe.<br />
* Implement some of the improvements, producing production-ready code that can be included in the next release of KStars after GSoC 2015.<br />
<br />
==== Project: Fix our deep-sky data handling ====<br />
<br />
'''Brief explanation:''' Currently, KStars handles data from deep-sky object catalogues in an SQLite database. While this is working well, there are some more features we would like to have, and some that should be implemented in order to sanitize the deep-sky data handling, such as automatic cross-referencing of deep-sky objects across catalogs, organizing deep-sky data better in the database etc using Hierarchical Triangular Mesh, etc.<br />
<br />
More details here: http://techbase.kde.org/Projects/Edu/KStars/Better_deep-sky_handling<br />
<br />
'''Expected results:''' Some, or all of the improvements to deep-sky handling suggested above (or maybe even your own suggestions), implemented completely in solid, release-worthy code.<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt, understanding of astronomical catalogues, some experience with data structures.<br />
<br />
'''Mentors:''' Rafal Kulaga (IRC: rkulaga)<br />
<br />
The student will need to:<br />
<br />
* Look at the relevant code, and propose a tractable plan for implementing some of the improvements within the GSoC timeframe.<br />
* Implement some of the improvements, producing production-ready code that can be included in the next release of KStars after GSoC 2015.<br />
<br />
PS: If all this looks daunting, that's because you have not (yet) talked to us. If you're really interested, get onto #kde-kstars and ping the mentors.<br />
<br />
==== Project: Propose your own project ====<br />
<br />
'''Brief explanation:''' If you have some interesting ideas about KStars that can be implemented within the GSoC timeframe, you are very welcome to propose them, because we seem to have run out of ideas.<br />
<br />
'''Mentors:''' Rafal Kulaga (IRC: rkulaga)<br />
<br />
=== KDE Edu ===<br />
<br />
==== Project: Integrate Cantor into LabPlot====<br />
[http://labplot.sourceforge.net/ LabPlot] is a KDE-application for interactive graphing and analysis of scientific data.<br />
<br />
'''Brief explanation:''' The integration is twofold:<br />
<br />
# currently, for the created plots LabPlot uses either the data provided by hand in a spreadseet or by using data imported from external ascii-files. By having Cantor within LabPlot it should be possible to access the data sets created in a computer algebra session (say Maxima) provided by Cantor. Cantor's session have to be integrated into LabPlot's model-view framework and have to be put onto the same foot as all the other objects managable in LabPlot (spreadsheet, worksheets etc.).<br />
# By calling a CAS-specific command for creating a 2D-plot in Cantor, Cantor creates an external process that renders the plot and embeds the result as a pixmap. Instead of such a static pixmap, LabPlot's plots should be embeded. This would provide high degree of control of the plot appearance as provided by LabPlot.<br />
<br />
'''Mentor:''' Alexander Semke<br />
<br />
==== Project: Integrate [http://en.wikipedia.org/wiki/VTK VTK] into LabPlot, investigate [http://en.wikipedia.org/wiki/Tulip_(software) Tulip] ====<br />
[http://labplot.sourceforge.net/ LabPlot] is a KDE-application for interactive graphing and analysis of scientific data.<br />
<br />
'''Brief explanation:'''<br />
# LabPlot lacks 3D-functionality. In the old KDE3-based LabPlot qwt3D was used for this that is not an option anymore. The task consists of the integration of [http://en.wikipedia.org/wiki/VTK VTK] -libs. Also, the relevant widgets for 3D-plot editting should be created in a manner similar for all the other objects available in LabPlot now.<br />
# Investigate whether it's reasonable to use LabPlot as a frontend (or to extend it to be a frontend) to the functionality provided by [http://en.wikipedia.org/wiki/Tulip_(software) Tulip] yes, how?<br />
<br />
'''Mentor:''' Alexander Semke<br />
<br />
==== Project: Port of GCompris in Qt Quick====<br />
<br />
[http://gcompris.net GCompris] is a an educational software suite comprising of numerous activities for children aged 2 to 10. Originaly written in Gtk+ it's development team decided to rewrite it from scratch in [http://qt-project.org/doc/qt-5/gettingstartedqml.html Qt Quick]. It has also been decided that this version will be integrated in KDE which is the reason of the project being here.<br />
<br />
'''Goals:''' <br />
# Porting several GCompris activities in Qt Quick. There is a page that tracks the [http://gcompris.net/wiki/Qt_Quick_Migration_status porting effort] that will help you select the activity set you are interested in.<br />
# Creating new activities. There is a [http://gcompris.net/wiki/Ideas_for_activities list of ideas] of activities that have been identified as something we would like to have. You can also propose original ideas not on the list.<br />
<br />
'''Knowledge Prerequisite:''' By the start of GSoC you should<br />
# Be interested in children education<br />
# Be familiar with GCompris concept and content<br />
# Basic knowledge in a programming language (a 1 year school course is enough)<br />
# Be able to build the Qt Quick version of GCompris<br />
<br />
'''Application guide:'''<br />
# Writing or porting an activity takes about the same time. The advantage of the porting is that the tuning, the graphishm and the sounds are already available. You can count 1 week of development for a basic activity.<br />
# To keep the work interesting it is recommended to propose a mix of porting some activities and creating new one, either from the idea list or from an original idea you come with.<br />
# You have to follow the [http://gcompris.net/wiki/An_exercise_for_new_contributors instructions here] and provide your exercise as a pull request.<br />
<br />
'''Mentor:''' Bruno Coudoin (IRC: bdoin #gcompris on freenode)<br />
<br />
=== Keyboard Layouts ===<br />
<br />
Keyboard layouts in KDE allow user to use multiple keyboard layouts and switch between them. It consists of keyboard configuration module (in System Settings), keyboard layout widget/applet, and keyboard layout daemon.<br />
<br />
==== Project: Integrating Input Methods with keyboard layout configuration ====<br />
<br />
'''Brief explanation:''' Input method and keyboard layout configuration are serving the same purpose - to allow users to type text in non-default language. Currently KDE has integrated system to configure keyboard layouts but IM need to be configured somewhere else. Also when IM is configured it takes over some functions of keyboard layout configuration. So it would be nice if we could have IM and keyboard layout configuration in one place.<br />
It seems that IBus has already gained community acceptance so this will be the target for integration into KDE keyboard module.<br />
<br />
'''Expected results:''' Keyboard configuration module in System settings will include IM configuration and it will be integrated with existing keyboard layout options.<br />
<br />
'''Knowledge Prerequisite:''' good knowledge of C++, development experience with Qt and KDE, understanding of Input Methods (IBus)<br />
<br />
=== KDevelop ===<br />
<br />
==== Project: Clang Integration ====<br />
<br />
'''Brief explanation:''' Finish the kdev-clang plugin to make it a usable replacement for the existing C++ plugin.<br />
<br />
'''Expected results:''' Find the still missing features from the KDevelop4's C++ support and port them over to kdev-clang, so it can become the mainstream C/C++ Solution<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt. Knowledge about Clang is helpful<br />
<br />
'''Mentor:''' Kevin Funk<br />
<br />
==== Project: Checker Framework ====<br />
<br />
'''Brief explanation:''' A generic framework should be created which provides the foundation for other plugins to report errors. <br />
<br />
'''Expected results:''' Right now we have the problems toolview but it is tightly coupled to the DUChain. This should be changed to use a separate item repository which stores the problems for a given path. The data stored would be: Path and range of where the issue is found, a short error message and optionally a long description. Furthermore, plugins might want to store additional info from which the problem could be fixed (compare to the 'add include path' or similar wizards we have already in the language framework).<br />
<br />
This framework should then be used to integrate various tools.<br />
<br />
First of all the existing language plugins should show the problems they find there.<br />
The existing playground plugins for krazy and cppcheck integration should reuse that framework<br />
any other linters could be integrated, such as jslint, pylint, clang-check, etc. pp.<br />
runtime checkers could be integrated, such as valgrind's memcheck, ptrcheck, helgrind, drd, ...<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt. Knowledge of debugging tools is helpful.<br />
<br />
'''Mentor:''' Milian Wolff<br />
<br />
==== Project: SVN Plugin Rewrite ====<br />
<br />
'''Brief explanation:''' Rewrite the SVN plugin to use the C-API directly.<br />
<br />
'''Expected results:''' The existing SVN plugin uses an outdated kdevsvncpp checkout internally which causes troubles, warnings and licensing issues. Port the plugin to either the C-API of svn or alternatively try to reuse code from current kdevsvn. The result should be a tested, working plugin for SVN integration without licensing issues nor compile time warnings about usage of deprecated API.<br />
<br />
'''Knowledge Prerequisite:''' C, C++, Qt, SVN<br />
<br />
'''Mentor:''' Milian Wolff<br />
<br />
==== Project: LLDB Support ====<br />
<br />
'''Brief explanation:''' Write a new plugin to support LLDB on KDevelop<br />
<br />
'''Expected results:''' Come up with a new kdevelop plugin so that LLDB can be used as a debugging solution, especially on Mac OS X and Windows, where gdb support is rather scarce.<br />
<br />
'''Knowledge Prerequisite:''' C, C++, Qt, debugging intrinsic problems<br />
<br />
'''Mentor:''' KDevelop team<br />
<br />
=== KDE PIM ===<br />
<br />
The KDE PIM community work on a set of libraries and applications for Personal Information Management, including email, calendaring, contacts, and feed aggregation.<br />
<br />
==== Project: OpenHolidays ====<br />
<br />
'''Brief explanation:''' The KHolidays library provides KDE applications with information on public holidays around the world, however the file format is very hard to use and maintain and the library features are very limited and restricted to Qt users. The goal of the OpenHolidays project is to develop a new open standard and data repository that can be used by any project that needs the data. See http://community.kde.org/KDE_PIM/KHolidays for more details.<br />
<br />
'''Expected results:''' Define the new JSON file format and port the existing data files to the new format. Develop a shared Qt-only library to parse the holiday files and provide access to them with a iCal style event-based api. Implement an Akonadi resource to access the data. Extended goals: Develop a JavaScript library to use the files. Develop a web site and web service at openholidays.org to provide online access to the data files.<br />
<br />
'''Knowledge Prerequisite:''' C++ and Qt for core goals, JavaScript and web services for extended goals.<br />
<br />
'''Mentor:''' John Layt and other KDE PIM community members.<br />
<br />
==== Project: QtQuick ToDo API / Plasmoid====<br />
<br />
'''Brief explanation:''' KDE PIM wants to make it's data accessible for applications which use QML to declare their user interfaces, e.g. applications using QtQuick. For that they need data handling objects that are accessible through QML, e.g. item models that have a mapping of string based role names to enum value based roles in C++, etc.<br />
<br />
'''Expected results:''' Define and implement a general QML API for accessing and creating Akonadis ToDo data. Write / Port a ToDo Plasmoid for Plasma Desktop or Plasma Active to show off the new API. Bonus: Port Kontact Touch Task to the new API instead of, or in addition to the Plasmoid.<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt, QtQuick<br />
<br />
'''Possible Mentors:''' Kevin Krammer, and other KDE PIM community members<br />
<br />
=== Simon ===<br />
Simon is a speech recognition suite.<br />
<br />
[http://simon.kde.org Website] - [https://mail.kde.org/mailman/listinfo/kde-speech Mailing list] - IRC channel: #kde-speech on Freenode.<br />
<br />
==== Project: Streamline handling of various resources ====<br />
<br />
'''Brief explanation:''' Simon uses a multitude of different components: Scenarios, Base models, Shadow vocabulary, Language profiles, etc.<br />
<br />
While many of these components can be downloaded from within Simon, some can't and even for those that are better integrated, end-users still have to read additional documentation to know which components work together and which don't.<br />
<br />
The aim of this project is to bring the handling of these resources under a uniform and user-friendly interface.<br />
Specifically, the interface should resolve conflicts automatically and deduce an optimal default setup by itself (e.g. based on the system language and installed programs).<br />
<br />
'''Expected results:''' Much more user friendly setup.<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt<br />
<br />
'''Mentor:''' Peter Grasch <peter {+at+} grasch.net><br />
<br />
'''Resources:''' Some work (mostly brainstorming and UI design) was already conducted during Season of KDE 2013. Please contact me for details. This does not mean that this project is already assigned!<br />
<br />
=== KDE Telepathy===<br />
<br />
=== Okular ===<br />
<br />
Okular is a Document Viewer. <br />
<br />
* [http://okular.kde.org Okular project web site]<br />
* [https://mail.kde.org/mailman/listinfo/okular-devel Mailinglist]<br />
* [http://webchat.freenode.net/?channels=okular #okular IRC channel on Freenode]<br />
<br />
==== Project: Better Accessibility for Okular ====<br />
'''Brief explanation:''' We should implement Qt accessibility APIs to make Okular usable by more users. This would allow blind people to read documents.<br />
<br />
'''Expected results:''' You should be able to "read" Okular documents using Orca or other "screen reading" software. As long as the document exposes the contents in text form, we can let assistive technology pick it up and present it to the user in a different way (for example non-textual). An important goal is to transfer as much of the structure of the document as possible, so that ideally the sematics (this is a heading, here is normal text, page number) are preserved. Finding well working PDF solutions is still a challenge for blind people on any operating system. For now the focus will be on Orca since it's the best working screen reader on Linux used by most blind users.<br />
<br />
'''Knowledge Prerequisite:''' C++<br />
<br />
'''Mentor:''' Albert, Frederik helping out with the accessibility parts<br />
<br />
==== Project: Implement PDF Poppler features ====<br />
'''Brief explanation:''' Poppler has some support for features we don't support, implement them<br />
<br />
'''Expected results:''' Poppler has support for pdf layer views, tagged pdf support, linearized pdf support yet we in Okular don't offer that features to our users. The result from this project is having those exposed to the final users<br />
<br />
'''Knowledge Prerequisite:''' C++<br />
<br />
'''Mentor:''' Albert<br />
<br />
==== Project: Implement SecurityHandler V6 in Poppler ====<br />
'''Brief explanation:''' Poppler needs to support SecurityHandler V6 to be able to open some pdf files<br />
<br />
'''Expected results:''' Poppler (and hence Okular) can open files with SecurityHandler V6 like the ones in https://bugs.freedesktop.org/show_bug.cgi?id=85368 and https://bugs.freedesktop.org/show_bug.cgi?id=88151<br />
<br />
'''Knowledge Prerequisite:''' C++<br />
<br />
'''Mentor:''' Albert<br />
<br />
=== KDE Connect ===<br />
==== Project: Improve KDE Connect encryption ====<br />
'''Brief explanation:''' We want to implement a better encrypted protocol for KDE Connect, as discussed here: http://albertvaka.wordpress.com/2013/09/19/how-kde-connect-encryption-works/ I would like to see a solid and peer-reviewed design before accepting this project.<br />
<br />
'''Expected results:''' Have a secure encryption algorithm implemented in both KDE (C++/Qt) and Android (Java) clients.<br />
<br />
'''Knowledge Prerequisite:''' Deep knowledge about encryption and security.<br />
<br />
'''Mentor:''' Albert Vaca <albertvaka {+at+} gmail.com><br />
<br />
'''Resources:''' kdeconnect<br />
<br />
==== Project: Build a Qt-only multiplatform KDEConnect client ====<br />
'''Brief explanation:''' We want to implement a cross platform client written in Qt that can run in virtually any platform supported by Qt (Windows Phone, Jolla, iOS, OSX, etc.) using the QPA (Qt Platform Abstraction) and QML. It will be challenging because Qt5 for phones is still quite new and implementing some features might not be possible yet, but it will be worth it to investigate what is possible and what not, and even contribute patches to Qt for some aspects. A lot of the core classes used in KDE Connect for Plasma could be reused and shared because they are mostly Qt (and would be part of the GSOC to make sure they end only using Qt, so we can get to re-use them). Not every feature is going to be available to every platform, and some plugins will be platform-specific, but as part of this GSOC project I would love to see it running as good as possible in one of the platforms already mentioned, and with basic functionallity in a couple more. (That is: center it around a platform and make it work well there, writting platform-specific plugins and code if needed, but making sure it still compiles and runs in other platforms).<br />
<br />
'''Knowledge Prerequisite:''' Qt5 and building cross-platform code.<br />
<br />
'''Mentor:''' Albert Vaca <albertvaka {+at+} gmail.com><br />
<br />
'''Resources:''' kdeconnect<br />
=== Solid ===<br />
==== Project: Make Libbluedevil Async ====<br />
'''Brief explanation:''' Extend libbluedevil to have an asynchronous api, and port bluedevil to it.<br />
<br />
'''Expected results:''' libbluedevil should have an asynchronous api, and bluedevil should be ported to them.<br />
<br />
'''Knowledge Prerequisite:''' basic Qt and DBus<br />
<br />
'''Mentor:''' Àlex Fiestas <afiestas {+at+} kde.org><br />
<br />
'''Resources:''' libbluedevil, bluedevil, afiestas<br />
<br />
==== Project: Improve sharing experience ====<br />
'''Brief explanation:''' Improve the content sharing experience in Plasma by extending and improving Samba share, implementing other ways of sharing and write new ways of discovering other people's shares.<br />
<br />
'''Expected results:''' It should be possible to discover "shares" using dolphin (possibly via a new kioslave?) and it should be possible to share a folder between two Plasma computers really fast and easy (possibly implementing an http server plus discovery via avahi).<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt, extra points for KIO experience.<br />
<br />
'''Mentor:''' Àlex Fiestas <afiestas {+at+} kde.org><br />
<br />
'''Resources:''' avahi, http, kdenetwork-fileshare<br />
<br />
=== Muon ===<br />
==== Project: Better support for your distribution ====<br />
<br />
'''Brief explanation:''' Muon needs to be ensured to work perfectly on any distribution, this project should target one of the (major) distributions, enumerate the problems to solve and propose solutions.<br />
<br />
'''Expected results:''' Muon users of your distribution will be happy ever-after.<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt, the technology required for the platform<br />
<br />
'''Mentor:''' Aleix Pol<br />
<br />
<br />
=== KWin ===<br />
==== Project: DRM/KMS backend for kwin_wayland ====<br />
<br />
'''Brief explanation:'''<br />
KWin_wayland currently only supports rendering to another Wayland server. In future it should be possible to go down to the hardware directly. For this a DRM/KMS rendering backend is required. This requires that a new backend is implemented for the OpenGL compositor and maybe the QPainter compositor. As KWin needs to handle kernel mode settings in this mode the output information need to be queried from the hardware and an implementation for KWin::Screens needs to be provided and from there propagated to the Wayland clients. In addition if the time of the project permits it an interface should be exposed for KScreen to configure the outputs.<br />
<br />
'''Expected results:''' KWin_wayland can render to DRM/KMS and fetches output information from the hardware<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt, Wayland, KMS and C knowlege are from advantage<br />
<br />
'''Mentor:''' Martin Gräßlin <mgraesslin@kde.org><br />
<br />
===Trojitá===<br />
<br />
[http://trojita.flaska.net/ Trojitá] is a fast IMAP e-mail client. Since late 2012, it is a part of KDE's extragear. The project focuses on delivering a usable, fast, standards-compliant, cross-platform and reliable e-mail client which can scale from cell phones to huge e-mail archives without annoying slowdowns.<br />
<br />
==== Project: Port to BlackBerry OS 10 ====<br />
<br />
'''Brief explanation:'''<br />
This work involves improving the separation of business logic from the UI concerns, an effort started and well-underway due to the Ubuntu Touch project, and adding a new GUI wirrten in QML for BlackBerry OS 10.<br />
<br />
'''Expected results:''' Trojitá running on BlackBerry Z10 with basic features, including reading and writing e-mails<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt, QML<br />
<br />
'''Mentor:''' Jan Kundrát <jkt@kde.org><br />
<br />
=== Gluon ===<br />
[http://gamingfreedom.org Gluon] is a project to build a Qt and KDE based game engine and game development tool. The engine is designed to support both mobile and desktop game development. We have ported the engine to Qt5 last year and are currently working on releasing a first Qt5 based version.<br />
<br />
==== Project: Build a QtQml based script system ====<br />
'''Brief explanation:''' In Qt4 QtScript was the solution to scripting support for applications. With the port to Qt5 the new QtQml module was introduced, including a new scripting system, but QtScript was still available. With Qt5.5 QtScript is planned to be deprecated and completely removed in Qt5.6. This means that our scripting system, which is currently built on QtScript, needs to be ported to QtQml.<br />
<br />
'''Expected results:''' A scripting system that can be used to write scripts for games.<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt at least. Experience with QtQuick/QML is a strong advantage.<br />
<br />
'''Mentor:''' Arjen Hiemstra<br />
<br />
==== Project: Expand Gluon Input ====<br />
'''Brief explanation:''' During the port to Qt5 we also overhauled the input system in Gluon to be more capable. However, we kept the implementation rather limited since we also had other elements to work on. This project would expand GluonInput with support for additional devices and platforms.<br />
<br />
'''Expected results:''' Additional platform and device plugins for GluonInput.<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt at least. Experience with platform-specific input libraries like XInput2 for Xorg is an advantage.<br />
<br />
'''Mentor:''' Arjen Hiemstra<br />
<br />
[[Category:Mentoring]]<br />
<br />
=== Krita ===<br />
[http://www.krita.org Krita] is an advanced 2D painting application. It support creating images from scratch from begin to end. Krita is a complex application and developers need to have a fair amount of experience in order to be able to do something.<br />
<br />
==== Project: Integrate Animation in Krita's core ====<br />
'''Brief explanation:''' We have gone through three iterations of animation support code in Krita. With this experience, it's become clear that we need to work the support for animatins right into Krita's core engine. This project comprises partly that, and partly updating the existing animation gui that was created in 2014.<br />
<br />
'''Expected results:''' by the end of the summer, the animation support in Krita should be ready for end-users to create 2D animations with, whether for game sprites or short cartoons. <br />
<br />
'''Knowledge Prerequisite:''' C++/Qt at least.<br />
<br />
'''Mentor:''' Boudewijn Rempt<br />
<br />
==== Project: Add Python Scripting to Krita ====<br />
'''Brief explanation:''' Krita has had two attempts at scripting support: through kjs and through kross. Neither was good enough. The VFXindustry standard for scripting is Python, and the goal of project is to integrate Python and PyQt directly into Krita.<br />
<br />
'''Expected results:''' by the end of the summer, users should be able to automate repetitive tasks, file import and export and add gui elements such as dockers, all written in PyQt.<br />
<br />
'''Knowledge Prerequisite:''' Deep knowledge of Python, SIP, C++ and Qt.<br />
<br />
'''Mentor:''' Boudewijn Rempt<br />
<br />
==== Project: Improve Normal Mapping Workflow ====<br />
'''Brief explanation:''' Normal maps are textures that describe surface detail on a 3d model by describing how much each pixel deviates from the surface the texture is put on. A normal map gives the ability to tell the renderer there's a different normal per texel(texture pixel), this way, you can describe subtle differences in surface without requiring the polygons for it. It does so by describing the normal angle to the surface by using the R, G and B channels. Now, normal maps, due to them being quite mathematical, are usually baked. But these bakes are not always perfect. furthermore, there's a lot of interest into handpainting textures, amongst which normal maps.<br />
<br />
'''Expected results:''' by the end of the summer, a new brush engine, which takes the tilt-direction and has that control the redness and greenness. And then takes the tilt-elevation, and has that control the blueness.<br />
<br />
'''Knowledge Prerequisite:''' knowledge of C++, Qt. and mathematics<br />
<br />
'''Mentor:''' Boudewijn Rempt<br />
<br />
===Calligra===<br />
==== Project: Variable thickness lines ====<br />
<br />
'''Brief explanation:''' One of the most fundamental basics of drawing is varying the width of your lines to show shape, form and perspective. Almost every line tapers at either end, and often gets thicker and thinner in different places as needed. For purely technical and histrorical reasons though, every vector program (Illustrator, Inkscape, Karbon etc) make curves all one hard width. <br />
This proposal is to create a variable width path shape / tool, much like the path tool, would allow drawing curves, but where each node could have its width set so that the line width changed smoothly from node to node. <br />
As a plugin for the Calligra suite, this would clearly benefit apps as Karbon and also Krita.<br />
<br />
'''Expected results:''' variable width path tool is able to change the width of any path node to an arbitary percentage (say 155%) of the stroke width. See http://bugsfiles.kde.org/attachment.cgi?id=56995 for mockup. The shape needs to be able to save and load in svg/odf.<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt, SVG<br />
<br />
'''Mentor:''' Thorsten Zachmann < zachmann @ kde dot org ><br />
<br />
=== KIOSK ===<br />
==== Project: KIOSK Tool ====<br />
<br />
'''Brief explanation:''' Back in KDE 3 there was a tool to help administrators to configure the KDE Kiosk framework. The idea of this project is to start working on a new tool. The new application should be developed in close collaboration with the Visual Design Group to get a useful application for the targeted audience.<br />
<br />
'''Expected results:''' a functional prototype for a new Kiosk tool with a working backend to configure and restrict actions and configuration options.<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt<br />
<br />
'''Mentor:''' Martin Gräßlin <mgraesslin@kde.org><br />
<br />
=== Kubuntu ===<br />
==== Project: Port Ubiquity to Qt 5 ====<br />
<br />
'''Brief explanation:''' Ubiquity is the installer for Kubuntu. It should be ported to Qt 5. It is written in Python and can be fiddly to test because much of the development needs to be done on a live system. Once the Qt 5 port is complete there are numerous other bugs that can be fixed. Drop into #kubuntu-devel to say hi. Code is in launchpad.net/ubiquity.<br />
<br />
'''Expected results:''' Ubiquity bug free and running with Qt 5<br />
<br />
'''Knowledge Prerequisite:''' Python, PyQt<br />
<br />
'''Mentor:''' Jonathan Riddell</div>Leinirhttps://community.kde.org/index.php?title=GSoC/2015/Ideas&diff=41652GSoC/2015/Ideas2015-02-19T11:31:27Z<p>Leinir: /* Plasma */</p>
<hr />
<div>{{Note|Work in progress, proposals here are often copied from the GSoC 2014 list}}<br />
[[File:GoogleSummer 2015logo.jpg |200px|thumb|right|GSoC 2015 logo]]<br />
See also: [[../../|GSoc Instructions]], [[../../2014/Ideas|Last year ideas]]<br />
<br />
== Guidelines ==<br />
<br />
=== Information for Students ===<br />
<br />
These ideas were contributed by our developers and users. They are sometimes vague or incomplete. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at.<br />
<br />
Being accepted as a Google Summer of Code student is quite competitive. Accepted students typically have thoroughly researched the technologies of their proposed project and have been in frequent contact with potential mentors. Simply copying and pasting an idea here will not work. On the other hand, creating a completely new idea without first consulting potential mentors is unlikely to work out.<br />
<br />
When writing your proposal or asking for help from the general KDE community don't assume people are familiar with the ideas here. KDE is really big!<br />
<br />
If there is no specific contact given you can ask questions on the general KDE development list kde-devel@kde.org. See [http://www.kde.org/mailinglists/ the KDE mailing lists page] for information on available mailing lists and how to subscribe.<br />
<br />
=== Adding a Proposal ===<br />
<br />
{{Note|Follow the template of other proposals!}}<br />
<br />
==== Project: ====<br />
<br />
'''Brief explanation:'''<br />
<br />
'''Expected results:'''<br />
<br />
'''Knowledge Prerequisite:'''<br />
<br />
'''Mentor:'''<br />
<br />
When adding an idea to this section, please try to include the following data:<br />
<br />
:*if the application is not widely known, a description of what it does and where its code lives<br />
:*a brief explanation<br />
:*the expected results<br />
:*pre-requisites for working on your project<br />
:*if applicable, links to more information or discussions<br />
:*mailing list or IRC channel for your application/library/module<br />
:*your name and email address for contact (if you're willing to be a mentor)<br />
<br />
If you are not a developer but have a good idea for a proposal, get in contact with relevant developers first.<br />
<br />
<br />
==Ideas==<br />
<br />
===Your Own Idea ===<br />
<br />
==== Project: Something that you're totally excited about ====<br />
<br />
'''Brief explanation:''' Do you have an awesome idea you want to work on with KDE but that is not among the ideas below? That's cool. We love that! But please do us a favor: Get in touch with a mentor early on and make sure your project is realistic and within the scope of KDE. That will spare you and us a lot of frustration.<br />
<br />
'''Expected results:''' Something you and KDE loves<br />
<br />
'''Knowledge Prerequisite:''' Probably C++ and Qt but depends on your project<br />
<br />
'''Mentor:''' Try to see who in KDE is interested in what you want to work on and approach them. If you are unsure you can always ask in #kde-soc on Freenode IRC.<br />
<br />
===Plasma===<br />
<br />
==== Project: Port various KDE4 Plasmoids to Plasma 5 ====<br />
<br />
'''Brief explanation:''' When we ported from Plasma 4 to Plasma 5 some useful Plasmoids ended up not being initially ported. We want the more important existing applets to continue to run which . Students should select a few Plasmoids which they deem useful for their proposal along with some innovative ideas for improvements. Students should show knowledge of the level of work related. <br />
<br />
'''Expected results:''' A few fully working plasmoids, polished and better than before.<br />
<br />
'''Knowledge Prerequisite:''' QML skills. Ideally some Plasmoid experience<br />
<br />
'''Mentor:''' Sebastian Kugler with help of the Plasma team.<br />
<br />
==== Project: Port KSystemLog to use journald as a backend ====<br />
<br />
'''Brief explanation:''' KSystemLog is a tool for viewing log files. This has slowly started to fail as log files moved in various distributions. Journald provides a common interface to query programatically system and user logs which will fix the main issue. Applications should impress me with their ideas utilising the available features. <br />
<br />
'''Expected results:''' A ported to frameworks journald powered log viewer. <br />
<br />
'''Knowledge Prerequisite:''' C++, Qt. <br />
<br />
'''Mentor:''' David Edmundson with help of the Plasma team.<br />
<br />
== Plasma and Gluon ==<br />
<br />
==== Project: Extend gamingFreedom.org framework to be more generic ====<br />
<br />
'''Brief explanation:''' Over the last couple of years, the gamingFreedom.org website and server side components have been created, which implement Open Collaboration Services (OCS) in a generic and reusable form. We are now at a point where it would make sense to attempt to use this for further purposes, rather than only for gamingFreedom.org. Specifically, a new implementation of the server component employed for hosting Plasma related content is needed, and a website for presenting this content on the web.<br />
<br />
'''Expected results:''' A new website based on gamingFreedom.org's OCS client libraries, and a server implementation for hosting Plasma content.<br />
<br />
'''Knowledge Prerequisite:''' PHP for the client and server code<br />
<br />
'''Mentor:''' Claudio Desideri and Dan Leinir Turthra Jensen with help of the Plasma team.<br />
<br />
=== Kdenlive ===<br />
<br />
Kdenlive is an intuitive and powerful multi-track video editor, including most recent video technologies. Our software is completely free, as defined by the GNU foundation. Using Kdenlive is investing in a community driven project, which aims to establish relationships between people in order to built the best video tools.<br />
<br />
* [http://www.kdenlive.org Kdenlive project web site]<br />
* [http://community.kde.org/Kdenlive Kdenlive wiki]<br />
* [https://mail.kde.org/mailman/listinfo/kdenlive Mailinglist]<br />
* [http://webchat.freenode.net/?channels=kdenlive #kdenlive IRC channel on Freenode]<br />
<br />
==== Project: Add support for new Animation capabilities ====<br />
<br />
'''Brief explanation:''' MLT, the media frameworks we use for rendering, has recently added a new [http://mltframework.blogspot.com/2013/06/v090-released-with-new-property.html property animation] to its objects. This allows much simpler, smoother and more general animations than the traditional keyframes technology. We then need new widgets to edit these properties, and eventually evolve our on-monitor interactions.<br />
<br />
'''Expected results:''' At the end of the project, we should be able to add and graphically adjust these animation parameters through controls in the effects stack panel, and bonus on the monitor.<br />
<br />
'''Knowledge Prerequisite:''' In the end you will assemble QtWidgets and interact with MLT data through C++. So you should be at ease with C++ and Qt (no need to be an expert), and have a look to the MLT manual page about animation.<br />
<br />
'''Mentor:''' Vincent Pinon with help of the Kdenlive team.<br />
<br />
==== Project: Redesign titler using WebVFX ====<br />
<br />
'''Brief explanation:''' Our titler, the tool we use to add text and drawing objects over the video, relies on a home made module added to the MLT framework. Our module is limited in features, quite slow to render, and demands work to maintain. MLT has since then been plugged into WebVFX engine, which provides infinite possibilities through web technologies, and it is certainly more robust. The goal is then to port our titler to this engine, then maybe evolve the interface to offer new possibilities.<br />
<br />
'''Expected results:''' At the end of the project, the titler should rely only on MLT WebVFX module. Bonus we should be able to add and easily edit more objects types.<br />
<br />
'''Knowledge Prerequisite:''' First step is to translate our XML to Web formats inside the C++ code, so you should understand those dialects. For the UI rework, you would then work with Qt, in either C++ or QML.<br />
<br />
'''Mentor:''' Vincent Pinon with help of the Kdenlive team.<br />
<br />
==== Project: add import/export filters for video editors exchange formats ====<br />
<br />
'''Brief explanation:''' To reduce the barrier to switch to Kdenlive, users should be able to import and export with commercial editing softwares (at least partially). Some scripts already exist to crudely parse EDL or AAF formats, the goal is to do it cleanly integrated in Kdenlive.<br />
<br />
'''Expected results:''' At the end of the project, we should be able to exchange projects with one or more commercial tools. Effects and transitions will probably be limited, but timeline construction should be transferable.<br />
<br />
'''Knowledge Prerequisite:''' The work will consist in manipulating XML data with Qt (C++), so you should understand those dialects.<br />
<br />
'''Mentor:''' Vincent Pinon with help of the Kdenlive team.<br />
<br />
==== Project: make Kdenlive work on Windows and OSX ====<br />
<br />
'''Brief explanation:''' All the frameworks Kdenlive relies on are working on other platforms, and Kdenlive used run on those long time ago. The goal here is to setup build environments on one or two other OS's, and fix the things that prevent Kdenlive to work.<br />
<br />
'''Expected results:''' At the end of the project, Kdenlive should work reliably on one or two commercial OS's.<br />
<br />
'''Knowledge Prerequisite:''' Setting up and running builds, fixing things in C++, CMake, dependencies.<br />
<br />
'''Mentor:''' Vincent Pinon with help of the Kdenlive and KDE porting teams.<br />
<br />
=== Amarok ===<br />
<br />
Amarok is a Music player that helps you organize and rediscover your music. <br />
<br />
* [http://amarok.kde.org Amarok project web site]<br />
* [http://community.kde.org/Amarok Amarok wiki]<br />
* [https://mail.kde.org/mailman/listinfo/amarok-devel Mailinglist]<br />
* [https://plus.google.com/+amarok Google+ page]<br />
* [http://webchat.freenode.net/?channels=amarok #amarok IRC channel on Freenode]<br />
<br />
==== Project: Port Amarok to Qt5/Kf5/Plasma5 ====<br />
<br />
'''Brief explanation:''' Currently Amarok still depends on kdelibs 4.x and Qt4.<br />
<br />
'''Expected results:''' Amarok should compile with Qt 5.x, kdelibs4 dependencies should be replaced with kf5. Port most existing plasma widgets of the Context View to Plasma 5 (at least the most important should be ported). The default system themes should apply to Amarok flawlessly. A very important part of this project is testing the port and adapting the unit tests.<br />
<br />
'''Knowledge Prerequisite:''' good knowledge of C++/Qt, ideally being familiar with kf 5 and Plasma 5. The student should have some basic knowledge of the Amarok project and its functions as well as its architecture. All relevant information about Amarok, Qt5, kf5 and Plasma 5 can be found online, every suitable applicant should be able to find this documentation on their own.<br />
<br />
'''Mentor:''' To be determined. All discussions about the project should be held on the mailinglist and/or on IRC<br />
<br />
===digiKam===<br />
<br />
digiKam is an advanced digital photo management application for Linux, Windows, and Mac-OSX.<br />
<br />
* [http://www.digikam.org digiKam project web site]<br />
* [http://www.exiv2.org Exiv2 project web site]<br />
* [https://techbase.kde.org/Projects/Digikam/CodingSprint2014 digiKam port to KF5 status]<br />
* [https://mail.kde.org/mailman/listinfo/digikam-devel Mailinglist]<br />
* [https://plus.google.com/+digikam Google+ page]<br />
* [http://webchat.freenode.net/?channels=digikam #digikam IRC channel on Freenode]<br />
<br />
==== Project: Re-write database KIO-slaves as pure Qt5 using multithreading ====<br />
<br />
'''Brief explanation:''' Originally, KIO-Slaves have been implemented to run database queries in a separated process to prevent problem with SQlite. Since SQlite support re-entrancy and queries from separated threads, digiKam KIO-slaves used to process complex and long database queries can be re-written as core implementation using Qt thread API. This will improve digiKam availability in time when system is updated in low-level, and permit to adjust finely CPU cores assigned to database process.<br />
<br />
'''Dependencies:''' : digiKam core from "framework" branch (KF5) <br />
<br />
'''Links:''' [https://www.sqlite.org/threadsafe.html Using Sqlite in multi-threaded application], [https://bugs.kde.org/show_bug.cgi?id=146557 Bug #146557]<br />
<br />
'''Knowledge Prerequisite:''' C/C++, Qt, database, multi-threading<br />
<br />
'''Expected results:''' Identify all parts of digiKam core which query database through KIO-slaves mechanism, factorize code in same interface and write a multi-threaded wrapper to run SQlite queries. Write test code to check quickly if database core implementation changes don't affect wrapper functionality. Note : digiKam use internally URL + XML formating to pass data to KIO-slaves and this not be changed.<br />
<br />
'''Difficulty:''' high<br />
<br />
'''Lead Mentor:''' Gilles Caulier <caulier dot gilles at gmail dot com><br />
<br />
==== Project: Advanced Metadata HUB ====<br />
<br />
'''Brief explanation:''' digiKam has already some options to manage workflow between image metadata and database, through the setup/metadata configuration panel. The goal of this project is to write a more advance setup to control finely the most important metadata field in order to read from image and populate database and vis versa. The list of metadata to drive must be easily extensible and configurable. Also, the metadata workflow to synchronize image with database must be more flexible and must provide a way to synchronize files at end of digiKam session and not only in real time (typical case : editing image tags to write in images). <br />
<br />
'''Dependencies:''' : digiKam core and libkexiv2 from "framework" branch (KF5) <br />
<br />
'''Links:''' [https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&component=Metadata&list_id=1205997&product=digikam&query_format=advanced&short_desc=HUB&short_desc_type=allwordssubstr Bugs list from bugzilla]<br />
<br />
'''Knowledge Prerequisite:''' C/C++, Qt, database, multi-threading<br />
<br />
'''Expected results:''' Create metadata hub widget for settings panel, adjust current hub and image scanner implementations, add test code.<br />
<br />
'''Difficulty:''' high<br />
<br />
'''Lead Mentor:''' Gilles Caulier <caulier dot gilles at gmail dot com><br />
<br />
==== Project: Add WebP and WebM support ====<br />
<br />
'''Brief explanation:''' WebP/WebM is new wavelets based image/video format from Google, based on RIFF/MKV container. This format become more popular on the Web and both can be used through an open-source library. We need to support these formats as editable in digiKam (WebP) and manageable by database mechanism through metadata (WebP and WebM).<br />
<br />
'''Dependencies:''' : digiKam core and libkexiv2 from "framework" branch (KF5), Exiv2 library<br />
<br />
'''Links:''' [http://en.wikipedia.org/wiki/WebM WebM format], [http://en.wikipedia.org/wiki/WebP WebP format]<br />
<br />
'''Knowledge Prerequisite:''' C/C++, Qt, Metadata<br />
<br />
'''Expected results:''' Patch Exiv2 library to support both formats in read/write meta-data mode and add optional WebP support in digiKam core to be able to edit images (read/write image contents in 16 bits color depth). Write test code to check new functionality in time.<br />
<br />
'''Difficulty:''' high<br />
<br />
'''Mentors:''' Gilles Caulier <caulier dot gilles at gmail dot com> + Someone from Exiv2 team<br />
<br />
==== Project: Factorize and port to KF5 all web service Import/Export KIPI tools ====<br />
<br />
'''Brief explanation:''' All tools dedicated to import or export items from KIPI host applications to web services as Flickr, GDrive, Dropbox, Facebook, Picasa, etc... need to be factored and ported to KF5/Qt5. Factorization include to make common widgets (settings, GUI layout, rules, etc), and background processing to prevents duplicate code. Also, in order to reduce KIPI host application time loading, the number of tools must be limited. Tools must be grouped by categories, as Social Networks, Cloud Service, Photo Hosting, etc...<br />
<br />
'''Dependencies:''' : digiKam KIPI interface, KIPI Plugins <br />
<br />
'''Bugzilla entries:''' [https://bugs.kde.org/show_bug.cgi?id=221704 221704]<br />
<br />
'''Knowledge Prerequisite:''' C/C++, Qt/KDE, GUI<br />
<br />
'''Expected results:''' KIPI web services tools ported to KF5 and running with digiKam 5.0.0.<br />
<br />
'''Difficulty:''' high<br />
<br />
'''Lead Mentor:''' Gilles Caulier <caulier dot gilles at gmail dot com><br />
<br />
===Marble===<br />
Marble is a virtual globe and world atlas — your swiss army knife for maps. Find your way and explore the world!<br />
<br />
* [http://marble.kde.org/ Marble project website]<br />
* [https://mail.kde.org/mailman/listinfo/marble-devel Mailinglist]<br />
* [Marble Google+ page]<br />
* [http://webchat.freenode.net/?channels=marble #marble IRC channel on Freenode]<br />
<br />
(projects to appear here. Please ask in [http://webchat.freenode.net/?channels=marble #marble] in the meantime)<br />
<br />
=== KStars ===<br />
<br />
KStars is a very powerful tool for anyone interested in astronomy. It is part of the KDE Edu suite.<br />
<br />
==== Project: Ekos Scheduler ====<br />
<br />
'''Brief explanation:''' [http://www.indilib.org/about/ekos.html Ekos] is an advanced astrophotography tool for Linux. It utilizes [http://www.indilib.org INDI] for device control. With Ekos, the user can use the telescope, CCD, and other equipment to perform Astrophotography tasks. However, the user has to be present to configure the options and to command the actions to perform all the astrophotography related tasks, and hence a scheduler is required to automate observations to be constrained within certain limitations such as required minimum angular separation from the moon, whether conditions...etc. Furthermore, the observations should be triggered when certain conditions are met such as observation time, object's altitude...etc. The prospective student is expected to develop a ''Simple'' [http://indilib.org/forum/general/560-simple-ekos-schedular.html Ekos scheduler] to trigger observation runs when certain conditions are met and when the limitations are required.<br />
<br />
'''Expected results:''' Simple scheduler to automate astrophotography runs based on some conditions and within user-configurable limitations.<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt, INDI<br />
<br />
'''Mentors:''' Jasem Mutlaq (IRC: knro)<br />
<br />
The student will need to:<br />
<br />
* Look at the relevant code, and propose a tractable plan for implementing some of the improvements within the GSoC timeframe.<br />
* Implement some of the improvements, producing production-ready code that can be included in the next release of KStars after GSoC 2015.<br />
<br />
==== Project: Constellation art ====<br />
<br />
'''Brief explanation:''' KStars currently draws constellation lines, names, and boundaries, but constellation art is missing. The student is expected to study KStars API and develop a new SkyComponent to superimpose the constellation artwork unto the sky map while re-working other components in KStars to support this. The structure must support multiple sky cultures. The artwork itself must be available under a permissible license. New constellation artwork should be available for download using the KNewStuff framework. The user should be able to select the sky culture.<br />
<br />
'''Expected results:''' High quality artwork for Western constellations in addition to one non-western constellation artwork that can be switched on/off in the sky map.<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt<br />
<br />
'''Mentors:''' Jasem Mutlaq (IRC: knro)<br />
<br />
The student will need to:<br />
<br />
* Look at the relevant code, and propose a tractable plan for implementing some of the improvements within the GSoC timeframe.<br />
* Implement some of the improvements, producing production-ready code that can be included in the next release of KStars after GSoC 2015.<br />
<br />
==== Project: Fix our deep-sky data handling ====<br />
<br />
'''Brief explanation:''' Currently, KStars handles data from deep-sky object catalogues in an SQLite database. While this is working well, there are some more features we would like to have, and some that should be implemented in order to sanitize the deep-sky data handling, such as automatic cross-referencing of deep-sky objects across catalogs, organizing deep-sky data better in the database etc using Hierarchical Triangular Mesh, etc.<br />
<br />
More details here: http://techbase.kde.org/Projects/Edu/KStars/Better_deep-sky_handling<br />
<br />
'''Expected results:''' Some, or all of the improvements to deep-sky handling suggested above (or maybe even your own suggestions), implemented completely in solid, release-worthy code.<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt, understanding of astronomical catalogues, some experience with data structures.<br />
<br />
'''Mentors:''' Rafal Kulaga (IRC: rkulaga)<br />
<br />
The student will need to:<br />
<br />
* Look at the relevant code, and propose a tractable plan for implementing some of the improvements within the GSoC timeframe.<br />
* Implement some of the improvements, producing production-ready code that can be included in the next release of KStars after GSoC 2015.<br />
<br />
PS: If all this looks daunting, that's because you have not (yet) talked to us. If you're really interested, get onto #kde-kstars and ping the mentors.<br />
<br />
==== Project: Propose your own project ====<br />
<br />
'''Brief explanation:''' If you have some interesting ideas about KStars that can be implemented within the GSoC timeframe, you are very welcome to propose them, because we seem to have run out of ideas.<br />
<br />
'''Mentors:''' Rafal Kulaga (IRC: rkulaga)<br />
<br />
=== KDE Edu ===<br />
<br />
==== Project: Integrate Cantor into LabPlot====<br />
[http://labplot.sourceforge.net/ LabPlot] is a KDE-application for interactive graphing and analysis of scientific data.<br />
<br />
'''Brief explanation:''' The integration is twofold:<br />
<br />
# currently, for the created plots LabPlot uses either the data provided by hand in a spreadseet or by using data imported from external ascii-files. By having Cantor within LabPlot it should be possible to access the data sets created in a computer algebra session (say Maxima) provided by Cantor. Cantor's session have to be integrated into LabPlot's model-view framework and have to be put onto the same foot as all the other objects managable in LabPlot (spreadsheet, worksheets etc.).<br />
# By calling a CAS-specific command for creating a 2D-plot in Cantor, Cantor creates an external process that renders the plot and embeds the result as a pixmap. Instead of such a static pixmap, LabPlot's plots should be embeded. This would provide high degree of control of the plot appearance as provided by LabPlot.<br />
<br />
'''Mentor:''' Alexander Semke<br />
<br />
==== Project: Integrate [http://en.wikipedia.org/wiki/VTK VTK] into LabPlot, investigate [http://en.wikipedia.org/wiki/Tulip_(software) Tulip] ====<br />
[http://labplot.sourceforge.net/ LabPlot] is a KDE-application for interactive graphing and analysis of scientific data.<br />
<br />
'''Brief explanation:'''<br />
# LabPlot lacks 3D-functionality. In the old KDE3-based LabPlot qwt3D was used for this that is not an option anymore. The task consists of the integration of [http://en.wikipedia.org/wiki/VTK VTK] -libs. Also, the relevant widgets for 3D-plot editting should be created in a manner similar for all the other objects available in LabPlot now.<br />
# Investigate whether it's reasonable to use LabPlot as a frontend (or to extend it to be a frontend) to the functionality provided by [http://en.wikipedia.org/wiki/Tulip_(software) Tulip] yes, how?<br />
<br />
'''Mentor:''' Alexander Semke<br />
<br />
==== Project: Port of GCompris in Qt Quick====<br />
<br />
[http://gcompris.net GCompris] is a an educational software suite comprising of numerous activities for children aged 2 to 10. Originaly written in Gtk+ it's development team decided to rewrite it from scratch in [http://qt-project.org/doc/qt-5/gettingstartedqml.html Qt Quick]. It has also been decided that this version will be integrated in KDE which is the reason of the project being here.<br />
<br />
'''Goals:''' <br />
# Porting several GCompris activities in Qt Quick. There is a page that tracks the [http://gcompris.net/wiki/Qt_Quick_Migration_status porting effort] that will help you select the activity set you are interested in.<br />
# Creating new activities. There is a [http://gcompris.net/wiki/Ideas_for_activities list of ideas] of activities that have been identified as something we would like to have. You can also propose original ideas not on the list.<br />
<br />
'''Knowledge Prerequisite:''' By the start of GSoC you should<br />
# Be interested in children education<br />
# Be familiar with GCompris concept and content<br />
# Basic knowledge in a programming language (a 1 year school course is enough)<br />
# Be able to build the Qt Quick version of GCompris<br />
<br />
'''Application guide:'''<br />
# Writing or porting an activity takes about the same time. The advantage of the porting is that the tuning, the graphishm and the sounds are already available. You can count 1 week of development for a basic activity.<br />
# To keep the work interesting it is recommended to propose a mix of porting some activities and creating new one, either from the idea list or from an original idea you come with.<br />
# You have to follow the [http://gcompris.net/wiki/An_exercise_for_new_contributors instructions here] and provide your exercise as a pull request.<br />
<br />
'''Mentor:''' Bruno Coudoin (IRC: bdoin #gcompris on freenode)<br />
<br />
=== Keyboard Layouts ===<br />
<br />
Keyboard layouts in KDE allow user to use multiple keyboard layouts and switch between them. It consists of keyboard configuration module (in System Settings), keyboard layout widget/applet, and keyboard layout daemon.<br />
<br />
==== Project: Integrating Input Methods with keyboard layout configuration ====<br />
<br />
'''Brief explanation:''' Input method and keyboard layout configuration are serving the same purpose - to allow users to type text in non-default language. Currently KDE has integrated system to configure keyboard layouts but IM need to be configured somewhere else. Also when IM is configured it takes over some functions of keyboard layout configuration. So it would be nice if we could have IM and keyboard layout configuration in one place.<br />
It seems that IBus has already gained community acceptance so this will be the target for integration into KDE keyboard module.<br />
<br />
'''Expected results:''' Keyboard configuration module in System settings will include IM configuration and it will be integrated with existing keyboard layout options.<br />
<br />
'''Knowledge Prerequisite:''' good knowledge of C++, development experience with Qt and KDE, understanding of Input Methods (IBus)<br />
<br />
=== KDevelop ===<br />
<br />
==== Project: Clang Integration ====<br />
<br />
'''Brief explanation:''' Finish the kdev-clang plugin to make it a usable replacement for the existing C++ plugin.<br />
<br />
'''Expected results:''' Find the still missing features from the KDevelop4's C++ support and port them over to kdev-clang, so it can become the mainstream C/C++ Solution<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt. Knowledge about Clang is helpful<br />
<br />
'''Mentor:''' Kevin Funk<br />
<br />
==== Project: Checker Framework ====<br />
<br />
'''Brief explanation:''' A generic framework should be created which provides the foundation for other plugins to report errors. <br />
<br />
'''Expected results:''' Right now we have the problems toolview but it is tightly coupled to the DUChain. This should be changed to use a separate item repository which stores the problems for a given path. The data stored would be: Path and range of where the issue is found, a short error message and optionally a long description. Furthermore, plugins might want to store additional info from which the problem could be fixed (compare to the 'add include path' or similar wizards we have already in the language framework).<br />
<br />
This framework should then be used to integrate various tools.<br />
<br />
First of all the existing language plugins should show the problems they find there.<br />
The existing playground plugins for krazy and cppcheck integration should reuse that framework<br />
any other linters could be integrated, such as jslint, pylint, clang-check, etc. pp.<br />
runtime checkers could be integrated, such as valgrind's memcheck, ptrcheck, helgrind, drd, ...<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt. Knowledge of debugging tools is helpful.<br />
<br />
'''Mentor:''' Milian Wolff<br />
<br />
==== Project: SVN Plugin Rewrite ====<br />
<br />
'''Brief explanation:''' Rewrite the SVN plugin to use the C-API directly.<br />
<br />
'''Expected results:''' The existing SVN plugin uses an outdated kdevsvncpp checkout internally which causes troubles, warnings and licensing issues. Port the plugin to either the C-API of svn or alternatively try to reuse code from current kdevsvn. The result should be a tested, working plugin for SVN integration without licensing issues nor compile time warnings about usage of deprecated API.<br />
<br />
'''Knowledge Prerequisite:''' C, C++, Qt, SVN<br />
<br />
'''Mentor:''' Milian Wolff<br />
<br />
==== Project: LLDB Support ====<br />
<br />
'''Brief explanation:''' Write a new plugin to support LLDB on KDevelop<br />
<br />
'''Expected results:''' Come up with a new kdevelop plugin so that LLDB can be used as a debugging solution, especially on Mac OS X and Windows, where gdb support is rather scarce.<br />
<br />
'''Knowledge Prerequisite:''' C, C++, Qt, debugging intrinsic problems<br />
<br />
'''Mentor:''' KDevelop team<br />
<br />
=== KDE PIM ===<br />
<br />
The KDE PIM community work on a set of libraries and applications for Personal Information Management, including email, calendaring, contacts, and feed aggregation.<br />
<br />
==== Project: OpenHolidays ====<br />
<br />
'''Brief explanation:''' The KHolidays library provides KDE applications with information on public holidays around the world, however the file format is very hard to use and maintain and the library features are very limited and restricted to Qt users. The goal of the OpenHolidays project is to develop a new open standard and data repository that can be used by any project that needs the data. See http://community.kde.org/KDE_PIM/KHolidays for more details.<br />
<br />
'''Expected results:''' Define the new JSON file format and port the existing data files to the new format. Develop a shared Qt-only library to parse the holiday files and provide access to them with a iCal style event-based api. Implement an Akonadi resource to access the data. Extended goals: Develop a JavaScript library to use the files. Develop a web site and web service at openholidays.org to provide online access to the data files.<br />
<br />
'''Knowledge Prerequisite:''' C++ and Qt for core goals, JavaScript and web services for extended goals.<br />
<br />
'''Mentor:''' John Layt and other KDE PIM community members.<br />
<br />
==== Project: QtQuick ToDo API / Plasmoid====<br />
<br />
'''Brief explanation:''' KDE PIM wants to make it's data accessible for applications which use QML to declare their user interfaces, e.g. applications using QtQuick. For that they need data handling objects that are accessible through QML, e.g. item models that have a mapping of string based role names to enum value based roles in C++, etc.<br />
<br />
'''Expected results:''' Define and implement a general QML API for accessing and creating Akonadis ToDo data. Write / Port a ToDo Plasmoid for Plasma Desktop or Plasma Active to show off the new API. Bonus: Port Kontact Touch Task to the new API instead of, or in addition to the Plasmoid.<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt, QtQuick<br />
<br />
'''Possible Mentors:''' Kevin Krammer, and other KDE PIM community members<br />
<br />
=== Simon ===<br />
Simon is a speech recognition suite.<br />
<br />
[http://simon.kde.org Website] - [https://mail.kde.org/mailman/listinfo/kde-speech Mailing list] - IRC channel: #kde-speech on Freenode.<br />
<br />
==== Project: Streamline handling of various resources ====<br />
<br />
'''Brief explanation:''' Simon uses a multitude of different components: Scenarios, Base models, Shadow vocabulary, Language profiles, etc.<br />
<br />
While many of these components can be downloaded from within Simon, some can't and even for those that are better integrated, end-users still have to read additional documentation to know which components work together and which don't.<br />
<br />
The aim of this project is to bring the handling of these resources under a uniform and user-friendly interface.<br />
Specifically, the interface should resolve conflicts automatically and deduce an optimal default setup by itself (e.g. based on the system language and installed programs).<br />
<br />
'''Expected results:''' Much more user friendly setup.<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt<br />
<br />
'''Mentor:''' Peter Grasch <peter {+at+} grasch.net><br />
<br />
'''Resources:''' Some work (mostly brainstorming and UI design) was already conducted during Season of KDE 2013. Please contact me for details. This does not mean that this project is already assigned!<br />
<br />
=== KDE Telepathy===<br />
<br />
=== Okular ===<br />
<br />
Okular is a Document Viewer. <br />
<br />
* [http://okular.kde.org Okular project web site]<br />
* [https://mail.kde.org/mailman/listinfo/okular-devel Mailinglist]<br />
* [http://webchat.freenode.net/?channels=okular #okular IRC channel on Freenode]<br />
<br />
==== Project: Better Accessibility for Okular ====<br />
'''Brief explanation:''' We should implement Qt accessibility APIs to make Okular usable by more users. This would allow blind people to read documents.<br />
<br />
'''Expected results:''' You should be able to "read" Okular documents using Orca or other "screen reading" software. As long as the document exposes the contents in text form, we can let assistive technology pick it up and present it to the user in a different way (for example non-textual). An important goal is to transfer as much of the structure of the document as possible, so that ideally the sematics (this is a heading, here is normal text, page number) are preserved. Finding well working PDF solutions is still a challenge for blind people on any operating system. For now the focus will be on Orca since it's the best working screen reader on Linux used by most blind users.<br />
<br />
'''Knowledge Prerequisite:''' C++<br />
<br />
'''Mentor:''' Albert, Frederik helping out with the accessibility parts<br />
<br />
==== Project: Implement PDF Poppler features ====<br />
'''Brief explanation:''' Poppler has some support for features we don't support, implement them<br />
<br />
'''Expected results:''' Poppler has support for pdf layer views, tagged pdf support, linearized pdf support yet we in Okular don't offer that features to our users. The result from this project is having those exposed to the final users<br />
<br />
'''Knowledge Prerequisite:''' C++<br />
<br />
'''Mentor:''' Albert<br />
<br />
==== Project: Implement SecurityHandler V6 in Poppler ====<br />
'''Brief explanation:''' Poppler needs to support SecurityHandler V6 to be able to open some pdf files<br />
<br />
'''Expected results:''' Poppler (and hence Okular) can open files with SecurityHandler V6 like the ones in https://bugs.freedesktop.org/show_bug.cgi?id=85368 and https://bugs.freedesktop.org/show_bug.cgi?id=88151<br />
<br />
'''Knowledge Prerequisite:''' C++<br />
<br />
'''Mentor:''' Albert<br />
<br />
=== KDE Connect ===<br />
==== Project: Improve KDE Connect encryption ====<br />
'''Brief explanation:''' We want to implement a better encrypted protocol for KDE Connect, as discussed here: http://albertvaka.wordpress.com/2013/09/19/how-kde-connect-encryption-works/ I would like to see a solid and peer-reviewed design before accepting this project.<br />
<br />
'''Expected results:''' Have a secure encryption algorithm implemented in both KDE (C++/Qt) and Android (Java) clients.<br />
<br />
'''Knowledge Prerequisite:''' Deep knowledge about encryption and security.<br />
<br />
'''Mentor:''' Albert Vaca <albertvaka {+at+} gmail.com><br />
<br />
'''Resources:''' kdeconnect<br />
<br />
==== Project: Build a Qt-only multiplatform KDEConnect client ====<br />
'''Brief explanation:''' We want to implement a cross platform client written in Qt that can run in virtually any platform supported by Qt (Windows Phone, Jolla, iOS, OSX, etc.) using the QPA (Qt Platform Abstraction) and QML. It will be challenging because Qt5 for phones is still quite new and implementing some features might not be possible yet, but it will be worth it to investigate what is possible and what not, and even contribute patches to Qt for some aspects. A lot of the core classes used in KDE Connect for Plasma could be reused and shared because they are mostly Qt (and would be part of the GSOC to make sure they end only using Qt, so we can get to re-use them). Not every feature is going to be available to every platform, and some plugins will be platform-specific, but as part of this GSOC project I would love to see it running as good as possible in one of the platforms already mentioned, and with basic functionallity in a couple more. (That is: center it around a platform and make it work well there, writting platform-specific plugins and code if needed, but making sure it still compiles and runs in other platforms).<br />
<br />
'''Knowledge Prerequisite:''' Qt5 and building cross-platform code.<br />
<br />
'''Mentor:''' Albert Vaca <albertvaka {+at+} gmail.com><br />
<br />
'''Resources:''' kdeconnect<br />
=== Solid ===<br />
==== Project: Make Libbluedevil Async ====<br />
'''Brief explanation:''' Extend libbluedevil to have an asynchronous api, and port bluedevil to it.<br />
<br />
'''Expected results:''' libbluedevil should have an asynchronous api, and bluedevil should be ported to them.<br />
<br />
'''Knowledge Prerequisite:''' basic Qt and DBus<br />
<br />
'''Mentor:''' Àlex Fiestas <afiestas {+at+} kde.org><br />
<br />
'''Resources:''' libbluedevil, bluedevil, afiestas<br />
<br />
==== Project: Improve sharing experience ====<br />
'''Brief explanation:''' Improve the content sharing experience in Plasma by extending and improving Samba share, implementing other ways of sharing and write new ways of discovering other people's shares.<br />
<br />
'''Expected results:''' It should be possible to discover "shares" using dolphin (possibly via a new kioslave?) and it should be possible to share a folder between two Plasma computers really fast and easy (possibly implementing an http server plus discovery via avahi).<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt, extra points for KIO experience.<br />
<br />
'''Mentor:''' Àlex Fiestas <afiestas {+at+} kde.org><br />
<br />
'''Resources:''' avahi, http, kdenetwork-fileshare<br />
<br />
=== Muon ===<br />
==== Project: Better support for your distribution ====<br />
<br />
'''Brief explanation:''' Muon needs to be ensured to work perfectly on any distribution, this project should target one of the (major) distributions, enumerate the problems to solve and propose solutions.<br />
<br />
'''Expected results:''' Muon users of your distribution will be happy ever-after.<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt, the technology required for the platform<br />
<br />
'''Mentor:''' Aleix Pol<br />
<br />
<br />
=== KWin ===<br />
==== Project: DRM/KMS backend for kwin_wayland ====<br />
<br />
'''Brief explanation:'''<br />
KWin_wayland currently only supports rendering to another Wayland server. In future it should be possible to go down to the hardware directly. For this a DRM/KMS rendering backend is required. This requires that a new backend is implemented for the OpenGL compositor and maybe the QPainter compositor. As KWin needs to handle kernel mode settings in this mode the output information need to be queried from the hardware and an implementation for KWin::Screens needs to be provided and from there propagated to the Wayland clients. In addition if the time of the project permits it an interface should be exposed for KScreen to configure the outputs.<br />
<br />
'''Expected results:''' KWin_wayland can render to DRM/KMS and fetches output information from the hardware<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt, Wayland, KMS and C knowlege are from advantage<br />
<br />
'''Mentor:''' Martin Gräßlin <mgraesslin@kde.org><br />
<br />
===Trojitá===<br />
<br />
[http://trojita.flaska.net/ Trojitá] is a fast IMAP e-mail client. Since late 2012, it is a part of KDE's extragear. The project focuses on delivering a usable, fast, standards-compliant, cross-platform and reliable e-mail client which can scale from cell phones to huge e-mail archives without annoying slowdowns.<br />
<br />
==== Project: Port to BlackBerry OS 10 ====<br />
<br />
'''Brief explanation:'''<br />
This work involves improving the separation of business logic from the UI concerns, an effort started and well-underway due to the Ubuntu Touch project, and adding a new GUI wirrten in QML for BlackBerry OS 10.<br />
<br />
'''Expected results:''' Trojitá running on BlackBerry Z10 with basic features, including reading and writing e-mails<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt, QML<br />
<br />
'''Mentor:''' Jan Kundrát <jkt@kde.org><br />
<br />
=== Gluon ===<br />
[http://gamingfreedom.org Gluon] is a project to build a Qt and KDE based game engine and game development tool. The engine is designed to support both mobile and desktop game development. We have ported the engine to Qt5 last year and are currently working on releasing a first Qt5 based version.<br />
<br />
==== Project: Build a QtQml based script system ====<br />
'''Brief explanation:''' In Qt4 QtScript was the solution to scripting support for applications. With the port to Qt5 the new QtQml module was introduced, including a new scripting system, but QtScript was still available. With Qt5.5 QtScript is planned to be deprecated and completely removed in Qt5.6. This means that our scripting system, which is currently built on QtScript, needs to be ported to QtQml.<br />
<br />
'''Expected results:''' A scripting system that can be used to write scripts for games.<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt at least. Experience with QtQuick/QML is a strong advantage.<br />
<br />
'''Mentor:''' Arjen Hiemstra<br />
<br />
==== Project: Expand Gluon Input ====<br />
'''Brief explanation:''' During the port to Qt5 we also overhauled the input system in Gluon to be more capable. However, we kept the implementation rather limited since we also had other elements to work on. This project would expand GluonInput with support for additional devices and platforms.<br />
<br />
'''Expected results:''' Additional platform and device plugins for GluonInput.<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt at least. Experience with platform-specific input libraries like XInput2 for Xorg is an advantage.<br />
<br />
'''Mentor:''' Arjen Hiemstra<br />
<br />
[[Category:Mentoring]]<br />
<br />
=== Krita ===<br />
[http://www.krita.org Krita] is an advanced 2D painting application. It support creating images from scratch from begin to end. Krita is a complex application and developers need to have a fair amount of experience in order to be able to do something.<br />
<br />
==== Project: Integrate Animation in Krita's core ====<br />
'''Brief explanation:''' We have gone through three iterations of animation support code in Krita. With this experience, it's become clear that we need to work the support for animatins right into Krita's core engine. This project comprises partly that, and partly updating the existing animation gui that was created in 2014.<br />
<br />
'''Expected results:''' by the end of the summer, the animation support in Krita should be ready for end-users to create 2D animations with, whether for game sprites or short cartoons. <br />
<br />
'''Knowledge Prerequisite:''' C++/Qt at least.<br />
<br />
'''Mentor:''' Boudewijn Rempt<br />
<br />
==== Project: Add Python Scripting to Krita ====<br />
'''Brief explanation:''' Krita has had two attempts at scripting support: through kjs and through kross. Neither was good enough. The VFXindustry standard for scripting is Python, and the goal of project is to integrate Python and PyQt directly into Krita.<br />
<br />
'''Expected results:''' by the end of the summer, users should be able to automate repetitive tasks, file import and export and add gui elements such as dockers, all written in PyQt.<br />
<br />
'''Knowledge Prerequisite:''' Deep knowledge of Python, SIP, C++ and Qt.<br />
<br />
'''Mentor:''' Boudewijn Rempt<br />
<br />
==== Project: Improve Normal Mapping Workflow ====<br />
'''Brief explanation:''' Normal maps are textures that describe surface detail on a 3d model by describing how much each pixel deviates from the surface the texture is put on. A normal map gives the ability to tell the renderer there's a different normal per texel(texture pixel), this way, you can describe subtle differences in surface without requiring the polygons for it. It does so by describing the normal angle to the surface by using the R, G and B channels. Now, normal maps, due to them being quite mathematical, are usually baked. But these bakes are not always perfect. furthermore, there's a lot of interest into handpainting textures, amongst which normal maps.<br />
<br />
'''Expected results:''' by the end of the summer, a new brush engine, which takes the tilt-direction and has that control the redness and greenness. And then takes the tilt-elevation, and has that control the blueness.<br />
<br />
'''Knowledge Prerequisite:''' knowledge of C++, Qt. and mathematics<br />
<br />
'''Mentor:''' Boudewijn Rempt<br />
<br />
===Calligra===<br />
==== Project: Variable thickness lines ====<br />
<br />
'''Brief explanation:''' One of the most fundamental basics of drawing is varying the width of your lines to show shape, form and perspective. Almost every line tapers at either end, and often gets thicker and thinner in different places as needed. For purely technical and histrorical reasons though, every vector program (Illustrator, Inkscape, Karbon etc) make curves all one hard width. <br />
This proposal is to create a variable width path shape / tool, much like the path tool, would allow drawing curves, but where each node could have its width set so that the line width changed smoothly from node to node. <br />
As a plugin for the Calligra suite, this would clearly benefit apps as Karbon and also Krita.<br />
<br />
'''Expected results:''' variable width path tool is able to change the width of any path node to an arbitary percentage (say 155%) of the stroke width. See http://bugsfiles.kde.org/attachment.cgi?id=56995 for mockup. The shape needs to be able to save and load in svg/odf.<br />
<br />
'''Knowledge Prerequisite:''' C++, Qt, SVG<br />
<br />
'''Mentor:''' Thorsten Zachmann < zachmann @ kde dot org ><br />
<br />
=== KIOSK ===<br />
==== Project: KIOSK Tool ====<br />
<br />
'''Brief explanation:''' Back in KDE 3 there was a tool to help administrators to configure the KDE Kiosk framework. The idea of this project is to start working on a new tool. The new application should be developed in close collaboration with the Visual Design Group to get a useful application for the targeted audience.<br />
<br />
'''Expected results:''' a functional prototype for a new Kiosk tool with a working backend to configure and restrict actions and configuration options.<br />
<br />
'''Knowledge Prerequisite:''' C++/Qt<br />
<br />
'''Mentor:''' Martin Gräßlin <mgraesslin@kde.org><br />
<br />
=== Kubuntu ===<br />
==== Project: Port Ubiquity to Qt 5 ====<br />
<br />
'''Brief explanation:''' Ubiquity is the installer for Kubuntu. It should be ported to Qt 5. It is written in Python and can be fiddly to test because much of the development needs to be done on a live system. Once the Qt 5 port is complete there are numerous other bugs that can be fixed. Drop into #kubuntu-devel to say hi. Code is in launchpad.net/ubiquity.<br />
<br />
'''Expected results:''' Ubiquity bug free and running with Qt 5<br />
<br />
'''Knowledge Prerequisite:''' Python, PyQt<br />
<br />
'''Mentor:''' Jonathan Riddell</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2014/Work&diff=38947Sprints/Randa/2014/Work2014-08-12T09:16:01Z<p>Leinir: /* Monday, 11th of August */</p>
<hr />
<div>This is a new thing I (Mario) would like to try this year. At the end of every day everybody should take some minutes to write what she or he has done or learned this day at the Randa Meetings. Just some words or a sentence or a link to his or her blog post ;-).<br />
<br />
== Saturday, 9th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|Christian Esken<br />
|High-DPI support. https://git.reviewboard.kde.org/r/110399/<br />
|-<br />
|Valorie Zimmerman<br />
|met with team, created logins, sample chapters, discussed plans<br />
|-<br />
|Bruno Friedmann<br />
|met with team, setup computer's rooms, help here and there<br />
|-<br />
|Cristian Oneț<br />
|arrived, met people<br />
|-<br />
|Anton Kreuzkamp<br />
|Fixed some basic stuff in QmlWeb, I broke before.<br />
|-<br />
|Felix Rohrbach<br />
|Started porting GluonCreator to Qt5/KF5<br />
|-<br />
|Arjen Hiemstra<br />
|Arrival, planning discussions, some work on GluonInput. Merge Qt 5 branch to master.<br />
|-<br />
|Dan Leinir Turthra Jensen<br />
|Arrival and porting of GluonSmarts library to Qt5 and the new CMake system<br />
|-<br />
| Myriam Schweingruber<br />
| arrived rather late, tried to work, bad connections, went to bed rather early, closed a few obsolete bugs.<br />
|}<br />
<br />
== Sunday, 10th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|Christian Esken<br />
|Improve "Select Master Channel" dialog : https://git.reviewboard.kde.org/r/110645/<br />
|-<br />
|Valorie Zimmerman<br />
|met with Frameworks devels, discussed plans, cloned git repo [kde:scratch/garg/book], began editing content<br />
|-<br />
|Bruno Friedmann<br />
|cloned git repo, began creating cover's book drafts, welcome new french comers, publish the sat-sun picture made by Françoise on [https://plus.google.com/109140068131989370067/posts/HLe3hTa5WBh G+ profile] :-)<br />
|-<br />
|Cristian Oneț<br />
|KDE SDK on Windows meeting, started moving away KMyMoney from KDELibs4Support deprecated classes, updating my Windows frameworks build<br />
|-<br />
|Harald Sitter<br />
|Hackin' & Slashin'. Started to write a volume control application directly based on PulseAudio. Currently still working on the non-gui bits putting Qtness on top of the PulseAudio API. Discussed possibility of abandoning most of the Phonon 5 backend architecture and basing it primarily on libvlc.<br />
|-<br />
|Rohan Garg<br />
|Discussed plans for the book, started writing one of the first chapters, participated in the KDE SDK tooling discussion as well as the third party app developer story around KDE Frameworks 5<br />
|-<br />
|Andreas Cord-Landwehr<br />
|First KF5 porting session for Artikulate: it builds.<br />
|-<br />
|Anton Kreuzkamp<br />
|Fixed some basic stuff in QmlWeb, I broke before. Implemented support for attached properties (turned out to be a 10 minutes effort).<br />
|-<br />
|David Narvaez<br />
|Advanced Kig's port to Frameworks, only a couple of issues awa from a complete compilation<br />
|-<br />
|Arjen Hiemstra<br />
|Ported GluonGraphics to Qt5. Continued work on GluonInput.<br />
|-<br />
|Dan Leinir Turthra Jensen<br />
|Porting of GluonSmarts editor to Qt5<br />
|-<br />
| Myriam Schweingruber<br />
| triaged 84 Bugs, half Phonon, half Amarok<br />
|-<br />
|Felix Rohrbach<br />
|Continued to port GluonCreator, finished its library port<br />
|}<br />
<br />
== Monday, 11th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|Valorie Zimmerman<br />
|http://linuxgrandma.blogspot.ch/2014/08/randa-meetings-sprint-kde-frameworks.html<br />
|- <br />
|Bruno Friedmann<br />
|Fix external customers trouble, KDe book finish svg template and markdown text file, continue to publish picture album on [https://plus.google.com/109140068131989370067/posts/UrGKTEmnGpa G+]<br />
|- <br />
|Françoise Wybrecht & Lucie Robin<br />
|Writing Lucie interview for dot.kde.org, Start making video interview of participants and groups : aka create the Press Randa Team :-) <br />
|-<br />
|Arjen Hiemstra<br />
|Finished GluonInput rewrite. Discussed GluonAudio plans. Started work on proper plugin loading system.<br />
|-<br />
|Dan Leinir Turthra Jensen<br />
|Begin work on node editor for Gluon (based on ALGOholic's and NukeEngine's work)<br />
|-<br />
|Cristian Oneț<br />
|Updated and pushed KMyMoney Windows build scripts (mpir, alkimia, kmymoney) so now KMyMoney using frameworks can be build on Windows (using MSVC 2013). Continued porting away from KDELibs4Support. Built Kate on Windows and submitted the fixes which were needed to do this. <br />
|-<br />
|Harald Sitter<br />
|Dicussed possibility of automated dependency generation based on CMake data. Worked on pulseaudio based volume control https://apachelog.wordpress.com/2014/08/11/volume/ . Discussed KMix KF5 port possibility.<br />
|-<br />
|David Narvaez<br />
|Ported enough of Kig's code to KDE Frameworks to be able to compile the whole application. Currently not starting properly and missing the KUniqueApplication behavior.<br />
|-<br />
|Felix Rohrbach<br />
|Finished GluonCreator port, still some bugs with the loading of plugins. Discussed the GluonAudio design and started a rewrite of it.<br />
|}<br />
<br />
== Tuesday, 12th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|?<br />
|?<br />
|}<br />
<br />
== Wednesday, 13th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|?<br />
|?<br />
|}<br />
<br />
== Thursday, 14th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|?<br />
|?<br />
|}<br />
<br />
== Friday, 15th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|?<br />
|?<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2014/Work&diff=38946Sprints/Randa/2014/Work2014-08-12T09:15:05Z<p>Leinir: /* Sunday, 10th of August */</p>
<hr />
<div>This is a new thing I (Mario) would like to try this year. At the end of every day everybody should take some minutes to write what she or he has done or learned this day at the Randa Meetings. Just some words or a sentence or a link to his or her blog post ;-).<br />
<br />
== Saturday, 9th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|Christian Esken<br />
|High-DPI support. https://git.reviewboard.kde.org/r/110399/<br />
|-<br />
|Valorie Zimmerman<br />
|met with team, created logins, sample chapters, discussed plans<br />
|-<br />
|Bruno Friedmann<br />
|met with team, setup computer's rooms, help here and there<br />
|-<br />
|Cristian Oneț<br />
|arrived, met people<br />
|-<br />
|Anton Kreuzkamp<br />
|Fixed some basic stuff in QmlWeb, I broke before.<br />
|-<br />
|Felix Rohrbach<br />
|Started porting GluonCreator to Qt5/KF5<br />
|-<br />
|Arjen Hiemstra<br />
|Arrival, planning discussions, some work on GluonInput. Merge Qt 5 branch to master.<br />
|-<br />
|Dan Leinir Turthra Jensen<br />
|Arrival and porting of GluonSmarts library to Qt5 and the new CMake system<br />
|-<br />
| Myriam Schweingruber<br />
| arrived rather late, tried to work, bad connections, went to bed rather early, closed a few obsolete bugs.<br />
|}<br />
<br />
== Sunday, 10th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|Christian Esken<br />
|Improve "Select Master Channel" dialog : https://git.reviewboard.kde.org/r/110645/<br />
|-<br />
|Valorie Zimmerman<br />
|met with Frameworks devels, discussed plans, cloned git repo [kde:scratch/garg/book], began editing content<br />
|-<br />
|Bruno Friedmann<br />
|cloned git repo, began creating cover's book drafts, welcome new french comers, publish the sat-sun picture made by Françoise on [https://plus.google.com/109140068131989370067/posts/HLe3hTa5WBh G+ profile] :-)<br />
|-<br />
|Cristian Oneț<br />
|KDE SDK on Windows meeting, started moving away KMyMoney from KDELibs4Support deprecated classes, updating my Windows frameworks build<br />
|-<br />
|Harald Sitter<br />
|Hackin' & Slashin'. Started to write a volume control application directly based on PulseAudio. Currently still working on the non-gui bits putting Qtness on top of the PulseAudio API. Discussed possibility of abandoning most of the Phonon 5 backend architecture and basing it primarily on libvlc.<br />
|-<br />
|Rohan Garg<br />
|Discussed plans for the book, started writing one of the first chapters, participated in the KDE SDK tooling discussion as well as the third party app developer story around KDE Frameworks 5<br />
|-<br />
|Andreas Cord-Landwehr<br />
|First KF5 porting session for Artikulate: it builds.<br />
|-<br />
|Anton Kreuzkamp<br />
|Fixed some basic stuff in QmlWeb, I broke before. Implemented support for attached properties (turned out to be a 10 minutes effort).<br />
|-<br />
|David Narvaez<br />
|Advanced Kig's port to Frameworks, only a couple of issues awa from a complete compilation<br />
|-<br />
|Arjen Hiemstra<br />
|Ported GluonGraphics to Qt5. Continued work on GluonInput.<br />
|-<br />
|Dan Leinir Turthra Jensen<br />
|Porting of GluonSmarts editor to Qt5<br />
|-<br />
| Myriam Schweingruber<br />
| triaged 84 Bugs, half Phonon, half Amarok<br />
|-<br />
|Felix Rohrbach<br />
|Continued to port GluonCreator, finished its library port<br />
|}<br />
<br />
== Monday, 11th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|Valorie Zimmerman<br />
|http://linuxgrandma.blogspot.ch/2014/08/randa-meetings-sprint-kde-frameworks.html<br />
|- <br />
|Bruno Friedmann<br />
|Fix external customers trouble, KDe book finish svg template and markdown text file, continue to publish picture album on [https://plus.google.com/109140068131989370067/posts/UrGKTEmnGpa G+]<br />
|- <br />
|Françoise Wybrecht & Lucie Robin<br />
|Writing Lucie interview for dot.kde.org, Start making video interview of participants and groups : aka create the Press Randa Team :-) <br />
|-<br />
|Arjen Hiemstra<br />
|Finished GluonInput rewrite. Discussed GluonAudio plans. Started work on proper plugin loading system.<br />
|-<br />
|Cristian Oneț<br />
|Updated and pushed KMyMoney Windows build scripts (mpir, alkimia, kmymoney) so now KMyMoney using frameworks can be build on Windows (using MSVC 2013). Continued porting away from KDELibs4Support. Built Kate on Windows and submitted the fixes which were needed to do this. <br />
|-<br />
|Harald Sitter<br />
|Dicussed possibility of automated dependency generation based on CMake data. Worked on pulseaudio based volume control https://apachelog.wordpress.com/2014/08/11/volume/ . Discussed KMix KF5 port possibility.<br />
|-<br />
|David Narvaez<br />
|Ported enough of Kig's code to KDE Frameworks to be able to compile the whole application. Currently not starting properly and missing the KUniqueApplication behavior.<br />
|-<br />
|Felix Rohrbach<br />
|Finished GluonCreator port, still some bugs with the loading of plugins. Discussed the GluonAudio design and started a rewrite of it.<br />
|}<br />
<br />
== Tuesday, 12th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|?<br />
|?<br />
|}<br />
<br />
== Wednesday, 13th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|?<br />
|?<br />
|}<br />
<br />
== Thursday, 14th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|?<br />
|?<br />
|}<br />
<br />
== Friday, 15th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|?<br />
|?<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2014/Work&diff=38945Sprints/Randa/2014/Work2014-08-12T09:14:31Z<p>Leinir: /* Saturday, 9th of August */</p>
<hr />
<div>This is a new thing I (Mario) would like to try this year. At the end of every day everybody should take some minutes to write what she or he has done or learned this day at the Randa Meetings. Just some words or a sentence or a link to his or her blog post ;-).<br />
<br />
== Saturday, 9th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|Christian Esken<br />
|High-DPI support. https://git.reviewboard.kde.org/r/110399/<br />
|-<br />
|Valorie Zimmerman<br />
|met with team, created logins, sample chapters, discussed plans<br />
|-<br />
|Bruno Friedmann<br />
|met with team, setup computer's rooms, help here and there<br />
|-<br />
|Cristian Oneț<br />
|arrived, met people<br />
|-<br />
|Anton Kreuzkamp<br />
|Fixed some basic stuff in QmlWeb, I broke before.<br />
|-<br />
|Felix Rohrbach<br />
|Started porting GluonCreator to Qt5/KF5<br />
|-<br />
|Arjen Hiemstra<br />
|Arrival, planning discussions, some work on GluonInput. Merge Qt 5 branch to master.<br />
|-<br />
|Dan Leinir Turthra Jensen<br />
|Arrival and porting of GluonSmarts library to Qt5 and the new CMake system<br />
|-<br />
| Myriam Schweingruber<br />
| arrived rather late, tried to work, bad connections, went to bed rather early, closed a few obsolete bugs.<br />
|}<br />
<br />
== Sunday, 10th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|Christian Esken<br />
|Improve "Select Master Channel" dialog : https://git.reviewboard.kde.org/r/110645/<br />
|-<br />
|Valorie Zimmerman<br />
|met with Frameworks devels, discussed plans, cloned git repo [kde:scratch/garg/book], began editing content<br />
|-<br />
|Bruno Friedmann<br />
|cloned git repo, began creating cover's book drafts, welcome new french comers, publish the sat-sun picture made by Françoise on [https://plus.google.com/109140068131989370067/posts/HLe3hTa5WBh G+ profile] :-)<br />
|-<br />
|Cristian Oneț<br />
|KDE SDK on Windows meeting, started moving away KMyMoney from KDELibs4Support deprecated classes, updating my Windows frameworks build<br />
|-<br />
|Harald Sitter<br />
|Hackin' & Slashin'. Started to write a volume control application directly based on PulseAudio. Currently still working on the non-gui bits putting Qtness on top of the PulseAudio API. Discussed possibility of abandoning most of the Phonon 5 backend architecture and basing it primarily on libvlc.<br />
|-<br />
|Rohan Garg<br />
|Discussed plans for the book, started writing one of the first chapters, participated in the KDE SDK tooling discussion as well as the third party app developer story around KDE Frameworks 5<br />
|-<br />
|Andreas Cord-Landwehr<br />
|First KF5 porting session for Artikulate: it builds.<br />
|-<br />
|Anton Kreuzkamp<br />
|Fixed some basic stuff in QmlWeb, I broke before. Implemented support for attached properties (turned out to be a 10 minutes effort).<br />
|-<br />
|David Narvaez<br />
|Advanced Kig's port to Frameworks, only a couple of issues awa from a complete compilation<br />
|-<br />
|Arjen Hiemstra<br />
|Ported GluonGraphics to Qt5. Continued work on GluonInput.<br />
|-<br />
| Myriam Schweingruber<br />
| triaged 84 Bugs, half Phonon, half Amarok<br />
|-<br />
|Felix Rohrbach<br />
|Continued to port GluonCreator, finished its library port<br />
|}<br />
<br />
== Monday, 11th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|Valorie Zimmerman<br />
|http://linuxgrandma.blogspot.ch/2014/08/randa-meetings-sprint-kde-frameworks.html<br />
|- <br />
|Bruno Friedmann<br />
|Fix external customers trouble, KDe book finish svg template and markdown text file, continue to publish picture album on [https://plus.google.com/109140068131989370067/posts/UrGKTEmnGpa G+]<br />
|- <br />
|Françoise Wybrecht & Lucie Robin<br />
|Writing Lucie interview for dot.kde.org, Start making video interview of participants and groups : aka create the Press Randa Team :-) <br />
|-<br />
|Arjen Hiemstra<br />
|Finished GluonInput rewrite. Discussed GluonAudio plans. Started work on proper plugin loading system.<br />
|-<br />
|Cristian Oneț<br />
|Updated and pushed KMyMoney Windows build scripts (mpir, alkimia, kmymoney) so now KMyMoney using frameworks can be build on Windows (using MSVC 2013). Continued porting away from KDELibs4Support. Built Kate on Windows and submitted the fixes which were needed to do this. <br />
|-<br />
|Harald Sitter<br />
|Dicussed possibility of automated dependency generation based on CMake data. Worked on pulseaudio based volume control https://apachelog.wordpress.com/2014/08/11/volume/ . Discussed KMix KF5 port possibility.<br />
|-<br />
|David Narvaez<br />
|Ported enough of Kig's code to KDE Frameworks to be able to compile the whole application. Currently not starting properly and missing the KUniqueApplication behavior.<br />
|-<br />
|Felix Rohrbach<br />
|Finished GluonCreator port, still some bugs with the loading of plugins. Discussed the GluonAudio design and started a rewrite of it.<br />
|}<br />
<br />
== Tuesday, 12th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|?<br />
|?<br />
|}<br />
<br />
== Wednesday, 13th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|?<br />
|?<br />
|}<br />
<br />
== Thursday, 14th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|?<br />
|?<br />
|}<br />
<br />
== Friday, 15th of August ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Comment or Link<br />
|- <br />
|Your name<br />
|Your comment or link to your blog post<br />
|-<br />
|?<br />
|?<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2014/Travel&diff=38665Sprints/Randa/2014/Travel2014-07-28T07:57:06Z<p>Leinir: /* Departure */</p>
<hr />
<div>Please add below the information about your dates and times of arrival and departure. By type we mean the means of your transportation.<br />
<br />
== Arrival ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Type<br />
! Date<br />
! Time<br />
! Comment<br />
|- <br />
|Mario Fux<br />
|by foot<br />
|9th August<br />
|around 15:00<br />
|Nothing to add ;-)<br />
|-<br />
|Cristian Oneț<br />
|Car<br />
|9th August<br />
|around 19:00<br />
|<br />
|-<br />
|Aleix Pol<br />
|Plane, GVA<br />
|9th August<br />
|10:30<br />
|<br />
|-<br />
|David Edmundson<br />
|Plane, GVA<br />
|9th August<br />
|10:00<br />
|<br />
|-<br />
|Vishesh Handa<br />
|Plane, GVA<br />
|9th August<br />
|10:30<br />
|Actually arriving on the 8th, but I'll spend a day in Geneva.<br />
|-<br />
|Dan Leinir Turthra Jensen<br />
|Plane, ZRH<br />
|9th August<br />
|11:00<br />
|<br />
|-<br />
|Àlex Fiestas<br />
|Plane, GVA<br />
|9th August<br />
|10:30<br />
|Actually arriving on the 8th, but I'll spend a day in Geneva.<br />
|-<br />
|Martin Klapetek<br />
|Car<br />
|10th August<br />
|evening<br />
|<br />
|-<br />
|Rohan Garg<br />
|Plane, ZRH<br />
|9th August<br />
|9:00<br />
|<br />
|-<br />
|Felix Rohrbach<br />
|Train<br />
|9th August<br />
|12:30<br />
|<br />
|-<br />
|Nicolás Alvarez<br />
|Plane, ZRH<br />
|8th August<br />
|15:25<br />
|Staying with Pascal Mages for the day before Randa<br />
|-<br />
|Valorie Zimmerman<br />
|Plane, GVA<br />
|8th August<br />
|10:00<br />
|I hope to see some of Geneva, then hand out tickets the next day<br />
|<br />
|-<br />
|Sanjiban Bairagya<br />
|Plane, ZRH<br />
|9th August<br />
|6:20<br />
|<br />
|-<br />
|Vijay Dhameliya<br />
|Plane, ZRH<br />
|9th August<br />
|6:20<br />
|<br />
|-<br />
| Daniel Vrátil<br />
| Plane, ZRH<br />
| 10th August<br />
| 15:30<br />
|<br />
|-<br />
| Denis Steckelmacher<br />
| Train, Lausanne<br />
| 9th August<br />
| 15:43<br />
|<br />
|-<br />
| Holger Kälberer<br />
| Car<br />
| 9th August<br />
| (late) evening<br />
|<br />
|-<br />
| Kevin Funk<br />
| Plane, ZRH<br />
| 9th August<br />
| 08:20<br />
|<br />
|-<br />
| Arjen Hiemstra<br />
| Plane, GVA<br />
| 9th August<br />
| 11:05<br />
|<br />
|-<br />
| Manuel Nickschas<br />
| car<br />
| 9th August<br />
| evening<br />
|<br />
|-<br />
| Myriam Schweingruber<br />
| car <br />
| 9th August<br />
| evening<br />
| travelling with Manuel<br />
|-<br />
| Mark Kretschmann<br />
| car<br />
| 9th August<br />
| evening<br />
| travelling with Manuel<br />
|-<br />
| Joseph Wenninger (+Erminia Maltri)<br />
| car<br />
| 9th August<br />
| around 12:00<br />
|<br />
|-<br />
|Till Theato<br />
|Train<br />
|9th August<br />
|14:55<br />
|<br />
|-<br />
|Christian Esken<br />
|Plane, ZRH<br />
|9th August<br />
|14:15 at ZRH<br />
|<br />
|-<br />
|Bruno Coudoin<br />
|Plane, GVA<br />
|10th August<br />
|13:00 at GVA<br />
|<br />
|-<br />
|Vincent Pinon<br />
|car<br />
|10th August<br />
|around 18:00<br />
|departure/arrival depend on baby<br />
|-<br />
|Harald Sitter<br />
|choochoo<br />
|9th August<br />
|evening<br />
|going through Zurich<br />
|-<br />
|David Narvaez<br />
|Plane, ZRH<br />
|9th August<br />
|10:50<br />
|<br />
|}<br />
<br />
== Departure ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Type<br />
! Date<br />
! Time<br />
! Comment<br />
|- <br />
|Mario Fux<br />
|by foot<br />
|15th August<br />
|until everybody left<br />
|Nothing to add ;-)<br />
|-<br />
|Cristian Oneț<br />
|Car<br />
|15th August<br />
|in the morning<br />
|<br />
|-<br />
|Aleix Pol<br />
|Plane, GVA<br />
|15th August<br />
|19:00<br />
|<br />
|-<br />
|David Edmundson<br />
|Plane, GVA<br />
|15th August<br />
|19:00<br />
|<br />
|-<br />
|Vishesh Handa<br />
|Plane, GVA<br />
|15th August<br />
|19:00<br />
|<br />
|-<br />
|Àlex Fiestas<br />
|Plane, GVA<br />
|15th August<br />
|19:00<br />
|<br />
|-<br />
|Martin Klapetek<br />
|Car<br />
|14th August<br />
|afternoon<br />
|<br />
|-<br />
|Felix Rohrbach<br />
|Train<br />
|15th August<br />
|15:00<br />
|<br />
|-<br />
|Nicolás Alvarez<br />
|Plane, ZRH<br />
|17th August<br />
|17:10<br />
|Staying at a hotel after Randa<br />
|-<br />
|Valorie Zimmerman<br />
|Plane, GVA<br />
|15th August<br />
|13:10<br />
|I hope that is time enough for the train from Randa!<br />
|-<br />
|Sanjiban Bairagya<br />
|Plane, ZRH<br />
|16th August<br />
|12:45<br />
|It is the plane which departs at 12:45 pm :)<br />
|-<br />
|Vijay Dhameliya<br />
|Plane, ZRH<br />
|15th August<br />
|09:45<br />
|<br />
|-<br />
| Daniel Vrátil<br />
| Plane, ZRH<br />
| 15th August<br />
| 21:15<br />
|<br />
|-<br />
| Denis Steckelmacher<br />
| Train from Lausanne<br />
| 15th August<br />
| 12:24<br />
|<br />
|-<br />
| Rohan Garg<br />
| Plane, BSL<br />
| 15th August<br />
| 19:45<br />
|<br />
|-<br />
| Holger Kälberer<br />
| Car<br />
| 15th August<br />
| morning<br />
|<br />
|-<br />
| Kevin Funk<br />
| Plane, ZRH<br />
| 15th August<br />
| 18:00<br />
|<br />
|-<br />
| Arjen Hiemstra<br />
| Plane, GVA<br />
| 15th August<br />
| 17:00<br />
|<br />
|-<br />
| Joseph WenningerWenninger (+Erminia Maltri)<br />
| car<br />
| 14th August<br />
| around 12:00<br />
|<br />
|-<br />
|Till Theato<br />
|Train<br />
|15th August<br />
|10:55<br />
|<br />
|-<br />
|Christian Esken<br />
|Plane, ZRH<br />
|15th August<br />
|16:45 from ZRH<br />
|<br />
|-<br />
|Bruno Coudoin<br />
|Plane, GVA<br />
|15th August<br />
|13:40 from GVA<br />
|<br />
|-<br />
|Vincent Pinon<br />
|car<br />
|14th August<br />
|leave around 15:00<br />
|<br />
|-<br />
|Harald Sitter<br />
|choochoo<br />
|15th August<br />
|before noon<br />
|going through Zurich<br />
|-<br />
|David Narvaez<br />
|Plane, ZRH<br />
|18th August<br />
|13:00<br />
|Doing some tourism after Randa<br />
|-<br />
|Dan Leinir Turthra Jensen<br />
|plane, ZRH<br />
|16th August<br />
|07.15 from ZRH<br />
|As the plane departs very early, i will need to actually depart Randa the previous night<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2014/Travel&diff=38664Sprints/Randa/2014/Travel2014-07-28T07:56:44Z<p>Leinir: /* Departure */</p>
<hr />
<div>Please add below the information about your dates and times of arrival and departure. By type we mean the means of your transportation.<br />
<br />
== Arrival ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Type<br />
! Date<br />
! Time<br />
! Comment<br />
|- <br />
|Mario Fux<br />
|by foot<br />
|9th August<br />
|around 15:00<br />
|Nothing to add ;-)<br />
|-<br />
|Cristian Oneț<br />
|Car<br />
|9th August<br />
|around 19:00<br />
|<br />
|-<br />
|Aleix Pol<br />
|Plane, GVA<br />
|9th August<br />
|10:30<br />
|<br />
|-<br />
|David Edmundson<br />
|Plane, GVA<br />
|9th August<br />
|10:00<br />
|<br />
|-<br />
|Vishesh Handa<br />
|Plane, GVA<br />
|9th August<br />
|10:30<br />
|Actually arriving on the 8th, but I'll spend a day in Geneva.<br />
|-<br />
|Dan Leinir Turthra Jensen<br />
|Plane, ZRH<br />
|9th August<br />
|11:00<br />
|<br />
|-<br />
|Àlex Fiestas<br />
|Plane, GVA<br />
|9th August<br />
|10:30<br />
|Actually arriving on the 8th, but I'll spend a day in Geneva.<br />
|-<br />
|Martin Klapetek<br />
|Car<br />
|10th August<br />
|evening<br />
|<br />
|-<br />
|Rohan Garg<br />
|Plane, ZRH<br />
|9th August<br />
|9:00<br />
|<br />
|-<br />
|Felix Rohrbach<br />
|Train<br />
|9th August<br />
|12:30<br />
|<br />
|-<br />
|Nicolás Alvarez<br />
|Plane, ZRH<br />
|8th August<br />
|15:25<br />
|Staying with Pascal Mages for the day before Randa<br />
|-<br />
|Valorie Zimmerman<br />
|Plane, GVA<br />
|8th August<br />
|10:00<br />
|I hope to see some of Geneva, then hand out tickets the next day<br />
|<br />
|-<br />
|Sanjiban Bairagya<br />
|Plane, ZRH<br />
|9th August<br />
|6:20<br />
|<br />
|-<br />
|Vijay Dhameliya<br />
|Plane, ZRH<br />
|9th August<br />
|6:20<br />
|<br />
|-<br />
| Daniel Vrátil<br />
| Plane, ZRH<br />
| 10th August<br />
| 15:30<br />
|<br />
|-<br />
| Denis Steckelmacher<br />
| Train, Lausanne<br />
| 9th August<br />
| 15:43<br />
|<br />
|-<br />
| Holger Kälberer<br />
| Car<br />
| 9th August<br />
| (late) evening<br />
|<br />
|-<br />
| Kevin Funk<br />
| Plane, ZRH<br />
| 9th August<br />
| 08:20<br />
|<br />
|-<br />
| Arjen Hiemstra<br />
| Plane, GVA<br />
| 9th August<br />
| 11:05<br />
|<br />
|-<br />
| Manuel Nickschas<br />
| car<br />
| 9th August<br />
| evening<br />
|<br />
|-<br />
| Myriam Schweingruber<br />
| car <br />
| 9th August<br />
| evening<br />
| travelling with Manuel<br />
|-<br />
| Mark Kretschmann<br />
| car<br />
| 9th August<br />
| evening<br />
| travelling with Manuel<br />
|-<br />
| Joseph Wenninger (+Erminia Maltri)<br />
| car<br />
| 9th August<br />
| around 12:00<br />
|<br />
|-<br />
|Till Theato<br />
|Train<br />
|9th August<br />
|14:55<br />
|<br />
|-<br />
|Christian Esken<br />
|Plane, ZRH<br />
|9th August<br />
|14:15 at ZRH<br />
|<br />
|-<br />
|Bruno Coudoin<br />
|Plane, GVA<br />
|10th August<br />
|13:00 at GVA<br />
|<br />
|-<br />
|Vincent Pinon<br />
|car<br />
|10th August<br />
|around 18:00<br />
|departure/arrival depend on baby<br />
|-<br />
|Harald Sitter<br />
|choochoo<br />
|9th August<br />
|evening<br />
|going through Zurich<br />
|-<br />
|David Narvaez<br />
|Plane, ZRH<br />
|9th August<br />
|10:50<br />
|<br />
|}<br />
<br />
== Departure ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Type<br />
! Date<br />
! Time<br />
! Comment<br />
|- <br />
|Mario Fux<br />
|by foot<br />
|15th August<br />
|until everybody left<br />
|Nothing to add ;-)<br />
|-<br />
|Cristian Oneț<br />
|Car<br />
|15th August<br />
|in the morning<br />
|<br />
|-<br />
|Aleix Pol<br />
|Plane, GVA<br />
|15th August<br />
|19:00<br />
|<br />
|-<br />
|David Edmundson<br />
|Plane, GVA<br />
|15th August<br />
|19:00<br />
|<br />
|-<br />
|Vishesh Handa<br />
|Plane, GVA<br />
|15th August<br />
|19:00<br />
|<br />
|-<br />
|Àlex Fiestas<br />
|Plane, GVA<br />
|15th August<br />
|19:00<br />
|<br />
|-<br />
|Martin Klapetek<br />
|Car<br />
|14th August<br />
|afternoon<br />
|<br />
|-<br />
|Felix Rohrbach<br />
|Train<br />
|15th August<br />
|15:00<br />
|<br />
|-<br />
|Nicolás Alvarez<br />
|Plane, ZRH<br />
|17th August<br />
|17:10<br />
|Staying at a hotel after Randa<br />
|-<br />
|Valorie Zimmerman<br />
|Plane, GVA<br />
|15th August<br />
|13:10<br />
|I hope that is time enough for the train from Randa!<br />
|-<br />
|Sanjiban Bairagya<br />
|Plane, ZRH<br />
|16th August<br />
|12:45<br />
|It is the plane which departs at 12:45 pm :)<br />
|-<br />
|Vijay Dhameliya<br />
|Plane, ZRH<br />
|15th August<br />
|09:45<br />
|<br />
|-<br />
| Daniel Vrátil<br />
| Plane, ZRH<br />
| 15th August<br />
| 21:15<br />
|<br />
|-<br />
| Denis Steckelmacher<br />
| Train from Lausanne<br />
| 15th August<br />
| 12:24<br />
|<br />
|-<br />
| Rohan Garg<br />
| Plane, BSL<br />
| 15th August<br />
| 19:45<br />
|<br />
|-<br />
| Holger Kälberer<br />
| Car<br />
| 15th August<br />
| morning<br />
|<br />
|-<br />
| Kevin Funk<br />
| Plane, ZRH<br />
| 15th August<br />
| 18:00<br />
|<br />
|-<br />
| Arjen Hiemstra<br />
| Plane, GVA<br />
| 15th August<br />
| 17:00<br />
|<br />
|-<br />
| Joseph WenningerWenninger (+Erminia Maltri)<br />
| car<br />
| 14th August<br />
| around 12:00<br />
|<br />
|-<br />
|Till Theato<br />
|Train<br />
|15th August<br />
|10:55<br />
|<br />
|-<br />
|Christian Esken<br />
|Plane, ZRH<br />
|15th August<br />
|16:45 from ZRH<br />
|<br />
|-<br />
|Bruno Coudoin<br />
|Plane, GVA<br />
|15th August<br />
|13:40 from GVA<br />
|<br />
|-<br />
|Vincent Pinon<br />
|car<br />
|14th August<br />
|leave around 15:00<br />
|<br />
|-<br />
|Harald Sitter<br />
|choochoo<br />
|15th August<br />
|before noon<br />
|going through Zurich<br />
|-<br />
|David Narvaez<br />
|Plane, ZRH<br />
|18th August<br />
|13:00<br />
|Doing some tourism after Randa<br />
|-<br />
|Dan Leinir Turthra Jensen<br />
|plane, ZRH<br />
|16th August<br />
|07.15<br />
|As the plane departs very early, i will need to actually depart Randa the previous night<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Sprints/Randa/2014/Travel&diff=38663Sprints/Randa/2014/Travel2014-07-28T07:54:30Z<p>Leinir: /* Arrival */</p>
<hr />
<div>Please add below the information about your dates and times of arrival and departure. By type we mean the means of your transportation.<br />
<br />
== Arrival ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Type<br />
! Date<br />
! Time<br />
! Comment<br />
|- <br />
|Mario Fux<br />
|by foot<br />
|9th August<br />
|around 15:00<br />
|Nothing to add ;-)<br />
|-<br />
|Cristian Oneț<br />
|Car<br />
|9th August<br />
|around 19:00<br />
|<br />
|-<br />
|Aleix Pol<br />
|Plane, GVA<br />
|9th August<br />
|10:30<br />
|<br />
|-<br />
|David Edmundson<br />
|Plane, GVA<br />
|9th August<br />
|10:00<br />
|<br />
|-<br />
|Vishesh Handa<br />
|Plane, GVA<br />
|9th August<br />
|10:30<br />
|Actually arriving on the 8th, but I'll spend a day in Geneva.<br />
|-<br />
|Dan Leinir Turthra Jensen<br />
|Plane, ZRH<br />
|9th August<br />
|11:00<br />
|<br />
|-<br />
|Àlex Fiestas<br />
|Plane, GVA<br />
|9th August<br />
|10:30<br />
|Actually arriving on the 8th, but I'll spend a day in Geneva.<br />
|-<br />
|Martin Klapetek<br />
|Car<br />
|10th August<br />
|evening<br />
|<br />
|-<br />
|Rohan Garg<br />
|Plane, ZRH<br />
|9th August<br />
|9:00<br />
|<br />
|-<br />
|Felix Rohrbach<br />
|Train<br />
|9th August<br />
|12:30<br />
|<br />
|-<br />
|Nicolás Alvarez<br />
|Plane, ZRH<br />
|8th August<br />
|15:25<br />
|Staying with Pascal Mages for the day before Randa<br />
|-<br />
|Valorie Zimmerman<br />
|Plane, GVA<br />
|8th August<br />
|10:00<br />
|I hope to see some of Geneva, then hand out tickets the next day<br />
|<br />
|-<br />
|Sanjiban Bairagya<br />
|Plane, ZRH<br />
|9th August<br />
|6:20<br />
|<br />
|-<br />
|Vijay Dhameliya<br />
|Plane, ZRH<br />
|9th August<br />
|6:20<br />
|<br />
|-<br />
| Daniel Vrátil<br />
| Plane, ZRH<br />
| 10th August<br />
| 15:30<br />
|<br />
|-<br />
| Denis Steckelmacher<br />
| Train, Lausanne<br />
| 9th August<br />
| 15:43<br />
|<br />
|-<br />
| Holger Kälberer<br />
| Car<br />
| 9th August<br />
| (late) evening<br />
|<br />
|-<br />
| Kevin Funk<br />
| Plane, ZRH<br />
| 9th August<br />
| 08:20<br />
|<br />
|-<br />
| Arjen Hiemstra<br />
| Plane, GVA<br />
| 9th August<br />
| 11:05<br />
|<br />
|-<br />
| Manuel Nickschas<br />
| car<br />
| 9th August<br />
| evening<br />
|<br />
|-<br />
| Myriam Schweingruber<br />
| car <br />
| 9th August<br />
| evening<br />
| travelling with Manuel<br />
|-<br />
| Mark Kretschmann<br />
| car<br />
| 9th August<br />
| evening<br />
| travelling with Manuel<br />
|-<br />
| Joseph Wenninger (+Erminia Maltri)<br />
| car<br />
| 9th August<br />
| around 12:00<br />
|<br />
|-<br />
|Till Theato<br />
|Train<br />
|9th August<br />
|14:55<br />
|<br />
|-<br />
|Christian Esken<br />
|Plane, ZRH<br />
|9th August<br />
|14:15 at ZRH<br />
|<br />
|-<br />
|Bruno Coudoin<br />
|Plane, GVA<br />
|10th August<br />
|13:00 at GVA<br />
|<br />
|-<br />
|Vincent Pinon<br />
|car<br />
|10th August<br />
|around 18:00<br />
|departure/arrival depend on baby<br />
|-<br />
|Harald Sitter<br />
|choochoo<br />
|9th August<br />
|evening<br />
|going through Zurich<br />
|-<br />
|David Narvaez<br />
|Plane, ZRH<br />
|9th August<br />
|10:50<br />
|<br />
|}<br />
<br />
== Departure ==<br />
<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Name<br />
! Type<br />
! Date<br />
! Time<br />
! Comment<br />
|- <br />
|Mario Fux<br />
|by foot<br />
|15th August<br />
|until everybody left<br />
|Nothing to add ;-)<br />
|-<br />
|Cristian Oneț<br />
|Car<br />
|15th August<br />
|in the morning<br />
|<br />
|-<br />
|Aleix Pol<br />
|Plane, GVA<br />
|15th August<br />
|19:00<br />
|<br />
|-<br />
|David Edmundson<br />
|Plane, GVA<br />
|15th August<br />
|19:00<br />
|<br />
|-<br />
|Vishesh Handa<br />
|Plane, GVA<br />
|15th August<br />
|19:00<br />
|<br />
|-<br />
|Àlex Fiestas<br />
|Plane, GVA<br />
|15th August<br />
|19:00<br />
|<br />
|-<br />
|Martin Klapetek<br />
|Car<br />
|14th August<br />
|afternoon<br />
|<br />
|-<br />
|Felix Rohrbach<br />
|Train<br />
|15th August<br />
|15:00<br />
|<br />
|-<br />
|Nicolás Alvarez<br />
|Plane, ZRH<br />
|17th August<br />
|17:10<br />
|Staying at a hotel after Randa<br />
|-<br />
|Valorie Zimmerman<br />
|Plane, GVA<br />
|15th August<br />
|13:10<br />
|I hope that is time enough for the train from Randa!<br />
|-<br />
|Sanjiban Bairagya<br />
|Plane, ZRH<br />
|16th August<br />
|12:45<br />
|It is the plane which departs at 12:45 pm :)<br />
|-<br />
|Vijay Dhameliya<br />
|Plane, ZRH<br />
|15th August<br />
|09:45<br />
|<br />
|-<br />
| Daniel Vrátil<br />
| Plane, ZRH<br />
| 15th August<br />
| 21:15<br />
|<br />
|-<br />
| Denis Steckelmacher<br />
| Train from Lausanne<br />
| 15th August<br />
| 12:24<br />
|<br />
|-<br />
| Rohan Garg<br />
| Plane, BSL<br />
| 15th August<br />
| 19:45<br />
|<br />
|-<br />
| Holger Kälberer<br />
| Car<br />
| 15th August<br />
| morning<br />
|<br />
|-<br />
| Kevin Funk<br />
| Plane, ZRH<br />
| 15th August<br />
| 18:00<br />
|<br />
|-<br />
| Arjen Hiemstra<br />
| Plane, GVA<br />
| 15th August<br />
| 17:00<br />
|<br />
|-<br />
| Joseph WenningerWenninger (+Erminia Maltri)<br />
| car<br />
| 14th August<br />
| around 12:00<br />
|<br />
|-<br />
|Till Theato<br />
|Train<br />
|15th August<br />
|10:55<br />
|<br />
|-<br />
|Christian Esken<br />
|Plane, ZRH<br />
|15th August<br />
|16:45 from ZRH<br />
|<br />
|-<br />
|Bruno Coudoin<br />
|Plane, GVA<br />
|15th August<br />
|13:40 from GVA<br />
|<br />
|-<br />
|Vincent Pinon<br />
|car<br />
|14th August<br />
|leave around 15:00<br />
|<br />
|-<br />
|Harald Sitter<br />
|choochoo<br />
|15th August<br />
|before noon<br />
|going through Zurich<br />
|-<br />
|David Narvaez<br />
|Plane, ZRH<br />
|18th August<br />
|13:00<br />
|Doing some tourism after Randa<br />
|}</div>Leinirhttps://community.kde.org/index.php?title=Calligra/Ideas/Proper_nouns_definition_and_insertion_assistant&diff=29662Calligra/Ideas/Proper nouns definition and insertion assistant2013-01-23T19:45:29Z<p>Leinir: clarification on what a proper noun is</p>
<hr />
<div>To alleviate any future confusion on the topic: This suggestion is for keeping track of proper names and their definition. That is, names which uniquely define a single entity (Jupiter, Peter Jackson or similar), as opposed to common nouns which describe a class (tree, chair or similar). For more reading on the topic: http://en.wikipedia.org/wiki/Proper_noun :) (and yes, i'm now aware this should be called Proper names definition and insertion assistant, rather than Proper nouns...)<br />
<br />
As an author, in particular of stories and novels, one has to keep track of numerous characters or locations while writing, and the ability to handle such a thing would be quite useful. Such an idea would be approachable from a number of angles, and so, a number of workflows can be described like so:<br />
<br />
* Inserting a name into the document of a noun which is not currently defined<br />
* Inserting a name of a previously defined noun into the document<br />
* Inserting a pseudonym of a previously defined noun into the document<br />
* Defining a noun without inserting it into the document<br />
* Inserting a list of descriptions of a noun into the document<br />
* Inserting the description of a single noun into the document<br />
<br />
What's implied here is a few features, which we can then describe as follows:<br />
<br />
* A dialog or panel which allows an author to manage (add, edit, delete) all existing definitions in a document<br />
* A set of menu items:<br />
** Insert a pre-existing noun<br />
** Add a new definition<br />
** Add a pseudonym for an existing noun<br />
* An in-line assistant used to insert a noun while typing.<br />
<br />
Invoke the assistant by pressing ctrl+space (default) while typing. Pops up a menu with a set of proposed nouns based on the current word, and options to add a new noun or pseudonym for another noun and insert it at the cursor position (by default using the current word, but allowing editing).</div>Leinirhttps://community.kde.org/index.php?title=Calligra/Meetings/Spring_2013_Sprint&diff=29487Calligra/Meetings/Spring 2013 Sprint2013-01-16T10:08:58Z<p>Leinir: /* Attendees List */</p>
<hr />
<div>== General information ==<br />
<br />
The sprint will take place from ?.?.2013 to ?.?.2013 at ?<br />
<br />
KDE Sprint page: NONE yet, but requested<br />
<br />
=== Date ===<br />
Date finding page: http://doodle.com/dwznt2uk5de6zgn6<br />
<br />
Currently hot dates: March 8th-10th and March 15th-17th<br />
<br />
Plan is to arrive during Friday afternoon/evening and to leave Sunday afternoon/evening, as this usually fits people's time availability best.<br />
<br />
=== Location ===<br />
<br />
hot candidates: event happening both at<br />
* the [http://linuxhotel.de/ Linux Hotel (Essen, Germany)]<br />
* the office of ThoughtWorks Bangalore (fallback option: Intel Bangalore) in Bangalore in India (unless we find a sponsor to fly people over to the other continent), See [[/Bangalore/]]<br />
<br />
=== Attendees List ===<br />
<br />
Column explanations:<br />
; Sponsoring needed?: enter if you need sponsoring from the KDE e.V. or if you pay the travel/stay by yourself (please also ask any of your company/employer/donor if they would sponsor you, at least partially). Options are: "Yes", "For accomodation", "For travel", "No". Add note if you might be able/willing to take part of costs yourself, if really needed.<br />
; Estimated travel costs: enter the estimated travel costs you would have to travel to & from LinuxHotel or Bangalore<br />
; Estimated accomodation costs: if you are going to stay at the LinuxHotel, enter the days (e.g. Fri-Sun), if you are going to stay in Bangalore, also give a money estimate <br />
<br />
Also notice the section "3. Financial support" of the [http://ev.kde.org/rules/sprint_policy.php KDE Sprint Policy].<br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|- style="color: blue;"<br />
| Name <br />
| email <br />
| Area<br />
| Estimated travel costs <br />
| Estimated accomodation costs <br />
| Sponsoring needed? <br />
| Single / double / many room<br />
| Special<br />
|-<br />
| Friedrich W. H. Kossebau<br />
| kossebauATkde.org<br />
| cleaning up, core libs, Words<br />
| 140 €<br />
| LinuxHotel (Fri-Sun)<br />
| Yes (can take parts myself)<br />
| many<br />
| -<br />
|-<br />
| Boudewijn Rempt<br />
| boud@kde.org<br />
| parts stuff<br />
| 100 €<br />
| LinuxHotel (Fri-Sun)<br />
| For acco only <br />
| ?<br />
| -<br />
|-<br />
| Sven Langkamp<br />
| sven.langkamp@gmail.com<br />
| Krita<br />
| 0 €<br />
| LinuxHotel (Fri-Sun)<br />
| For acco only <br />
| ?<br />
| -<br />
|-<br />
| Dmitry Kazakov<br />
| dimula73@gmail.com<br />
| Krita<br />
| 280-330 € (depending on dates)<br />
| LinuxHotel (Fri-Sun)<br />
| Yes<br />
| ?<br />
| -<br />
|-<br />
| Thorsten Zachmann<br />
| zachmann@kde.org<br />
| Stage, Libs<br />
| 60-120 € (depending when booking is done)<br />
| LinuxHotel (Fri-Sun)<br />
| Yes<br />
| ?<br />
| -<br />
|-<br />
| Inge Wallin<br />
| inge@lysator.liu.se, ingwa@kde.org<br />
| Author, Words, libs, plugins, marketing<br />
| 300-400 € (depending when booking is done)<br />
| LinuxHotel (Fri-Sun)<br />
| Yes<br />
| ?<br />
| -<br />
|-<br />
| Marijn Kruisselbrink<br />
| mkruisselbrink@kde.org<br />
| Sheets<br />
| $1000 - $1200 (depending when booking is done)<br />
| LinuxHotel (Fri-Sun)<br />
| Yes<br />
| ?<br />
| Bangalore would be about the same travel costs for me<br />
|-<br />
| Yue Liu<br />
| yue.liu@mail.com<br />
| Flow, mac<br />
| $900 - $1000 (depending when booking is done)<br />
| LinuxHotel (Fri-Sun)<br />
| Yes<br />
| ?<br />
| Bangalore would be about the same travel costs for me<br />
|-<br />
| Shantanu Tushar<br />
| shantanu@kde.org<br />
| Active<br />
| -<br />
| -<br />
| No<br />
| -<br />
| Bangalore<br />
|-<br />
| Gopalakrishna Bhat A<br />
| gopalakbhat@gmail.com<br />
| Author, Formula Shape<br />
| -<br />
| -<br />
| No<br />
| -<br />
| Bangalore<br />
|-<br />
| Sujith Haridasan<br />
| sujith.h@gmail.com<br />
| Active<br />
| -<br />
| -<br />
| No<br />
| -<br />
| Bangalore<br />
|-<br />
| Jigar Raisinghani<br />
| jigarraisinghani@gmail.com<br />
| Sheets<br />
| 100-150 € ( Depending when booking is done) <br />
| Fri - Sun( 60 €)<br />
| Yes<br />
| ?<br />
| Bangalore<br />
|-<br />
|-<br />
| Arjen Hiemstra<br />
| ahiemstra@heimr.nl<br />
| core/libs, krita, ui design<br />
| 80-100€ <br />
| LinuxHotel, Fri-Sun<br />
| Yes<br />
| ?<br />
| -<br />
|-<br />
| Dan Leinir Turthra Jensen<br />
| admin@leinir.dk<br />
| core/libs, krita, author<br />
| 200€ <br />
| LinuxHotel, Fri-Sun<br />
| Yes<br />
| Any<br />
| -<br />
|-<br />
| Mani Chandrasekar<br />
| maninc@gmail.com<br />
| Words<br />
| -<br />
| -<br />
| No<br />
| -<br />
| Bangalore<br />
|-<br />
| Nityam Vakil<br />
| nityam.vakil@gmail.com<br />
| Sheets<br />
| 100-150 € ( Depending when booking is done)<br />
| Fri - Sun ( 60 €)<br />
| Yes<br />
| ?<br />
| Bangalore<br />
|-<br />
|}<br />
<br />
== Equipment ==<br />
<br />
Needed: reliable conferencing system to make space between India - Europe vanish virtually (sadly not possible for timezone difference)<br />
<br />
Any proposals, experiences?<br />
<br />
== Sprint agenda ==<br />
<br />
Below follows a suggested agenda for the sprint. It's free for anybody to put new items below. The actual contents and order for the agenda will be decided at the sprint. Please also indicate who is behind a certain suggestion. If you are interested in something that is already proposed and want to add your opinion, then add your name to the list.<br />
<br />
=== Presentations ===<br />
<br />
''Presentations of things interesting to the Calligra community. Please state targeted audience.''<br />
<br />
* ''Add your presentation here''<br />
<br />
=== BoFs ===<br />
<br />
* Fill in topics here...<br />
<br />
=== Projects ===<br />
<br />
''Projects we'll work on in small groups, mostly coding or creating other concrete results.''<br />
<br />
* ''Add your project here''<br />
<br />
=== Discussions ===<br />
<br />
''Discussions about topics, which are relevant to all or a sub group of people. Please state audience and desired result of the discussion.''<br />
<br />
==== ''Add your discussion topic here'' ====<br />
<br />
== Meeting Notes ==<br />
<br />
''Notes will go here''<br />
<br />
== Blogs ==<br />
<br />
''When you blog about the meeting (and you should ;-), please add a link here''</div>Leinirhttps://community.kde.org/index.php?title=Calligra/Meetings/Spring_2013_Sprint&diff=29465Calligra/Meetings/Spring 2013 Sprint2013-01-15T13:11:21Z<p>Leinir: /* Attendees List */</p>
<hr />
<div>== General information ==<br />
<br />
The sprint will take place from ?.?.2013 to ?.?.2013 at ?<br />
<br />
KDE Sprint page: NONE yet, but requested<br />
<br />
=== Date ===<br />
Date finding page: http://doodle.com/dwznt2uk5de6zgn6<br />
<br />
Currently hot dates: March 8th-10th and March 15th-17th<br />
<br />
Plan is to arrive during Friday afternoon/evening and to leave Sunday afternoon/evening, as this usually fits people's time availability best.<br />
<br />
=== Location ===<br />
<br />
hot candidates: event happening both at<br />
* the [http://linuxhotel.de/ Linux Hotel (Essen, Germany)]<br />
* the office of ThoughtWorks Bangalore (fallback option: Intel Bangalore) in Bangalore in India (unless we find a sponsor to fly people over to the other continent), See [[/Bangalore/]]<br />
<br />
=== Attendees List ===<br />
<br />
Column explanations:<br />
; Sponsoring needed?: enter if you need sponsoring from the KDE e.V. or if you pay the travel/stay by yourself (please also ask any of your company/employer/donor if they would sponsor you, at least partially). Options are: "Yes", "For accomodation", "For travel", "No". Add note if you might be able/willing to take part of costs yourself, if really needed.<br />
; Estimated travel costs: enter the estimated travel costs you would have to travel to & from LinuxHotel or Bangalore<br />
; Estimated accomodation costs: if you are going to stay at the LinuxHotel, enter the days (e.g. Fri-Sun), if you are going to stay in Bangalore, also give a money estimate <br />
<br />
Also notice the section "3. Financial support" of the [http://ev.kde.org/rules/sprint_policy.php KDE Sprint Policy].<br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|- style="color: blue;"<br />
| Name <br />
| email <br />
| Area<br />
| Estimated travel costs <br />
| Estimated accomodation costs <br />
| Sponsoring needed? <br />
| Special<br />
|-<br />
| Friedrich W. H. Kossebau<br />
| kossebauATkde.org<br />
| cleaning up, core libs, Words<br />
| 140 €<br />
| LinuxHotel (Fri-Sun)<br />
| Yes (can take parts myself)<br />
| -<br />
|-<br />
| Boudewijn Rempt<br />
| boud@kde.org<br />
| parts stuff<br />
| 100 €<br />
| LinuxHotel (Fri-Sun)<br />
| For acco only <br />
| -<br />
|-<br />
| Sven Langkamp<br />
| sven.langkamp@gmail.com<br />
| Krita<br />
| 0 €<br />
| LinuxHotel (Fri-Sun)<br />
| For acco only <br />
| -<br />
|-<br />
| Dmitry Kazakov<br />
| dimula73@gmail.com<br />
| Krita<br />
| 280-330 € (depending on dates)<br />
| LinuxHotel (Fri-Sun)<br />
| Yes<br />
| -<br />
|-<br />
| Thorsten Zachmann<br />
| zachmann@kde.org<br />
| Stage, Libs<br />
| 60-120 € (depending when booking is done)<br />
| LinuxHotel (Fri-Sun)<br />
| Yes<br />
| -<br />
|-<br />
| Marijn Kruisselbrink<br />
| mkruisselbrink@kde.org<br />
| Sheets<br />
| $1000 - $1200 (depending when booking is done)<br />
| LinuxHotel (Fri-Sun)<br />
| Yes<br />
| Bangalore would be about the same travel costs for me<br />
| -<br />
|-<br />
| Yue Liu<br />
| yue.liu@mail.com<br />
| Flow, mac<br />
| $900 - $1000 (depending when booking is done)<br />
| LinuxHotel (Fri-Sun)<br />
| Yes<br />
| Bangalore would be about the same travel costs for me<br />
| -<br />
|-<br />
| Shantanu Tushar<br />
| shantanu@kde.org<br />
| Active<br />
| -<br />
| -<br />
| No<br />
| Bangalore<br />
|-<br />
| Gopalakrishna Bhat A<br />
| gopalakbhat@gmail.com<br />
| Author, Formula Shape<br />
| -<br />
| -<br />
| No<br />
| Bangalore<br />
|-<br />
| Sujith Haridasan<br />
| sujith.h@gmail.com<br />
| Active<br />
| -<br />
| -<br />
| No<br />
| Bangalore<br />
|-<br />
| Jigar Raisinghani<br />
| jigarraisinghani@gmail.com<br />
| Sheets<br />
| 100-150 € ( Depending when booking is done) <br />
| Fri - Sun( 60 €)<br />
| Yes<br />
| Bangalore<br />
|-<br />
|-<br />
| Arjen Hiemstra<br />
| ahiemstra@heimr.nl<br />
| core/libs, krita, ui design<br />
| 80-100€ <br />
| LinuxHotel, Fri-Sun<br />
| Yes<br />
| -<br />
|-<br />
| Dan Leinir Turthra Jensen<br />
| admin@leinir.dk<br />
| core/libs, krita, author<br />
| 200€ <br />
| LinuxHotel, Fri-Sun<br />
| Yes<br />
| -<br />
|-<br />
| Mani Chandrasekar<br />
| maninc@gmail.com<br />
| Words<br />
| -<br />
| -<br />
| No<br />
| Bangalore<br />
|-<br />
| (Your name)<br />
| (your email address)<br />
| (what do you plan to work on)<br />
| (rough realistic amount)<br />
| (days, rough realistic amount)<br />
| (Need sponsoring, for?)<br />
| (anything else, comments?)<br />
|-<br />
|}<br />
<br />
== Equipment ==<br />
<br />
Needed: reliable conferencing system to make space between India - Europe vanish virtually (sadly not possible for timezone difference)<br />
<br />
Any proposals, experiences?<br />
<br />
== Sprint agenda ==<br />
<br />
Below follows a suggested agenda for the sprint. It's free for anybody to put new items below. The actual contents and order for the agenda will be decided at the sprint. Please also indicate who is behind a certain suggestion. If you are interested in something that is already proposed and want to add your opinion, then add your name to the list.<br />
<br />
=== Presentations ===<br />
<br />
''Presentations of things interesting to the Calligra community. Please state targeted audience.''<br />
<br />
* ''Add your presentation here''<br />
<br />
=== BoFs ===<br />
<br />
* Fill in topics here...<br />
<br />
=== Projects ===<br />
<br />
''Projects we'll work on in small groups, mostly coding or creating other concrete results.''<br />
<br />
* ''Add your project here''<br />
<br />
=== Discussions ===<br />
<br />
''Discussions about topics, which are relevant to all or a sub group of people. Please state audience and desired result of the discussion.''<br />
<br />
==== ''Add your discussion topic here'' ====<br />
<br />
== Meeting Notes ==<br />
<br />
''Notes will go here''<br />
<br />
== Blogs ==<br />
<br />
''When you blog about the meeting (and you should ;-), please add a link here''</div>Leinirhttps://community.kde.org/index.php?title=Calligra/Ideas/Proper_nouns_definition_and_insertion_assistant&diff=29115Calligra/Ideas/Proper nouns definition and insertion assistant2013-01-05T23:15:19Z<p>Leinir: An initial description of the idea of the proper noun assistant</p>
<hr />
<div>As an author, in particular of stories and novels, one has to keep track of numerous characters or locations while writing, and the ability to handle such a thing would be quite useful. Such an idea would be approachable from a number of angles, and so, a number of workflows can be described like so:<br />
<br />
* Inserting a name into the document of a noun which is not currently defined<br />
* Inserting a name of a previously defined noun into the document<br />
* Inserting a pseudonym of a previously defined noun into the document<br />
* Defining a noun without inserting it into the document<br />
* Inserting a list of descriptions of a noun into the document<br />
* Inserting the description of a single noun into the document<br />
<br />
What's implied here is a few features, which we can then describe as follows:<br />
<br />
* A dialog or panel which allows an author to manage (add, edit, delete) all existing definitions in a document<br />
* A set of menu items:<br />
** Insert a pre-existing noun<br />
** Add a new definition<br />
** Add a pseudonym for an existing noun<br />
* An in-line assistant used to insert a noun while typing.<br />
<br />
Invoke the assistant by pressing ctrl+space (default) while typing. Pops up a menu with a set of proposed nouns based on the current word, and options to add a new noun or pseudonym for another noun and insert it at the cursor position (by default using the current word, but allowing editing).</div>Leinirhttps://community.kde.org/index.php?title=Calligra/Ideas&diff=29114Calligra/Ideas2013-01-05T22:51:05Z<p>Leinir: /* Ideas */</p>
<hr />
<div>=Ideas=<br />
<br />
This page is used to collect ideas for projects that could be done for Calligra. It could be anything from refactorings of internals to a new application of an extension.<br />
<br />
In principle anybody could write here and the idea could be reasonably small or very large. <br />
<br />
When a developer decides to use an idea and create a project from it, s/he should create a project page under [[Calligra/Projects]]. See the policy for projects at that page.<br />
<br />
* [[Calligra/Ideas/Proper nouns definition and insertion assistant|Proper nouns definition and insertion assistant]]<br />
* [[Calligra/Ideas/Bibliography|Bibliography]]<br />
* [[Calligra/Ideas/Open Street Map Integration|Open Streetmap integration]]<br />
* [[Calligra/Ideas/Colordialogs|A proposal for new color dialogs]]<br />
* [[Calligra/Ideas/Outliners|Outliners]]<br />
* [[Calligra/Ideas/Collaboration|Collaboration]]<br />
* [[User:Jstaniek/Calligra_Sprint_2011.2_presentation#BoF_Topics|jstaniek's ideas presented at 2nd Calligra sprint]]</div>Leinirhttps://community.kde.org/index.php?title=Gluon/Core&diff=27087Gluon/Core2012-12-04T15:34:27Z<p>Leinir: /* Tasks */</p>
<hr />
<div>== Tasks ==<br />
<br />
;Port back to Eigen<br />
: After doing some simple testing of matrix concatenation it turns out Eigen is easily two times as fast as QMatrix4x4 in release mode. In addition, Eigen has a more pleasant API to work with since it matches closer to the actual mathematics. Therefore it has been decided to port Gluon back to using Eigen as vector library.<br />
;Create a proper logging system<br />
: The current logging system is pretty inadequate. While it works for very basic debug output, actually doing things like getting warnings to show up in the messages pane in Creator is unneccesarily complex and convoluted. Therefore I propose to create a logging system based around a singleton logging object that can handle reporting multiple levels of messages and ouput to different targets. This will also help development on Windows since it would avoid the necessity of things like "DebugView". Singleton logger is created for use with things not obviously linked to the game tree (such as render targets and the graphics backend object), and levels are added to the current debugging system (debug, info, warning, error and fatal, others if they become required (such as verbose, for super-verbose info such as "this asset support the filetype(s): ...")). Finally, module information is added to the debug output, so filters can be applied.</div>Leinirhttps://community.kde.org/index.php?title=Gluon/Core&diff=27086Gluon/Core2012-12-04T15:31:43Z<p>Leinir: /* Tasks */ Refine logging task</p>
<hr />
<div>== Tasks ==<br />
<br />
;Port back to Eigen<br />
: After doing some simple testing of matrix concatenation it turns out Eigen is easily two times as fast as QMatrix4x4 in release mode. In addition, Eigen has a more pleasant API to work with since it matches closer to the actual mathematics. Therefore it has been decided to port Gluon back to using Eigen as vector library.<br />
;Create a proper logging system<br />
: The current logging system is pretty inadequate. While it works for very basic debug output, actually doing things like getting warnings to show up in the messages pane in Creator is unneccesarily complex and convoluted. Therefore I propose to create a logging system based around a singleton logging object that can handle reporting multiple levels of messages and ouput to different targets. This will also help development on Windows since it would avoid the necessity of things like "DebugView". Singleton logger is created for use with things not obviously linked to the game tree (such as render targets and the graphics backend object), and levels are added to the current debugging system (debug, info, warning, error and fatal, others if they become required). Finally, module information is added to the debug output, so filters can be applied.</div>Leinir