Skip to content

Meeting Notes 11 02 2018

Jump to bottom
Jordan Cantrell edited this page Nov 20, 2018 · 1 revision

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 (P)
Connor Kuehl (P) Cole Nixon (P) Nikk Forbus (P)
Jordan Cantrell (P) James Foster (P) Jeff Takahashi (P)

Meeting Agenda & Summary

  1. ~~Long term scribe: Call for volunteers (~1 minute)~~ - Nikk

    • Let's get this out of the way quick so we can get to business!

  2. Requirements Elicitation (5-7 minutes)

    • Thank you to Jeff Takahashi and Connor Kuehl for making yourselves available.

      • Jeff followed up with Kees on C++ standard.

      • “I don't think the C++ standard makes a difference, but I could be wrong. I think it’s fine to do it in whatever style you prefer.” - Kees

      • This means we have to figure it out!

      • Connor mentioned “We’ll use whichever standard it’s currently written in as that’s the only way the patch will be accepted upstream.”

      • I’m unfamiliar with the process of reaching out to upstream devs, but Kees warned us about “goons” :)

        • Reach out and ensure no one else is working on this project that the upstream devs know up.
        • Announce project?

    • https://docs.google.com/document/d/10yPUPiW0bsJzlUXPG61egxYL2LGxANauGwCR2ORk49w/edit

    • We’re signed off. Add comments if you wish, but no write access (Only Connor, Jeff, and Tim.)

    • AR: Verify C++ version

  3. Previous weeks action items (~10 minutes)

    • Team availability -- Connor

      • Tim said he’d pencil this in to a google calendar, but I’d like to do another call for volunteers. Who wants it?
      • Real overlap is Fridays @ 1pm, Mondays during capstone block
      • AR: (Connor) Resend out doodle poll for availability, keeping telecommute options in mind

    • Bart for Google Group, Tim as secondary on group -- Tim Nikk

      • We’ll make a google drive and toss all docs in there. Tims keeping an eye on what’s been written down.

    • Emailing Kees tomorrow (10/30) for initial meeting on requirements gathering - Tim

    • Add google hangouts to Slack and invite Kees - Tim

      • Decided not to add Kees. Not necessary.
      • Initiate a hangout via slack by doing ‘ /hangout ’

    • 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

      • My takeaway from the elicitation was that we’ll need to figure this out.

      • There was some discussion in slack about sticking with Git vs Subversion, but Tim is a bit hesitant if we’ll need to backtrack (concerning them using SVN). Thus Tim hasn’t made the github yet. I’m no Subversion expert, nor know how valid the porting process is.

      • Do we want/need hardware set up so that there is a unified/uniform test environment? -Jeff

        • Tim reached out to an old colleague in OITs High Computing Dept. to see if they can help us get a build server with backups going. Just fired it off today @ 3:30pm, should hopefully hear back soon!

        • Need to try and get Clang building to see if we’ll run into issues

      • Reach out: Instructor Sergio Antoy - Tim

        • Noda

      • Reach out: Instructor Mark Morrissey - Tim

        • Good discussion, but can’t aide us on our quest

      • Reach out: Instructor Mark Phillip Jones - Tim

        • Another good discussion, but no aide provided

  4. Reach out: Charles Wright (1-2 Minutes)

    • A co team lead let me know Instructor Charles Wright has some information on randstruct stuff.

    • Call for volunteers: Who wants to reach out?

      • Jeff

  5. Steven Libby PhD Student → slibby@pdx I think? (1-2 Minutes)

    • Can’t remember whom suggested we reach out to him.

    • Call for volunteers: Who wants to reach out?

      • Jeff

  6. Jeremiah Peschka (Mark Jones PhD student) (via Mark Morrissey, I don’t know his name) (1-2 Minutes)

    • Call for volunteers: Who wants to reach out?
      • Connor

  7. No private slack channels (~30 seconds)

    • Bart wanted the team leads to mention this.

  8. Verify your badges (~30 seconds)

    • CS lounge, labs, EB 95

  9. Jenkins (5 minutes)

    • I’m familiar with making jenkins jobs, but not installation. I think it’d be simple to do.

    • What are peoples thoughts on this?

      • PVS-Studio.Their Jenkin plugin only works on Windows (from what I read)

    • If the team agrees this is good, then it’s settled.

  10. Waterfall, SCRUM, some hybrid (~5 minutes)

    • I had to be the bad bear, but Bart recommends a hybrid (Waterfall with daily check ins or status updates)

    • I think this is appropriate, it’ll help us on comms, make us used to our own styles and quirks (Did I mention I love plant identification?).

    • Yes! It’s okay if there is nothing to report, just say so!

      • I already got sick over the weekend, and had to take a day. Sometimes homework happens. We’re human, it will be important to remember this as we work together.

  11. Take what Bart says to heart (~2 minutes or faster)

    • Bart’s done this rodeo plenty of times.
    • Keeping Bart happy makes for smooth sailing.
    • WWBD? What should I do?
      • When in doubt you need to decide some things yourself, to reach out to Tim, or to reach out to Bart
      • Most important item in our life according to Bart: CAPSTONE
      • Backups
      • Git pull requests

  12. Final Thoughts

    • Yes Smaug is our logo (We’re on a quest after all..)
    • Veterans Day
    • Project Presentations and Barts Discussion today
      • Describe requirements and scope
      • MVP (Minimum viable product)
        • Insurance policy
      • How to build it
        • Building blocks, language
      • Project plan:schedule and milestones
      • Risk management plan
      • Things to show up
      • prototypes , mockups
      • Documents
      • Risk management
        • Severity and likelihood
      • Git discipline
    • When the music plays, the meeting needs to begin to wrap up!
    • Books. Tims got a bunch of em. Ask you shall receive (on loan..)
    • Questions
    • Anything we believe we missed or needs to be added
    • Weekly Quote
    • Weekly Music Tune
Clone this wiki locally