Changeset 0089335


Ignore:
Timestamp:
Apr 16, 2011, 4:21:42 AM (15 years ago)
Author:
Alex Dehnert <adehnert@…>
Branches:
master, space-access, stable, stage, test-hooks
Children:
3080d89
Parents:
3728ed0
git-author:
Alex Dehnert <adehnert@…> (04/16/11 04:21:23)
git-committer:
Alex Dehnert <adehnert@…> (04/16/11 04:21:42)
Message:

Notes from stakeholder meeting

Location:
design
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • design/agreement.txt

    r3728ed0 r0089335  
    33DRAFT: Alex Dehnert, ASA UMAL
    44
    5 1. Stakeholders
     51. Purpose
     6
     7The ASA Database serves as a central source for information about ASA-recognized student groups, and is thus used by groups and offices around MIT for getting information about name, website, constitution, authorizations (administrative, financial, and reservation), membership, etc.. In some cases, the database may also store information about non-recognized groups, when it provides significant value to the various users of the database.
     8
     92. Stakeholders
    610
    711The ASA Executive Board has principal ownership over the ASA Database.
    … …  
    1721* Student activities (represented by ASA Exec)
    1822
    19 We designate the following as core stakeholders, due to having a particularly frequent and extensive needs to work with the database:
     23The DSL central administration also provides some support around the database.
     24
     25We designate the following as core stakeholders, due to having particularly frequent and extensive needs to work with the database:
    2026* ASA Exec
    2127* Student Activities Office
    … …  
    2632The core stakeholders are expected to each provide at least one representative who is willing to actively watch the relevant mailing lists (asa-db-stakeholders@mit.edu and asa-db-core-stakeholders@mit.edu), respond to requests for information, and attend database-related meetings as necessary.
    2733
    28 2. Code and Server Access
     343. Code and Server Access
    2935
    3036The ASA database code will be made publicly available. Anyone at MIT (or elsewhere in the world) will be able to read the code and the history of changes to it (though not configuration such as passwords, or group data such as signatories). (Moira, the system MIT uses for handling user accounts, mailing lists, hostnames, etc., similarly has publicly-available source.) The mailing list asa-db-commits@mit.edu will receive commit information and will be public.
    … …  
    3238Any stakeholder will be able to propose an individual for commit access or server access by contacting core stakeholders. A core stakeholder (generally whichever stakeholder is proposing the individual) must sponsor the request. If no objection is made within one week, they may be given access. If an objection occurs, the core stakeholders should attempt to reach a consensus.
    3339
    34 3. Infrastructure
     404. Infrastructure
    3541
    3642The ASA Database will run on the scripts.mit.edu / sql.mit.edu hosting platform out of a dedicated locker in IS&T's AFS cell. Write access to the locker will generally limited to those with "server access". Write access to the source repository will be provided to those with "commit access".
    … …  
    3844Nightly backups will be automatically taken and stored into the locker, from which they will be copied to an off-site location automatically by IS&T's regular backup procedures.
    3945
    40 4. Development Process
     465. Development Process
    4147
    4248a) Major changes should be discussed first with the stakeholders. Consensus should be achieved that the change is desirable. For particularly large, complex, and potentially objectionable changes, one should solicit opinions for at least a week, via email and possibly an in-person meeting.
    … …  
    5258When a consensus is reached among the core stakeholders or for simple, time-critical bugfixes, exceptions to this process can be made. In all cases, core stakeholders should be informed of changes.
    5359
    54 5. Amendments
     606. Amendments
    5561
    5662This document may be amended through consensus decision of the stakeholders. Minor changes can be made through consensus decision of the core stakeholders only, if desired. Amendments must be discussed for at least a week over email before they can be made.

  • design/notes.txt

    rd92d14c r0089335  
    11Based on meeting on 2010-12-02.
    22Attendees: 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
    39
    410* Categories as a many-to-many relationship is nice
    … …  
    2228    * Signatory updates to the groups?
    2329    * 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
    2437* Associating notes with groups
    2538    * Groups leaving notes for themselves   (notes by group)
    … …  
    3649    * Assign each space a space category (e.g., storage, office, etc.)
    3750        * Shared office / office --- script to run occasionally to auto-update?
     51    * Should include ASA and non-ASA space
    3852    * Cap number of people with access from a group by space category
    3953    * Office ACL?
    … …  
    4458        * Standard
    4559        * 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
    4664* Indicate what mode you're in
    4765    * Nice, but not needed
    … …  
    5472        * Officer email
    5573        * Locker name
    56         * President / treasurer / financial signatories / people who can update record
     74        * President / treasurer / financial signatories / people who can update record [[stakeholders were fine with this being MIT-public]]
    5775        * Description
    5876        * Category
    … …  
    7593* Why does CAC use a printed list?
    7694    * Same as above.
     95=> [[ Student worker access. If student workers get direct, read-only access, then they can get rid of the lists. ]]
    7796* Ask Accounts if they care about the DB
     97=> [[ Yes, but not very much. ]]
    7898
    7999Stakeholders:
Note: See TracChangeset for help on using the changeset viewer.