r4 - 14 Jun 2007 - 10:48:25 - MimiYinYou are here: OSAF >  Journal Web  >  ContributorNotes > PriscillaChungNotes > MtgNotesPlanningZeroDotThree

Meeting Notes: Scooby Planning 0.3

  • Currently there are concerns about how Chandler/Cosmo sharing will affect Scooby, see discussions on the dev list.

We've isolated two potiential candidates for the Target User:

  1. 'Individual Contribuor' user – Web access to participate in collaboration workflows without having to adopt a desktop client. See target user definitions in spreadsheet.
  2. Remote access for Chandler users - People using Chandler to view their calendar on the web.

  • The decision is to tackle target user No.1 first – The 'Individual Contribuor'.
  • What is missing that is presenting a Casual Collaborator user?

How should it be phased? (Suggested not set in stone)

  1. Just calendar --> alpha
  2. Calendar + stuff later -->beta

Usage scenario for 0.3 the 'Individual Contributor' user

  • The 'Individual Contributor' user wants to update their PTO on the office calendar.

Need to come up with storyboards/design session for the following scenarios

  • In addition if you receive a link to edit on Scooby, it would be nice to just show you the event detail
  • Chandler event --> notification--> email w/ attachement, the link is a ticket to the event item issue URL for your item
  • Editing items-->event url emailing -->Scooby needs a view to support this dependency: Scooby understanding stamps
  • Build ability to subscribe URL passing around URL w/out events.

Project Timeline

  • End of July/Early August --> Architecture for sharing would ideally be in place (TBD)
  • During that time front end devlopment can still build widgets that are not related to
  • Beta is 12 months
  • Tha plan is to have beta done in February.

Definition of phasing

  • Alpha - experimentally usable Casual Collaborator user
  • Beta - exp. usable remote access Chandler users
  • 1.0 - usable for both.
  • Perhaps by 0.5 - users can subscribe the RSS feed, but not all the edit is working.
  • 0.3 plan of record - work done on users

Three usage scenarios

  1. A docent co-ordinator uses email/phone calls to schedule timeslots for the docents and once she has the calendar set up, you are using Scooby to view the information-publish set of information (ie. tasks)
  2. Using Scooby to collaborate one item or collection
  3. Remote access for Chandler

Please Note: Individual Contributor target user may be able to update his PTO, but sharing will not work when more then one user is updating their PTO. Need UI work, that the page is locked etc. ie. Wiki pages. In a small group collaboration this may be fine for now. Though this issues will be addressed again in the future.

-- PriscillaChung - 23 May 2006

  • Casual Collaborator Diagram:

Casual Collaborator Diagram

toggleopenShow attachmentstogglecloseHide attachments
Topic attachments
I Attachment Action Size Date Who Comment
gifgif casualContDiagram.gif manage 16.4 K 24 May 2006 - 18:03 PriscillaChung Casual Collaborator Diagram
gifgif casualCollbDiagram.gif manage 16.4 K 25 May 2006 - 10:48 PriscillaChung Casual Collaborator Diagram
Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r4 < r3 < r2 < 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.