https://community.kde.org/index.php?title=KDE_PIM/Meetings/Akademy_2005&feed=atom&action=historyKDE PIM/Meetings/Akademy 2005 - Revision history2024-03-29T08:25:19ZRevision history for this page on the wikiMediaWiki 1.40.2https://community.kde.org/index.php?title=KDE_PIM/Meetings/Akademy_2005&diff=10339&oldid=prevMahoutsukai: add info about PIM BoF at Akademy 20052011-02-26T13:33:55Z<p>add info about PIM BoF at Akademy 2005</p>
<p><b>New page</b></p><div>Akademy 2005 in Malaga yielded a number of important decisions<br />
related to KDE4 and KDE PIM. These are explained below.<br />
<br />
= KDE PIM BoF Minutes =<br />
<br />
== Agenda ==<br />
<br />
* Porting to Qt4/KDE4<br />
* Merging Branches<br />
* Redesigns<br />
* Syncing<br />
* Groupware Server<br />
* Messaging<br />
* Offline Mode for KMail/etc<br />
* Meetings<br />
* Alliances<br />
* Website<br />
* Artists<br />
* 3.6<br />
* 3.5 usability emergency surgery<br />
<br />
<br />
== Porting to Qt4/KDE4 ==<br />
<br />
* Check diff between 3.5 branch port and trunk (Ingo)<br />
* Copy 3.5 to trunk (danimo)<br />
* Merge Getting things done (SoC), kalle and proko2 changes<br />
* Open trunk for KDE4 development<br />
* use kdelibs from before the restructuring of libs<br />
* Goal: Do library mode, more kdepim libs tgo kdelibs<br />
* Start now<br />
<br />
<br />
== Merging Branches ==<br />
<br />
Existing branches:<br />
<br />
* SoC branches<br />
** Scripting (merge later)<br />
** Getting things done (merge to trunk after copying)<br />
** Living KDE (merge later)<br />
* Proko2 (till needs to merge 2-3 patches)<br />
* Kalle (no problem)<br />
* OpenSync branch (no problem, merge later)<br />
* KoPI branch (carefully migrate individual patches)<br />
* Two porting strategies<br />
** Tag of current kde libs and port pim based on this tag<br />
** "Wildwest" based on current trunk (risky)<br>=> we'll for now go with the tagged version, but want to switch later to seize the possiblity of taking influence in lib development<br />
<br />
<br />
== Redesign ==<br />
<br />
* KResource<br />
* libkabc (e.g. async loading)<br />
* stabilize libkcal (Reinhold)<br />
* General access to PIMdata between KDE PIM applications<br />
* Design APIs (Cross-Desktop, Evo DS, etc., check Evolution IPC, maybe use DBUS)<br />
* UI redesign for resources, multiple calenders<br />
<br />
<br />
== Syncing ==<br />
<br />
* OpenSync meeting held before aKademy: Armin Bauer, Cornelius Schumacher, Holger Freyther and Tobias K&ouml;nig attended.<br />
* Goal: make OpenSync standard on the Linux desktop<br />
* OpenSync is the successor to MultiSync. They have separated the GUI and the backend.<br />
* written in C and glib internally<br />
* Results<br />
** C++/Qt wrapper<br />
** KDE GUI<br />
** KDE PIM plugin (in branch)<br />
* Existing Plugins<br />
** File<br />
** Palm<br />
** SyncML<br />
* "KDE is the best GUI implementation" (Cornelius)<br />
* OpenSync is the way to go<br />
* New KitcheSync will replace KitchenSync, KSync, Kandy (which will not be ported to trunk), and eventually KPilot<br />
* Till says "make a fuss on the dot, send clear message that KDE has decided to move to OpenSync"<br />
* Will asked "should we use OpenSync for syncing resources and groupware servers" -- "No because specialized sync algorithms can do a better job, risk of dataloss if the index is broken, however some features of OpenSync are attractive, we should try to provide better groupware middleware and reduce code duplication"<br />
<br />
<br />
== Groupware Servers ==<br />
<br />
* Get rid of all of the half-working Exchange connectors, reason: we don't have either vendor support nor resources to do it properly, so better not support it. Still possible to readd it, if somebody commits to it fulltime.<br />
** Result: Disable from compilation in 3.5, remove in 4.0<br />
* Stress commercial support makes effective groupware resources possible.<br />
* Concentrate on working resources<br />
<br />
<br />
== Messaging ==<br />
<br />
* IM, VoIP, other messaging important to KDE PIM<br />
* improve integration of messaging - kopete, kcall, etc<br />
* consider move of kopete to KDE PIM - consult kopete devs<br />
* reconsider KIMProxy design, esp. wrt DBUS and standardization<br />
* Will leads the way<br />
* Integrating Kopete into kdepim?<br />
<br />
<br />
== Offlinemode in KMail/etc. ==<br />
<br />
* Abstraction of KMail backend<br />
* General offline mode (multiple online modes)<br />
<br />
<br />
== Meetings ==<br />
<br />
* Osnabrück 4 would be a great idea (Jan 06)<br />
* Alternative: Chemnitz (March 06)<br />
* Possibly: KDE-NL again<br />
* probably no need for further meetings this year<br />
<br />
<br />
== Alliances ==<br />
<br />
* raise awareness that KDE has strong commercial support<br />
* PR for existing collaborations<br />
* Joint announcements<br />
* Get KDE PIM supporters into KDE e.V.<br />
<br />
<br />
== Website ==<br />
<br />
* split into developer/community and user/promo site has succeeded.<br />
* Need artists (ask inside Novell?, Will)<br />
* Need webmaster (IRC? Users List?) (danimo)<br />
* Direction is ok <br />
<br />
<br />
== Artists ==<br />
<br />
* kde-artists doesn't seem to work for us<br />
* Oxygen for 4.0<br />
* Keep what we have for 3.5 (unless we can get something really better)<br />
<br />
<br />
== 3.6 ==<br />
<br />
* KitchenSync release beginning next year (with OpenSync 1.0)<br />
* SoC : GTD, maybe more<br />
* Translations?<br />
* Coordinate with other modules<br />
<br />
<br />
== 3.5. usability emergency surgery ==<br />
<br />
* Some small improvements (usability)<br />
** Resource selector improvements needed in KOrganizer and KAB<br />
* Talk to the usability people<br />
* Fix mailloss bug (Online IMAP)<br />
* Everyone: please look for things that are obviously horrible, by starting a session with a clean .kde/</div>Mahoutsukai