On Nov 25, 2009, at 12:52 AM, Peter Mogensen wrote:

I've been looking into the state of Twisted and CalendarServer and I'm a little confused about the roadmap.

Twisted developers write: "Twisted Web 2 was (emphasis past tense!) a complete re-write of Twisted Web, with a new HTTP/1.1 implementation and a new resource publishing model. We decided this was a mistake and development focus has shifted to porting the best parts of Twisted Web 2 back to Twisted Web where existing applications will benefit from them."

But CalendarServer relies heavily on Web2 features (DAV/ACls), so it would seem that unless there will be a 1-1 migrate path from Web2 to never versions of Twisted.web for these features, then CalendarServer is stuck on an unmaintained branch of Twisted.

In other places people mention that there's plan to merge the dav-take-two-3081-4 branch back onto twisted trunk as soon as it's ready, but from the above that seem like it's an old abandoned plan?

Could anyone elaborate on the plans for Twisted in CalendarServer?

Geez, you ask hard questions. :-) Twisted plans to add all of the functionality from web2 back to web. At that point, we can look at implementing the DAV stuff there (with the benefit of hindsight, I can think of many ways that implementation could have been better), then rebuild CalDAV there (again, hindsight will help). That's a pretty long-term plan. Medium-term... not sure. I'm open to ideas. One thing we're considering is pulling web2.dav into the CalendarServer project so it's not on a dead branch in Twisted, but that's really just a tactical move for our convenience. Glyph (founder of Twisted, now on my team at Apple) is putting a lot of thought here, so it's not being ignored, but it's going to take some time to sort through it. -wsv