‹ Home
Exported

Data Science Team Training 2022 (Class 2)

Hub for learners to connect, find calendar events, & documents related to CSTE's DSTT program.
Amanda Masters, Director of Workforce Development at CSTEJessica Arrazola, Director of Educational Strategy at CSTEElyse Bevers, WALaura Cronquist, Epidemiologist at ND Dept of HealthZhen-Qiang MaLaurel Harduar MoranoNhan NguyenKelley Bemis, Epidemiologist IVLifeng LiElisia RayDanielle SassLucinda GardnerLaura Fox, Environmental Public Health Tracking EpidemiologistStephanie HasanaliClaire Nguyen +127 others
Posted by Jeremy Kuo ·

Git Repo Services

Hi all,
First off, congratulations to all the teams on a job well done this year!

Here in Michigan, after our final presentation we were able to have additional presentations and follow-up internally and are looking ahead at what's next for our team and agency. We are revisiting the idea of using git repo hosting services for sharing and collaborating on different projects. Earlier in the year, our coach Josh Levy, Bio- and health informatics consultant Josh had introduced our team to the idea and even shared on a workshop about it! Unfortunately, at that time, we were restricted from using many of the popular products discussed and the solution that was provided by our department of technology was less than ideal, for a number of reasons. However, with the momentum of our team's successes from this year, along with shared interest from other groups at our agency, we're taking another look at options, which I'm already very grateful for. I've seen some chatter here and there around the use of github, but I was hoping to use what remaining time we have here on Basecamp to put out some feelers for the other teams and ask:
  1. Which git hosting service(s) are you using?
  2. Are these services officially supported by your agency?
  3. How are you using it?

Any input would be greatly appreciated! Please also feel free to contact me directly via email, if you'd prefer: kuoj1@michigan.gov

Thanks all!

Comments & Events

Josh Levy, Bio- and health informatics consultant Josh Levy, Bio- and health informatics consultant
Just to add to what I've said in the past...in my experience, for most purposes, if you want private repos, I haven't seen a huge difference in the services I've used. For what I've needed, github, gitlab and whatever repo Microsoft Azure offers are pretty much the same. That includes some CI stuff like automation of docker builds and pushing to a container repo.

And some clients use whatever service their company/organization tells them to use, and it's generally fine - ie one client has an Azure agreement, so all their repos are in Azure...etc.
Notified 141 people
Jeremy Kuo Jeremy Kuo
Josh Levy, Bio- and health informatics consultant Josh thanks for the insight! Reassuring to know that many of these products will offer similar experiences. And you probably remember when we looked into it, but for others, Microsoft Azure is indeed what our technology management department officially offers as a solution. 

However, to use it, program areas would need to pay a fee, we'd be limited to a single repository for all of our projects/work instead of multiple repos, and end-users wouldn't really have permissions to make changes, so for any pull requests, branch management, etc. we'd have to contact them to do for us. 

Paying to use a helpful tool wouldn't be the worst thing in the world but being limited to a single repo for an entire program area was the tougher pill to swallow. Having it be completely externally managed by the tech folks was the deal-breaker, at the time. Obviously this setup is not necessarily by Microsoft's design but our own internal policies. With exploring options again now, Azure is certainly still on the table, but hopefully there'd be some room for revisiting some of those policies to make it easier for folks across the department to use. 

If any other jurisdictions are using any repo services successfully, it'd be great to hear about to provide examples to our tech folks. 
Notified 141 people