2016-11-03 Meeting Notes

Owned by Margaret Mellinger (Unlicensed)
Last updated: Nov 03, 2016 by Steve Van Tuyl (Unlicensed)Version comment

Date

03 November 2016

Attendees

  • Margaret Mellinger (Unlicensed)

    • Who: Director of the department

    • What: Go to meetings and worry
    • Best: hanging out, no meetings
    • Worst: trying to understand what to do with the department as we move forward
    • Minion: all

  • Ryan Ordway (Unlicensed)

    • Who: Systems Person

    • What: keep everything from blowing up
    • Best: solve interesting problems
    • Worst: keeping up with everything
    • Minion: all the uninteresting things
  • David Manela (Unlicensed)

    • Who: public computer and specialty station support, buy things, 

    • What: 
    • Best: all of it, of course
    • Worst: all
    • Minion: all
  • Mike Eaton (Unlicensed)

    • Who: programmer analyst

    • What: software development 

    • Best: variety of problems and challenges
    • Worst: 
    • Minion: 
  • Marc Rempel (Unlicensed)

    • Who: programmer analyst

    • What: software development 

    • Best: variety of problems and challenges
    • Worst: 
    • Minion: 
  • Gregorio Luis Ramirez (Unlicensed)

    • Who: programmer analyst

    • What: software development 

    • Best: variety of problems and challenges
    • Worst: 
    • Minion: 
  • Brandon Straley (Unlicensed)

    • Who: programmer analyst

    • What: write hopefully elegant code, learn new stuff 

    • Best: learning new technologies
    • Worst: learning tech, interpersonal issues related to tech
    • Minion: stand behind me and tell me i'm a great guy 
  • Josh Gum (Unlicensed)

    • Who: programmer analyst

    • What: software development 

    • Best: variety of problems and challenges
    • Worst: variety of challenges
    • Minion: accurate and complete documentation
  • Hui Zhang (Unlicensed)

    • Who: digital applications librarian

    • What: keeping dspace up and running, content integration, developing tools for SA@OSU

    • Best: freedom of having ideas and support for doing them
    • Worst: promoting a new project/tool to users and communities
    • Minion: uninterested but required things
  • Steve Van Tuyl (Unlicensed)

    • Who: public computer and specialty station support, buy things, 

    • What: 
    • Best: all of it, of course
    • Worst: all
    • Minion: all
  • Ryan Wick (Unlicensed)   

    • Who: programmer analyst (ETS/SCARC)

    • What: primarily OD, SA, CVM, Omeka, fun stuff

    • Best: working with different people in the library on projects
    • Worst: documentation and keeping up
    • Minion: documentation and data cleanup
  •                                                                                                                                                                                                                                                                              

Discussion Items

TimeItemWhoNotes
5 minsPersonnel update  
15-20 minIntroductionsAll

Each person answer these questions

  1. What do you currently do (in ETS or in CDSS)?
  2. What part/s of your job do you like the best?
  3. Which part/s of your job do you find most challenging?
  4. If you had a minion (or a horde), what parts of your job would or could you delegate?

20 minDiscussionAllBrainstorm how to cover Mike's responsibilities in the near, medium and long-term.

Discussion

  • Introduction
  • Cover Mike
    • Check in at the beginning of the week with everyone
    • Set and track priorities
    • PHP stuff that nobody likes
    • Website update and maintain
    • Road buddy
  • What does Mike think the department should do now?
    • Talk to Steve about SA@OSU: where we are, what is next, get that on the calendar
    • Set priorities for OD
      • Roadmap Meeting
      • Get sprints on the calendar
    • Check in on the Trello board
    • Opportunities and vision?
      • Another Project Manager type to help track stuff and guide development would be helpful
  • What do we do about documentation?
    • Automatic documentation generation (though there are mixed reviews)
    • In many ways it's just a matter of sitting down and writing it out - make it a consistent practice
    • Documentation Day (with LEAD)
    • Documentation at all levels
    • Documentation pairing
    • Building a "run book" to, at a minimum, get something up and running
    • Especially important if there are elements of the project that are external
    • Maintenance is an issue - the more doc you have the more you have to maintain
    • "It still just kinda sucks" - Mike Eaton
    • Don't get too bogged down in details and just do it

Action Items

  •