Re: Cyrus CalDAV design decision

2011-09-06 Thread Robert Mueller
(Resending to include cyrus-devel) > > At the moment, the storage format in use is iCalendar, being stored as > > RFC5322 messages. > > That sounds very much like what Kolab did in version 1. > > After trying to make this interoperate for several years it was given > up in favor of the Kolab XM

Re: MESSAGE quota resource implemention

2011-09-06 Thread Julien Coloos
Le 06/09/2011 19:48, Julien Coloos a écrit : Le 06/09/2011 10:23, Greg Banks a écrit : So I think we'll need another round, sorry :( Given that the annotations quota is broken and I'll be reimplementing it anyway, you may as well ignore QUOTA_ANNOTSTORAGE in all commits, and leave out the func

Re: MESSAGE quota resource implemention

2011-09-06 Thread Julien Coloos
Le 06/09/2011 10:23, Greg Banks a écrit : So I think we'll need another round, sorry :( Given that the annotations quota is broken and I'll be reimplementing it anyway, you may as well ignore QUOTA_ANNOTSTORAGE in all commits, and leave out the function annotatemore_computequota() for now. We'

Re: Cyrus CalDAV design decision

2011-09-06 Thread Jeroen van Meeuwen (Kolab Systems)
Ken Murchison wrote: > Bron Gondwana wrote: > > On Tue, Aug 23, 2011 at 02:44:46PM -0400, Dave McMurtrie wrote: > >> 3) Store DAV resources in a separate hierarchy like the DELETED > >> hierarchy. I think Ken and I initially liked this idea, but the > >> more we talk about it, the more it seems li

Re: Cyrus CalDAV design decision

2011-09-06 Thread Jeroen van Meeuwen (Kolab Systems)
Dave McMurtrie wrote: > Good day, > > Ken, Bron and I have had various disjointed conversations about where > CalDAV data should be stored. We're getting to a point where we really > need to finalize that design decision, so I'm soliciting feedback here. > > The current Cyrus CalDAV code stores

Re: Subject : git best practices

2011-09-06 Thread Jeroen van Meeuwen (Kolab Systems)
Olivier ROLAND wrote: > 2011/8/19 Henrique de Moraes Holschuh : > > IMHO, if you're going to come up with rules for that, better do as it is > > done in the Linux kernel or in git itself. > > > > The rules are: > > * detailed changelogs on every commit > > * only cleaned up commits are sen

Re: MESSAGE quota resource implemention

2011-09-06 Thread Greg Banks
On 06/09/11 02:55, Julien Coloos wrote: > Le 05/09/2011 06:12, Greg Banks a écrit : >> >> Julien, I think we agreed on everything else, right? I'm looking >> forward to your next iteration. > After picking your 'uquota_t removal' commit, I also removed it on my > end, and changed the code accordin