4 areas of work:

1. UI
   • Getting at the ticket-URLs
     • A new dialog box, and hopefully ability to copy URLs to clipboard automatically
   • Manually subscribing to a collection in which a URL has been provided out-of-band
2. Sharing layer
   • Some ticket integration
     • The Share object probably is where the ticket URLs get stored (?)
   • Merging
     • Look at different ways to approach this, possibly using the repository merge facility
3. Networking layer
   • Finish transition to new library
   • Handle ticket requesting and use
   • Make sure we use ETAG "if-match" headers appropriately to prevent overwriting data
4. Server
   • Handle ticket creation requests
   • Honor URLs with tickets

Questions:

• Synchronous or Async/background?
  • Goal is for async
• Do we support both ticket-based and non-ticket-based sharing?
  • Yes -- use tickets on servers that provide them