| 1 | Based on meeting on 2010-12-02. |
|---|
| 2 | Attendees: Alex Dehnert (adehnert) (notes-taker) and Rachel Meyer (remeyer) |
|---|
| 3 | |
|---|
| 4 | * Categories as a many-to-many relationship is nice |
|---|
| 5 | * Need to think some more about what categories are reasonable |
|---|
| 6 | * Probably want to occassionally go yell at people about having too many |
|---|
| 7 | * Officer-y fields / associating people with groups |
|---|
| 8 | * Multiple presidents |
|---|
| 9 | * Multiple treasurers |
|---|
| 10 | * Add some field of "people we trust enough for office access control, mailbox control, etc." |
|---|
| 11 | * Financial signatories |
|---|
| 12 | * Reservation signatories |
|---|
| 13 | * Set a standard cap for each of these fields, but allow increasing it |
|---|
| 14 | * Probably: ASA can exceed the cap when adding, not "ASA can increase the self-service cap" |
|---|
| 15 | * Self-service enhancements |
|---|
| 16 | * Allow self-service officer's list updating |
|---|
| 17 | * Send mail to ASA Exec |
|---|
| 18 | * Send mail to GSC Funding Board or Finboard, as applicable |
|---|
| 19 | * Self-service constitution updating? |
|---|
| 20 | * Update mail? |
|---|
| 21 | * Send mail on updates? |
|---|
| 22 | * Signatory updates to the groups? |
|---|
| 23 | * Treasurer updates to Kerri? |
|---|
| 24 | * Associating notes with groups |
|---|
| 25 | * Groups leaving notes for themselves (notes by group) |
|---|
| 26 | * ASA Exec leaving notes for groups (notes to group) |
|---|
| 27 | * ASA/SAO for funding board (funding notes) |
|---|
| 28 | * ASA internal notes (ASA notes) |
|---|
| 29 | * Funding board access |
|---|
| 30 | * Viewing funding status |
|---|
| 31 | * Viewing account numbers |
|---|
| 32 | * Membership numbers |
|---|
| 33 | * Basically everything but notes |
|---|
| 34 | * Office access |
|---|
| 35 | * Do this per-space |
|---|
| 36 | * Assign each space a space category (e.g., storage, office, etc.) |
|---|
| 37 | * Shared office / office --- script to run occasionally to auto-update? |
|---|
| 38 | * Cap number of people with access from a group by space category |
|---|
| 39 | * Office ACL? |
|---|
| 40 | * Make sure the status options are generally changeable |
|---|
| 41 | * Status: Active, Suspended, Derecognized |
|---|
| 42 | * Class: various, editable by us |
|---|
| 43 | * Dorm/FSILG |
|---|
| 44 | * Standard |
|---|
| 45 | * Sponsored |
|---|
| 46 | * Indicate what mode you're in |
|---|
| 47 | * Nice, but not needed |
|---|
| 48 | * What info is available |
|---|
| 49 | * MIT-public |
|---|
| 50 | * Name |
|---|
| 51 | * Acronym |
|---|
| 52 | * Recognition date |
|---|
| 53 | * Last updated date |
|---|
| 54 | * Officer email |
|---|
| 55 | * Locker name |
|---|
| 56 | * President / treasurer / financial signatories / people who can update record |
|---|
| 57 | * Description |
|---|
| 58 | * Category |
|---|
| 59 | * Constitution |
|---|
| 60 | * Website URL |
|---|
| 61 | * Fields in the DB |
|---|
| 62 | * Kill meeting times |
|---|
| 63 | * Add membership description |
|---|
| 64 | * Validate constitution and website links on submit |
|---|
| 65 | * Make copies of constitutions (cron job) (keeping old versions) |
|---|
| 66 | * Cron job to get warnings |
|---|
| 67 | * Check link validity |
|---|
| 68 | * Check president/treasurer student status |
|---|
| 69 | * Check list existence |
|---|
| 70 | |
|---|
| 71 | Things to ask stakeholders about: |
|---|
| 72 | * Why does SAO use the printed signatory list? |
|---|
| 73 | * Would a more useful signatory report be good for them? |
|---|
| 74 | * Do they want update mail? |
|---|
| 75 | * Why does CAC use a printed list? |
|---|
| 76 | * Same as above. |
|---|
| 77 | * Ask Accounts if they care about the DB |
|---|
| 78 | |
|---|
| 79 | Stakeholders: |
|---|
| 80 | * SAO |
|---|
| 81 | * SAFO |
|---|
| 82 | * CAC |
|---|
| 83 | * Schedules |
|---|
| 84 | * Account |
|---|
| 85 | * Funding boards (UA, GSC) |
|---|
