Transitioning to Git:
Joanne foresees a large amount of work involved in transitioning to git due to the SLAC cvs structure involving large numbers of symlinked packages. She is concerned with possible drift from glastrelease and ScienceTools, since both have overlapping tools.
We settled on keeping the release manager/cvs system the same for now, but have all commits go through git. An automated script/utility would port any git changes to CVS and would be the only 'user' to have commit privileges on the CVS repository in order to prevent collisions.
Updates from Tuesday Morning:
Brian and Jim began process of porting CVS to git using cvstogit utility
-in principle you can restrict the groups that have write permission
-newer CVS to git seems to retain the history, based on svn to git utility
-main hurdle is permissions problem
-Need to restrict checkins to CVS to only git script
-Need to be able to allow users to access CVS users area without affecting/conflicting with git/cvs checkins
-submodules/details not sorted yet, just prepping for transition now by moving repo to SSD
Brian update:
-Took list and made CSV file for table on confluence, grep through repo for needed files
-Copied entire CVS repo locally to machine in order to ease transition
-Doesn't anticipate too many problems with this, but there are a few hiccups like author matching
-Org: fermi-lat
-Alex and I will be added to the fermi-lat team on github
-Test conversion of Likelihood (github.com/brianv0/Likelihood)
Externals:
Generally in favor of jettisoning most external packages. Python can be provided by users, no need to carry our own versions around.
IRF generation require ROOT, nothing else does. Can be removed from main FSSC ScienceTools for the public release, however, it would be good to keep it around for internal/developer use.
Updates from Tuesday Morning:
-Went through externals and determined statuses/necessity of each package
-Also determined whether or not we needed to provided packages or if they were available in conda