Meeting Notes 11 09 2018

"What good shall I do this day?" - Benjamin Franklin

Clang randstruct Meeting Notes 2018

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

Date: 11/09/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	(N)
Jordan Cantrell	(P)	James Foster	(P)	Jeff Takahashi	(P)

Meeting Agenda & Summary

1. New scheduling poll - Connor

2. Filling in google calendar - Tim

3. Verify C++ Mailing List - Jordan

4. Confirm you’re on the google group - Everyone

5. Decide on which C++ version we’re using (11, 14, 17?) - Team

   • C++ 17

6. Make a git repo prototype and see if we can convert it into Subversion - Cole (jeff has been looking into this as well::)

   • Introductory walkthrough from some random
   • Adjacent: Unofficial github mirror of LLVN

7. Request for resources - Skip for now

   • CAT, OIT, Google Cloud Platform
   • OIT request form
   • ** after some querying, Jeff can get a VM from the CAT ** ← Great!

8. Prototype Travis CI - Jeff Connor

   • Travis CI is enabled for the github repo, we will add a build script for it when we begin implementation.

9. Reaching out to Steven Libby - Jeff

10. Charles Wright - Tim

    • Another person interetested in what we’re doing but can’t provide much in the way of help.

11. Make a new channel exclusively for daily checkins - Cole

12. Hangouts meeting on Veterans Day

    • Cole, Jeff, Tim, Jordan, Connor, James, Nikk - Yes!

13. Vagrantfile - Can this be useful?

14. Google Team Drive - Tim

    • Bank those files

15. Github - Connor - https://github.com/connorkuehl/clang_randstruct

    • Github Issues
    • Github project tracker
    • Other github tools
    • Pull requests required

16. Minimum Viable Product - Tim

1. Badge Access + Please double check!

1. License compatibility

2. Stand alone plugin or into Clang - Team

   1. LLVM pass. Compiled with Clang tree
   2. We’ll send Kees an email with other questions
   3. Narrow possible approaches to project (eliminate time sinks)

3. Research vector of approach for this project! - ALL MEMBERS