Hi Jared,

Thanks for writing this up. I'm replying on the Design List as I think this is really about Planning and Usability/Design.

Many of these items are on the 1.0 List for Cosmo: http:// chandlerproject.org/Notes/OneDotZeroServerBugs

See below for details.

It seems like the big picture idea here is that it is very important Chandler Hub performs well when users show up to 'kick the tires' which includes implementing features that move us closer to satisfying standalone users. At the same time, we need to make sure that we don't lose potential casual collaborators by smoothing out the sign-up + subscribe workflow.

Is that in-line with your motivations for this list Jared?

Mimi

On Oct 29, 2007, at 2:46 PM, Jared Rhine wrote:

My overall current list looks like:

Fundamental standalone operations
  - Create a new collection (and delete)
Bug#8498 Add/Delete a collection (not shared)

  - Share a collection (create tickets and send read-write to friend)
P1 Bug#8509 Rationalize ticket and URL UI
P1 Bug#10261 Generate ticket-URL for 'my' collections on Chandler Hub
P1 Bug#8499 Subscribe/unsubscribe to a collection on web UI

  - Search titles/descriptions to narrow the dashboard view
Bug#8764 Search in the web ui

Signup/login foibles
  - Log person into PIM directly from activation

Is there already a bug for this?

  - Improve experience when double-clicking on activation email

Bug#10431 Better error message when user clicks on activate account link 2x

  - Get login page down to couple hundred-millisecond load

Is there already a bug for this?

  - ie7 ssl logins bz 10682
  - Make list/calendar switch much more obvious

I've logged a superbug to process Floss Usability feedback: Bug# 11270

- Shorten minimum required password length to 4

Is there already a bug for this?

Feel like a modern web app
  - Auto-default date entry to current at least, then improve date
    entry on multiple dimensions

Bug#10962 Set start and end date to today when stamping an item as an event


  - :443 drop (activation emails, collection detail dialog,forgot
    password emails, atom discovery URLs)

??

  - Login page served in under 250ms

Is there already a bug for this?

  - Make description field readable: use an auto-expanding field

I think there were implementation issues here. Should this be a cosmo- dev discussion? I've logged a bug: Bug#
11271

  - when clicked, or support detachment.

??

  - Save username/password in login box

As in, remember me? Is there already a bug for this?

  - Revisit autosave

Bug#8397 Auto save in event details area


  - Tune "waiting" operations (bz 10238)
  - Add small refresh button (bz 10160)

I'm not sure about this one. How often are we pulling stuff down from the server?


Open service features
  - Need feature to support closing a user account (user reported)
  - Network backup and restore

Interop
- As usage demands (nothing specifically being tracked for Hub right now)

My suggestion for short-list, across these areas is:

Suggested priority
  - Create a new collection
  - Share a collection
  - :443 drop from public URLs when scheme is https
  - Log user in directly from activation
  - IE7 SSL logins (bz 10682)

I wanted to acknowledge that I've had to edit this list a couple of times because the Cosmo team is moving fast and working in substantial improvements, with important stuff first (overlays, month view, etc). Good chunks of stuff that's important to me has already gotten fixed! So thanks to the teams for all the work!

-- Jared
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

Reply via email to