where to post the tech memo for review?

[sgaichas]

Looks like we have two relatively easy options for posting a copy of the compiled tech memo for review: Rstudio Connect or GitHub GitHub looks slightly more complicated. I can enable the editing feature for the book either place. Thoughts?

[slarge]

I've been thinking about this... I really like the travis-ci workflow (commit - push to branch - pull request - verify with travis-ci - merge to master if OK) because it prevents pushing a breaking change to the master that will prevent the book from building. This workflow works with GH pages, which would keep everything contained within the NOAA-EDAB/tech-memo repo.

I think this would be a (potentially) more complicated flavor of your slightly more complicated suggestion. I'm happy to help with any of the above, but won't have much time until next Thursday

[sgaichas]

That does look ideal; I'll see what I can set up. It would be great to let people look at the draft before or at the workshop on their own computers if possible, but if I can't swing it we can just show a local version on one of our machines.

[slarge]

I agree. Perhaps the travis-ci bit is not necessary for now but we can add later (or next iteration).

[sgaichas]

if I sign up with travis-ci it has an option for "grant access" to NOAA-EDAB organization; should I do that?

[slarge]

yeah, I think that's OK

[sgaichas]

• [x] sign us up with Travis-CI
  • [x] figure out security token
• [x] set up gh-pages branch
  • [x] create local gh-pages branch with all files removed
  • [x] add .nojekyll
  • [x] initial local commit to gh-pages branch
  • [x] push local gh-pages to origin
• [x] put the current _book output directory onto the gh pages branch
• [x] .travis.yml file for master branch
  • [x] sets language (R), pandoc version
  • [x] build script
  • [x] deploy script
  • [x] linux packages needed for rgdal, rnetcdf4, magick added to yml
• [x] DESCRIPTION file for master branch
  • [x] list dependencies in here (all packages used in book!)
  • [x] breaking on dependencies, can't install all packages needed, debugging...fixed
• [x] finish this list
• [x] probably lots of debugging

[sgaichas]

It works! tech memo is live for future we may want to streamline the number of packages and dependencies--if one R package can work instead of several that would streamline build