Action items

  •  

Parking Lot

  • Creating branches - need to determine if we follow same process in Github or follow a new convention

Agenda

WhoTopicNotesFollow Up
Luigi

Summary of managing GeoStream project.

  • We will have a confluence page updated by Developers
  • Developers insert the Jira entry (project specific) or Github entry (GeoStreams core) on the page
  • Developers do this update every Monday morning by 10 am
  • Management team (Luigi, Jong and Shannon) will review the doc before Thurs Tech meeting
  • At the tech meeting, the blocking issues will be discussed and issues that require discussion
  • Purpose of inserting Jira or Github issue:

    • So that we enforce developers that the Jira issues or Github issues are created and updated properly (proper description, current status, etc.)
  • One private slack channel to rule them all #geostreams

Confluence Page to be updated by Developers: GeoStreams Tech Weekly Update


For a start of a dashboard: GeoStreams Dashboard


New Projects coming in - Aaraj- ARPA-E SmartFarm

All other slack channels will be retired and go to geostreams

Aaraj suggested: Check into tagging group for slack


Luigi/Kaveh

Releases today - 3.01 and 3.02

Bug fixes for performances - Trends analysis page on GLM

Dashboard - 3.4 release - mostly changes from Kaveh which affect detail page for other projects

  • Done in GitHub: https://github.com/geostreams - generic functionality goes here
  • Ideally we want to do everything on here - core and general purpose coding - including issues
  • Project specific goes in BitBucket
  • Creating branches - need to determine if we follow same process in Github or follow a new convention - Luigi likes having ticket number in branch name - but github does link well (you need to make sure to put the link in there)






FYI

WhoNotes