[Scooby] [Proposal] Prioritizing features for Scooby 0.2

[Priscilla Chung]

Part of planning the features in 0.2 we need to think of the must have, 
should have and could have.

+ Must have - must complete all of these features for the release to 
achieve it's goals
+ Should have - feature that should be worked on if time allows in the 
schedule
+ Could have - not hard to do, time allows, this would be a 'nice to have'.

So here is the first pass at proposing the features based on two lists:

+ The feature 'out' list in the original 0.1 release: 
http://wiki.osafoundation.org/bin/view/Journal/ScoobyPlanning20060113
+ Wish list: 
http://wiki.osafoundation.org/bin/view/Journal/Scooby0_2Wishlist

*Next steps:*
All of these features listed below will be logged into bugzilla as 
enhancements. Then each item will be given a SWAG if it's 'in' for 0.2 
or 'out' for a later future release date.

Copy of this list on the wiki: 
http://wiki.osafoundation.org/bin/view/Journal/FirstDraftProposalPrioritizingFeaturesZeroDotTwo

-Priscilla
*Please direct all reply to the scooby list - thank you!!

---
*Must haves: (To meet Target User Release, but may not meet 0.2 time frame)
*Note: Although some features may take longer to build within the 0.2 
time frame, it will still be in the queue and roll over into the next 
release cycle. A SWAG will be determined at a later date.

Account Viewing/Creation
+ To view the User's (Chandler) calendar on Cosmo-demo. (Open issue. See 
below.)
+ Make it simple process for an end-user to create an account and login 
to a Scooby session
+ Specify a URL for cosmo, as opposed to separate properties for 
hostname, port, etc.

Navigation
+ Day view
+ Multiple Calendars - Show the "display name" instead of the path name 
(no calendar overlay, but be able to switch between the different calendars)
+ Basic mini calendar (will define in spec as to the basic functionality 
to meet target user)
+ Sidebar - Should the user be able to view not only their calendar, but 
all the subscription calendar once logged onto Scooby? (Open issue. See 
below.)

Managing events
+ Creation of editing of recurring events
+ Special Chandler event types to display correctly in Scooby (@time, 
anytime events)
+ Creation and display of alarms
+ Creation or display of event status (confirmed, tentative, fyi)

Calendar canvas interactions
+ Overlapping events to be displayed correctly (ie. staggered as in 
Chandler or at least side by side view)
+ Reconciliation of the "same event" on "multiple calendars" (Open 
issue. See below.)
+ Setting timezone for the calendar  (Open issue. See below)

---
*Should haves:*
Navigation
+ Jump-to-date

Calendar canvas interactions
+ Time line on the left
+ Visual tweaks consistent to Chandler (ie. Scooby logo, consistent icon 
set, small aesthetics tweaks--will break down in bugzilla)
+ Public calendar - Be able to display Read-Only calendars, e.g. a 
public calendar for play rehearsals via a simple URL without the user 
having to have an account
*
*Infrastructure
+ CalDAV4j -

        * Figure out the real name of this project (even if it's CalDAV4j)
        * Separate CalDAVCalendarCollection^?
          <http://wiki.osafoundation.org/bin/edit/Journal/CalDAVCalendarCollection?topicparent=Journal.Scooby0_2Wishlist>
          API into a DAO and a manager
        * Extend the Slide Client WebDAV collection API so that it can
          return CalDAVCalendarCollections^?
          <http://wiki.osafoundation.org/bin/edit/Journal/CalDAVCalendarCollections?topicparent=Journal.Scooby0_2Wishlist>
          and find calendar collections that are within it
        * Add caching in various areas
              o cache Event UID --> Resource Path
              o cache icalendar resources w/ etags
        * Add Ticket Support
        * Free busy reports
        * make sure previous work is caught up to the latest CalDAV spec

Testing*
*+ Integrate JS unit tests into Maven build process
+ Write lots more unit tests - especially for CalDAV4j and scooby <==> 
icalendar conversion utils
*
*Code Standards
+ Have some sort of Coding standards for Java and JavaScript
+ Organize JS files into folders to resemble "packages" in Java

---
*Could have/Nice to have*
Navigation
+ Month view

Managing calendars
+ Publish/subscribe workflows - no dialogs to type in urls
+ Import/export features
+ Setting timezones on events(Open issue. See below.)

Internationalization
+ Allow user to choose other languages from those installed.

Security
+ Implement finer grained security for RPC calls - right now only auth'd 
users can get in, but maybe we want anonymous users to be able to do 
SOME webservices, like AUTH

CMP
+ How about a CMP client library for talking to cosmo?

---
*'Out' list
*+ No calendar overlays (color etc.)*
*+ Dragging and droppings events to add them to a different calendar

---
*Some 'open issues' that needs to be addressed:*

*Editing*

    * How much editing is really needed for Scooby for meet target users
      release?
    * If the event lives on multiple calendars, should users be able to
      remove events on other calendars when refreshed? Perhaps for
      target user release, we not trying to support a fully functional
      editing on Scooby.
    * Only concerned with read scenarios. Write scenarios don't need to
      work?
    * Reconciliation of the "same event" on "multiple calendars"? (Need
      clarification?)

*Viewing your (Chandler) calendar on Scooby*

    * Is Scooby intended to be a web version of Chandler -- for now?
    * To view the User's (Chandler) calendar on Cosmo-demo. (Will the
      idea of OSAF as a 'service' need to be introduced for target user
      release?)
    * Would a user be able to view all the collections once logged on to
      Scooby or would the user be able to select the collections they
      want to have published to Scooby?

*Timezones*

    * Should users be able to change the default timezone on Scooby? If
      this release is only usable for read-only scenarios then this may
      not be needed as we're mostly focused on display issues?
    * Let the users set a default timezone
    * Be able to set the timezone on events

**

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/scooby-dev/attachments/20060312/2a675c51/attachment.htm