Changeset 952077b


Ignore:
Timestamp:
Mar 23, 2011, 1:22:35 AM (15 years ago)
Author:
Alex Dehnert <adehnert@…>
Branches:
master, fysm-4-1, space-access, stable, stage, test-hooks
Children:
31e4eaa
Parents:
7fcc82e
git-author:
Alex Dehnert <adehnert@…> (03/23/11 01:22:30)
git-committer:
Alex Dehnert <adehnert@…> (03/23/11 01:22:35)
Message:

Design: punt attachments, fix spelling

(This is the email actually sent.)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • design/stakeholders/2011-03-followup.txt

    r7fcc82e r952077b  
    44CC: asa-db@mit.edu, asa-exec@mit.edu
    55Reply-To: asa-db@mit.edu
    6 Attachment: /mit/asa/Scripts/django/asa-db/design/notes.txt
    7 Attachment: /mit/asa/Scripts/django/asa-db/design/stakeholders/pre/responses.txt
    86
    97
    108Hi again,
    119
    12 A couple weeks ago, ASA, SAO, CAC, and DSL met to discuss possible plans for organizing development of the ASA Database. At the meeting it became clear that we lacked information abotu what the stakeholders needed out of a new Database development process. This is more preliminary than the specific features that each of our groups said they currently used and wanted from the Database (the topic of my December e-mail), since the sense of the meeting participants was that we needed to know more about how each stakeholder wants to interact with continued development of the ASA Database.
     10A couple weeks ago, ASA, SAO, CAC, and DSL met to discuss possible plans for organizing development of the ASA Database. At the meeting it became clear that we lacked information about what the stakeholders needed out of a new Database development process. This is more preliminary than the specific features that each of our groups said they currently used and wanted from the Database (the topic of my December e-mail), since the sense of the meeting participants was that we needed to know more about how each stakeholder wants to interact with continued development of the ASA Database.
    1311
    1412Therefore, I'd like to know:
Note: See TracChangeset for help on using the changeset viewer.