Brief overview of areas for which we need to start the design-eng dialog (ordered in priority)
1. item sharing/item versioning
2. collection sharing (subscriber status)
3. collection design and filtering (deletion semantics)
4. IMAP folder reconciliation
Identify engineering point people for top 3 items
Agree on a meeting schedule for the next 2-3 weeks for the 2 top priorities. (use 3rd as backup if some resources become critical path for 0.4 and are unavailable)
Discussion of next steps
Item versioning
huge cost for development
versioning is mos of work for couple of developers (BIG)
item sharing is possible
cases for item versioning
-> item and collection sharing
-> conflict resolution
-> editing emails
-> no current safeguards on people making changes
-> undo might be a solution
Next Steps: "Versioning"
Design will puts together a concise compilation of information that has now been assembled (CL)
Forward to Katie and Lisa for review and schedule a brief meeting to discuss.
Collection Sharing (Not BIG)
subscriber status - 2 week item development
automatic sync - 2-6 weeks to deal with polling (threading issues)
what are the overall Kibble goals? (CL)
how can we stage this over the next few releases
ACL for collection sharing
sharing a subset of a collection.
Next Steps: "Collection Sharing"
put together initial workflows for next phases of sharing (SM)
Katie and Lisa will be point people to talk to.
Deletion Semantics
first pass at design goals
then iterate on that
-> deletion and undeleting
-> when do you garbage collect something
-> what is the UI workflow to move to trash, out of trash when it's gone
Next Steps: "Deletion Semantics"
design team needs to spec out the deletion semantics then Katie will review and decide who needs to be brought into the discussion.
Sharing a Filtered Collection:
-> separate discussion
-> supposed to be a followup discussion
Katie and Lisa will identify who is going to own item collections.
Next Steps: "Sharing Filtered Collections"
meeting with John and Ted and Katie (Lisa)
IMAP folder reconciliation
have a bucket list of features that we want to have
need Brian/Lisa to scope these
the next step is that someone prepare a proposal
what are the gui folders (imap mental model)?
how to store items coming from other folder - including the inbox.
nested imap folders are considered flat.
what it means to flatten imap folders - still talk about the requirements
cost out what is required with out brian's input
Lisa will review IMAP mental model and comment on what's missing etc.
look at the features and do guesses without individual engineers
Next Steps: "IMAP Folders"
Lisa will read the sidebar spec and comment on the IMAP mental model.
followup with a meeting with Chao, Lisa to discuss
Next meeting scheduleed for 1:00pm Sept 9th - Agenda TBD