https://community.kde.org/api.php?action=feedcontributions&user=Sandro&feedformat=atomKDE Community Wiki - User contributions [en]2024-03-29T12:44:41ZUser contributionsMediaWiki 1.40.2https://community.kde.org/index.php?title=KDE_PIM/Meetings/Osnabrueck_12&diff=90844KDE PIM/Meetings/Osnabrueck 122021-01-08T00:59:31Z<p>Sandro: /* List of participants */</p>
<hr />
<div>From 2003 to 2012 the KDE PIM community used to meet at Osnabrück for its traditional new year meeting. Originating from a project to bring FOSS groupware to German public institutions, these meetings were instrumental in forming the KDE PIM community, shaped the development of Kontact, and acted as birthplace for famous and infamous technologies, such as Akonadi.<br />
<br />
In 2021 we want to revive this tradition for a one-time get-together of former and current members of the KDE PIM community. As we can't meet in person we will do this as an online afternoon meeting: "Virtual Osnabrück".<br />
<br />
The meeting will take place on BigBlueButton on '''Saturday, January 9th, 2021 from 14:00 to 17:00 (Osnabrück time zone, i.e. UTC+1)'''. We'll meet in the [https://meet.kde.org/b/all-dfq-c8d KDEPIM room]. Just follow the link.<br />
<br />
The purpose of the meeting is to (re)connect the community, to meet old friends, and to talk past, current, and future KDE PIM. We will have time for mingling and chatting, but also will have a couple of short presentations.<br />
<br />
This will be a fun meeting, reviving old bonds and creating new ones, a glimpse into how KDE PIM came to be and what it is today. Looking forward to see you in January. As Till once wrote in 2012: ''"Osnabrück is not a place :)."''<br />
<br />
== Agenda ==<br />
<br />
(all times are Osnabrück timezone, i.e. UTC+1)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Time !! Session !! Description<br />
|-<br />
| 14:00 - 14:30 || "Dom-Hotel" || Greetings, welcome, catching up<br />
|-<br />
| 14:30 - 15:15 || "Große Straße" || [[#Presentation round: KDE PIM at Osnabrück|Presentation round: KDE PIM at Osnabrück]]<br />
|-<br />
| 15:15 - 15:45 || "Hase" || We will figure out how to take a virtual group photo<br />
|-<br />
| 15:45 - 16:30 || "Neuer Graben" || [[#Presentation round: KDE PIM today and in the future|Presentation round: KDE PIM today and in the future]]<br />
|-<br />
| 16:30 - 17:00 || "Rampendahl" || Social event, bring your favorite beverage, open end<br />
|}<br />
<br />
=== Presentation round: KDE PIM at Osnabrück ===<br />
<br />
* Bernhard Reiter: How the Osnabrück Meeting came to be<br />
* Till Adam: The origins of Akonadi<br />
* Thorsten Stärk: KTimeTracker<br />
* Open discussion<br />
<br />
=== Presentation round: KDE PIM today and in the future ===<br />
<br />
* Bernhard Reiter: Kontact and encrypted Email<br />
* Christian Mollekopf: State of Kube<br />
* Volker Krause: KDE Itinerary & friends<br />
* Open discussion<br />
<br />
== How to participate ==<br />
<br />
Everybody interested in KDE PIM is welcome to participate. Special invitations to all those who have participated in previous Osnabrück meetings. To be able to plan ahead a bit, please add your name to the list below or [mailto:schumacher@kde.org contact Cornelius Schumacher], if you intend to participate. Spontaneous appearance is welcome as well, though :-)<br />
<br />
== List of participants ==<br />
<br />
* Cornelius Schumacher <schumacher@kde.org><br />
* Volker Krause <vkrause@kde.org><br />
* Ingo Klöcker <kloecker@kde.org><br />
* Bernhard Reiter <bernhard.reiter@intevation.de><br />
* Christian Mollekopf <christian@mkpf.ch><br />
* Till Adam <adam@kde.org><br />
* Jos Poortvliet <jospoortvliet@kde.org><br />
* David Jarvie <djarvie@kde.org><br />
* Marc Deop <marcdeop@fedoraproject.org><br />
* Kevin Ottens<br />
* Sandro Knauß <knauss@kde.org><br />
<br />
== Call for presentations ==<br />
<br />
We are looking for a couple of short (about 5-10 mins) presentations. Anything is welcome, from slides with a project update to you telling your favorite Osnabrück story, and everything inbetween and beyond.<br />
<br />
Some topics for inspiration:<br />
<br />
* History or lessons learned from the Osnabrück meetings<br />
* What happened to project XYZ we conceived or talked about at Osnabrück?<br />
* KDE PIM anecdotes<br />
* What's hot in KDE PIM today?<br />
* I have this idea...<br />
<br />
If you would like to contribute a short presentation, please reach out to [mailto:schumacher@kde.org Cornelius Schumacher <schumacher@kde.org>] so we can coordinate the agenda. A title and one sentence of what it will be, are enough. If you are unsure or just have a vague idea, please don't hesitate to reach out as well, and we'll figure out how to put it together. Spontaneous contributions at the meeting will also be welcome, as time permits.</div>Sandrohttps://community.kde.org/index.php?title=Akademy/2019/GPGKeys&diff=86108Akademy/2019/GPGKeys2019-09-08T13:05:44Z<p>Sandro: add my key to gpg list</p>
<hr />
<div>= Why =<br />
<br />
GPG signing is our preferred method of establishing authenticity of anything ranging from mails to release tarballs/tags. To make this easy to verify and trustworthy it is useful to have yourself wired into the KDE web of trust (i.e. get your key signed by other KDE contributors).<br />
<br />
If you are release manager of a project or a distribution packager it is<br />
highly recommended that you attend this BoF to get yourself wired into<br />
the release web of trust which makes tarball signature verification a<br />
lot easier.<br />
<br />
There's lots of good guides on GPG in general and key signing in specific out on the internet, it is recommended you read up on this a bit. We'll only explain the process in broad strokes at the BoF. If you have questions you can send a mail to sitter@kde.org<br />
<br />
= How This Works - READ THIS! =<br />
<br />
Add the name and email address of your key as well as the fingerprint below. Tuesday at 12:00 someone is going to do a print out for all listed attendants. If you would like to do your own print out, please send a mail to ''sitter@kde.org''. Please make sure that you send a mail if you add yourself after the deadline. It may be too late or not, but I definitely want to know.<br />
<br />
To get your key fingerprint, you'll want to run gpg or gpg2 with the --fingerprint argument and your name or short ID. e.g.<code>gpg2 --fingerprint Sitter</code><br />
<br/><br />
<br/><br />
''' For the BoF Please: '''<br />
* Bring an ID card or preferably a passport so we can verify you are who you claim to be<br />
* Write down your fingerprint or print it out so you can verify your own fingerprint<br />
<br />
Failing to do either will slow down everyone! Help us out and be prepared :)<br />
<br/><br />
<br/><br />
{| class="wikitable" border="1"<br />
|-<br />
! Key OK<br />
! Name <EMail> <br />
! Fingerpint<br />
! ID OK<br />
|-<br />
| ☐ <br />
| Harald Sitter <sitter@kde.org><br />
| CB93 8752 1E1E E012 7DA8 0484 3FDB B550 84CC 5D84<br />
| ☐<br />
|-<br />
| ☐<br />
| Stefan Derkits <stefan@derkits.at><br />
| 7786 B507 E1EF 5B9E 89BC B2FE 9591 D7BA 4228 0CA8<br />
| ☐<br />
|-<br />
| ☐<br />
| Timothée Giet <animtim@gmail.com><br />
| D2FA AB62 1F61 8D42 685B 427B 63D7 264C 0568 7D7E<br />
| ☐<br />
|-<br />
| ☐<br />
| Jonathan Riddell <jr@jriddell.org><br />
| 2D1D 5B05 8835 7787 DE9E E225 EC94 D18F 7F05 997E<br />
| ☐<br />
|-<br />
| ☐<br />
| Ivan Čukić <ivan@cukic.co><br />
| 8FE4 D32F 7061 EA9C 8232 07AE 01C6 CE2B FF04 1C12<br />
| ☐<br />
|-<br />
|-<br />
| ☐<br />
| Sandro Knauß <sknauss@kde.org, bugs@sandroknauss.de, hefee@debian.org><br />
| 39EC 11A0 2016 B729 2649 1A06 E3AD B008 5060 5636<br />
| ☐<br />
|-<br />
| ☐<br />
| Your Name <youremail@host.tld><br />
| 1234 1234 1234 FINGER PRINT<br />
| ☐<br />
|-</div>Sandrohttps://community.kde.org/index.php?title=Sprints/Privacy/2019&diff=82922Sprints/Privacy/20192019-02-12T22:25:33Z<p>Sandro: </p>
<hr />
<div>=Organization=<br />
* Sandro Knauß<br />
* Florian Müller<br />
<br />
=Venue=<br />
<br />
ehemaliges Fernsprechamt (ancient telephone-exchange)<br/><br />
Schadowstraße 10-12<br/><br />
04177 Leipzig<br/><br />
Germany<br />
<br />
https://www.openstreetmap.org/?mlat=51.33485&mlon=12.33242#map=19/51.33485/12.33242<br />
<br />
and only 100m away "Die ganze Bäckerei" (the whole Bakery) at Josephstraße 9<br />
<br />
How to get there ? <br />
<br />
normally you need to go to the main station, if you arrive via train or plane. From main station you catch the<br />
trams to the station "Lindenauer Markt". Both trams start from the middle track 3 in front of the main station. You can buy tickets (2,70€) in the tram at a ticket machine, only with coins:<br />
<br />
* 7 (direction Böhlitz-Ehrenberg)<br />
* 15 (direction Miltitz)<br />
<br />
The ride takes about 15 min and the interval is about every 10 min.<br />
<br />
you find the connection here ( only on German)<br />
https://www.l.de/verkehrsbetriebe/fahrplan<br />
<br />
Fun note: The ticket machine in the trams are often not working. The metal plate on the ticket machine is telling you, that in case of a non working ticket machine, it is fine to travel without a ticket.<br />
<br />
=Topics=<br />
<br />
* Integration of alternatives to proprietary cloud services (KDE Connect, Itinerary, Nextcloud, etc.)<br />
* Plasma Mobile<br />
* Security in general<br />
* Vault<br />
* Qt security<br />
* general organization of the Privacy goal<br />
<br />
=Sprint Schedule=<br />
March 22-26, 2019<br />
<br />
=Travel Reimbursement=<br />
File a request on https://reimbursements.kde.org/events/82<br />
<br />
=Attendance=<br />
<br />
=Arrival and departure times=<br />
<br />
=Report=</div>Sandrohttps://community.kde.org/index.php?title=Sprints/Privacy/2019&diff=82895Sprints/Privacy/20192019-02-11T08:01:23Z<p>Sandro: first start with the sprint page</p>
<hr />
<div>=Organization=<br />
* Sandro Knauß<br />
* Florian Müller<br />
<br />
=Venue=<br />
<br />
ehemaliges Fernsprechamt (ancient telephone-exchange)<br/><br />
Schadowstraße 10-12<br/><br />
04177 Leipzig<br/><br />
Germany<br />
<br />
https://www.openstreetmap.org/?mlat=51.33485&mlon=12.33242#map=19/51.33485/12.33242<br />
<br />
and only 100m away "Die ganze Bäckerei" (the whole Bakery) at Josephstraße 9<br />
<br />
How to get there ? <br />
<br />
normally you need to go to the main station, if you arrive via train or plane. From main station you catch the<br />
trams to the station "Lindenauer Markt". Both trams start from the middle track 3 in front of the main station. You can buy tickets (2,70€) in the tram at a ticket machine, only with coins:<br />
<br />
* 7 (direction Böhlitz-Ehrenberg)<br />
* 15 (direction Miltitz)<br />
<br />
The ride takes about 15 min and the interval is about every 10 min.<br />
<br />
you find the connection here ( only on German)<br />
https://www.l.de/verkehrsbetriebe/fahrplan<br />
<br />
Fun note: The ticket machine in the trams are often not working. The metal plate on the ticket machine is telling you, that in case of a non working ticket machine, it is fine to travel without a ticket.<br />
<br />
=Sprint Schedule=<br />
March 22-26, 2019<br />
<br />
=Travel Reimbursement=<br />
File a request on https://reimbursements.kde.org/events/82<br />
<br />
=Attendance=<br />
<br />
=Arrival and departure times=<br />
<br />
=Report=</div>Sandrohttps://community.kde.org/index.php?title=Sprints&diff=82893Sprints2019-02-11T07:28:32Z<p>Sandro: add subpage for privacy sprint</p>
<hr />
<div>[[File:Mascot konqi-app-dev.png|thumbnail|right|Join [[Konqi]] and do some coding together!]]<br />
KDE Developer Sprints are focused gatherings of KDE developers to work on a specific part of KDE. Sprints are an opportunity to plan, design, and hack (think 20% socialization and 80% perspiration). They are supported by KDE e.V. financially and organizationally.<br />
<br />
Want to organize a sprint or attending a sprint? Everyone should read the [http://ev.kde.org/rules/sprint_policy.php KDE Sprint Policy] for information about the KDE Developer Sprint process.<br />
<br />
== Upcoming Sprints ==<br />
* [[Sprints/Privacy/2019 | Goal sprint - privacy, 22-26 March, Leipzig, Germany]] [https://phabricator.kde.org/T8622 some information on T8622]<br />
* Goal sprint - onboarding, tbd, tbd<br />
* Goal sprint - productivity and usability, tbd, tbd<br />
<br />
== Past Sprints ==<br />
<br />
=== 2019 ===<br />
* [[Sprints/Plasma Mobile/2019 | Plasma Mobile Sprint 2019, 4-9 February, Berlin, Germany]]<br />
<br />
=== 2018 ===<br />
* [[Sprints/Plasma/2018 | Plasma Sprint 2018, 21-27 April, Berlin, Germany]]<br />
* Kdenlive Sprint 2018, 25-29 April, France<br />
* KDE e.V. board meeting, 28-29 April, Berlin, Germany <br />
* [[Krita/Sprint2018|Krita Sprint 2018, 17 - 21 May, Deventer, The Netherlands]]<br />
* KDE Connect Sprint 2018, 23-25 March, Barcelona, Spain<br />
* [[Sprints/Promo/2018 | KDE Promo Sprint, 16-18 February, Barcelona, Spain]]<br />
* [[Sprints/PIM/2018 | PIM Sprint 2018, 20-22 April, Toulouse, France]]<br />
<br />
=== 2017 ===<br />
* KDE e.V. board meeting, 14-15, October, Berlin, Germany<br />
* KDE Edu sprint, 7-9, October, Germany<br />
* Randa Meetings, 10-16 September, Randa, Switzerland<br />
* QtCon Brazil, 18-20, August, Brazil<br />
* KDE e.V. board meeting, 13-14 May, Berlin, Germany<br />
* LaKademy, 28 April - 1 May, Brazil<br />
* KDE PIM sprint, 7-9, April, France<br />
* conf.kde.in, 10-12, March, India<br />
* Plasma Sprint, 6-12 February, Germany<br />
* WikiToLearn Conf India, 18-19 January, India<br />
<br />
=== 2016 ===<br />
* Krita 2016, 25-28 August, Deventer, Netherlands <br />
** [https://krita.org/en/item/2016-krita-sprint-day-1/ Day 1]<br />
** [https://krita.org/en/item/new-builds-to-test-krita-sprint-to-end-soon/ Final day]<br />
* Randa Meetings 2016, 11-18 June, Randa, Switzerland <br />
**[https://community.kde.org/Sprints/Randa/2016#News_Articles News Articles]<br />
* KDE Store Sprint 2016, 4-7 June, Bielefeld, Germany <br />
* LaKademy 2016, 25-28 May, Rio de Janeiro, Brazil <br />
**[https://dot.kde.org/2016/06/14/lakademy-2016-%E2%80%92-strewing-floss-culture Dot article]<br />
* KDE PIM Spring Sprint 2016, 31-3 April, Toulouse, France <br />
**[https://dot.kde.org/2016/04/15/kde-pim-spring-sprint-report-toulouse Dot article]<br />
* KDE CERN 2016, 6-12 March, Geneva, Switzerland <br />
**[https://dot.kde.org/2016/03/23/plasma-team-gets-physical Dot article about the Plasma side]<br />
* New Year 2016 Words Sprint, 21-23 January, Deventer, Netherlands<br />
**[https://frinring.wordpress.com/2016/01/25/new-year-calligra-words-sprint/ Friedrich W. H. Kossebau Blog]<br />
<br />
=== 2015 ===<br />
* Kate/Kile/KDevelop Sprint 2015, 6-10 October, Berlin, Germany<br />
** [https://kate-editor.org/2015/10/11/katekdevelop-sprint-2015-summary-for-kate/ Kate Editor Blog]<br />
* WikiToLearn Sprint 2015, 28-30 September, Bormio, Italy<br />
** [http://blogs.fsfe.org/ruphy/2015/10/voices-from-the-first-wikitolearn-sprin/ Riccardo Iaconelli]<br />
* Randa Meetings 2015, 5-12 September, Randa, Switzerland <br />
** [https://dot.kde.org/2015/12/07/randa-meetings-2015-huge-success-again Dot Article]<br />
* LaKademy 2015, 3-6 June, Salvador, Brazil<br />
** [https://dot.kde.org/2015/07/12/lakademy-2015 Dot Article]<br />
* KDE PIM Spring 2015 Sprint, 9-11 April, Toulouse, France <br />
** [https://dot.kde.org/2015/10/12/kde-pim-sprint-toulouse Dot Article]<br />
* Plasma Sprint 2015, 16-22 February, Barcelona, Spain<br />
** [https://dot.kde.org/2015/04/08/plasma-sprint-2015 Dot Article]<br />
<br />
=== 2014 ===<br />
<br />
* PIM Winter Sprint 2014, 21-23 November, Munich, Germany <br />
* Digikam Sprint 2014, 14-16 November, Berlin, Germany <br />
** [https://dot.kde.org/2015/03/05/digikam-sprint-2014 Dot Article]<br />
* Randa Meetings 2014, 9-15 August, Randa, Switzerland <br />
** [https://dot.kde.org/2014/12/08/randa-meetings-2014-another-great-success Dot Article]<br />
* Calligra Sprint 2014, 4-6 July, Deventer, Netherlands <br />
** [https://dot.kde.org/2014/07/27/2014-calligra-sprint-deventer Dot Article]<br />
* Krita 2014 Sprint, 16-18 May, Deventer, Netherlands <br />
** [http://dot.kde.org/2014/06/04/2014-krita-sprint-deventer-netherlands Dot Article]<br />
* Okular Sprint, 8-11 May, Barcelona, Spain<br />
** [https://dot.kde.org/2014/07/27/first-okular-sprint-ever-barcelona Dot Article]<br />
* KDE Frameworks 2014, 24-28 April, Barcelona, Spain<br />
** [https://dot.kde.org/2014/08/13/kde-frameworks-sprint-how-release-platform Dot Article]<br />
* KDE Telepathy 2014, 10-15 April, Barcelona, Spain<br />
** [http://dot.kde.org/2014/04/29/kde-telepathy-sprint Dot Article]<br />
* KDE PIM Sprint 2014, 28-31 March, Barcelona, Spain<br />
** [http://dot.kde.org/2014/05/02/kde-pim-2014-spring-sprint Dot Article]<br />
* Kate and KDevelop Sprint 2014, 18-25 January, Barcelona, Spain<br />
** [http://dot.kde.org/2014/06/05/kate-and-kdevelop-sprint-january-2014 Dot Article]<br />
* Plasma 2, 10-16 January, Barcelona, Spain<br />
** [http://dot.kde.org/2014/01/24/plasma-team-gathers-barcelona Dot Article]<br />
<br />
=== 2013 ===<br />
<br />
* [[KDE_PIM/Meetings/PIM_Autumn_2013_meeting | PIM Autumn 2013 meeting, Brno, November 2013]]<br />
** [http://dot.kde.org/2014/03/03/kde-pim-november-sprint Dot article]<br />
* [[KDEEdu/Sprint2013|KDE Edu Sprint, A Coruña (Galicia Spain), October 2013]]<br />
** [http://dot.kde.org/2013/11/11/kde-edu-2013-sprint Dot article]<br />
* Solid 2013, 18-21 April, Brno, Czech Repulic<br />
** [http://ev.kde.org/reports/ev-quarterly-2013_Q2Q3.pdf Report on 4th page of the Q2+Q3 2013 KDE e.V. report]<br />
* [[Plasma/Tokamak6|Plasma Tokamak 7 Sprint, Nürnberg, April 2013]]<br />
** [http://dot.kde.org/2013/04/24/plasma-pow-wow-produces-detailed-plans-workspace-convergence Dot Article]<br />
* [http://community.kde.org/Calligra/Meetings/Spring_2013_Sprint Calligra spring 2013 sprint, Essen/Bangalore, March 2013]<br />
** [http://ev.kde.org/reports/ev-quarterly-2013_Q1.pdf Report on 6th page of the Q1 2013 KDE e.V. report]<br />
* [http://community.kde.org/KDE_PIM/Meetings/Osnabrueck_11 KDE PIM New Year Meeting 2013, 1-3 March, Berlin, Germany]<br />
** [http://dot.kde.org/2013/04/11/kde-pim-sprint-berlin-2013-cuter-pictures Dot article]<br />
<br />
=== 2012 ===<br />
<br />
* [https://sprints.kde.org/sprint/110 KDE PIM sprint, Berlin, October 2012]<br />
** [http://dot.kde.org/2012/10/25/kde-pim-october-sprint Report on the dot about the sprint]<br />
* [http://dot.kde.org/2012/11/24/katekdevelop-october-sprint-whats-new-kate Kate/KDevelop sprint, Vienna, October 2012]<br />
* [http://www.omat.nl/2012/09/29/minisprint-day-1/] [http://www.omat.nl/2012/09/30/minisprint-day-2/] Webteam/Sysadmin mini sprint, Essen, September 2012<br />
* [http://dot.kde.org/2012/08/13/support-2012-kde-randa-meetings-inspired-and-intense Randa meeting, Randa, September 2012]<br />
* [http://saroengels.blogspot.nl/2012/08/waiting.html KDE on Windows, Osnabrück, August 2012]<br />
* [http://vizzzion.org/blog/2012/06/next-iterations-of-the-kde-workspaces/ KDE Workspaces sprint, Pineda de Mar, June 2012]<br />
* [http://liveblue.wordpress.com/2012/05/06/lakademy-hierarchical-edge-bundles-and-kdevelop/ LaKademy, Porto Alegre, April 2012]<br />
* [http://dot.kde.org/2012/03/13/plasma-active-three-sprint Plasma Active Meeting, Darmstadt, March 2012]<br />
* [http://blogs.kde.org/node/4540] [http://blogs.kde.org/node/4541] Calligra Text Undo Mini Sprint, 19-22 February, Munich<br />
* [[KDE_PIM/Meetings/Osnabrueck_10|KDE PIM Meeting at Osnabrück, February 2012]]<br />
* [http://dot.kde.org/2012/02/22/digikam-team-meets-genoa-italy DigiKam Sprint, Genoa, January 2012]<br />
<br />
=== 2011 ===<br />
<br />
* [http://community.kde.org/KDE_Mobile/Sprints/November2011-Planning KDE Mobile on Harmattan Sprint, 18-20 November, Berlin]<br />
* [http://community.kde.org/KDE_e.V./Sprint2011 KDE e.V. Sprint, 19-20 November, Berlin]<br />
* Calligra Fall 2011, 11-13 November, Helsinki, Finland<br />
* [[Gluon/Sprint_Oct2011|Gluon Sprint Fall 2011, Munich, Germany, 21-23 October]]<br />
* [[Solid/Sprint2011 | Solid sprint, 29 September to 2 October, Madrid]]<br />
* [http://community.kde.org/Telepathy/Events/TelepathySprint2 KDE Telepathy sprint, Cambridge, UK, September 2011]<br />
* [https://sprints.kde.org/sprint/37 Plasma Active sprint, Darmstadt, Germany, September 2011]<br />
* [http://dot.kde.org/2011/06/29/platform-frameworks-kde-hackers-meet-switzerland, Randa, Switzerland, June 2011]<br />
* [[Sprints/Randa/2011/Nepomuk|Nepomuk Sprint, Randa, Switzerland, June 2011]]<br />
* [[Amarok/RandaSprint2011 |Multimedia Sprint, Randa, Switzerland, June 2011]]<br />
* [[Sprints/Randa/2011|KDevelop-Kate Sprint, Randa, Switzerland, June 2011]]<br />
* [[KDE-WWW/WebWorld2011|WebWorld 2011 Sprint - LinuxHotel in Essen, from 1st to 5th June 2011]]<br />
** [http://dot.kde.org/2011/06/08/webworld-2011-building-next-kde-web WebWorld 2011: Building next KDE Web]<br />
* [http://community.kde.org/Plasma/Tokamak5 Plasma/Tokamak 5 Meeting, Nijmengen, The Netherlands, 25 April-1 May 2011]<br />
* [http://dot.kde.org/2011/05/18/open-collaboration-services-next-sprint Open Collaboration Services Next sprint], Berlin, Germany, 14-15 May 2011<br />
* [http://community.kde.org/Sprints/Promo/2011 Promo sprint], Southampton, England, May 2011<br />
** [http://dot.kde.org/2011/05/16/promo-sprint-2011 Promo Sprint 2011]<br />
* [http://krita.org/component/content/article/10-news/77-second-day-of-the-third-krita-sprint Krita 2011 Sprint 20-22 May, Amsterdam, Netherlands]<br />
** [http://dot.kde.org/2011/06/02/what-happens-when-artists-and-developers-come-together-2011-krita-sprint Krita Sprint 2011]<br />
* [[Sprints/ownCloud2011| ownCloud sprint, Stuttgart, 15-18, April 2011]]<br />
** [http://dot.kde.org/2011/04/21/first-owncloud-sprint ownCloud Sprint]<br />
* [[Sprints/UX2011| KDE UX Sprint, Berlin, 15-17, April 2011]]<br />
* [http://community.kde.org/KDEEdu/Sprint2011 KDE Edu Sprint, Bilbao, Spain, 7-11 April 2011]<br />
* [http://dot.kde.org/2011/04/15/first-calligra-sprint First Calligra sprint], Berlin, Germany, April 2011<br />
* [http://community.kde.org/KDE_Games/Sprint_2011 KDE Games Sprint 2011 - Dresden, Germany, 25-27 March 2011]<br />
* [http://community.kde.org/KDE_PIM/Meetings/Osnabrueck_9 Osnabrück 9, annual KDE PIM meeting], Osnabrück, Germany, February 2011<br />
** [http://dot.kde.org/2011/03/15/9th-annual-pim-meeting-renews-commitment-innovation Osnabrück Annual KDE PIM meeting]<br />
<br />
=== 2010 ===<br />
* [[KDE_Mobile/Sprints/November2010-Results|KDE Mobile Meeting, Berlin, Germany, November 2010]]<br />
** [http://dot.kde.org/2010/12/03/kdes-mobile-team-meets-first-sprint The KDE Mobile team meets in Berlin for first sprint]<br />
* [[Multimedia/MarbleWeekend|KDE Marble sprint, Nuremberg, Germany, 5th to 7th November 2010]]<br />
** [http://dot.kde.org/2010/11/10/kdes-marble-team-holds-first-contributor-sprint The KDE Marble team at the first contributor sprint]<br />
* [http://amarok.kde.org/blog/archives/1188-Ovi-and-KDE-Sprint.html Ovi and KDE sprint, Munich, Germany, October 2010]<br />
*[[Solid/Sprint2010|Solid sprint, Madrid, Spain, 1st to 3rd October 2010]]<br />
** [http://dot.kde.org/2010/10/13/solid-sprint-enhances-key-kde-platform-technologies The KDE Solid team at the sprint in Madrid]<br />
*[[KDE_e.V./Sprints/Telepathy-2010-09|KDE Telepathy sprint, Cambridge, England, September 2010]]<br />
** [http://dot.kde.org/2010/10/17/kde-telepathy-sprint The KDE Telepathy sprint in Cambridge]<br />
* [http://www.digikam.org/drupal/node/538 KDE Imaging sprint, Aix-en-Provence, France, August 2010]<br />
* [http://dot.kde.org/2010/06/25/koffice-2010-summer-sprint-report KOffice sprint, Essen, Germany, June 2010]<br />
* KDE Windows meeting, Osnabrueck, Germany, June 2010<br />
* [http://dot.kde.org/2010/06/03/kde-pim-stabilization-sprint Akonadi meeting, Berlin, Germany, May 2010]<br />
* [[KDE_e.V./Sprints/Multimedia-2010-05|Multimedia sprint, Randa, Switzerland, May 2010]]<br />
* [[KDE_e.V./Sprints/Amarok-2010-05|Amarok sprint, Randa, Switzerland, May 2010]]<br />
* [[KDE_e.V./Sprints/KdeEdu-2010|KDE-Edu 2010, KDE-Edu Meeting in Randa, Switzerland, 20th to 25th May 2010]]<br />
** [http://dot.kde.org/2010/06/19/report-successful-multimedia-and-edu-sprint-randa Joint meeting with KDE multimedia]<br />
* [http://dot.kde.org/2010/07/15/successful-kde-finances-sprint-held KDE Finance Apps Meeting, Frankfurt, Germany, April/May 2010]<br />
* [http://br.kde.org/Akademy-BR_2010 Akademy-br, Praia do Forte, Brazil, April 2010]<br />
* [http://dot.kde.org/2010/03/15/second-krita-sprint-ends-tea Krita sprint, Deventer, The Netherlands, February 2010]<br />
* [http://www.valdyas.org/fading/index.cgi/2010/02/22 KPresenter sprint, February 2010]<br />
* [http://dot.kde.org/2010/03/08/kate-kdevelop-and-okteta-developers-meet-berlin KWrite/Kate & KDevelop Meeting, Berlin, Germany, February 2010]<br />
* [[KDE_e.V./Sprints/Tokamak4|Tokamak 4, Plasma, KWin and Oxygen Meeting, Nürnberg, Germany, February 2010 ]]<br />
* [http://dot.kde.org/2010/01/14/annual-osnabr%C3%BCck-pim-meeting-brings-exciting-announcements-and-ambitious-plans KDE PIM Meeting, Osnabrück, Germany, January 2010]<br />
** [http://www.linux-magazine.com/Online/News/Cold-War-at-the-Eighth-KDE-PIM-Gathering Linux Magazine article about the KDE PIM Meeting]<br />
<br />
=== 2009 ===<br />
<br />
* [http://dot.kde.org/2009/11/22/digikam-and-kipi-sprint KDE Imaging Sprint, Essen, November 2009]<br />
* [http://dot.kde.org/2009/11/20/booth-web-and-marketing-sprint KDE Marketing & Promo Meeting, Stuttgart, November 2009]<br />
* [http://dot.kde.org/2009/11/29/second-koffice-developer-sprint-2009-kickoff KOffice Meeting, Oslo, November 2009]<br />
* KDE Coherence Meeting, Barcelona, October 2009<br />
* [http://dot.kde.org/2009/10/28/gluon-sprint-wrap KDE Games Meeting, Munich, October 2009]<br />
* [http://dot.kde.org/2009/11/06/second-akonadi-sprint-re-factors-communication Akonadi Meeting, Berlin, October 2009]<br />
* [http://dot.kde.org/2009/09/08/third-plasma-summit-lifts-kde-desktop-higher-grounds Plasma Meeting, Tokamak 3, Randa, September 2009]<br />
* KDE Wiki Meeting, Berlin, July 2009<br />
* [http://dot.kde.org/2009/06/13/koffice-2009-sprint-berlin KOffice Meeting, Berlin, June 2009]<br />
* Nepomuk Meeting, Freiburg, June 2009<br />
* [http://dot.kde.org/2009/06/10/network-manager-sprint-oslo Network Manager Meeting, Oslo, June 2009]<br />
* GSoC Meeting, Boston, May 2009<br />
* [http://dot.kde.org/2009/05/07/amarok-developer-sprint-looking-back-rocking-weekend Amarok Meeting, Berlin, May 2009]<br />
* KDE Coherence Meeting, Paris, May 2009<br />
* KDevelop Meeting, Mykolayiv, April 2009<br />
* [http://dot.kde.org/2009/04/06/pim-hackers-boost-akonadi-future Akonadi Meeting, Berlin, April 2009]<br />
* [http://dot.kde.org/2009/02/11/plasma-team-looks-future Plasma Meeting, Tokamak 2, Oporto, February 2009]<br />
* KDE PIM Meeting, Osnabrück, January 2009<br />
* [http://camp.kde.org Camp KDE Jamaica, January 2009]<br />
<br />
=== 2008 ===<br />
<br />
* [http://dot.kde.org/2008/11/11/koffice-sprint-2008 KOffice Meeting, Berlin, November 2008]<br />
* Akonadi Halloween Sprint, Essen, November 2008<br />
* KDE Graphics, Genoa, October 2008<br />
* KPhotoalbum Sprint, Aalborg, September 2008<br />
* Syncing Meeting, Berlin, August 2008<br />
* [http://dot.kde.org/2008/07/21/kde-bindings-kross-meeting KDE Bindings / Kross Meeting, Berlin, July 2008]<br />
* [http://dot.kde.org/2008/04/10/kdevelop-team-meeting-agenda KDevelop Team Meeting, Munich, April 2008]<br />
* [http://dot.kde.org/2008/04/21/tokamak-sprint-turns-plasma-upside-down Tokamak Plasma Sprint, Milan, April 2008]<br />
* [http://dot.kde.org/2008/04/15/kate-developers-meeting Kate Developer Meeting, Darmstadt, April 2008]<br />
* [http://dot.kde.org/2008/03/27/akonadi-sprint-readies-kde-41 Akonadi Developer Meeting, Berlin, March 2008]<br />
* [http://dot.kde.org/2008/02/21/kde-pim-team-meets-talk-akonadi-and-kde-41 KDE PIM Meeting in Osnabrück, February 2008]<br />
* [http://dot.kde.org/2008/01/20/second-day-kde-40-release-event KDE 4.0 Release Event, Mountain View, January 2008]<br />
<br />
<br />
=== 2007 ===<br />
<br />
* [http://dot.kde.org/2007/12/06/first-kde-education-meeting-great-success KDE EDU Meeting, Paris, December 2007]<br />
* [http://dot.kde.org/2007/10/30/second-koffice-sprint-berlin-focuses-release-polish KOffice Spit'n'Polish meeting, Berlin, October 2007]<br />
* [http://dot.kde.org/2007/09/18/windows-developers-meet-berlin KDE on Windows Meeting, Berlin, September 2007]<br />
* Amarok meeting at aKademy, Glasgow, July 2007<br />
* Oxygen meeting in Milan, June 2007<br />
* [http://dot.kde.org/2007/05/14/koffice-odf-sprint-report ODF meeting in Berlin, May 2007]<br />
* [http://dot.kde.org/2007/04/25/akonadi-hacking-meeting Akonadi meeting in Berlin, April 2007]<br />
* [http://dot.kde.org/2007/01/29/kde-pim-annual-meeting-pushes-advanced-design-enterprise-stability KDE PIM Meeting at Osnabrück, January 2007]<br />
<br />
=== 2006 ===<br />
* [http://dot.kde.org/1151271635/ KDE 4 Core, Trysil, July 2006]</div>Sandrohttps://community.kde.org/index.php?title=Sprints&diff=82441Sprints2019-01-08T09:55:11Z<p>Sandro: Add Privacy Sprint in March in Leipzig</p>
<hr />
<div>[[File:Mascot konqi-app-dev.png|thumbnail|right|Join [[Konqi]] and do some coding together!]]<br />
KDE Developer Sprints are focused gatherings of KDE developers to work on a specific part of KDE. Sprints are an opportunity to plan, design, and hack (think 20% socialization and 80% perspiration). They are supported by KDE e.V. financially and organizationally.<br />
<br />
Want to organize a sprint or attending a sprint? Everyone should read the [http://ev.kde.org/rules/sprint_policy.php KDE Sprint Policy] for information about the KDE Developer Sprint process.<br />
<br />
== Upcoming Sprints ==<br />
* [[Sprints/Plasma Mobile/2019 | Plasma Mobile Sprint 2019, 4-9 February, Berlin, Germany]]<br />
* Goal sprint - privacy, 22-26 March, Leipzig, Germany [https://phabricator.kde.org/T8622 some information on T8622]<br />
* Goal sprint - onboarding, tbd, tbd<br />
* Goal sprint - productivity and usability, tbd, tbd<br />
<br />
== Past Sprints ==<br />
<br />
=== 2018 ===<br />
* [[Sprints/Plasma/2018 | Plasma Sprint 2018, 21-27 April, Berlin, Germany]]<br />
* Kdenlive Sprint 2018, 25-29 April, France<br />
* KDE e.V. board meeting, 28-29 April, Berlin, Germany <br />
* [[Krita/Sprint2018|Krita Sprint 2018, 17 - 21 May, Deventer, The Netherlands]]<br />
* KDE Connect Sprint 2018, 23-25 March, Barcelona, Spain<br />
* [[Sprints/Promo/2018 | KDE Promo Sprint, 16-18 February, Barcelona, Spain]]<br />
* [[Sprints/PIM/2018 | PIM Sprint 2018, 20-22 April, Toulouse, France]]<br />
* [[Sprints/Plasma/2018 | Plasma Sprint, Berlin ]]<br />
<br />
=== 2017 ===<br />
* KDE e.V. board meeting, 14-15, October, Berlin, Germany<br />
* KDE Edu sprint, 7-9, October, Germany<br />
* Randa Meetings, 10-16 September, Randa, Switzerland<br />
* QtCon Brazil, 18-20, August, Brazil<br />
* KDE e.V. board meeting, 13-14 May, Berlin, Germany<br />
* LaKademy, 28 April - 1 May, Brazil<br />
* KDE PIM sprint, 7-9, April, France<br />
* conf.kde.in, 10-12, March, India<br />
* Plasma Sprint, 6-12 February, Germany<br />
* WikiToLearn Conf India, 18-19 January, India<br />
<br />
=== 2016 ===<br />
* Krita 2016, 25-28 August, Deventer, Netherlands <br />
** [https://krita.org/en/item/2016-krita-sprint-day-1/ Day 1]<br />
** [https://krita.org/en/item/new-builds-to-test-krita-sprint-to-end-soon/ Final day]<br />
* Randa Meetings 2016, 11-18 June, Randa, Switzerland <br />
**[https://community.kde.org/Sprints/Randa/2016#News_Articles News Articles]<br />
* KDE Store Sprint 2016, 4-7 June, Bielefeld, Germany <br />
* LaKademy 2016, 25-28 May, Rio de Janeiro, Brazil <br />
**[https://dot.kde.org/2016/06/14/lakademy-2016-%E2%80%92-strewing-floss-culture Dot article]<br />
* KDE PIM Spring Sprint 2016, 31-3 April, Toulouse, France <br />
**[https://dot.kde.org/2016/04/15/kde-pim-spring-sprint-report-toulouse Dot article]<br />
* KDE CERN 2016, 6-12 March, Geneva, Switzerland <br />
**[https://dot.kde.org/2016/03/23/plasma-team-gets-physical Dot article about the Plasma side]<br />
* New Year 2016 Words Sprint, 21-23 January, Deventer, Netherlands<br />
**[https://frinring.wordpress.com/2016/01/25/new-year-calligra-words-sprint/ Friedrich W. H. Kossebau Blog]<br />
<br />
=== 2015 ===<br />
* Kate/Kile/KDevelop Sprint 2015, 6-10 October, Berlin, Germany<br />
** [https://kate-editor.org/2015/10/11/katekdevelop-sprint-2015-summary-for-kate/ Kate Editor Blog]<br />
* WikiToLearn Sprint 2015, 28-30 September, Bormio, Italy<br />
** [http://blogs.fsfe.org/ruphy/2015/10/voices-from-the-first-wikitolearn-sprin/ Riccardo Iaconelli]<br />
* Randa Meetings 2015, 5-12 September, Randa, Switzerland <br />
** [https://dot.kde.org/2015/12/07/randa-meetings-2015-huge-success-again Dot Article]<br />
* LaKademy 2015, 3-6 June, Salvador, Brazil<br />
** [https://dot.kde.org/2015/07/12/lakademy-2015 Dot Article]<br />
* KDE PIM Spring 2015 Sprint, 9-11 April, Toulouse, France <br />
** [https://dot.kde.org/2015/10/12/kde-pim-sprint-toulouse Dot Article]<br />
* Plasma Sprint 2015, 16-22 February, Barcelona, Spain<br />
** [https://dot.kde.org/2015/04/08/plasma-sprint-2015 Dot Article]<br />
<br />
=== 2014 ===<br />
<br />
* PIM Winter Sprint 2014, 21-23 November, Munich, Germany <br />
* Digikam Sprint 2014, 14-16 November, Berlin, Germany <br />
** [https://dot.kde.org/2015/03/05/digikam-sprint-2014 Dot Article]<br />
* Randa Meetings 2014, 9-15 August, Randa, Switzerland <br />
** [https://dot.kde.org/2014/12/08/randa-meetings-2014-another-great-success Dot Article]<br />
* Calligra Sprint 2014, 4-6 July, Deventer, Netherlands <br />
** [https://dot.kde.org/2014/07/27/2014-calligra-sprint-deventer Dot Article]<br />
* Krita 2014 Sprint, 16-18 May, Deventer, Netherlands <br />
** [http://dot.kde.org/2014/06/04/2014-krita-sprint-deventer-netherlands Dot Article]<br />
* Okular Sprint, 8-11 May, Barcelona, Spain<br />
** [https://dot.kde.org/2014/07/27/first-okular-sprint-ever-barcelona Dot Article]<br />
* KDE Frameworks 2014, 24-28 April, Barcelona, Spain<br />
** [https://dot.kde.org/2014/08/13/kde-frameworks-sprint-how-release-platform Dot Article]<br />
* KDE Telepathy 2014, 10-15 April, Barcelona, Spain<br />
** [http://dot.kde.org/2014/04/29/kde-telepathy-sprint Dot Article]<br />
* KDE PIM Sprint 2014, 28-31 March, Barcelona, Spain<br />
** [http://dot.kde.org/2014/05/02/kde-pim-2014-spring-sprint Dot Article]<br />
* Kate and KDevelop Sprint 2014, 18-25 January, Barcelona, Spain<br />
** [http://dot.kde.org/2014/06/05/kate-and-kdevelop-sprint-january-2014 Dot Article]<br />
* Plasma 2, 10-16 January, Barcelona, Spain<br />
** [http://dot.kde.org/2014/01/24/plasma-team-gathers-barcelona Dot Article]<br />
<br />
=== 2013 ===<br />
<br />
* [[KDE_PIM/Meetings/PIM_Autumn_2013_meeting | PIM Autumn 2013 meeting, Brno, November 2013]]<br />
** [http://dot.kde.org/2014/03/03/kde-pim-november-sprint Dot article]<br />
* [[KDEEdu/Sprint2013|KDE Edu Sprint, A Coruña (Galicia Spain), October 2013]]<br />
** [http://dot.kde.org/2013/11/11/kde-edu-2013-sprint Dot article]<br />
* Solid 2013, 18-21 April, Brno, Czech Repulic<br />
** [http://ev.kde.org/reports/ev-quarterly-2013_Q2Q3.pdf Report on 4th page of the Q2+Q3 2013 KDE e.V. report]<br />
* [[Plasma/Tokamak6|Plasma Tokamak 7 Sprint, Nürnberg, April 2013]]<br />
** [http://dot.kde.org/2013/04/24/plasma-pow-wow-produces-detailed-plans-workspace-convergence Dot Article]<br />
* [http://community.kde.org/Calligra/Meetings/Spring_2013_Sprint Calligra spring 2013 sprint, Essen/Bangalore, March 2013]<br />
** [http://ev.kde.org/reports/ev-quarterly-2013_Q1.pdf Report on 6th page of the Q1 2013 KDE e.V. report]<br />
* [http://community.kde.org/KDE_PIM/Meetings/Osnabrueck_11 KDE PIM New Year Meeting 2013, 1-3 March, Berlin, Germany]<br />
** [http://dot.kde.org/2013/04/11/kde-pim-sprint-berlin-2013-cuter-pictures Dot article]<br />
<br />
=== 2012 ===<br />
<br />
* [https://sprints.kde.org/sprint/110 KDE PIM sprint, Berlin, October 2012]<br />
** [http://dot.kde.org/2012/10/25/kde-pim-october-sprint Report on the dot about the sprint]<br />
* [http://dot.kde.org/2012/11/24/katekdevelop-october-sprint-whats-new-kate Kate/KDevelop sprint, Vienna, October 2012]<br />
* [http://www.omat.nl/2012/09/29/minisprint-day-1/] [http://www.omat.nl/2012/09/30/minisprint-day-2/] Webteam/Sysadmin mini sprint, Essen, September 2012<br />
* [http://dot.kde.org/2012/08/13/support-2012-kde-randa-meetings-inspired-and-intense Randa meeting, Randa, September 2012]<br />
* [http://saroengels.blogspot.nl/2012/08/waiting.html KDE on Windows, Osnabrück, August 2012]<br />
* [http://vizzzion.org/blog/2012/06/next-iterations-of-the-kde-workspaces/ KDE Workspaces sprint, Pineda de Mar, June 2012]<br />
* [http://liveblue.wordpress.com/2012/05/06/lakademy-hierarchical-edge-bundles-and-kdevelop/ LaKademy, Porto Alegre, April 2012]<br />
* [http://dot.kde.org/2012/03/13/plasma-active-three-sprint Plasma Active Meeting, Darmstadt, March 2012]<br />
* [http://blogs.kde.org/node/4540] [http://blogs.kde.org/node/4541] Calligra Text Undo Mini Sprint, 19-22 February, Munich<br />
* [[KDE_PIM/Meetings/Osnabrueck_10|KDE PIM Meeting at Osnabrück, February 2012]]<br />
* [http://dot.kde.org/2012/02/22/digikam-team-meets-genoa-italy DigiKam Sprint, Genoa, January 2012]<br />
<br />
=== 2011 ===<br />
<br />
* [http://community.kde.org/KDE_Mobile/Sprints/November2011-Planning KDE Mobile on Harmattan Sprint, 18-20 November, Berlin]<br />
* [http://community.kde.org/KDE_e.V./Sprint2011 KDE e.V. Sprint, 19-20 November, Berlin]<br />
* Calligra Fall 2011, 11-13 November, Helsinki, Finland<br />
* [[Gluon/Sprint_Oct2011|Gluon Sprint Fall 2011, Munich, Germany, 21-23 October]]<br />
* [[Solid/Sprint2011 | Solid sprint, 29 September to 2 October, Madrid]]<br />
* [http://community.kde.org/Telepathy/Events/TelepathySprint2 KDE Telepathy sprint, Cambridge, UK, September 2011]<br />
* [https://sprints.kde.org/sprint/37 Plasma Active sprint, Darmstadt, Germany, September 2011]<br />
* [http://dot.kde.org/2011/06/29/platform-frameworks-kde-hackers-meet-switzerland, Randa, Switzerland, June 2011]<br />
* [[Sprints/Randa/2011/Nepomuk|Nepomuk Sprint, Randa, Switzerland, June 2011]]<br />
* [[Amarok/RandaSprint2011 |Multimedia Sprint, Randa, Switzerland, June 2011]]<br />
* [[Sprints/Randa/2011|KDevelop-Kate Sprint, Randa, Switzerland, June 2011]]<br />
* [[KDE-WWW/WebWorld2011|WebWorld 2011 Sprint - LinuxHotel in Essen, from 1st to 5th June 2011]]<br />
** [http://dot.kde.org/2011/06/08/webworld-2011-building-next-kde-web WebWorld 2011: Building next KDE Web]<br />
* [http://community.kde.org/Plasma/Tokamak5 Plasma/Tokamak 5 Meeting, Nijmengen, The Netherlands, 25 April-1 May 2011]<br />
* [http://dot.kde.org/2011/05/18/open-collaboration-services-next-sprint Open Collaboration Services Next sprint], Berlin, Germany, 14-15 May 2011<br />
* [http://community.kde.org/Sprints/Promo/2011 Promo sprint], Southampton, England, May 2011<br />
** [http://dot.kde.org/2011/05/16/promo-sprint-2011 Promo Sprint 2011]<br />
* [http://krita.org/component/content/article/10-news/77-second-day-of-the-third-krita-sprint Krita 2011 Sprint 20-22 May, Amsterdam, Netherlands]<br />
** [http://dot.kde.org/2011/06/02/what-happens-when-artists-and-developers-come-together-2011-krita-sprint Krita Sprint 2011]<br />
* [[Sprints/ownCloud2011| ownCloud sprint, Stuttgart, 15-18, April 2011]]<br />
** [http://dot.kde.org/2011/04/21/first-owncloud-sprint ownCloud Sprint]<br />
* [[Sprints/UX2011| KDE UX Sprint, Berlin, 15-17, April 2011]]<br />
* [http://community.kde.org/KDEEdu/Sprint2011 KDE Edu Sprint, Bilbao, Spain, 7-11 April 2011]<br />
* [http://dot.kde.org/2011/04/15/first-calligra-sprint First Calligra sprint], Berlin, Germany, April 2011<br />
* [http://community.kde.org/KDE_Games/Sprint_2011 KDE Games Sprint 2011 - Dresden, Germany, 25-27 March 2011]<br />
* [http://community.kde.org/KDE_PIM/Meetings/Osnabrueck_9 Osnabrück 9, annual KDE PIM meeting], Osnabrück, Germany, February 2011<br />
** [http://dot.kde.org/2011/03/15/9th-annual-pim-meeting-renews-commitment-innovation Osnabrück Annual KDE PIM meeting]<br />
<br />
=== 2010 ===<br />
* [[KDE_Mobile/Sprints/November2010-Results|KDE Mobile Meeting, Berlin, Germany, November 2010]]<br />
** [http://dot.kde.org/2010/12/03/kdes-mobile-team-meets-first-sprint The KDE Mobile team meets in Berlin for first sprint]<br />
* [[Multimedia/MarbleWeekend|KDE Marble sprint, Nuremberg, Germany, 5th to 7th November 2010]]<br />
** [http://dot.kde.org/2010/11/10/kdes-marble-team-holds-first-contributor-sprint The KDE Marble team at the first contributor sprint]<br />
* [http://amarok.kde.org/blog/archives/1188-Ovi-and-KDE-Sprint.html Ovi and KDE sprint, Munich, Germany, October 2010]<br />
*[[Solid/Sprint2010|Solid sprint, Madrid, Spain, 1st to 3rd October 2010]]<br />
** [http://dot.kde.org/2010/10/13/solid-sprint-enhances-key-kde-platform-technologies The KDE Solid team at the sprint in Madrid]<br />
*[[KDE_e.V./Sprints/Telepathy-2010-09|KDE Telepathy sprint, Cambridge, England, September 2010]]<br />
** [http://dot.kde.org/2010/10/17/kde-telepathy-sprint The KDE Telepathy sprint in Cambridge]<br />
* [http://www.digikam.org/drupal/node/538 KDE Imaging sprint, Aix-en-Provence, France, August 2010]<br />
* [http://dot.kde.org/2010/06/25/koffice-2010-summer-sprint-report KOffice sprint, Essen, Germany, June 2010]<br />
* KDE Windows meeting, Osnabrueck, Germany, June 2010<br />
* [http://dot.kde.org/2010/06/03/kde-pim-stabilization-sprint Akonadi meeting, Berlin, Germany, May 2010]<br />
* [[KDE_e.V./Sprints/Multimedia-2010-05|Multimedia sprint, Randa, Switzerland, May 2010]]<br />
* [[KDE_e.V./Sprints/Amarok-2010-05|Amarok sprint, Randa, Switzerland, May 2010]]<br />
* [[KDE_e.V./Sprints/KdeEdu-2010|KDE-Edu 2010, KDE-Edu Meeting in Randa, Switzerland, 20th to 25th May 2010]]<br />
** [http://dot.kde.org/2010/06/19/report-successful-multimedia-and-edu-sprint-randa Joint meeting with KDE multimedia]<br />
* [http://dot.kde.org/2010/07/15/successful-kde-finances-sprint-held KDE Finance Apps Meeting, Frankfurt, Germany, April/May 2010]<br />
* [http://br.kde.org/Akademy-BR_2010 Akademy-br, Praia do Forte, Brazil, April 2010]<br />
* [http://dot.kde.org/2010/03/15/second-krita-sprint-ends-tea Krita sprint, Deventer, The Netherlands, February 2010]<br />
* [http://www.valdyas.org/fading/index.cgi/2010/02/22 KPresenter sprint, February 2010]<br />
* [http://dot.kde.org/2010/03/08/kate-kdevelop-and-okteta-developers-meet-berlin KWrite/Kate & KDevelop Meeting, Berlin, Germany, February 2010]<br />
* [[KDE_e.V./Sprints/Tokamak4|Tokamak 4, Plasma, KWin and Oxygen Meeting, Nürnberg, Germany, February 2010 ]]<br />
* [http://dot.kde.org/2010/01/14/annual-osnabr%C3%BCck-pim-meeting-brings-exciting-announcements-and-ambitious-plans KDE PIM Meeting, Osnabrück, Germany, January 2010]<br />
** [http://www.linux-magazine.com/Online/News/Cold-War-at-the-Eighth-KDE-PIM-Gathering Linux Magazine article about the KDE PIM Meeting]<br />
<br />
=== 2009 ===<br />
<br />
* [http://dot.kde.org/2009/11/22/digikam-and-kipi-sprint KDE Imaging Sprint, Essen, November 2009]<br />
* [http://dot.kde.org/2009/11/20/booth-web-and-marketing-sprint KDE Marketing & Promo Meeting, Stuttgart, November 2009]<br />
* [http://dot.kde.org/2009/11/29/second-koffice-developer-sprint-2009-kickoff KOffice Meeting, Oslo, November 2009]<br />
* KDE Coherence Meeting, Barcelona, October 2009<br />
* [http://dot.kde.org/2009/10/28/gluon-sprint-wrap KDE Games Meeting, Munich, October 2009]<br />
* [http://dot.kde.org/2009/11/06/second-akonadi-sprint-re-factors-communication Akonadi Meeting, Berlin, October 2009]<br />
* [http://dot.kde.org/2009/09/08/third-plasma-summit-lifts-kde-desktop-higher-grounds Plasma Meeting, Tokamak 3, Randa, September 2009]<br />
* KDE Wiki Meeting, Berlin, July 2009<br />
* [http://dot.kde.org/2009/06/13/koffice-2009-sprint-berlin KOffice Meeting, Berlin, June 2009]<br />
* Nepomuk Meeting, Freiburg, June 2009<br />
* [http://dot.kde.org/2009/06/10/network-manager-sprint-oslo Network Manager Meeting, Oslo, June 2009]<br />
* GSoC Meeting, Boston, May 2009<br />
* [http://dot.kde.org/2009/05/07/amarok-developer-sprint-looking-back-rocking-weekend Amarok Meeting, Berlin, May 2009]<br />
* KDE Coherence Meeting, Paris, May 2009<br />
* KDevelop Meeting, Mykolayiv, April 2009<br />
* [http://dot.kde.org/2009/04/06/pim-hackers-boost-akonadi-future Akonadi Meeting, Berlin, April 2009]<br />
* [http://dot.kde.org/2009/02/11/plasma-team-looks-future Plasma Meeting, Tokamak 2, Oporto, February 2009]<br />
* KDE PIM Meeting, Osnabrück, January 2009<br />
* [http://camp.kde.org Camp KDE Jamaica, January 2009]<br />
<br />
=== 2008 ===<br />
<br />
* [http://dot.kde.org/2008/11/11/koffice-sprint-2008 KOffice Meeting, Berlin, November 2008]<br />
* Akonadi Halloween Sprint, Essen, November 2008<br />
* KDE Graphics, Genoa, October 2008<br />
* KPhotoalbum Sprint, Aalborg, September 2008<br />
* Syncing Meeting, Berlin, August 2008<br />
* [http://dot.kde.org/2008/07/21/kde-bindings-kross-meeting KDE Bindings / Kross Meeting, Berlin, July 2008]<br />
* [http://dot.kde.org/2008/04/10/kdevelop-team-meeting-agenda KDevelop Team Meeting, Munich, April 2008]<br />
* [http://dot.kde.org/2008/04/21/tokamak-sprint-turns-plasma-upside-down Tokamak Plasma Sprint, Milan, April 2008]<br />
* [http://dot.kde.org/2008/04/15/kate-developers-meeting Kate Developer Meeting, Darmstadt, April 2008]<br />
* [http://dot.kde.org/2008/03/27/akonadi-sprint-readies-kde-41 Akonadi Developer Meeting, Berlin, March 2008]<br />
* [http://dot.kde.org/2008/02/21/kde-pim-team-meets-talk-akonadi-and-kde-41 KDE PIM Meeting in Osnabrück, February 2008]<br />
* [http://dot.kde.org/2008/01/20/second-day-kde-40-release-event KDE 4.0 Release Event, Mountain View, January 2008]<br />
<br />
<br />
=== 2007 ===<br />
<br />
* [http://dot.kde.org/2007/12/06/first-kde-education-meeting-great-success KDE EDU Meeting, Paris, December 2007]<br />
* [http://dot.kde.org/2007/10/30/second-koffice-sprint-berlin-focuses-release-polish KOffice Spit'n'Polish meeting, Berlin, October 2007]<br />
* [http://dot.kde.org/2007/09/18/windows-developers-meet-berlin KDE on Windows Meeting, Berlin, September 2007]<br />
* Amarok meeting at aKademy, Glasgow, July 2007<br />
* Oxygen meeting in Milan, June 2007<br />
* [http://dot.kde.org/2007/05/14/koffice-odf-sprint-report ODF meeting in Berlin, May 2007]<br />
* [http://dot.kde.org/2007/04/25/akonadi-hacking-meeting Akonadi meeting in Berlin, April 2007]<br />
* [http://dot.kde.org/2007/01/29/kde-pim-annual-meeting-pushes-advanced-design-enterprise-stability KDE PIM Meeting at Osnabrück, January 2007]<br />
<br />
=== 2006 ===<br />
* [http://dot.kde.org/1151271635/ KDE 4 Core, Trysil, July 2006]</div>Sandrohttps://community.kde.org/index.php?title=Akademy/2018/GPGKeys&diff=81097Akademy/2018/GPGKeys2018-08-11T21:59:18Z<p>Sandro: Added myself to list</p>
<hr />
<div>= Why =<br />
<br />
GPG signing is our preferred method of establishing authenticity of anything ranging from mails to release tarballs/tags. To make this easy to verify and trustworthy it is useful to have yourself wired into the KDE web of trust (i.e. get your key signed by other KDE contributors).<br />
<br />
If you are release manager of a project or a distribution packager it is<br />
highly recommended that you attend this BoF to get yourself wired into<br />
the release web of trust which makes tarball signature verification a<br />
lot easier.<br />
<br />
There's lots of good guides on GPG in general and key signing in specific out on the internet, it is recommended you read up on this a bit. We'll only explain the process in broad strokes at the BoF. If you have questions you can send a mail to sitter@kde.org<br />
<br />
= How This Works - READ THIS! =<br />
<br />
Add the name and email address of your key as well as the fingerprint below. Tuesday morning at 10:00 Harald is going to do a print out for all listed attendants. If you would like to do your own print out, please send a mail to ''sitter@kde.org''. If you are not listed by Tuesday morning you'll have to pay 900 Euros penalty (increased from 2017 because of inflation and Brexit uncertainties)! Please make sure that you send a mail if you add yourself after the deadline.<br />
<br />
To get your key fingerprint, you'll want to run gpg or gpg2 with the --fingerprint argument and your name or short ID.<br />
<br />
<code><br />
gpg2 --fingerprint Sitter<br />
</code><br />
<br />
'''Make sure to bring an ID card or preferably a passport so we can verify you are who you claim to be at the BoF.'''<br />
{| class="wikitable" border="1"<br />
|-<br />
! Key OK<br />
! Name <EMail> <br />
! Fingerpint<br />
! ID OK<br />
|-<br />
| ☐ <br />
| Harald Sitter <sitter@kde.org><br />
| CB93 8752 1E1E E012 7DA8 0484 3FDB B550 84CC 5D84<br />
| ☐<br />
|-<br />
| ☐<br />
| Bhushan Shah <bshah@kde.org><br />
Bhushan Shah <bhush94@gmail.com> <br />
| 0AAC 775B B643 7A8D 9AF7 A3AC FE07 8411 7FBC E11D<br />
| ☐<br />
|-<br />
| ☐ <br />
| Elvis Angelaccio <elvis.angelaccio@kde.org><br />
| F07D 85CA A18A CF46 A346 FD01 7C7F C6EA 8633 B4EA<br />
| ☐<br />
|-<br />
| ☐ <br />
| Stefan Derkits <stefan@derkits.at><br />
| E676 487A F993 5EE7 FB42 DDF9 959B C031 5FCD 8062<br />
| ☐<br />
|-<br />
| ☐ <br />
| Andre Heinecke <aheinecke@gnupg.org><br />
Andre Heinecke <andre@heinecke.or.at><br />
| 94A5 C9A0 3C2F E5CA 3B09 5D8E 1FDF 723C F462 B6B1<br />
| ☐<br />
|-<br />
| ☐ <br />
| Andre Heinecke (Release Signing Key)<br />
| 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28<br />
| ☐<br />
|-<br />
| ☐<br />
| Johannes Zarl-Zierl <johannes@zarl-zierl.at><br />
Johannes Zarl <jzarl@fsfe.org><br />
| D7B0 1148 9F51 2947 2F7E A1C8 DB12 106E 8B7E BB88<br />
| ☐<br />
|-<br />
| ☐<br />
| Jonathan Riddell <jr@jriddell.org><br />
| 2D1D 5B05 8835 7787 DE9E E225 EC94 D18F 7F05 997E<br />
| ☐<br />
|-<br />
| ☐<br />
| David Faure <faure@kde.org><br />
| 53E6 B47B 45CE A3E0 D5B7 4577 58D0 EE64 8A48 B3BB<br />
| ☐<br />
|-<br />
| ☐<br />
| Albert Astals Cid <aacid@kde.org><br />
| CA26 2C6C 83DE 4D2F B28A 332A 3A6A 4DB8 39EA A6D7<br />
| ☐<br />
|-<br />
| ☐<br />
| Aditya Mehra <aix.m@outlook.com><br />
| ED60 21FB FF1D 7A30 D6B0 1E1F 6376 5612 B338 ECC9<br />
| ☐<br />
|-<br />
| ☐<br />
| Michael Pyne <mpyne@kde.org><br />
| 5406 ECE8 3665 DA9D 201D 3572 0BAF 0C9C 7B6A E9F2<br />
| ☐<br />
|-<br />
| ☐<br />
| Fabian Vogt <fabian@ritter-vogt.de><br />
Fabian Vogt <fabian@suse.de><br />
| 21EC 3FD7 5D26 B39E 820B E6FB D27C 2C1A F21D 8BAD<br />
| ☐<br />
|-<br />
| ☐<br />
| Sandro Knauß <bugs@sandroknauss.de>,<br />
<sknauss@kde.org>,<br />
<hefee@debian.org><br />
| 39EC 11A0 2016 B729 2649 1A06 E3AD B008 5060 5636<br />
| ☐<br />
|-<br />
| ☐<br />
| Sandro Knauß <mail@sandroknauss.de><br />
(personal mails)<br />
| D256 4951 1272 8840 BB5E 99F2 E680 31D2 99A6 527C<br />
| ☐<br />
|-<br />
| ☐<br />
| Your Name <youremail@host.tld><br />
| 1234 1234 1234 FINGER PRINT<br />
| ☐<br />
|-</div>Sandrohttps://community.kde.org/index.php?title=Akademy/2018/Config_Workshop&diff=81096Akademy/2018/Config Workshop2018-08-11T21:53:31Z<p>Sandro: </p>
<hr />
<div>== Why? ==<br />
<br />
KDE has very complex configuration settings. Many of these are not visible within GUIs. Users can make their desktop dysfunctional by simple edits of configuration files. It is not easily possible to share configuration settings between desktops etc.<br />
<br />
== Who? ==<br />
<br />
* Markus Raab <markus.raab@tuwien.ac.at> is only KDE user but a researcher about configuration settings and maintainer of the Elektra Initiative https://www.libelektra.org (see also https://fosdem.org/2018/schedule/speaker/markus_raab)<br />
* Aleix Pol <aleixpol@kde.org><br />
* David Faure <faure@kde.org><br />
* Elvis Angelaccio <elvis.angelaccio@kde.org><br />
* Sandro Knauß <sknauss@kde.org> (will go to KDE PIM BOF starting at 14 o'clock - get input for config situation in KDEPIM).<br />
* You? (Please enter yourself here if you want to participate. If you want to also have talk slots, please say about which topics you want to talk.)<br />
<br />
== When&Where? ==<br />
<br />
[[Akademy/2018/Tuesday#Room_125_.2820_people.29_-_14th_August|Tuesday, Room 125]], two sessions from 10:30-12:30, then lunch together (participants are invited), last session 14:00-15:00.<br />
<br />
<br />
== Topics! ==<br />
<br />
I think we will have more than enough to share (experience with config<br />
lib dev, code gen, config updates, ...) and I would be also interested<br />
in future cooperation. I am interested in:<br />
<br />
* kconf_update<br />
* KConfig XT (code generation)<br />
* reduce complexity of configuration (auto detection, ...)<br />
* what happened with the caching of configuration files (iirc it was available somehwere in KDE3)<br />
* make configuration safer&configuration specifications in general<br />
* kiosk mode (who used it and how), ...<br />
<br />
We might shuffle around the topics depending on who has time at which slot.<br />
<br />
== How? ==<br />
<br />
The workshop will be highly interactive. We will have 5-10 minutes talks (by different persons), then 10 minutes discussions and also brain storming sessions and similar. For socializing we will have lunch together.</div>Sandrohttps://community.kde.org/index.php?title=Akademy/2016/GPGKeys&diff=73884Akademy/2016/GPGKeys2016-09-05T10:06:18Z<p>Sandro: Add Sandro to the list of gpgkeys</p>
<hr />
<div>= How This Works =<br />
<br />
Add the name and email address of your key as well as the fingerprint below. Tuesday morning Harald is going to do a print out for all listed attendants. If you would like to do your own print out, please send a mail to ''sitter@kde.org''. If you are not listed by Tuesday morning you'll have to pay 300 Euros penalty!<br />
<br />
To get your key fingerprint, you'll want to run gpg or gpg2 with the --fingerprint argument and your name or short ID.<br />
<br />
<code><br />
gpg --fingerprint Sitter<br />
</code><br />
<br />
'''Make sure to bring an ID card or passport so we can verify you are who you claim to be at the BoF.'''<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Name <EMail> <br />
! Fingerpint<br />
|-<br />
| Harald Sitter <sitter@kde.org><br />
| CB93 8752 1E1E E012 7DA8 0484 3FDB B550 84CC 5D84<br />
|-<br />
| Jonathan Riddell <jriddell@ubuntu.com><br />
| 13C1 6D03 EDE7 2851 4473 AA73 A506 E6D4 DD4D 5088<br />
|-<br />
| David Faure <faure@kde.org><br />
| EEFA 895F EF2D 5532 4DC0 A3B5 EF62 9C54 09B0 6E10<br />
|-<br />
| Ingo Klöcker <kloecker@kde.org><br />
| 712A 0910 321A C762 D480 5408 1A74 7E45 30E0 B9D8<br />
|-<br />
| Bhushan Shah <bshah@kde.org><br />
| 0AAC 775B B643 7A8D 9AF7 A3AC FE07 8411 7FBC E11D<br />
|-<br />
| Andreas Cord-Landwehr <cordlandwehr@kde.org><br />
| FAA4 0058 0FA1 E4F7 5F35 E4FB BC8C 4A71 4B1C 6625<br />
|-<br />
| Luigi Toscano <luigi.toscano@tiscali.it><br />
| 6C88 3324 DE32 27A7 7DA3 BF88 2EB3 8401 2EB7 1358<br />
|-<br />
| Sandro Knauß <bugs@sandroknauss.de><br />
| 39EC 11A0 2016 B729 2649 1A06 E3AD B008 5060 5636<br />
|-<br />
| Sandro Knauß <sknauss@kolabsystems.com><br />
| 0305 ABBD B918 5BFE 662A 44F7 C255 AD42 CE81 539E<br />
|-<br />
| Your Name <email><br />
| 1234<br />
|}</div>Sandrohttps://community.kde.org/index.php?title=KDE_PIM/Meetings/Toulouse2016&diff=59751KDE PIM/Meetings/Toulouse20162016-04-03T21:58:27Z<p>Sandro: /* Release-impacting changes for 16.08 */</p>
<hr />
<div>== Attendees ==<br />
<br />
* Laurent<br />
* K´evin<br />
* Franck<br />
* Dan<br />
* Andre<br />
* John<br />
* Sandro<br />
* Christian<br />
* Volker<br />
<br />
== Notes ==<br />
<br />
=== libkleo dependencies / libkleo/qgpgme future ===<br />
Andre/Christian/Sandro<br />
<br />
Andre already started dropping dependencies and made some optional, so the situations is much better, than it was evelulated for kube.<br />
<br />
Currently libkleo is used in kleopatra, mimetreeparser and messagecomposer.<br />
<br />
libkleo is currenty a bundly of things:<br />
* jobs around gpgme++<br />
- will move lower the stack to qgpgme<br />
* widegt for selected keys, showingWarnings...<br />
* different backend support chiasmus/gnupg<br />
- chiasmus support will very likly to be dropped from libkleo<br />
<br />
For mimetreeparser the moving of jobs to lower stack is enough move the dependency to qgpgme.<br />
Without chiasmus the whole idea of libkleo is getting away, so maybe get rid of it completly?<br />
* open question is where to move widgets that are used from messagecomposer and kleopatra<br />
<br />
Additionally qgpgme will get support for a higher Qt API to request f.ex<br />
* a more user orintated API instead of a API around what gnupg exposes<br />
* a key for a keyid (from verification/ decryption result) <br />
* add more advanded errors/warnings ("missing secrect key" instead of "decryption failed")<br />
<br />
=== ICal TimeZones ===<br />
<br />
Plan:<br />
* drop KCalCore::IcalTimeZone* classes<br />
* just provide a list of available additional time zones known to KCalCore<br />
<br />
Existing users:<br />
* incidence editor time zone combo box -> reduced dependency to name-based lookup for a string provided by UI<br />
* ical Akonadi serializer, used as a timezone cache for system timezones -> move inside KCalCore to hide from API<br />
<br />
=== C++11 usage ===<br />
<br />
==== auto ====<br />
<br />
Two views on this: always-auto fans and people concerned about readability of code.<br />
<br />
Therefore we start with the following compromise: Use auto primarily to avoid duplicated type information (ie. when the type is already written on the right hand side), or when the type is "generally known" and inconvenient to write (e.g. iterators).<br />
<br />
==== libraries ====<br />
<br />
Follow KF5 guidelines.<br />
<br />
==== application ====<br />
<br />
GCC 4.8 and MSVC2015 which is basically the complete C++11 language feature set (but not the library feature set).<br />
<br />
<br />
=== QML representation for mails in Kube ===<br />
<br />
Christian/Sandro<br />
<br />
To get rid of rendering the whole email to html and implement the handling inside html (like requestion decrpytion, handling attachments). We want to do thing handling inside QML and only show the actually mail content inside a QWebView.<br />
<br />
=== mimtetreeparser dependencies ===<br />
* move attachmenttemporaryfilesdirs to mimetreeparser<br />
* nodehelper should no longer be necessary (we should be able to iterate over the parts ourselves)<br />
* quoteHtmlChars is not necessary if we move the html generation out of mimetreeparser<br />
* move html messagepart to messageviewer and thus remove "to plaintext" functionality from mimetreeparser<br />
<br />
=== Bumping so version number ===<br />
Some distributions complained that we broke ABI without bumping so version numbers.<br />
* some devs see it as an inconvenience to selectively bump so version numbers, because it's no longer obvious what is the latest set.<br />
* it is also precieved as standard to have the so version synchronized to the library version.<br />
<br />
We will either bump all so versions collectively with every release (since most change currently anyways), or only bump the ones that actually changed (since most won't change eventually). Of course everything that goes to frameworks follows frameworks policy anyways.<br />
<br />
Sandro will evaluate the siutation in kdepim again, how in flux we actually are, and discuss the problems that distributions actually have again, and then suggest a solution.<br />
<br />
=== Zanshinification of KDE PIM ===<br />
<br />
==== Architecture ====<br />
<br />
* Move to onion architecture, with application-specific domain model in the center.<br />
* Domain objects need to consider performance and scalability, Zanshin's approach of using QObjects with copied data wont work for KMail.<br />
<br />
Moving from layer architecture to onion:<br />
# develop application specific minimal domain model<br />
# develop proxy model or ETM sub-class for mapping to domain model objects<br />
# switch view code or other model using code to use domain model objects<br />
# find manually created Akonadi jobs<br />
# create repository interface for domain objects, for creating/updating/removing and whatever extra operations beyond that are used (higher-level actions).<br />
# port application to domain object roles (for reading) and domain object repositories (for writing)<br />
<br />
Aiming at moving direct Akonadi use out of the application. All steps above should be unit tested.<br />
<br />
==== Code ====<br />
<br />
* StorageInterface: more of less directly useable, move to libakonadi and extend to all operations<br />
* Dependency Manager: Kevin will push that to QtCore.<br />
* Reactive Collections: Might move to KAsync, Christian will investigate when working on IMAP for Sink<br />
<br />
=== KDELibs4Support Removal ===<br />
<br />
Some progress:<br />
* no more KPrintPreview<br />
* no more KCalendarSystem (apart from KAlaram)<br />
* KAddressBook no longer needs KDELibs4Support<br />
* reduced ICalTimeZone usage<br />
* ported some KTimeZone usage to QTimeZone, but this is largely blocked by KDateTime<br />
* ported most remaining KLocale usage<br />
<br />
Still to do, based on John's input:<br />
* use12HourClock -> contains("a")/constains("A") on the QLocale date format string<br />
* weeksInYear: std::max(QDate::weekNumber()) for the last 7 days in the year.<br />
<br />
=== Release-impacting changes for 16.08 ===<br />
<br />
* kdepimlibs is going to be split and been removed afterwards (split to akonadi-calendar, akonadi-notes, akonadi-mail, kioslaves will move into kdepim-runtime) - montel is doning the stuff<br />
* KHolidays is becoming a framework, John is kicking off the review on frameworks-devel<br />
* kleopatra is splitted out as single application (has already its own repo) kleopatra will have two different release cyles to follow one KDE Applications for Linux and GPG4Win for windows builds<br />
* messagelib will change it dependecy from libkleo to qgpgme <br />
* gpgme++ will be move to upsteam gnupg</div>Sandrohttps://community.kde.org/index.php?title=KDE_PIM/Meetings/Toulouse2016&diff=59747KDE PIM/Meetings/Toulouse20162016-04-03T12:44:09Z<p>Sandro: /* Release-impacting changes for 16.08 */</p>
<hr />
<div>== Attendees ==<br />
<br />
* Laurent<br />
* K´evin<br />
* Franck<br />
* Dan<br />
* Andre<br />
* John<br />
* Sandro<br />
* Christian<br />
* Volker<br />
<br />
== Notes ==<br />
<br />
=== libkleo dependencies / libkleo/qgpgme future ===<br />
Andre/Christian/Sandro<br />
<br />
Andre already started dropping dependencies and made some optional, so the situations is much better, than it was evelulated for kube.<br />
<br />
Currently libkleo is used in kleopatra, mimetreeparser and messagecomposer.<br />
<br />
libkleo is currenty a bundly of things:<br />
* jobs around gpgme++<br />
- will move lower the stack to qgpgme<br />
* widegt for selected keys, showingWarnings...<br />
* different backend support chiasmus/gnupg<br />
- chiasmus support will very likly to be dropped from libkleo<br />
<br />
For mimetreeparser the moving of jobs to lower stack is enough move the dependency to qgpgme.<br />
Without chiasmus the whole idea of libkleo is getting away, so maybe get rid of it completly?<br />
* open question is where to move widgets that are used from messagecomposer and kleopatra<br />
<br />
Additionally qgpgme will get support for a higher Qt API to request f.ex<br />
* a more user orintated API instead of a API around what gnupg exposes<br />
* a key for a keyid (from verification/ decryption result) <br />
* add more advanded errors/warnings ("missing secrect key" instead of "decryption failed")<br />
<br />
=== ICal TimeZones ===<br />
<br />
Plan:<br />
* drop KCalCore::IcalTimeZone* classes<br />
* just provide a list of available additional time zones known to KCalCore<br />
<br />
Existing users:<br />
* incidence editor time zone combo box -> reduced dependency to name-based lookup for a string provided by UI<br />
* ical Akonadi serializer, used as a timezone cache for system timezones -> move inside KCalCore to hide from API<br />
<br />
=== C++11 usage ===<br />
<br />
==== auto ====<br />
<br />
Two views on this: always-auto fans and people concerned about readability of code.<br />
<br />
Therefore we start with the following compromise: Use auto primarily to avoid duplicated type information (ie. when the type is already written on the right hand side), or when the type is "generally known" and inconvenient to write (e.g. iterators).<br />
<br />
==== libraries ====<br />
<br />
Follow KF5 guidelines.<br />
<br />
==== application ====<br />
<br />
GCC 4.8 and MSVC2015 which is basically the complete C++11 language feature set (but not the library feature set).<br />
<br />
<br />
=== QML representation for mails in Kube ===<br />
<br />
Christian/Sandro<br />
<br />
To get rid of rendering the whole email to html and implement the handling inside html (like requestion decrpytion, handling attachments). We want to do thing handling inside QML and only show the actually mail content inside a QWebView.<br />
<br />
=== mimtetreeparser dependencies ===<br />
* move attachmenttemporaryfilesdirs to mimetreeparser<br />
* nodehelper should no longer be necessary (we should be able to iterate over the parts ourselves)<br />
* quoteHtmlChars is not necessary if we move the html generation out of mimetreeparser<br />
* move html messagepart to messageviewer and thus remove "to plaintext" functionality from mimetreeparser<br />
<br />
=== Bumping so version number ===<br />
Some distributions complained that we broke ABI without bumping so version numbers.<br />
* some devs see it as an inconvenience to selectively bump so version numbers, because it's no longer obvious what is the latest set.<br />
* it is also precieved as standard to have the so version synchronized to the library version.<br />
<br />
We will either bump all so versions collectively with every release (since most change currently anyways), or only bump the ones that actually changed (since most won't change eventually). Of course everything that goes to frameworks follows frameworks policy anyways.<br />
<br />
Sandro will evaluate the siutation in kdepim again, how in flux we actually are, and discuss the problems that distributions actually have again, and then suggest a solution.<br />
<br />
=== Zanshinification of KDE PIM ===<br />
<br />
==== Architecture ====<br />
<br />
* Move to onion architecture, with application-specific domain model in the center.<br />
* Domain objects need to consider performance and scalability, Zanshin's approach of using QObjects with copied data wont work for KMail.<br />
<br />
Moving from layer architecture to onion:<br />
# develop application specific minimal domain model<br />
# develop proxy model or ETM sub-class for mapping to domain model objects<br />
# switch view code or other model using code to use domain model objects<br />
# find manually created Akonadi jobs<br />
# create repository interface for domain objects, for creating/updating/removing and whatever extra operations beyond that are used (higher-level actions).<br />
# port application to domain object roles (for reading) and domain object repositories (for writing)<br />
<br />
Aiming at moving direct Akonadi use out of the application. All steps above should be unit tested.<br />
<br />
==== Code ====<br />
<br />
* StorageInterface: more of less directly useable, move to libakonadi and extend to all operations<br />
* Dependency Manager: Kevin will push that to QtCore.<br />
* Reactive Collections: Might move to KAsync, Christian will investigate when working on IMAP for Sink<br />
<br />
=== KDELibs4Support Removal ===<br />
<br />
Some progress:<br />
* no more KPrintPreview<br />
* no more KCalendarSystem (apart from KAlaram)<br />
* KAddressBook no longer needs KDELibs4Support<br />
* reduced ICalTimeZone usage<br />
* ported some KTimeZone usage to QTimeZone, but this is largely blocked by KDateTime<br />
<br />
=== Release-impacting changes for 16.08 ===<br />
<br />
* kdepimlibs is going to be split and been removed afterwards (split to akonadi-calendar, akonadi-notes, akonadi-mail, kioslaves will move into kdepim-runtime) - montel is doning the stuff<br />
* KHolidays is becoming a framework, John is kicking off the review on frameworks-devel<br />
* kleopatra is splitted out as single application (has already its own repo) kleopatra will have two different release cyles to follow one KDE Applications for Linux and GPG4Win for windows builds<br />
* messagelib will change it dependecy from libkleo to qgpgme <br />
* gpgme++ will be move to upsteam gnupg <br />
* libkleo will maybe gone</div>Sandrohttps://community.kde.org/index.php?title=KDE_PIM/Meetings/Toulouse2016&diff=59746KDE PIM/Meetings/Toulouse20162016-04-03T12:37:07Z<p>Sandro: /* Release-impacting changes for 16.08 */</p>
<hr />
<div>== Attendees ==<br />
<br />
* Laurent<br />
* K´evin<br />
* Franck<br />
* Dan<br />
* Andre<br />
* John<br />
* Sandro<br />
* Christian<br />
* Volker<br />
<br />
== Notes ==<br />
<br />
=== libkleo dependencies / libkleo/qgpgme future ===<br />
Andre/Christian/Sandro<br />
<br />
Andre already started dropping dependencies and made some optional, so the situations is much better, than it was evelulated for kube.<br />
<br />
Currently libkleo is used in kleopatra, mimetreeparser and messagecomposer.<br />
<br />
libkleo is currenty a bundly of things:<br />
* jobs around gpgme++<br />
- will move lower the stack to qgpgme<br />
* widegt for selected keys, showingWarnings...<br />
* different backend support chiasmus/gnupg<br />
- chiasmus support will very likly to be dropped from libkleo<br />
<br />
For mimetreeparser the moving of jobs to lower stack is enough move the dependency to qgpgme.<br />
Without chiasmus the whole idea of libkleo is getting away, so maybe get rid of it completly?<br />
* open question is where to move widgets that are used from messagecomposer and kleopatra<br />
<br />
Additionally qgpgme will get support for a higher Qt API to request f.ex<br />
* a more user orintated API instead of a API around what gnupg exposes<br />
* a key for a keyid (from verification/ decryption result) <br />
* add more advanded errors/warnings ("missing secrect key" instead of "decryption failed")<br />
<br />
=== ICal TimeZones ===<br />
<br />
Plan:<br />
* drop KCalCore::IcalTimeZone* classes<br />
* just provide a list of available additional time zones known to KCalCore<br />
<br />
Existing users:<br />
* incidence editor time zone combo box -> reduced dependency to name-based lookup for a string provided by UI<br />
* ical Akonadi serializer, used as a timezone cache for system timezones -> move inside KCalCore to hide from API<br />
<br />
=== C++11 usage ===<br />
<br />
==== auto ====<br />
<br />
Two views on this: always-auto fans and people concerned about readability of code.<br />
<br />
Therefore we start with the following compromise: Use auto primarily to avoid duplicated type information (ie. when the type is already written on the right hand side), or when the type is "generally known" and inconvenient to write (e.g. iterators).<br />
<br />
==== libraries ====<br />
<br />
Follow KF5 guidelines.<br />
<br />
==== application ====<br />
<br />
GCC 4.8 and MSVC2015 which is basically the complete C++11 language feature set (but not the library feature set).<br />
<br />
<br />
=== QML representation for mails in Kube ===<br />
<br />
Christian/Sandro<br />
<br />
To get rid of rendering the whole email to html and implement the handling inside html (like requestion decrpytion, handling attachments). We want to do thing handling inside QML and only show the actually mail content inside a QWebView.<br />
<br />
=== mimtetreeparser dependencies ===<br />
* move attachmenttemporaryfilesdirs to mimetreeparser<br />
* nodehelper should no longer be necessary (we should be able to iterate over the parts ourselves)<br />
* quoteHtmlChars is not necessary if we move the html generation out of mimetreeparser<br />
* move html messagepart to messageviewer and thus remove "to plaintext" functionality from mimetreeparser<br />
<br />
=== Bumping so version number ===<br />
Some distributions complained that we broke ABI without bumping so version numbers.<br />
* some devs see it as an inconvenience to selectively bump so version numbers, because it's no longer obvious what is the latest set.<br />
* it is also precieved as standard to have the so version synchronized to the library version.<br />
<br />
We will either bump all so versions collectively with every release (since most change currently anyways), or only bump the ones that actually changed (since most won't change eventually). Of course everything that goes to frameworks follows frameworks policy anyways.<br />
<br />
Sandro will evaluate the siutation in kdepim again, how in flux we actually are, and discuss the problems that distributions actually have again, and then suggest a solution.<br />
<br />
=== Zanshinification of KDE PIM ===<br />
<br />
==== Architecture ====<br />
<br />
* Move to onion architecture, with application-specific domain model in the center.<br />
* Domain objects need to consider performance and scalability, Zanshin's approach of using QObjects with copied data wont work for KMail.<br />
<br />
Moving from layer architecture to onion:<br />
# develop application specific minimal domain model<br />
# develop proxy model or ETM sub-class for mapping to domain model objects<br />
# switch view code or other model using code to use domain model objects<br />
# find manually created Akonadi jobs<br />
# create repository interface for domain objects, for creating/updating/removing and whatever extra operations beyond that are used (higher-level actions).<br />
# port application to domain object roles (for reading) and domain object repositories (for writing)<br />
<br />
Aiming at moving direct Akonadi use out of the application. All steps above should be unit tested.<br />
<br />
==== Code ====<br />
<br />
* StorageInterface: more of less directly useable, move to libakonadi and extend to all operations<br />
* Dependency Manager: Kevin will push that to QtCore.<br />
* Reactive Collections: Might move to KAsync, Christian will investigate when working on IMAP for Sink<br />
<br />
=== KDELibs4Support Removal ===<br />
<br />
Some progress:<br />
* no more KPrintPreview<br />
* no more KCalendarSystem (apart from KAlaram)<br />
* KAddressBook no longer needs KDELibs4Support<br />
* reduced ICalTimeZone usage<br />
* ported some KTimeZone usage to QTimeZone, but this is largely blocked by KDateTime<br />
<br />
=== Release-impacting changes for 16.08 ===<br />
<br />
* kdepimlibs is going to be split and been removed afterwards (split to akonadi-calendar, akonadi-notes, akonadi-mail, kioslaves will move into kdepim-runtime) - montel is doning the stuff<br />
* KHolidays is becoming a framework, John is kicking off the review on frameworks-devel<br />
* kleopatra is splitted out as single application (has already its own repo) kleopatra will have two different release cyles to follow one KDE Applications for Linux and GPG4Win for windows builds</div>Sandrohttps://community.kde.org/index.php?title=KDE_PIM/Meetings/Toulouse2016&diff=59745KDE PIM/Meetings/Toulouse20162016-04-03T12:32:22Z<p>Sandro: adding release stuff</p>
<hr />
<div>== Attendees ==<br />
<br />
* Laurent<br />
* K´evin<br />
* Franck<br />
* Dan<br />
* Andre<br />
* John<br />
* Sandro<br />
* Christian<br />
* Volker<br />
<br />
== Notes ==<br />
<br />
=== libkleo dependencies / libkleo/qgpgme future ===<br />
Andre/Christian/Sandro<br />
<br />
Andre already started dropping dependencies and made some optional, so the situations is much better, than it was evelulated for kube.<br />
<br />
Currently libkleo is used in kleopatra, mimetreeparser and messagecomposer.<br />
<br />
libkleo is currenty a bundly of things:<br />
* jobs around gpgme++<br />
- will move lower the stack to qgpgme<br />
* widegt for selected keys, showingWarnings...<br />
* different backend support chiasmus/gnupg<br />
- chiasmus support will very likly to be dropped from libkleo<br />
<br />
For mimetreeparser the moving of jobs to lower stack is enough move the dependency to qgpgme.<br />
Without chiasmus the whole idea of libkleo is getting away, so maybe get rid of it completly?<br />
* open question is where to move widgets that are used from messagecomposer and kleopatra<br />
<br />
Additionally qgpgme will get support for a higher Qt API to request f.ex<br />
* a more user orintated API instead of a API around what gnupg exposes<br />
* a key for a keyid (from verification/ decryption result) <br />
* add more advanded errors/warnings ("missing secrect key" instead of "decryption failed")<br />
<br />
=== ICal TimeZones ===<br />
<br />
Plan:<br />
* drop KCalCore::IcalTimeZone* classes<br />
* just provide a list of available additional time zones known to KCalCore<br />
<br />
Existing users:<br />
* incidence editor time zone combo box -> reduced dependency to name-based lookup for a string provided by UI<br />
* ical Akonadi serializer, used as a timezone cache for system timezones -> move inside KCalCore to hide from API<br />
<br />
=== C++11 usage ===<br />
<br />
==== auto ====<br />
<br />
Two views on this: always-auto fans and people concerned about readability of code.<br />
<br />
Therefore we start with the following compromise: Use auto primarily to avoid duplicated type information (ie. when the type is already written on the right hand side), or when the type is "generally known" and inconvenient to write (e.g. iterators).<br />
<br />
==== libraries ====<br />
<br />
Follow KF5 guidelines.<br />
<br />
==== application ====<br />
<br />
GCC 4.8 and MSVC2015 which is basically the complete C++11 language feature set (but not the library feature set).<br />
<br />
<br />
=== QML representation for mails in Kube ===<br />
<br />
Christian/Sandro<br />
<br />
To get rid of rendering the whole email to html and implement the handling inside html (like requestion decrpytion, handling attachments). We want to do thing handling inside QML and only show the actually mail content inside a QWebView.<br />
<br />
=== mimtetreeparser dependencies ===<br />
* move attachmenttemporaryfilesdirs to mimetreeparser<br />
* nodehelper should no longer be necessary (we should be able to iterate over the parts ourselves)<br />
* quoteHtmlChars is not necessary if we move the html generation out of mimetreeparser<br />
* move html messagepart to messageviewer and thus remove "to plaintext" functionality from mimetreeparser<br />
<br />
=== Bumping so version number ===<br />
Some distributions complained that we broke ABI without bumping so version numbers.<br />
* some devs see it as an inconvenience to selectively bump so version numbers, because it's no longer obvious what is the latest set.<br />
* it is also precieved as standard to have the so version synchronized to the library version.<br />
<br />
We will either bump all so versions collectively with every release (since most change currently anyways), or only bump the ones that actually changed (since most won't change eventually). Of course everything that goes to frameworks follows frameworks policy anyways.<br />
<br />
Sandro will evaluate the siutation in kdepim again, how in flux we actually are, and discuss the problems that distributions actually have again, and then suggest a solution.<br />
<br />
=== Zanshinification of KDE PIM ===<br />
<br />
==== Architecture ====<br />
<br />
* Move to onion architecture, with application-specific domain model in the center.<br />
* Domain objects need to consider performance and scalability, Zanshin's approach of using QObjects with copied data wont work for KMail.<br />
<br />
Moving from layer architecture to onion:<br />
# develop application specific minimal domain model<br />
# develop proxy model or ETM sub-class for mapping to domain model objects<br />
# switch view code or other model using code to use domain model objects<br />
# find manually created Akonadi jobs<br />
# create repository interface for domain objects, for creating/updating/removing and whatever extra operations beyond that are used (higher-level actions).<br />
# port application to domain object roles (for reading) and domain object repositories (for writing)<br />
<br />
Aiming at moving direct Akonadi use out of the application. All steps above should be unit tested.<br />
<br />
==== Code ====<br />
<br />
* StorageInterface: more of less directly useable, move to libakonadi and extend to all operations<br />
* Dependency Manager: Kevin will push that to QtCore.<br />
* Reactive Collections: Might move to KAsync, Christian will investigate when working on IMAP for Sink<br />
<br />
=== KDELibs4Support Removal ===<br />
<br />
Some progress:<br />
* no more KPrintPreview<br />
* no more KCalendarSystem (apart from KAlaram)<br />
* KAddressBook no longer needs KDELibs4Support<br />
* reduced ICalTimeZone usage<br />
* ported some KTimeZone usage to QTimeZone, but this is largely blocked by KDateTime<br />
<br />
=== Release-impacting changes for 16.08 ===<br />
<br />
* kdepimlibs is going to be split and been removed afterwards<br />
(split to akonadi-calendar, akonadi-notes, akonadi-mail, kioslaves will move into kdepim-runtime) - montel is doning the stuff<br />
* KHolidays is becoming a framework, John is kicking off the review on frameworks-devel<br />
* kleopatra is splitted out as single application (has already its own repo)</div>Sandrohttps://community.kde.org/index.php?title=KDE_PIM/Meetings/Toulouse2016&diff=59726KDE PIM/Meetings/Toulouse20162016-04-02T14:09:56Z<p>Sandro: QML mail in Kube</p>
<hr />
<div>== Attendees ==<br />
<br />
* Laurent<br />
* K´evin<br />
* Franck<br />
* Dan<br />
* Andre<br />
* John<br />
* Sandro<br />
* Christian<br />
* Volker<br />
<br />
== Notes ==<br />
<br />
=== libkleo dependencies / libkleo/qgpgme future ===<br />
Andre/Christian/Sandro<br />
<br />
Andre already started dropping dependencies and made some optional, so the situations is much better, than it was evelulated for kube.<br />
<br />
Currently libkleo is used in kleopatra, mimetreeparser and messagecomposer.<br />
<br />
libkleo is currenty a bundly of things:<br />
* jobs around gpgme++<br />
- will move lower the stack to qgpgme<br />
* widegt for selected keys, showingWarnings...<br />
* different backend support chiasmus/gnupg<br />
- chiasmus support will very likly to be dropped from libkleo<br />
<br />
For mimetreeparser the moving of jobs to lower stack is enough move the dependency to qgpgme.<br />
Without chiasmus the whole idea of libkleo is getting away, so maybe get rid of it completly?<br />
* open question is where to move widgets that are used from messagecomposer and kleopatra<br />
<br />
Additionally qgpgme will get support for a higher Qt API to request f.ex<br />
* a more user orintated API instead of a API around what gnupg exposes<br />
* a key for a keyid (from verification/ decryption result) <br />
* add more advanded errors/warnings ("missing secrect key" instead of "decryption failed")<br />
<br />
=== ICal TimeZones ===<br />
<br />
Plan:<br />
* drop KCalCore::IcalTimeZone* classes<br />
* just provide a list of available additional time zones known to KCalCore<br />
<br />
Existing users:<br />
* incidence editor time zone combo box<br />
<br />
=== C++11 usage ===<br />
<br />
==== auto ====<br />
<br />
Two views on this: always-auto fans and people concerned about readability of code.<br />
<br />
Therefore we start with the following compromise: Use auto primarily to avoid duplicated type information (ie. when the type is already written on the right hand side), or when the type is "generally known" and inconvenient to write (e.g. iterators).<br />
<br />
==== libraries ====<br />
<br />
Follow KF5 guidelines.<br />
<br />
==== application ====<br />
<br />
GCC 4.8 and MSVC2015 which is basically the complete C++11 language feature set (but not the library feature set).<br />
<br />
<br />
=== QML representation for mails in Kube ===<br />
<br />
Christian/Sandro<br />
<br />
To get rid of rendering the whole email to html and implement the handling inside html (like requestion decrpytion, handling attachments). We want to do thing handling inside QML and only show the actually mail content inside a QWebView.</div>Sandrohttps://community.kde.org/index.php?title=KDE_PIM/Meetings/Toulouse2016&diff=59725KDE PIM/Meetings/Toulouse20162016-04-02T14:00:49Z<p>Sandro: libkleo dependency -> libkleo future</p>
<hr />
<div>== Attendees ==<br />
<br />
* Laurent<br />
* K´evin<br />
* Franck<br />
* Dan<br />
* Andre<br />
* John<br />
* Sandro<br />
* Christian<br />
* Volker<br />
<br />
== Notes ==<br />
<br />
=== libkleo dependencies / libkleo/qgpgme future ===<br />
Andre/Christian/Sandro<br />
<br />
Andre already started dropping dependencies and made some optional, so the situations is much better, than it was evelulated for kube.<br />
<br />
Currently libkleo is used in kleopatra, mimetreeparser and messagecomposer.<br />
<br />
libkleo is currenty a bundly of things:<br />
* jobs around gpgme++<br />
- will move lower the stack to qgpgme<br />
* widegt for selected keys, showingWarnings...<br />
* different backend support chiasmus/gnupg<br />
- chiasmus support will very likly to be dropped from libkleo<br />
<br />
For mimetreeparser the moving of jobs to lower stack is enough move the dependency to qgpgme.<br />
Without chiasmus the whole idea of libkleo is getting away, so maybe get rid of it completly?<br />
* open question is where to move widgets that are used from messagecomposer and kleopatra<br />
<br />
Additionally qgpgme will get support for a higher Qt API to request f.ex<br />
* a more user orintated API instead of a API around what gnupg exposes<br />
* a key for a keyid (from verification/ decryption result) <br />
* add more advanded errors/warnings ("missing secrect key" instead of "decryption failed")<br />
<br />
=== ICal TimeZones ===<br />
<br />
Plan:<br />
* drop KCalCore::IcalTimeZone* classes<br />
* just provide a list of available additional time zones known to KCalCore<br />
<br />
Existing users:<br />
* incidence editor time zone combo box<br />
<br />
=== C++11 usage ===<br />
<br />
==== auto ====<br />
<br />
Two views on this: always-auto fans and people concerned about readability of code.<br />
<br />
Therefore we start with the following compromise: Use auto primarily to avoid duplicated type information (ie. when the type is already written on the right hand side), or when the type is "generally known" and inconvenient to write (e.g. iterators).<br />
<br />
==== libraries ====<br />
<br />
Follow KF5 guidelines.<br />
<br />
==== application ====<br />
<br />
GCC 4.8 and MSVC2015 which is basically the complete C++11 language feature set (but not the library feature set).</div>Sandrohttps://community.kde.org/index.php?title=Plasma/InstallingNext&diff=46651Plasma/InstallingNext2016-01-31T18:51:56Z<p>Sandro: Siduction has no more a special kf5 repos, it is using the default from debian</p>
<hr />
<div>=How to install test versions of Plasma Next=<br />
<br />
==Kubuntu==<br />
<br />
'''Packages for Kubuntu Utopic''' Next and Next backports PPAs for Utopic (14.10) are now deprecated. <br />
<br />
To test upgrade to Vivid, please use the PPA-purge package to remove those PPAs and packages, and then install `kubuntu-desktop` meta-package, and finally:<br />
<syntaxhighlight lang="bash"><br />
sudo apt update && sudo apt full-upgrade <br />
</syntaxhighlight><br />
before initiating:<br />
<syntaxhighlight lang="bash"><br />
sudo kubuntu-devel-release-upgrade<br />
</syntaxhighlight><br />
to move to [http://www.kubuntu.org/news/kubuntu-vivid-beta-1 Vivid beta].<br />
[https://help.ubuntu.com/community/UtopicUpgrades/Kubuntu Full instructions to upgrade from 14.10].<br />
<br />
'''Live Image of Kubuntu Vivid with Packages from Git''' The [http://files.kde.org/snapshots/ Weekly Live Image], updated every Friday with latest source from Git to run a full system from a USB disk. Based on Kubuntu 15.04, Vivid.<br />
<br />
KDE Frameworks 5 and Plasma 5 is available in the '''Vivid development version''' of Kubuntu, now in [http://www.kubuntu.org/news/kubuntu-vivid-beta-1 beta].<br />
<br />
==openSUSE==<br />
openSUSE offers snapshots from git master updated frequently as well. Add the KDE:Unstable:Frameworks repository (http://en.opensuse.org/SDB:KDE_repositories#Plasma_Next) and the Qt53 repository (available at the same link) and install the plasma-next-session package to have a session available at the next login.<br />
<br />
==Gentoo==<br />
<br />
Gentoo provides beta as well as live ebuilds inside kde overlay, with dependencies in qt overlay. The following assumes you have a basic understanding of Gentoo Portage and already [http://wiki.gentoo.org/wiki/Layman set up layman] initially:<br />
<syntaxhighlight lang="bash"><br />
layman -a kde && layman -a qt<br />
emerge @kde-next-live --autounmask-write=y<br />
</syntaxhighlight><br />
<br />
<br />
To make the most of it, run<br />
<syntaxhighlight lang="bash"><br />
layman -S && smart-live-rebuild<br />
</syntaxhighlight><br />
to get the latest packaging changes for qt and kde and update any ''live'' packages that got new commits since last time.<br />
<br />
See also: [http://wiki.gentoo.org/wiki/Project:KDE/Frameworks Gentoo KDE/Frameworks Packaging Status]<br />
<br />
==Fedora==<br />
Now that Plasma 5 has been released, Fedora packaging only tracks the official Plasma 5 releases, not snapshots. See [[Plasma/Packages#Fedora]] for installation instructions.<br />
<br />
==Arch==<br />
Plasma 5 workspace is available through the official repositories. For the full installation, simply install [https://www.archlinux.org/groups/x86_64/plasma-next/ plasma-next].<br /><br />
Frameworks 5 libraries are also in the official repositories under [https://www.archlinux.org/groups/x86_64/kf5/ kf5] and [https://www.archlinux.org/groups/x86_64/kf5-aids/ kf5-aids].<br /><br />
There are git versions of the above, as well as many other Frameworks 5 applications installable through the [https://aur.archlinux.org/ AUR].<br />
<br />
See the [https://wiki.archlinux.org/index.php/KDE KDE] page on the ArchWiki for more information.<br />
<br />
==From Source==<br />
Following the instructions here it will automatically build all KDE software that has a KF5 port, most notably the Plasma workspaces, but also development previews of Kate, Konsole and Dolphin.<br />
<br />
Afterwards follow the guides for "Runtime setup" and then run "kwin --replace" and "plasmashell".<br />
<br />
==Live CD==<br />
Kubuntu-based Live CD:<br />
http://files.kde.org/snapshots/neon5-latest.iso (More information at http://kshadeslayer.wordpress.com/2013/12/03/introducing-project-neon-5-isos/)<br />
<br />
Fedora-based LiveCD:<br />
https://dvratil.fedorapeople.org/plasma5/iso/ (More information at http://www.progdan.cz/2014/05/kde-frameworks-5-beta-and-plasma-next-preview-on-fedora/)</div>Sandrohttps://community.kde.org/index.php?title=Sprints/Randa/2015&diff=44103Sprints/Randa/20152015-09-02T22:19:03Z<p>Sandro: addhefees blog post</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 />
* 2 ExoPC (1:?, 1: frinring)<br />
* 1 WeTab<br />
* 1 Touch monitor 27''<br />
* 1 Projector<br />
* and more TBD<br />
* 2x [https://support.lenovo.com/en/documents/pd100258 ThinkVision 28 - Touch 28-inch 4K2K Tegra K1 Entertainment Center] - 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 - 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 />
* Sandro Knauß (hefee) (September 2) [https://exote.ch/blogs/sandro/kontact-and-gnupg-under-windows/ Kontact and GnuPG under Windows]<br />
* Dennis Nienhüser (Earthwings) (September 1) [http://nienhueser.de/blog/?p=614 Announcing Marble Maps for Android Open Beta]<br />
* Sanjiban Bairagya (fewcha) (August 31) [https://sanjibandotme.wordpress.com/2015/08/31/randa-meetings-2015-what-i-plan-to-do/ Randa Meetings 2015 – What I plan to do]<br />
* Christian Mollekopf (cmollekopf) (August 29) [https://cmollekopf.wordpress.com/2015/08/29/bringing-akonadi-next-up-to-speed/ Bringing Akonadi Next up to speed]<br />
* Andreas Cord-Landwehr (CoLa) (August 28) [https://cordlandwehr.wordpress.com/2015/08/28/artikulate-plans/ Artikulate Plans for Randa]<br />
* Dan Leinir Turthra Jensen (leinir) (August 26) [http://kath-leinir.blogspot.co.uk/2015/08/gemini-at-randa-2015.html Gemini at Randa 2015]<br />
* Albert Vaca (albertvaka) (August 25) [https://albertvaka.wordpress.com/2015/08/25/mobile-development-sprint-in-randa-kde-connect-and-more/ Mobile development sprint in Randa: KDE Connect, and more!]<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 27): [https://dot.kde.org/2015/08/27/kde-sprints-who-wins KDE Sprints - who wins?]<br />
* Dot story (August 24): [https://dot.kde.org/2015/08/24/another-kde-success-story-incubator-part-4 Another KDE success story - the Incubator - Part 4]<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>Sandrohttps://community.kde.org/index.php?title=KDE_PIM/Development/Bug_Reports&diff=41725KDE PIM/Development/Bug Reports2015-02-26T11:30:04Z<p>Sandro: howto get usefull logs</p>
<hr />
<div>= Reporting Bugs =<br />
<br />
Bugs of KDE PIM applications should be reported at [http://bugs.kde.org/ bugs.kde.org]. This includes feature requests<br />
which should be reported as wishlist items. There is a [http://bugs.kde.org/wizard.cgi bug reporting wizard] which asks for<br />
all relevant information and then creates an entry in the bug tracking<br />
system.<br />
<br />
To make your bug report as useful as possible you should keep some things in<br />
mind:<br />
* Check that the bug hasn't been reported before.<br />
* Tell us how to reproduce the bug<br />
* Include all relevant information about KDE version, operating system, special configurations, etc.<br />
* Keep in mind that we do care about bug reports, but that most of us work on KDE in their spare time and might not be able to address the bug immediately.<br />
<br />
= Querying bug reports =<br />
<br />
You can query bug reports on the generic<br />
[http://bugs.kde.org/query.cgi KDE Bugzilla query page]. Here are some<br />
predefined queries:<br />
<br />
* [http://bugs.kde.org/buglist.cgi?product=akregator&product=kaddressbook&product=kalarm&product=kandy&product=karm&product=kitchensync&product=kmail&product=knode&product=knotes&product=konsolekalendar&product=kontact&product=korganizer&product=kpilot&product=ktnef&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED All open kdepim bugs]<br />
* [http://bugs.kde.org/buglist.cgi?product=kontact&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED All open Kontact bugs]<br />
* [http://bugs.kde.org/buglist.cgi?product=kmail&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED All open KMail bugs]<br />
* [http://bugs.kde.org/buglist.cgi?product=korganizer&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED All open KOrganizer bugs]<br />
* [http://bugs.kde.org/buglist.cgi?product=kaddressbook&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED All open KAddressBook bugs]<br />
* [http://bugs.kde.org/buglist.cgi?product=kpilot&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED All open KPilot bugs]<br />
* [http://bugs.kde.org/buglist.cgi?short_desc_type=regexp&short_desc=JJ.*&product=akregator&product=kaddressbook&product=kalarm&product=kandy&product=karm&product=kitchensync&product=kmail&product=knode&product=knotes&product=konsolekalendar&product=kontact&product=korganizer&product=kpilot&product=ktnef&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED KDE PIM Junior Jobs]<br />
<br />
= IMAP log =<br />
<br />
If you use problems with an IMAP or kolab resource than an IMAP log can be very usefull, because a developen can really see that is sent/received from the IMAP server. Please be aware, that the IMAP log shows all content, so there can be very private suff inside. Have a look into the IMAP log before sending it around.<br />
<br />
KIMAP_LOGFILE=/tmp/imap.log akonadictl restart<br />
<br />
Afterwards you find for each imap connection a file /tmp/imap.log.<PID>.<ID>.<br />
<br />
= akonadi log =<br />
<br />
Having problems with akonadi and/or one resource its often helpfull to get log. There are different levels where usfull information can be.<br />
<br />
== console output ==<br />
<br />
Developvers put many debug logs into there code to make it esay to follow, that is going on, when. But by default these informations are not displayed. So we should start and activate them:<br />
<br />
kdebugdialog<br />
<br />
search for akonadi and select everything that is involed in your problem. Maybe also you should activate something like kssl, kio,... depending on your problem. Afterwards just restart akonadi:<br />
<br />
akonadictl restart<br />
<br />
Than you see the log in the console.<br />
<br />
== using akonadiconsole ==<br />
<br />
Akonadiconsole is a very good debug tool.<br />
<br />
[[File:akonadiconsole.png]]<br />
<br />
start akonaidconsole<br />
<br />
1. select the debugger tab<br />
<br />
2. activate debugger<br />
<br />
do what every you want to debug<br />
<br />
3. search for the matching tab<br />
<br />
4. save logs to file<br />
<br />
= Statistics =<br />
<br />
* [https://bugs.kde.org/weekly-bug-summary.cgi KDE-wide weekly bug summary]</div>Sandrohttps://community.kde.org/index.php?title=KDE_PIM/Meetings/Osnabrueck_11&diff=30460KDE PIM/Meetings/Osnabrueck 112013-03-05T03:08:01Z<p>Sandro: The little longer guide</p>
<hr />
<div>The annual [[KDE_PIM/Meetings|KDE PIM Meeting]] will take place from 1.3.2012 to 3.3.2012 at the KDAB offices in Berlin.<br />
<br />
[[File:pim_sprint_berlin_2013.jpg]]<br />
<br />
== Topics ==<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 />
* KDE Dependencies Repository: create and fill a repository containing all essential dependencies for kdelibs, kde-runtime, kdepimlibs, kdepim-runtime and kdepim, primarily for use on Mac and Windows. Define update policy for those packages.<br />
* KDE-wide metacontacts (KPeople) - general overview of the state, architecture and possible uses<br />
* Review John's proposed QTimeZone scheduled for inclusion in Qt 5.1 to ensure meets KDEPIM requirements, bug fixes, code improvements, etc<br />
*WebAccounts integration for an unified way of managing web (google, facebook, ownCloud) accounts.<br />
* Google Integration - creating dedicated IMAP resource with native support for GMail IMAP extensions and adding support for Google Reader to the family of Akonadi resources for Google services<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 />
==== Future Development ====<br />
<br />
'''Audience:''' all, '''Desired Results:''' Plan regarding future 4.x releases and port to KF5<br />
<br />
* How to move to KF5?<br />
* KHolidays2 - Use JSON files? Try make standalone project for all PIM apps and desktops to use?<br />
<br />
==== Marketing ====<br />
<br />
'''Audience:''' all, '''Desired Results:''' Input on timeline, facts on good things on Akonadi, agreement on communication, group hug<br />
<br />
Follow up on what we did at Osnabrück 10.<br />
<br />
==== ''Add your discussion topic here'' ====<br />
=====QML Calendar API=====<br />
There is some awesome calendar stuff living in branches right now. That however is the C++ side. We don't seem to have any "developer friendly" QML layer to use all it's abilities. I'd like to draft up a "QML API" to make the calendar data easily available in QML. This is for the "calendaring" branch: http://quickgit.kde.org/?p=kdepim.git&a=shortlog&h=6854a4bb1b3843234ecc2ee9eb319585f56b84c9 Should we use a dataengine or a dedicated QML component?<br />
<br />
We do already have the calendar engine: http://quickgit.kde.org/?p=kde-workspace.git&a=tree&h=0c2732e5a4bcd5f508ed52b3c7967e452cc04931&hb=b01fae8966132826097a97237bbf6954ebad6732&f=plasma%2Fgeneric%2Fdataengines%2Fcalendar. Should that be extended or should we go for a dedicated QML component as API like so:<br />
<br />
<syntaxhighlight lang="javascript"><br />
Calendar {<br />
id: todaysItemsFromX<br />
<br />
// If no date is provided, all entries will be returned<br />
day: QDateTime something..<br />
<br />
// Fetchtype determines which events to return. Enum with TodoEntries, EventEntries, YournalEntries, .... etc.<br />
fetchType: Calendaring.EventEntries<br />
<br />
// The calendar from which to fetch the entries. If none provided then it will fetch the requested entries from all available calendars.<br />
calendar: "x"<br />
<br />
// The model containing the data with the filters applied.<br />
model<br />
}<br />
</syntaxhighlight><br />
<br />
Above is just a "braindump". I'd like to discuss this idea with some people at the sprint and implement it.<br />
<br />
=====Plasma Calendar=====<br />
<br />
Added by John Layt.<br />
<br />
We need to push for the completion of the Plasma integration, this years GSOC could be a good opportunity with its theme of polishing existing things. See http://www.layt.net/john/blog/odysseus/fame_akademy for my blog on what needs doing and http://community.kde.org/Plasma/Clock for more details. In short:<br />
* Ability to choose Collections to display in a widget<br />
* Ability to add simple Events and Todo's<br />
* KAlarm integration<br />
* Various UI improvements<br />
<br />
It may be worth considering if we want to continue with the current Plasma widget or come up with something new.<br />
<br />
One problem that also needs addressing is the Plasma Calendar launching Akonadi only to discover that no calendars are configured. To quote my blog:<br />
<br />
"One other area that needs solving is what to do when a user doesn't actually use KDEPIM or Akonadi for their PIM needs but Akonadi has still been installed by the distro by default? At the moment we launch Akonadi by default inside the Plasma Calendar as soon as the user clicks on the Clock, and query it for any available events. Naturally it finds none, but by then it is too late, Akonadi has been launched and is seen to be using resources. "Oh noes, big bad bloated KDE!" Many distro's avoid this by changing the default setting to not showing Events, but then users may not realise that they can be enabled. A far better solution would be if there was a passive way to query if any Akonadi Calendar Resources have been configured and only launch Akonadi if they have. We could also then offer a wizard to configure Akonadi Resources if none have been. This of course is something that would have to be implemented by the KDEPIM/Akonadi team."<br />
<br />
=== Presentations ===<br />
<br />
''Presentations of things interesting to the KDE PIM community. Please state targeted audience.''<br />
<br />
* ''Add your presentation here''<br />
<br />
== Agenda ==<br />
<br />
=== Friday ===<br />
<br />
16:00 Start meeting, fill agenda, get organized<br />
<br />
=== Saturday ===<br />
<br />
10:00 Review first batch of work, get organized<br />
<br />
10:30-12:00 Presentations, discussions targeted at whole group<br />
<br />
13:30 Group photo<br />
<br />
17:00 Review second batch of work, get organized<br />
<br />
17:30-18:30 Presentations, discussions targeted at whole group<br />
<br />
=== Sunday ===<br />
<br />
10:00 Review third batch of work, get organized<br />
<br />
10:30-11:30 Presentations, discussions targeted at whole group<br />
<br />
14:00 Close meeting, collect next steps<br />
<br />
== Meeting Notes ==<br />
<br />
===Porting to KDE Frameworks 5===<br />
<br />
* Report from Kevin & David on status<br />
* Progress made on prep work, Qt upstream<br />
* kdeui main blocker<br />
* also date/time<br />
* once done will split<br />
* Tech Preview end of this year<br />
* Then QA process<br />
* Will need early porters to test results before final release<br />
* KDE PIM to be guinea pig?<br />
* already kdepimlibs-frameworks branch<br />
* initial port to build on kf5<br />
* then make kpl "dissapper"<br />
* Can use CMake features earlier, e.g. automoc in 4.11<br />
* Same of K??? can be done in 4.11<br />
* kdepim no branch before tech preview, too much changing<br />
* kpl branch has value as unit tests etc exercises code<br />
* cmd line args stuff needed in Qt, have branch in Gerrit, hard sell into Qt, volunteer(s) needed for 5.2!<br />
* lots of widgets stuff needs to move to Qt, need volunteers for 5.2!<br />
* libpimutils?<br />
* next meeting will be position to address kpl and kp porting<br />
* can remove any q3support NOW!<br />
* Could look to move K -> Q classes where not using the K extra features, but tricky to know<br />
<br />
=== Akonadi/Nepomuk integration ===<br />
<br />
* vHanda: Looking into using the nepomuk feeders for KPeople. Currently too slow (2 or 3 emails per second, goal = 10 emails per second). Already better than the previous situation, 10 s per mail.<br />
* Completion in kmail composer (via nepomuk) is enabled again... but the goal is to replace that with KPeople (which has the contacts in memory).<br />
* vHanda: Planned: adding support for persistent queries.<br />
* C.M.: Letting the user control the feeder process -- people report CPU usage bugs, but if they could see that it's indexing emails, then we can differ that from actual bugs.<br />
* vHanda: Missing features for complex searches: query emails by date range etc. (feature set == see search dialog in kmail)<br />
<br />
=== Virtuoso ===<br />
<br />
vHanda: "I think I can write a virtuoso replacement in a month or two" (!)<br />
== mainly a SPARQL to SQL converter (limited to the SPARQL subset used in KDE)<br />
<br />
Problems with virtuoso:<br />
* Their use case is web-based stuff, so no consistency checking (it's not strongly typed at all, all values go into the same column).<br />
* Some fields cannot be indexed (e.g. no date/time searches)<br />
* Memory consumption (Milian, help!). Caches in virtuoso + caches in nepomuk.<br />
* No support for cancelling queries (although, with Sebastian now working on virtuoso, we could push for that)<br />
* Two databases, we could use akonadi's DB instead.<br />
* No support for stemming in text-based searches.<br />
* Lots of data copying (e.g. for one email, there's the email on disk, in akonadi DB, in virtuoso's SQL table, in virtuoso's full text index).<br />
* This extra data copying cannot be streamed. So the text content of the large pdf files is loaded into memory and pushed all in one go into virtuoso cause there are no steaming operators. With our own solution, we would not store this extra data and we could just directly pass it into the full text indexer.<br />
<br />
Instead of one big table, one table per property -> more control over indexing.<br />
Need to choose a full-text-indexing solution, one idea is XAPIAN.<br />
<br />
=== GSOC Ideas ===<br />
<br />
* Kontact Touch<br />
* Plasma Calendar / Workspace Integration<br />
* Kontact Summary as Plasmoids<br />
* Update KMail UI (improve delegates)<br />
* LinkedIn Resource<br />
* KPeople Integration in KMail (searching)<br />
* Port Plasma Notes to Akonadi<br />
* News resource for Akonadi and KMail<br />
* Mail and reminder notifications Plasmoids (maybe as part of workspace integration)<br />
* Document integration<br />
* Application scripting, contact actions<br />
* Marble integration with KAddressBook (there is an old experiemental branch)<br />
* Social feed interaction<br />
* KHolidays with JSON data files<br />
* OS X platform integration<br />
<br />
=== Calendar API for QML ===<br />
We've had a discussion to determine the needs for a Calendar API exposed in QML. In that discussion we made a list of requirements:<br />
* Make calendar data accessible through pure QML.<br />
* Make it possible to access all data or just parts of it.<br />
** Fetch Event items<br />
** Fetch Todo items<br />
** Fetch Journal items<br />
** a mixture of the above<br />
* Per item, be able to edit it<br />
* Add new items<br />
* make those items available under the QML import name: "org.kde.pim.calendar"<br />
All of the above needs to be possible in plain QML for an application developer.<br />
For the first part (the non editing and adding part) we drafted up this [[Calendar_API_QML|Calendar API for QML]] which Tobias implemented. A working proof of concept is available for those that want to see it. More work will obviously have to be done in this area.<br />
<br />
The part for editing and adding items will be done through controller classes. No work has been done in that area, yet. <br />
<br />
''Other notes will go here''<br />
<br />
=== Encrypting & Signing mails in kmail with umlaut/unicode characters ===<br />
The problem with encrypted/signed mails in kmail is, that signed/encrypted messages have a none matching contetTransferEncoding.<br />
So the contentTransferEnconding of the mail is determied for the actual text to encrypt/signed. For non ascii messages this is quoted-prinable or base64. The encryped/signed content doesn't necessarily should have the same contentTransferEncoding.<br />
But netherless the contenttransferEncoding and the content must be in match together. We fiddled around in the code and created [https://git.reviewboard.kde.org/r/109272 #109272] on reviewboad, that fixes this issue and two bugs [http://bugs.kde.org/289722 #289722] and [http://bugs.kde.org/289728 #289728].<br />
<br />
=== A short wiki entry for stating to develop kdepim ===<br />
<br />
== Blogs ==<br />
http://community.kde.org/KDE_PIM/Development/Start#The_little_longer_guide (ok no blog, but a wiki entry based on http://blogs.fsfe.org/torsten.grote/2012/10/03/compiling-kde-kontact-from-source/ )<br />
<br />
<br />
''When you blog about the meeting (and you should ;-), please add a link here''<br />
<br />
== Organization ==<br />
<br />
See the [[KDE_PIM/Meetings/Osnabrueck_11/Organization|Osnabrück 11 organization]] page for organizational details.</div>Sandrohttps://community.kde.org/index.php?title=KDE_PIM/Development/Start&diff=30459KDE PIM/Development/Start2013-03-05T03:01:24Z<p>Sandro: /* The little longer guide */</p>
<hr />
<div>= Getting Started =<br />
<br />
To get started, all you really need is a [[#Git - a Source Code Control System|git clone]]. After that, you can compile and run the latest-and-greatest (and maybe buggy) versions of the KDE PIM applications.<br />
When you find a bug, you can fix it, create a patch, and send it to us! That's the way KDE PIM applications are continually improving. There is much more information available to begin with, though.<br />
<br />
Here is a checklist of things to launch yourself into the world of KDE PIM development.<br />
For lots of them, it is most important that you know they exist:<br />
<br />
* Subscribe to the right [[#Mailing Lists|mailing lists]]. Read them regularly.<br />
* Browse the information about the [[#Common KDE Developer information|development tools]], to choose one. Most KDE PIM hackers use kate, vi, or emacs as editor and just compile in a konsole window, though.<br />
* Take a brief look at the [http://doc.trolltech.com/4.7 Qt documentation]. It is excellent, and you should know about QWidgets and QObjects a little before continuing.<br />
* Take a brief look at the [http://api.kde.org/ KDE documentation]. It is a bit overwhelming.<br />
* Spend some time over at the [http://www.kde.org/community/getinvolved/ KDE Community website].<br />
* Get the [[#prerequisites|prerequisites]] for building KDE PIM master. Note that you really want to follow master to make a positive contribution to KDE PIM. <br /><br />
If you work on or with the last released version, you're usually a month or four behind the times, and that makes a huge difference in KDE PIM. You can work with a stable system -- the latest released KDE libs and base -- and put (relatively) unstable PIM HEAD on it.<br />
* Clone the relevant [[#Git - a Source Code Control System|Git repositories]].<br />
* Compile it and install.<br />
* Report bugs, wishes, fix bugs, get involved!<br />
<br />
== Mailing Lists ==<br />
<br />
Mailing lists are probably the ultimate source of development information. Follow discussions of KDE core and application developers and ask your questions. Unless you don't think about what you are saying, you will surely get an answer. Subscribe to the [http://mail.kde.org/mailman/listinfo/kde-pim kde-pim mailing list]. It is for '''discussion about development'''. Please don't wildly post all your compilation problems there. Ask on [[#IRC (Chat)|IRC]] for such issues.<br />
<br />
== IRC (Chat) ==<br />
<br />
Most of the developers hang around in one development IRC channel or another. On [http://www.freenode.net/ freenode] (irc.kde.org), you can find:<br />
<br />
* #KDE for the user questions.<br />
* #akonadi for development discussion on Akonadi.<br />
* #kontact for development discussion on Kontact and its components. Please don't post user-questions there.<br />
<br />
There are a variety of IRC (Chat) programs available. KDE ships with [http://konversation.kde.org/ Konversation]. XChat is available in many installations as well.<br />
<br />
== Common KDE Developer information ==<br />
<br />
Visit the [http://techbase.kde.org KDE techbase site] for very detailed information about KDE development.<br />
You'll find lots of stuff, e.g. documentation, tutorials, reference guides, etc.<br />
<br />
http://techbase.kde.org/Projects/PIM has lots of informations you may read before starting contributing to KDE PIM.<br />
<br />
http://userbase.kde.org/Kontact is the central place for user tips and tricks.<br />
<br />
[http://www.kdevelop.org/ KDevelop] is an Integrated Development Environment for KDE.<br />
<br />
For recent news about KDE development you may not miss the KDE news site at [http://dot.kde.org/ dot.kde.org].<br />
<br />
== Prerequisites ==<br />
<br />
the whole KDE PIM suite is composed of four modules. You're highly encouraged to checkout and build all of them:<br />
* [http://www.akonadi-project.org/ Akonadi], The PIM Storage Service<br />
* KDEPIMLIBS, the base libraries for all the PIM applications<br />
* KDEPIM-RUNTIME, the Akonadi resources which are required at runtime to let the kdepim applications communicate with the Akonadi server<br />
* KDEPIM, All the PIM applications<br />
<br />
In order to build and use the KDEPIM modules, you may use the last released KDE version.<br />
<br />
You might want to make a backup of your valuable data, though. Most of it lives in <small>.kde</small>, in your home directory; You may also backup your Akonadi server config files in <small>$HOME/.config/akonadi</small> and your kdepim applications data in <small>$HOME/.local/share</small>.<br />
It may be easier to just create an additional user and give it a copy of your data, and run PIM HEAD there. <br />
<br />
== Git - a Source Code Control System ==<br />
<br />
The KDE PIM repositories can be visited via WWW at http://projects.kde.org or http://gitweb.kde.org.<br />
<br />
== The really short guide ==<br />
<br />
This short guide will explain how to build Akonadi, kdepim and kdepim-runtime checked out from Git.<br />
<br />
You may use the following commands to check out the different repositories:<br />
<br />
* Akonadi:<br />
<syntaxhighlight lang="bash"><br />
git clone http://anongit.kde.org/akonadi<br />
</syntaxhighlight><br />
<br />
* kdepimlibs:<br />
<syntaxhighlight lang="bash"><br />
git clone http://anongit.kde.org/kdepimlibs<br />
</syntaxhighlight><br />
<br />
* kdepim-runtime:<br />
<syntaxhighlight lang="bash"><br />
git clone http://anongit.kde.org/kdepim-runtime<br />
</syntaxhighlight><br />
<br />
* kdepim:<br />
<syntaxhighlight lang="bash"><br />
git clone http://anongit.kde.org/kdepim<br />
</syntaxhighlight><br />
<br />
You can now build the modules in the following order:<br />
<pre><br />
Akonadi > kdepimlibs > kdepim > kdepim-runtime<br />
</pre><br />
<br />
Complete guides to build KDE modules can be found on http://techbase.kde.org.<br />
<br />
== The little longer guide ==<br />
If you are in the position to have a distribution (debian,ubuntu,...) , that doesn't ship the newest kde stable version you have to build more packages.<br />
First you should get the two really fancy scripts build-config, findup, kde-bashrc from [http://techbase.kde.org/Getting_Started/Build/Environment Getting Started/Build/Environment]. For the next part I assume that you have following layout and would suggest to create a dececated user:<br />
<pre><br />
~/bin/findup<br />
~/build-config<br />
~/kde/src<br />
~/kde/build<br />
~/kde/inst<br />
~/kde/kde-bashrc <br />
~/kde/get-all.sh<br />
~/kde/build-all.sh<br />
</pre><br />
<br />
Now make sure that build-config is refernced in your .profile as fall back you should add /usr:<br />
<syntaxhighlight lang="bash"><br />
...<br />
<br />
source ./build-config<br />
export KDEDIRS=$KDEDIRS:/usr<br />
</syntaxhighlight><br />
<br />
Now also install the two scripts get-all.sh and /build-all.sh from below.<br />
<br />
And now run them:<br />
<syntaxhighlight lang="bash"><br />
cd ~/kde<br />
get-all.sh<br />
build-all.sh<br />
</syntaxhighlight><br />
<br />
<br />
Afterwars you can just login with your new created user and have the possibility to start developing :)<br />
<br />
You may need much packages to install on your system for compiling (see [http://techbase.kde.org/Getting_Started/Build/Distributions Getting Started/Build/Distributions]).<br />
<br />
<br />
<br />
===get-all.sh===<br />
<syntaxhighlight lang="bash"><br />
#!/bin/bash<br />
<br />
DIR=`pwd`<br />
PROGS=( kdelibs soprano strigi nepomuk-core nepomuk-widgets kactivities kde-runtime akonadi kdepimlibs kdepim-runtime kdepim )<br />
<br />
mkdir -p $DIR/src<br />
<br />
for D in "${PROGS[@]}"<br />
do<br />
echo<br />
echo "Getting $D"<br />
echo<br />
<br />
cd $DIR/src<br />
git clone kde:$D.git<br />
done<br />
</syntaxhighlight><br />
<br />
<br />
===build-all.sh===<br />
<syntaxhighlight lang="bash"><br />
#!/bin/bash<br />
<br />
DIR=`pwd`<br />
PROGS=( soprano strigi kdelibs nepomuk-core nepomuk-widgets kactivities kde-runtime akonadi kdepimlibs kdepim-runtime kdepim )<br />
<br />
source kde-bashrc<br />
<br />
for D in "${PROGS[@]}"<br />
do<br />
echo<br />
echo "Compiling $D"<br />
echo<br />
<br />
cs $D<br />
git pull --rebase<br />
cmakekde || break<br />
done<br />
</syntaxhighlight><br />
<br />
Idea taken from [http://blogs.fsfe.org/torsten.grote/2012/10/03/compiling-kde-kontact-from-source/ Torsten Grote:compiling-kde-kontact-from-source]</div>Sandrohttps://community.kde.org/index.php?title=KDE_PIM/Meetings/Osnabrueck_11&diff=30417KDE PIM/Meetings/Osnabrueck 112013-03-03T21:33:36Z<p>Sandro: /* Encrypting & Signing mails in kmail with umlaut/unicode characters */</p>
<hr />
<div>The annual [[KDE_PIM/Meetings|KDE PIM Meeting]] will take place from 1.3.2012 to 3.3.2012 at the KDAB offices in Berlin.<br />
<br />
[[File:pim_sprint_berlin_2013.jpg]]<br />
<br />
== Topics ==<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 />
* KDE Dependencies Repository: create and fill a repository containing all essential dependencies for kdelibs, kde-runtime, kdepimlibs, kdepim-runtime and kdepim, primarily for use on Mac and Windows. Define update policy for those packages.<br />
* KDE-wide metacontacts (KPeople) - general overview of the state, architecture and possible uses<br />
* Review John's proposed QTimeZone scheduled for inclusion in Qt 5.1 to ensure meets KDEPIM requirements, bug fixes, code improvements, etc<br />
*WebAccounts integration for an unified way of managing web (google, facebook, ownCloud) accounts.<br />
* Google Integration - creating dedicated IMAP resource with native support for GMail IMAP extensions and adding support for Google Reader to the family of Akonadi resources for Google services<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 />
==== Future Development ====<br />
<br />
'''Audience:''' all, '''Desired Results:''' Plan regarding future 4.x releases and port to KF5<br />
<br />
* How to move to KF5?<br />
* KHolidays2 - Use JSON files? Try make standalone project for all PIM apps and desktops to use?<br />
<br />
==== Marketing ====<br />
<br />
'''Audience:''' all, '''Desired Results:''' Input on timeline, facts on good things on Akonadi, agreement on communication, group hug<br />
<br />
Follow up on what we did at Osnabrück 10.<br />
<br />
==== ''Add your discussion topic here'' ====<br />
=====QML Calendar API=====<br />
There is some awesome calendar stuff living in branches right now. That however is the C++ side. We don't seem to have any "developer friendly" QML layer to use all it's abilities. I'd like to draft up a "QML API" to make the calendar data easily available in QML. This is for the "calendaring" branch: http://quickgit.kde.org/?p=kdepim.git&a=shortlog&h=6854a4bb1b3843234ecc2ee9eb319585f56b84c9 Should we use a dataengine or a dedicated QML component?<br />
<br />
We do already have the calendar engine: http://quickgit.kde.org/?p=kde-workspace.git&a=tree&h=0c2732e5a4bcd5f508ed52b3c7967e452cc04931&hb=b01fae8966132826097a97237bbf6954ebad6732&f=plasma%2Fgeneric%2Fdataengines%2Fcalendar. Should that be extended or should we go for a dedicated QML component as API like so:<br />
<br />
<syntaxhighlight lang="javascript"><br />
Calendar {<br />
id: todaysItemsFromX<br />
<br />
// If no date is provided, all entries will be returned<br />
day: QDateTime something..<br />
<br />
// Fetchtype determines which events to return. Enum with TodoEntries, EventEntries, YournalEntries, .... etc.<br />
fetchType: Calendaring.EventEntries<br />
<br />
// The calendar from which to fetch the entries. If none provided then it will fetch the requested entries from all available calendars.<br />
calendar: "x"<br />
<br />
// The model containing the data with the filters applied.<br />
model<br />
}<br />
</syntaxhighlight><br />
<br />
Above is just a "braindump". I'd like to discuss this idea with some people at the sprint and implement it.<br />
<br />
=====Plasma Calendar=====<br />
<br />
Added by John Layt.<br />
<br />
We need to push for the completion of the Plasma integration, this years GSOC could be a good opportunity with its theme of polishing existing things. See http://www.layt.net/john/blog/odysseus/fame_akademy for my blog on what needs doing and http://community.kde.org/Plasma/Clock for more details. In short:<br />
* Ability to choose Collections to display in a widget<br />
* Ability to add simple Events and Todo's<br />
* KAlarm integration<br />
* Various UI improvements<br />
<br />
It may be worth considering if we want to continue with the current Plasma widget or come up with something new.<br />
<br />
One problem that also needs addressing is the Plasma Calendar launching Akonadi only to discover that no calendars are configured. To quote my blog:<br />
<br />
"One other area that needs solving is what to do when a user doesn't actually use KDEPIM or Akonadi for their PIM needs but Akonadi has still been installed by the distro by default? At the moment we launch Akonadi by default inside the Plasma Calendar as soon as the user clicks on the Clock, and query it for any available events. Naturally it finds none, but by then it is too late, Akonadi has been launched and is seen to be using resources. "Oh noes, big bad bloated KDE!" Many distro's avoid this by changing the default setting to not showing Events, but then users may not realise that they can be enabled. A far better solution would be if there was a passive way to query if any Akonadi Calendar Resources have been configured and only launch Akonadi if they have. We could also then offer a wizard to configure Akonadi Resources if none have been. This of course is something that would have to be implemented by the KDEPIM/Akonadi team."<br />
<br />
=== Presentations ===<br />
<br />
''Presentations of things interesting to the KDE PIM community. Please state targeted audience.''<br />
<br />
* ''Add your presentation here''<br />
<br />
== Agenda ==<br />
<br />
=== Friday ===<br />
<br />
16:00 Start meeting, fill agenda, get organized<br />
<br />
=== Saturday ===<br />
<br />
10:00 Review first batch of work, get organized<br />
<br />
10:30-12:00 Presentations, discussions targeted at whole group<br />
<br />
13:30 Group photo<br />
<br />
17:00 Review second batch of work, get organized<br />
<br />
17:30-18:30 Presentations, discussions targeted at whole group<br />
<br />
=== Sunday ===<br />
<br />
10:00 Review third batch of work, get organized<br />
<br />
10:30-11:30 Presentations, discussions targeted at whole group<br />
<br />
14:00 Close meeting, collect next steps<br />
<br />
== Meeting Notes ==<br />
<br />
===Porting to KDE Frameworks 5===<br />
<br />
* Report from Kevin & David on status<br />
* Progress made on prep work, Qt upstream<br />
* kdeui main blocker<br />
* also date/time<br />
* once done will split<br />
* Tech Preview end of this year<br />
* Then QA process<br />
* Will need early porters to test results before final release<br />
* KDE PIM to be guinea pig?<br />
* already kdepimlibs-frameworks branch<br />
* initial port to build on kf5<br />
* then make kpl "dissapper"<br />
* Can use CMake features earlier, e.g. automoc in 4.11<br />
* Same of K??? can be done in 4.11<br />
* kdepim no branch before tech preview, too much changing<br />
* kpl branch has value as unit tests etc exercises code<br />
* cmd line args stuff needed in Qt, have branch in Gerrit, hard sell into Qt, volunteer(s) needed for 5.2!<br />
* lots of widgets stuff needs to move to Qt, need volunteers for 5.2!<br />
* libpimutils?<br />
* next meeting will be position to address kpl and kp porting<br />
* can remove any q3support NOW!<br />
* Could look to move K -> Q classes where not using the K extra features, but tricky to know<br />
<br />
=== Akonadi/Nepomuk integration ===<br />
<br />
* vHanda: Looking into using the nepomuk feeders for KPeople. Currently too slow (2 or 3 emails per second, goal = 10 emails per second). Already better than the previous situation, 10 s per mail.<br />
* Completion in kmail composer (via nepomuk) is enabled again... but the goal is to replace that with KPeople (which has the contacts in memory).<br />
* vHanda: Planned: adding support for persistent queries.<br />
* C.M.: Letting the user control the feeder process -- people report CPU usage bugs, but if they could see that it's indexing emails, then we can differ that from actual bugs.<br />
* vHanda: Missing features for complex searches: query emails by date range etc. (feature set == see search dialog in kmail)<br />
<br />
=== Virtuoso ===<br />
<br />
vHanda: "I think I can write a virtuoso replacement in a month or two" (!)<br />
== mainly a SPARQL to SQL converter (limited to the SPARQL subset used in KDE)<br />
<br />
Problems with virtuoso:<br />
* Their use case is web-based stuff, so no consistency checking (it's not strongly typed at all, all values go into the same column).<br />
* Some fields cannot be indexed (e.g. no date/time searches)<br />
* Memory consumption (Milian, help!). Caches in virtuoso + caches in nepomuk.<br />
* No support for cancelling queries (although, with Sebastian now working on virtuoso, we could push for that)<br />
* Two databases, we could use akonadi's DB instead.<br />
* No support for stemming in text-based searches.<br />
* Lots of data copying (e.g. for one email, there's the email on disk, in akonadi DB, in virtuoso's SQL table, in virtuoso's full text index).<br />
* This extra data copying cannot be streamed. So the text content of the large pdf files is loaded into memory and pushed all in one go into virtuoso cause there are no steaming operators. With our own solution, we would not store this extra data and we could just directly pass it into the full text indexer.<br />
<br />
Instead of one big table, one table per property -> more control over indexing.<br />
Need to choose a full-text-indexing solution, one idea is XAPIAN.<br />
<br />
=== GSOC Ideas ===<br />
<br />
* Kontact Touch<br />
* Plasma Calendar / Workspace Integration<br />
* Kontact Summary as Plasmoids<br />
* Update KMail UI (improve delegates)<br />
* LinkedIn Resource<br />
* KPeople Integration in KMail (searching)<br />
* Port Plasma Notes to Akonadi<br />
* News resource for Akonadi and KMail<br />
* Mail and reminder notifications Plasmoids (maybe as part of workspace integration)<br />
* Document integration<br />
* Application scripting, contact actions<br />
* Marble integration with KAddressBook (there is an old experiemental branch)<br />
* Social feed interaction<br />
* KHolidays with JSON data files<br />
* OS X platform integration<br />
<br />
=== Calendar API for QML ===<br />
We've had a discussion to determine the needs for a Calendar API exposed in QML. In that discussion we made a list of requirements:<br />
* Make calendar data accessible through pure QML.<br />
* Make it possible to access all data or just parts of it.<br />
** Fetch Event items<br />
** Fetch Todo items<br />
** Fetch Journal items<br />
** a mixture of the above<br />
* Per item, be able to edit it<br />
* Add new items<br />
* make those items available under the QML import name: "org.kde.pim.calendar"<br />
All of the above needs to be possible in plain QML for an application developer.<br />
For the first part (the non editing and adding part) we drafted up this [[Calendar_API_QML|Calendar API for QML]] which Tobias implemented. A working proof of concept is available for those that want to see it. More work will obviously have to be done in this area.<br />
<br />
The part for editing and adding items will be done through controller classes. No work has been done in that area, yet. <br />
<br />
''Other notes will go here''<br />
<br />
=== Encrypting & Signing mails in kmail with umlaut/unicode characters ===<br />
The problem with encrypted/signed mails in kmail is, that signed/encrypted messages have a none matching contetTransferEncoding.<br />
So the contentTransferEnconding of the mail is determied for the actual text to encrypt/signed. For non ascii messages this is quoted-prinable or base64. The encryped/signed content doesn't necessarily should have the same contentTransferEncoding.<br />
But netherless the contenttransferEncoding and the content must be in match together. We fiddled around in the code and created [https://git.reviewboard.kde.org/r/109272 #109272] on reviewboad, that fixes this issue and two bugs [http://bugs.kde.org/289722 #289722] and [http://bugs.kde.org/289728 #289728].<br />
<br />
== Blogs ==<br />
<br />
''When you blog about the meeting (and you should ;-), please add a link here''<br />
<br />
== Organization ==<br />
<br />
See the [[KDE_PIM/Meetings/Osnabrueck_11/Organization|Osnabrück 11 organization]] page for organizational details.</div>Sandrohttps://community.kde.org/index.php?title=KDE_PIM/Meetings/Osnabrueck_11&diff=30416KDE PIM/Meetings/Osnabrueck 112013-03-03T21:32:34Z<p>Sandro: Encrypting & Signing mails in kmail with umlaut/unicode characters</p>
<hr />
<div>The annual [[KDE_PIM/Meetings|KDE PIM Meeting]] will take place from 1.3.2012 to 3.3.2012 at the KDAB offices in Berlin.<br />
<br />
[[File:pim_sprint_berlin_2013.jpg]]<br />
<br />
== Topics ==<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 />
* KDE Dependencies Repository: create and fill a repository containing all essential dependencies for kdelibs, kde-runtime, kdepimlibs, kdepim-runtime and kdepim, primarily for use on Mac and Windows. Define update policy for those packages.<br />
* KDE-wide metacontacts (KPeople) - general overview of the state, architecture and possible uses<br />
* Review John's proposed QTimeZone scheduled for inclusion in Qt 5.1 to ensure meets KDEPIM requirements, bug fixes, code improvements, etc<br />
*WebAccounts integration for an unified way of managing web (google, facebook, ownCloud) accounts.<br />
* Google Integration - creating dedicated IMAP resource with native support for GMail IMAP extensions and adding support for Google Reader to the family of Akonadi resources for Google services<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 />
==== Future Development ====<br />
<br />
'''Audience:''' all, '''Desired Results:''' Plan regarding future 4.x releases and port to KF5<br />
<br />
* How to move to KF5?<br />
* KHolidays2 - Use JSON files? Try make standalone project for all PIM apps and desktops to use?<br />
<br />
==== Marketing ====<br />
<br />
'''Audience:''' all, '''Desired Results:''' Input on timeline, facts on good things on Akonadi, agreement on communication, group hug<br />
<br />
Follow up on what we did at Osnabrück 10.<br />
<br />
==== ''Add your discussion topic here'' ====<br />
=====QML Calendar API=====<br />
There is some awesome calendar stuff living in branches right now. That however is the C++ side. We don't seem to have any "developer friendly" QML layer to use all it's abilities. I'd like to draft up a "QML API" to make the calendar data easily available in QML. This is for the "calendaring" branch: http://quickgit.kde.org/?p=kdepim.git&a=shortlog&h=6854a4bb1b3843234ecc2ee9eb319585f56b84c9 Should we use a dataengine or a dedicated QML component?<br />
<br />
We do already have the calendar engine: http://quickgit.kde.org/?p=kde-workspace.git&a=tree&h=0c2732e5a4bcd5f508ed52b3c7967e452cc04931&hb=b01fae8966132826097a97237bbf6954ebad6732&f=plasma%2Fgeneric%2Fdataengines%2Fcalendar. Should that be extended or should we go for a dedicated QML component as API like so:<br />
<br />
<syntaxhighlight lang="javascript"><br />
Calendar {<br />
id: todaysItemsFromX<br />
<br />
// If no date is provided, all entries will be returned<br />
day: QDateTime something..<br />
<br />
// Fetchtype determines which events to return. Enum with TodoEntries, EventEntries, YournalEntries, .... etc.<br />
fetchType: Calendaring.EventEntries<br />
<br />
// The calendar from which to fetch the entries. If none provided then it will fetch the requested entries from all available calendars.<br />
calendar: "x"<br />
<br />
// The model containing the data with the filters applied.<br />
model<br />
}<br />
</syntaxhighlight><br />
<br />
Above is just a "braindump". I'd like to discuss this idea with some people at the sprint and implement it.<br />
<br />
=====Plasma Calendar=====<br />
<br />
Added by John Layt.<br />
<br />
We need to push for the completion of the Plasma integration, this years GSOC could be a good opportunity with its theme of polishing existing things. See http://www.layt.net/john/blog/odysseus/fame_akademy for my blog on what needs doing and http://community.kde.org/Plasma/Clock for more details. In short:<br />
* Ability to choose Collections to display in a widget<br />
* Ability to add simple Events and Todo's<br />
* KAlarm integration<br />
* Various UI improvements<br />
<br />
It may be worth considering if we want to continue with the current Plasma widget or come up with something new.<br />
<br />
One problem that also needs addressing is the Plasma Calendar launching Akonadi only to discover that no calendars are configured. To quote my blog:<br />
<br />
"One other area that needs solving is what to do when a user doesn't actually use KDEPIM or Akonadi for their PIM needs but Akonadi has still been installed by the distro by default? At the moment we launch Akonadi by default inside the Plasma Calendar as soon as the user clicks on the Clock, and query it for any available events. Naturally it finds none, but by then it is too late, Akonadi has been launched and is seen to be using resources. "Oh noes, big bad bloated KDE!" Many distro's avoid this by changing the default setting to not showing Events, but then users may not realise that they can be enabled. A far better solution would be if there was a passive way to query if any Akonadi Calendar Resources have been configured and only launch Akonadi if they have. We could also then offer a wizard to configure Akonadi Resources if none have been. This of course is something that would have to be implemented by the KDEPIM/Akonadi team."<br />
<br />
=== Presentations ===<br />
<br />
''Presentations of things interesting to the KDE PIM community. Please state targeted audience.''<br />
<br />
* ''Add your presentation here''<br />
<br />
== Agenda ==<br />
<br />
=== Friday ===<br />
<br />
16:00 Start meeting, fill agenda, get organized<br />
<br />
=== Saturday ===<br />
<br />
10:00 Review first batch of work, get organized<br />
<br />
10:30-12:00 Presentations, discussions targeted at whole group<br />
<br />
13:30 Group photo<br />
<br />
17:00 Review second batch of work, get organized<br />
<br />
17:30-18:30 Presentations, discussions targeted at whole group<br />
<br />
=== Sunday ===<br />
<br />
10:00 Review third batch of work, get organized<br />
<br />
10:30-11:30 Presentations, discussions targeted at whole group<br />
<br />
14:00 Close meeting, collect next steps<br />
<br />
== Meeting Notes ==<br />
<br />
===Porting to KDE Frameworks 5===<br />
<br />
* Report from Kevin & David on status<br />
* Progress made on prep work, Qt upstream<br />
* kdeui main blocker<br />
* also date/time<br />
* once done will split<br />
* Tech Preview end of this year<br />
* Then QA process<br />
* Will need early porters to test results before final release<br />
* KDE PIM to be guinea pig?<br />
* already kdepimlibs-frameworks branch<br />
* initial port to build on kf5<br />
* then make kpl "dissapper"<br />
* Can use CMake features earlier, e.g. automoc in 4.11<br />
* Same of K??? can be done in 4.11<br />
* kdepim no branch before tech preview, too much changing<br />
* kpl branch has value as unit tests etc exercises code<br />
* cmd line args stuff needed in Qt, have branch in Gerrit, hard sell into Qt, volunteer(s) needed for 5.2!<br />
* lots of widgets stuff needs to move to Qt, need volunteers for 5.2!<br />
* libpimutils?<br />
* next meeting will be position to address kpl and kp porting<br />
* can remove any q3support NOW!<br />
* Could look to move K -> Q classes where not using the K extra features, but tricky to know<br />
<br />
=== Akonadi/Nepomuk integration ===<br />
<br />
* vHanda: Looking into using the nepomuk feeders for KPeople. Currently too slow (2 or 3 emails per second, goal = 10 emails per second). Already better than the previous situation, 10 s per mail.<br />
* Completion in kmail composer (via nepomuk) is enabled again... but the goal is to replace that with KPeople (which has the contacts in memory).<br />
* vHanda: Planned: adding support for persistent queries.<br />
* C.M.: Letting the user control the feeder process -- people report CPU usage bugs, but if they could see that it's indexing emails, then we can differ that from actual bugs.<br />
* vHanda: Missing features for complex searches: query emails by date range etc. (feature set == see search dialog in kmail)<br />
<br />
=== Virtuoso ===<br />
<br />
vHanda: "I think I can write a virtuoso replacement in a month or two" (!)<br />
== mainly a SPARQL to SQL converter (limited to the SPARQL subset used in KDE)<br />
<br />
Problems with virtuoso:<br />
* Their use case is web-based stuff, so no consistency checking (it's not strongly typed at all, all values go into the same column).<br />
* Some fields cannot be indexed (e.g. no date/time searches)<br />
* Memory consumption (Milian, help!). Caches in virtuoso + caches in nepomuk.<br />
* No support for cancelling queries (although, with Sebastian now working on virtuoso, we could push for that)<br />
* Two databases, we could use akonadi's DB instead.<br />
* No support for stemming in text-based searches.<br />
* Lots of data copying (e.g. for one email, there's the email on disk, in akonadi DB, in virtuoso's SQL table, in virtuoso's full text index).<br />
* This extra data copying cannot be streamed. So the text content of the large pdf files is loaded into memory and pushed all in one go into virtuoso cause there are no steaming operators. With our own solution, we would not store this extra data and we could just directly pass it into the full text indexer.<br />
<br />
Instead of one big table, one table per property -> more control over indexing.<br />
Need to choose a full-text-indexing solution, one idea is XAPIAN.<br />
<br />
=== GSOC Ideas ===<br />
<br />
* Kontact Touch<br />
* Plasma Calendar / Workspace Integration<br />
* Kontact Summary as Plasmoids<br />
* Update KMail UI (improve delegates)<br />
* LinkedIn Resource<br />
* KPeople Integration in KMail (searching)<br />
* Port Plasma Notes to Akonadi<br />
* News resource for Akonadi and KMail<br />
* Mail and reminder notifications Plasmoids (maybe as part of workspace integration)<br />
* Document integration<br />
* Application scripting, contact actions<br />
* Marble integration with KAddressBook (there is an old experiemental branch)<br />
* Social feed interaction<br />
* KHolidays with JSON data files<br />
* OS X platform integration<br />
<br />
=== Calendar API for QML ===<br />
We've had a discussion to determine the needs for a Calendar API exposed in QML. In that discussion we made a list of requirements:<br />
* Make calendar data accessible through pure QML.<br />
* Make it possible to access all data or just parts of it.<br />
** Fetch Event items<br />
** Fetch Todo items<br />
** Fetch Journal items<br />
** a mixture of the above<br />
* Per item, be able to edit it<br />
* Add new items<br />
* make those items available under the QML import name: "org.kde.pim.calendar"<br />
All of the above needs to be possible in plain QML for an application developer.<br />
For the first part (the non editing and adding part) we drafted up this [[Calendar_API_QML|Calendar API for QML]] which Tobias implemented. A working proof of concept is available for those that want to see it. More work will obviously have to be done in this area.<br />
<br />
The part for editing and adding items will be done through controller classes. No work has been done in that area, yet. <br />
<br />
''Other notes will go here''<br />
<br />
== Encrypting & Signing mails in kmail with umlaut/unicode characters ==<br />
The problem with encrypted/signed mails in kmail is, that signed/encrypted messages have a none matching contetTransferEncoding.<br />
So the contentTransferEnconding of the mail is determied for the actual text to encrypt/signed. For non ascii messages this is quoted-prinable or base64. The encryped/signed content doesn't necessarily should have the same contentTransferEncoding.<br />
But netherless the contenttransferEncoding and the content must be in match together. We fiddled around in the code and created [https://git.reviewboard.kde.org/r/109272 #109272] on reviewboad, that fixes this issue and two bugs [http://bugs.kde.org/289722 #289722] and [http://bugs.kde.org/289728 #289728].<br />
== Blogs ==<br />
<br />
''When you blog about the meeting (and you should ;-), please add a link here''<br />
<br />
== Organization ==<br />
<br />
See the [[KDE_PIM/Meetings/Osnabrueck_11/Organization|Osnabrück 11 organization]] page for organizational details.</div>Sandro