• Bear working on python scripts that call Zanshin library
• Bear has them real close to being available to the public.
• trying to coordinate these to work with memory profiler

Cosmo Performance Tuning/Enhanements

• Storage needs down 1 order of magnitude due to use of Derby and not storing Calendar metadata (just indexing them)
• These changes have been merged to trunk
• Performance roughly 2x as fast

Problem with Cosmo connections timing out

• Don't know much yet - could be due to proxies

Scooby Design

• Mimi has mock ups of new design for bottom detail view
• Will save on horizontal space
• Popup philosophy - great if ephemeral(and modal?) - more permanent popups are bad as they obscure.

*Scooby/Cosmo Account Info Storage/Authentication

• For the future, it will be a requirement to get user info from and authenticate using stuff besides Cosmo - i.e. Shibboleth, LDAP, etc.
• Right now just Cosmo is fine, but we need to write up some use cases for the different scenarious
• As far as storing cal data for 0.1:
  • Read write cosmo is a requirement
  • Bookmark other calendars on other servers nice to have, and probably pretty doable.

Ops

• Todd delivered regression tests for get and puts in Foxmarks very rapidly
• Foxmarks - going live we'll need to wipe repo when we go to .2 --> .3. Any way to avoid?
  • bcm to create a one off import/export tool
• Jared needs more heap memory by default in cosmoctl
• bcm to increase the memory slightly, but can be overridden by environment variables (he doesn't want to make assumptions about the environments that cosmo will be running on, so doesn't want to increase mem too much.)