What are we trying to solve with a Shared Documents Model for CSS?
Anne's Framing Questions
Panel |
---|
In an email from June 27, 2006, Anne reminded us:
|
...
Existing Conditions...
Our default approach to collaborative work seems to be:
...
|
|
---|---|
Operational Plan. | Now a word document of mostly bulleted text with a table or two. For fun, this is the is a Wikified version of the draft FY07 CSS Operational Plan Compare this version to the one in scripts.mit.edu -- http://scripts.mit.edu/~support/wiki/index.php?title=June_26%2C_2006_version |
Quarterly Reports |
|
| Generated on a quarterly basis. |
Meeting Schedule, Agendas, Outcomes | Intermittently used as a formal work planning modus operandi within CSS. |
Process Documentation |
|
Resource Allocation Model | Currently maintained on sparkler1 as the official copy, with the working master on Rob's laptop. |
Which technologies are likely to be best for what?
Confidentiality is one forcing factor. Documents with sensitive data need to be closely protected. We need to be able to have documents locked down so that as few as three people only are able to view and update.
...