Open lbross opened 3 years ago
Spoke with Bryan Lanier in the Forest Service. He recommends we stay with the public option we are on. At some point ( year or more from now most likely) we will need to clone the current branch of code from the public BioSum github to a FS github so that the CIO can inspect the code if they so desire (with bots). They don't care about preserving issues. They are targeting to get 80% of FS code onto their github at some point, but it does not need to be the development github- more of a repository. UNLV currently has their own github and the periodically clone it to the FS github to comply. Their apps hit the Data Center so are required to have their code propagated to the FS gitbuh periodically. BioSum will not hit the data center by the time we are done with it, so there is not that need. the sooner we are out of ORACLE the better. He is happy to set up a BioSum FS github site when we need one, and assign users etc. FS github website users do have to be on FS network with lincpass etc. The FS ALSO has a public github that they clone their code out to in order to put it in the public domain. But we already have a pubic github so no advantages for us there. Bryan can also give us a contact at UNLV for mechanics of cloning the latest branch from our public BioSum github to the FS GitHub which we can ask for when needed.