• Matt showed off latest changes to http://www.fleegix.org/demo/scooby1.html -- snap-to-grid
• work on what happens when you resize event to zero minutes...
• swap selected color with not-selected color
• add border to edges
• Next step to do overlapping events (big challenge)

Interop issues

• Currently developing on Mozilla with work on IE ongoing -- can't use in Safari
• Need to invest early in adding support for browsers other than Mozilla/IE -- otherwise complicated work like overlapping events might have to be completely redone at greater expense later
• Note that safari only allows GET and POST
  • could put the "actual method" in the URL
  • Some clients don't support adding headers either!!
• Brian proposes that we don't do anything but GET and POST initially anyway -- not try to support CalDAV directly from the browser driven by
• Discussion of meaning of figures on ScoobyBrowserSupport
• Straw-man decision: make sure that the initial calendar/event layout logic works with Safari; do initial development work on all three major browsers. Later when we know how much time Matt actually spends supporting Safari, we can decide whether to cut that (or find volunteers??)
• Matt will need to get Tiger in order to get Safari 2.0.

Cosmo-demo, Cosmo-qa, and upgrading in synch with Chandler

• what versions of Chandler interoperate with different versions of Cosmo?
• for now (while development of CalDAV on each side is so volatile) we may have to keep upgrades in lock-step -- e.g. we may have to upgrade cosmo-demo and cosmo-qa to 0.3-2 at the same time people start using Chandler 0.6 against those servers
• Next phase -- BCM will get "ahead" of Chandler and implement features that will be deployed to Cosmo in advance of Chandler needing them
• Cosmo-demo gets upgraded at release points (not just dot releases but also "dash releases")
• Data retention problem right now doing upgrades of cosmo-- relatively soon we need to avoid blowing away all the cosmo data
• IT can take over cosmo-qa and manage upgrades

Cosmo release upcoming

• Release 0.2 will be next week (no 0.2-5 milestone expected)

Issue tracking

• What do we do when we find an issue with Chandler operating on Cosmo?
• Enter a bug in Chandler first unless we're certain it's an issue with Cosmo
• If Morgen or Grant determines that it really is a cosmo bug, they can open a cosmo bug
• Jared asks that Cosmo bugs make it clear which machine and which version the bug was found on

Hosting service -- publicity

• Still a lot of non-agreement about what to say about the service
• can be discussed internally
• The Chandler M5 report card won't mention the service because that report card will be disseminated
• We don't know if this is in Pieter's list of issues

Calconnect

• BCM did some pre-testing - we ought to do pretty well
• Calconnect clients will hit BCM's desktop...
• Jared has issues with Calconnect and address assignment...

Subversion

• Scooby is currently checked into Matt's sandbox in SVN
• When do we move it out of Matt's sandbox?
• advantages of Matt's sandbox: can be half-finished
• advantages of a normal project: more obvious to other people curious about the code
• Matt will work with Bear on this...