Notes from talking to Anthony

Interacting with Python community

• Who is following Python discussion lists?
• PyCon participation
• Splinter off projects that can be used by community
• Personal goals along lines of "what have you done for the community lately"
• Read up on Python style guide
• Consider making an IMAP client library into a separate open package
  • Start by getting something basically working and then make open
  • See if people help you finish your work (but don't count on it)
• Generally, rather than expect people to contribute to "Chandler", break down into more manageable chunks like an IMAP client library that people can get a handle on and use more easily.

Parcel ideas

• Parcels should be able to call each others as APIs
• Easy ways to dynamically load parcels, so that a developer working on a parcel doesn't have to restart Chandler constantly
• Parcels don't have to have UIs

Libraries

• Twisted may soon include Rendezvous support
• Core Python IMAP support is very basic, low-level
• Recommends writing and distributing own IMAP client library
• Next Python alpha possibly July

Notes from reviewing sharing use cases with Chao

Content Model TODO: Add information about "Conversation" element

• Every shared Content Item has a Conversation item.
• Unshared Content Items won't generally show the conversation even if there used to be one.
• The Conversation item can get appended to by any user sharing the parent item
• How do we replicate this? Does a Conversation have multiple Message items with timestamps? Or is it just plain text concatenation?

Sharing Protocol problem:

• We need to handle the case where B shares their calendar, A adds an item to B's calendar and the same item to A's own calendar, however A's calendar is never shared.
• Either A creates a new event in B's calendar then creates a binding in their own calendar, or vice versa -- either one should work.
• If B stops sharing B's calendar, then A can no longer see the event or anything else in B's calendar. However, A still has a copy of the item and a binding into A's own calendar.
• This may show the need for independent UUIDs in different repositories, because the next move may be for A to share A's calendar, and B replicates it. Wouldn't B be surprised to see an event that B already had!

Email invitations to sharing:

• We need to design how an email will contain an invitation to join a sharing circle. Headers? Body magic? What content does it contain?

Sharing Circles:

• I suspect there should be both open and closed sharing circles

-- LisaDusseault - 08 Apr 2004