Project Meeting 2017.09.28

Repository transfer to Pooled Funds

Pooled funds group starts mid October
Need to transfer repo #44 before RFP released in mid Nov, so within ~6 weeks
@Ben to setup a meeting the week of Oct 23rd with the AASHTO and ODOT projects so we can discuss timing and approach
We're thinking of transferring ownership and then forking back to the repos we're currently working in for the existing AASHTO and ODOT projects
We decided to postpone discussion regarding splitting things into separate repos until after the pooled funds is up and running #129. We agree this is a good idea in principle, but it needs a good plan + a decent amount of effort to pull it off.
Work flow will likely be similar: transferred VE repo for distribution (i.e. release), a separate branch/repo for development , and forks for development (off the development branch/repo)

VE GUI automatic testing is now working #108
It runs the VERPAT demo and makes sure it completes
@Adi working on better documentation for the VEGUI code and the wiki related to test setup

See #131
Code is working in a separate branch
Need to update VEGUI code, which we can do under the amendment
Workflow is Brian creates fork and turns off VEGUI test so he can test his revisions. Then he pushes a new branch to the master repo. Next RSG pulls the new branch, updates the VEGUI code and test and turns the test back on. RSG pushes to the master repo and merges to development. Once all tests pass, development is merged to master.

See #122
VERSPM modules updated to implement new requirements
@Brian to update VERPAT modules as well so the revisions will pass all the tests

See #132
CALL spec essentially overloads a function call with a different GET list of inputs
@Brian to add example to the issue since I had some questions about whether to "merge" or just "replace" the GET list of inputs