Skip to content

Meeting Notes 10 29 2018

jcantrell edited this page Nov 20, 2018 · 2 revisions

MCECS logo Team logo

"My armour is like tenfold shields, my teeth are swords, my claws spears, the shock of my tail a thunderbolt, my wings a hurricane, and my breath death!" -Smaug

Clang randstruct Meeting Notes 2018

Meeting Name:Workshop (Group Mail/Group Mail) (Project Slides)

Date: 11/02/2018

Attendees and Key: P=present, A=absent, S=scribe, N=not required

Member Status Member Status Member Status
Kees Cook (N) Bart Massey (N) Tim Pugh (S)
Connor Kuehl (P) Cole Nixon (P) Nikk Forbus (P)
Jordan Cantrell (P) James Foster (P) Jeff Takahashi (P)

Meeting Agenda & Summary Note: This document is a copy of the meeting notes on the google drive. Personal contact information is deliberately omitted here For contact details, see the team drive google document

  1. Get to know your teammates. Please provide contact information as well. (~15 Minutes)

    • Tim Pugh
    • Nikk Forbus
    • James Foster
    • Jordan Cantrell
    • Jeff Takahashi
    • Cole Nixon
    • Connor Kuehl
  2. Team Project Introduction (+-10 minutes)

    • Review the slides (specific to our project first)
    • Get familiar with project sponsor (material in slides)
    • What we’re trying to accomplish, questions, and further discussion
  3. Accounts, Shared Resources, Final Thoughts (Remainder)

    • Slack
      • Voice Comm add-on via Google Hangouts
    • Github
    • Google Drive
    • Google Calendar and Scheduling
    • Github issues for work tracking
    • Backup Contact Info
      • This is optional but encase of an emergency we’d like to reach out
    • Team Picture - First Day (and last only)
    • Final Thoughts
    • Action items
      • Team availability -- Connor
      • Bart for Google Group -- Tim Nikk
      • Emailing Kees tomorrow (10/30) for initial meeting on requirements gathering - Tim
      • Add google hangouts to Slack and invite Kees - Tim
      • Speak with Kees Cook to get his thoughts about C++ standard versioning. C++14? C++17? -Jeff
      • Probably also worth speaking to Kees about the upstream process, there is some verbiage that isn’t clicking, but I could just not be far enough into the doc. -Jeff
      • Do we want/need hardware set up so that there is a unified/uniform test environment? -Jeff
      • Steven Libby PhD Student → slibby@pdx I think?
      • Reach out: Instructor Sergio Antoy - Tim
      • Reach out: Instructor Mark Morrissey - Tim
      • Reach out: Instructor Mark Phillip Jones - Tim
      • Git to SVN - Cole
  4. Jenkins Team:

    • Cole Nixon
    • Jeff Takahashi
    • <Volunteers>