windows-nt/Source/XPSP1/NT/windows/winstate/doc/email/odysseydsm scenarios mtg wbshah.rtf
2020-09-26 16:20:57 +08:00

23 lines
2.1 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}{\f1\fnil\fcharset2 Symbol;}}
{\colortbl ;\red0\green0\blue0;\red0\green0\blue128;}
\viewkind4\uc1\pard\fi-1800\li1800\tx1800\cf1\b\f0\fs20 From:\b0\tab Chris Steck (Exchange)\par
\b Sent:\b0\tab Monday, December 20, 1999 6:10 PM\par
\b To:\b0\tab Bharat Shah (NT) (Exchange); Alex Armanasu (Exchange)\par
\b Cc:\b0\tab Michele Freed (Exchange); Murthy Srinivas (Exchange)\par
\b Subject:\b0\tab OdysseyDSM Scenarios mtg w/BShah\par
\pard\cf0 Today, Alex and I met with Bharat to review the DSM scenarios we want to support in Odyssey.\par
\par
Most of the time was spent walking through the doc, and Bharat agreed with the scenarios and priorities pretty much as is, ( the only scenario addendum was to encompass managing the storage/retrieval of persona from multiple concurrent locations.) and the resultant discussion surrounded the following issues and next steps:\par
\par
\b Issues \par
\pard{\pntext\f1\'B7\tab}{\*\pn\pnlvlblt\pnf1\pnindent0{\pntxtb\'B7}}\fi-380\li380\b0 How does the reorg of the consumer migration tool group into Deb's org affect our priorities?\cf2\b \cf0\b0\par
{\pntext\f1\'B7\tab}How does the merging of Neptune and Odyssey (do we have a name for this yet?) into a single release affect our priorities as a business unit and thusly impact our DSM scenarios? \par
\pard\par
\b Next Steps\b0\par
\pard{\pntext\f1\'B7\tab}{\*\pn\pnlvlblt\pnf1\pnindent0{\pntxtb\'B7}}\fi-380\li380 Alex will deliver architecture and dev estimates based on supporting these scenarios. These docs will contrast the approaches of modifying the stand-alone 1.0 DSM tool vs. full integration into OS as well as any hybrid approaches. (First week of January)\par
{\pntext\f1\'B7\tab}Chris will outline the functional requirements by 12/27, and submit for review in email.\par
{\pntext\f1\'B7\tab}Chris to gather 5.0 tool alpha status to ensure we are delivering the right settings/features\par
{\pntext\f1\'B7\tab}Upper Management to help resolve the issues above\par
\pard\fi-1800\li1800\tx1800\cf1\par
}