[Kolab-devel] zpush: name of the annotation

Bernhard Reiter bernhard at intevation.de
Thu Mar 25 18:21:00 CET 2010


Am Donnerstag, 25. März 2010 17:41:21 schrieb Georg C. F. Greve:
> On Thursday 25 March 2010 16:31:12 Bernhard Reiter wrote:
> > Having no annotation on the folder or not having the id of the device in
> > question in the annotation will lead to a folder not being synced to that
> > device.
>
> I don't think that's a very good idea.
>
> The most common use case would be for users to set the folders that would
> be synced by default with all their phones. The second most common use case
> would be to define deviations from that for one or two particular phones.

You did agree to the notion before that the default cannot be YES:

Am Montag, 22. März 2010 13:34:43 schrieb Georg C. F. Greve:
> > Note that anyone could just give you an ACL on a folder, so if the
> > default is "yes", this means I can just spam your appointments by giving
> > you a folder that immedeately gets synced. So a default of NO seems to be
> > the better solution. Or something like YES for folders where in my
> > personal namespace and NO for all others.
>
> Agreed.

Am Donnerstag, 25. März 2010 17:41:21 schrieb Georg C. F. Greve:
> Having to turn off the default for a folder, in order to then turn it on
> for all phones that are supposed to sync, only to exclude the one that you
> wanted to exlude in the first place, seems a rather circuitous route.

Then we can do it the other ways around:
Existance of the annotation means: The folder can get synced,
unless the device is listed as explicit value.

You still need to enable sync then, though, but you only need to enable it 
once for a folder and it will work with all devices.

> And not syncing anything by default is likely to be perceived as a bug, and
> would provide rather maintenance intensive (and thus costly) support for
> all those users who just want to sync their standard folders.

What your standard folders are cannot be determined that easily.
There are the default folders of each account, but users might already depend 
on folders from group accounts, anonymous accounts or simply other users.
You must enable those to get a good experience, and they cannot be 
automatically enabled as YES.

So I guess one good solution is to have an activation function in the clients, 
especially in the web client. So people will have to configure the device and 
then use the activation function in their client, this one will ask list all 
folders they currently have and will ask if it should set the sync annotation 
on them.

As we need this anyway, we could keep things simple at that point and do not 
introduce another role for default folders or the folders that are under the 
namespace of the first primary user and all that.

Bernhard



-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Deputy Coordinator Germany: fsfe.org. Board member: www.kolabsys.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20100325/23c67d1e/attachment.sig>


More information about the devel mailing list