Projects/PIM/Akonadi/Meeting2009-04 - Revision history

Vkrause: Add blog and dot story links.

2009-04-10T08:14:21Z

Add blog and dot story links.

2009-04-05T07:54:34Z

‎Meeting Notes

2009-04-05T07:54:04Z

‎Agenda

2009-04-04T18:18:22Z

‎Meeting Notes

2009-04-04T09:19:48Z

‎Meeting Notes

2009-04-04T09:15:54Z

‎Agenda

2009-04-04T07:54:18Z

fix links

2009-04-04T07:51:29Z

small correction

2009-04-03T21:40:54Z

2009-04-03T12:44:35Z

‎Agenda

@@ Line 129: / Line 129: @@
 ** Clients have to re-expand the recurrence of the items in the selected time interval, which is acceptable (more or less constant for increasing calendar sizes)
 [[Category:Akonadi]]
 [[Category:PIM]]

@@ Line 129: / Line 129: @@
 ** Clients have to re-expand the recurrence of the items in the selected time interval, which is acceptable (more or less constant for increasing calendar sizes)
 [[Category:Akonadi]]
 [[Category:PIM]]

@@ Line 18: / Line 18: @@
 * Resolve the POP3 agent/resource design disagreement
 * Do we need to set some standards of compliance for names of Payload parts? Considering not all resources from third parties will use our stuff (KABC etc) we need to make sure they use the same names for payload parts.
 * Should Monitor be configurable to watch {un,}subscribed collections?
 * Do we need a way to know what payload parts are available to an item (or is it possible) or a bool Item::hasFullPayload()?
 === Friday ===
@@ Line 38: / Line 34: @@
 ** Should it be possible to link collections as well as items?
 ** Should it be possible to cascade virtual collections? (nepomuk tag trees say yes). This is possibly a non issue because there is actually nothing virtual about virtual collections. It could be a regular collection tree which happens to contain no real items and only links to items.
 === Saturday ===
@@ Line 45: / Line 44: @@
 * KAddressbook vs. KContactManager
 * KOrganizer porting
 === Sunday ===
 * GSoC selection
 == Meeting Notes ==

@@ Line 113: / Line 113: @@
 * Disadvantages:
 ** Slight overhead on the resource side
 {{improve|}}

← Older revision		Revision as of 09:19, 4 April 2009
Line 101:		Line 101:
	* Whether a user operation such as a move is permitted to/from the collection shall be determined by the permissions of collections (write/change/read-only).		* Whether a user operation such as a move is permitted to/from the collection shall be determined by the permissions of collections (write/change/read-only).

		+
		+	=== IMAP/Kolab resource design ===
		+
		+	* Use separate resources for IMAP and Kolab/Scalix
		+	* Implement Kolab/Scalix as proxy resources, which map IMAP source items to groupware items.
		+	* Advantages:
		+	** avoids duplication of IMAP resource code for Kolab/Scalix
		+	** separates Kolab/Scalix code from generic IMAP stuff
		+	** still allows access to the raw IMAP messages for testing/debugging
		+	** allows separate testing of Kolab code by eg. using a local maildir as source
		+	* Disadvantages:
		+	** Slight overhead on the resource side

	{{improve\|}}		{{improve\|}}

@@ Line 17: / Line 17: @@
 == Agenda ==
 * Resolve the POP3 agent/resource design disagreement
 * Progress on implementing move support in akonadi. ([http://thread.gmane.org/gmane.comp.kde.devel.pim/23754 thread])
 * Can we have a recursive version of contentMimeTypes? (needed by entityTreeModel and could make filtering more sensible)
@@ Line 43: / Line 29: @@
 * Investigate the Lionmail performance issue
 == Meeting Notes ==

@@ Line 53: / Line 53: @@
 === Akregator/Akonadi RSS resource (Dmitry) ===
-* See [[/Projects/PIM/RSS_framework_for_Akonadi|RSS framework for Akonadi]].
+* See [[Projects/PIM/RSS_framework_for_Akonadi|RSS framework for Akonadi]].
 * Dmitry wrote an RSS library for Akonadi
-* Dmitry pointed out a few problems he noticed when using Akonadi (already added to [[/Projects/PIM/Akonadi#Core|Akonadi TODO list]]):
+* Dmitry pointed out a few problems he noticed when using Akonadi (already added to [[Projects/PIM/Akonadi#Core|Akonadi TODO list]]):
 ** An ItemLinkJob was missing when he was working on his GSoC project (it's implemented now)
 ** Searching is missing.

@@ Line 46: / Line 46: @@
 == Meeting Notes ==
-* Lionmail speed problem: Don't download the entire Gmane server in the background helps with that ;-)
+=== Lion Mail (Sebastian) ===
 {{improve|}}

@@ Line 23: / Line 23: @@
 * Resolve the POP3 agent/resource design disagreement
 * User feedback
 * Mail part splitting
 * Searching
@@ Line 40: / Line 39: @@
 * Do we need a way to know what payload parts are available to an item (or is it possible) or a bool Item::hasFullPayload()?
 * Group photo
 == Meeting Notes ==