source: design/notes.txt @ 6aa3517

space-accessstablestagetest-hooks
Last change on this file since 6aa3517 was 0089335, checked in by Alex Dehnert <adehnert@…>, 14 years ago

Notes from stakeholder meeting

  • Property mode set to 100644
File size: 3.9 KB
Line 
1Based on meeting on 2010-12-02.
2Attendees: Alex Dehnert (adehnert) (notes-taker) and Rachel Meyer (remeyer)
3
4Revised at stakeholder meeting 2011-04-15.
5Attendees:
6    * ASA: Alex Dehnert, Rachel Meyer, Geoffrey Thomas
7    * SAO: Leah Flynn, Kerri Mills
8    * CAC: Phil Walsh, Jennifer Smith
9
10* Categories as a many-to-many relationship is nice
11    * Need to think some more about what categories are reasonable
12    * Probably want to occassionally go yell at people about having too many
13* Officer-y fields / associating people with groups
14    * Multiple presidents
15    * Multiple treasurers
16    * Add some field of "people we trust enough for office access control, mailbox control, etc."
17    * Financial signatories
18    * Reservation signatories
19    * Set a standard cap for each of these fields, but allow increasing it
20        * Probably: ASA can exceed the cap when adding, not "ASA can increase the self-service cap"
21* Self-service enhancements
22    * Allow self-service officer's list updating
23        * Send mail to ASA Exec
24        * Send mail to GSC Funding Board or Finboard, as applicable
25    * Self-service constitution updating?
26        * Update mail?
27* Send mail on updates?
28    * Signatory updates to the groups?
29    * Treasurer updates to Kerri?
30    * CAC wants:
31        * new/derecognized group emails
32        * (maybe) space assignment changes
33        * NOT signatory changes
34    * SAO wants:
35        * Financial signatory, president, treasurer change emails
36        * New/derecognized group emails
37* Associating notes with groups
38    * Groups leaving notes for themselves   (notes by group)
39    * ASA Exec leaving notes for groups     (notes to group)
40    * ASA/SAO for funding board             (funding notes)
41    * ASA internal notes                    (ASA notes)
42* Funding board access
43    * Viewing funding status
44    * Viewing account numbers
45    * Membership numbers
46    * Basically everything but notes
47* Office access
48    * Do this per-space
49    * Assign each space a space category (e.g., storage, office, etc.)
50        * Shared office / office --- script to run occasionally to auto-update?
51    * Should include ASA and non-ASA space
52    * Cap number of people with access from a group by space category
53    * Office ACL?
54* Make sure the status options are generally changeable
55    * Status: Active, Suspended, Derecognized
56    * Class: various, editable by us
57        * Dorm/FSILG
58        * Standard
59        * Sponsored
60        * PSC?
61        * "unrecognized" / "sponsored"
62            * cover things like a capella Exec (which has space), dorms (which have signatories), subgroups (which have accounts and signatories), etc.
63            * Might want a "sponsor" or "affiliation" field
64* Indicate what mode you're in
65    * Nice, but not needed
66* What info is available
67    * MIT-public
68        * Name
69        * Acronym
70        * Recognition date
71        * Last updated date
72        * Officer email
73        * Locker name
74        * President / treasurer / financial signatories / people who can update record [[stakeholders were fine with this being MIT-public]]
75        * Description
76        * Category
77        * Constitution
78        * Website URL
79* Fields in the DB
80    * Kill meeting times
81    * Add membership description
82    * Validate constitution and website links on submit
83    * Make copies of constitutions (cron job) (keeping old versions)
84* Cron job to get warnings
85    * Check link validity
86    * Check president/treasurer student status
87    * Check list existence
88
89Things to ask stakeholders about:
90* Why does SAO use the printed signatory list?
91    * Would a more useful signatory report be good for them?
92    * Do they want update mail?
93* Why does CAC use a printed list?
94    * Same as above.
95=> [[ Student worker access. If student workers get direct, read-only access, then they can get rid of the lists. ]]
96* Ask Accounts if they care about the DB
97=> [[ Yes, but not very much. ]]
98
99Stakeholders:
100* SAO
101* SAFO
102* CAC
103* Schedules
104* Accounts
105* Funding boards (UA, GSC)
Note: See TracBrowser for help on using the repository browser.