CDI Software Development Cluster

Meeting Notes

August 30th, 2018, 3:30PM EDT

 

Git, a deeper dive
Presented by George Rolston

 

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/696628840

Or iPhone one-tap :

US: +16699006833,,696628840# or +14087403766,,696628840#

Or Telephone:

Dial(for higher quality, dial a number based on your current location):

US: +1 669 900 6833 or +1 408 740 3766 or +1 646 876 9923

Meeting ID: 696 628 840

Note that we have switched from GSTalk to Zoom for the time being, due to a number of usability/compatibility issues with the GSTalk platform.

 

Meeting Notes in Google Drive: Shared Google Drive Folder:

https://docs.google.com/document/d/1w7T9OHQjeDJ_4B8ZanFXxJ_NAGVWRRxb5oNIc1ROy9Q/edit?usp=sharing

 

Attendees

Name

Email (if you are new)

Michelle Guy

 

George Rolston

 

Leslie Hsu

 

Dennis Walworth

 

Tamar Norkin

 

Drew Ignizio

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Agenda

     Welcome and announcements

     Please fill in name and email in the attendees table

     We are still always looking for topics, and your input and participation!

     We have created a form for submitting presentation proposals for future Software Dev Cluster meetings

     https://docs.google.com/forms/d/e/1FAIpQLSccsoCmFH4aT1OQNKaMDG7-ngIAlyGgmqSRQwJc_uYFf_tVUQ/viewform

    CDI bison connect google calendar of all the collaboration area meetings and events - name is “GS CDI” owner is gs_cdi@usgs.gov

    Free, online event on DevOps in October   https://www.alldaydevops.com/

    Git, a deeper dive ( George Rolston )

      Google drive presentation  (in the CDI Software Dev google drive folder and available via https://drive.google.com/file/d/0B101UEJHbXWYcVNMSl9WSlh3VGNqUjd3ZkZQWGVjTjBPYmNv/view?usp=sharing)

     Example project with support on using labels in your branching strategy https://code.chs.usgs.gov/usgs-chs/labels/blob/master/README.md

     Open mic

     Announcements?

     Questions?

     Lessons learned?

     Fun projects under way?

     Next Month: Git, a deeper dive by George Rolston

 

Discussion/Notes

      Can simplify by not doing branches under a fork, or possibly not doing forks, but this takes away from the motivation and getting code reviews, etc

      Infinite possible workflows in Git, adjust it, make it work for you, Atlassian is a good resource https://www.atlassian.com/git/tutorials/comparing-workflows

      Branch naming conventions? Can use issue code/identifier this can help you trace back to details on the issue or motivation for the code changes