r1 - 13 Apr 2006 - 11:20:43 - KatieCappsParlanteYou are here: OSAF >  Journal Web  >  MeetingNotes > StaffMeetingNotes > StaffMeetingNotes20060413

Staff meeting 13 April 2006

Agenda

  • Scooby 0.2 presentation
  • Scooby demo
  • Chandler demo

Notes

  • Scooby 0.2
    • Target users have not been finalized
    • Possible target users:
      • chandler users accessing calendar from the web
      • non chandler users who want to access a calendar from a chandler user
      • small working groups/colleges who need to publish calendars
    • Possible usage scenarios:
      • student activities calendar
    • 0.2 tenets
      • developer release, not a usable release
      • continue down the original 0.1 plan
      • show progress from 0.1 to raise excitement in developer community
      • allow chandler users to view the calendars they've published
      • continue performance, stability and compatibility over 0.1
    • Will do
      • easy viewing of chandler calendars on scooby
      • focus on read-only use cases
      • will have more visual consistency with Chandler and show the beginnings of a high quality consumer application
    • Won't do
      • calendar overlays
      • while editing is functional, not focusing on editing use cases
      • complete polished look and feel -- visual design will change over time
    • Future release plans
      • infrastructure mashups (webapp hybrid)
      • public calendar - being able to display read only calendar
        • view play rehearsals via a simple url w/out having a user account
      • some development for future release will commence, but will not be part of the scooby 0.2 release
    • Feature sets
      • account/viewing/creating
      • navigation
      • calendar canvas
        • visual tweaks to be consistent with chandler
        • reconciliation of the same event on multiple calendars
        • overlapping events within the same calendar
      • user preferences
      • infrastructure (caldav4j, skinning for ui templates)
      • coding standards
      • testing
    • Next steps
      • Kickoff date: April 10
      • 6 weeks of development, 2 weeks qa, documentation/refactoring
      • open issues on design list [scooby]
      • setting up time in design discussions to discuss some open issues
      • continue with spec writing and add visuals
    • ScoobyZeroDotTwo

  • Scooby demo: overlapping events
    • Re-used algorithm from Chandler, saving some time

  • Scooby 0.2 release will be important for affecting perception, demonstrate the ecosystem functioning
  • Google calendar
    • One distinguishing feature of osaf ecosystem from google: google owns the data
    • We own the data as well, running cosmo-demo
    • Someone could run their own server, but only if we put some work into making this work well
  • Pull together in one place: collect info about the cl2 story
    • presentation at staff meeting next week?

  • Chandler demo: drag and drop
    • email onto calendar -- item stamped as both email and event
    • outlook to chandler (requires various "stop sucking" prefs, like "internet standards")
      • special case UTC? if timezones are off outlook data is messed up
    • all day to timed canvas
    • bear suggests: dragging items from a web page with hCalendar to chandler
    • bumps in the road: different clients prevent different obstacles
    • bcm points out: integrate with web, make it work with scooby
    • ted asks: what about the mac? jeffrey: thats next on my plate

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.