Participants
- Matt
- Jim
- Trey
- Robyn
- Alyona
- Rushiraj
Activities review
- Technical diagrams:
- Github pointers:
- Project board:
Discussion
- High-level architecture
- We should define acronyms (e.g., what is “OGDC”)
- Add a legend
- Consider labeling components with different colors
- Expand the “recipe” box. Show that this is how one specifies:
- Input dataset
- data transformations (e.g., reprojection)
- CI board background
- Claire Porter: Polar Geospatial Center. Direct experience with large geospatial dataset processing
- Carl Boettiger: Analytical & GIS background, provides user-perspective
- Some technologies like Argo and K8s may be new to board memebers, but they have deep understanding of geospatial data processing
- We should be ready to ask questions and seek advice. The CI board is here for our benefit. concerns.
- We should develop some slides that describe/introduce the project and setup the discussion around the architecture diagrams
- Show how things work now, in as much detail as possible. (e.g., how does parallelization work)
- Walk through an example
- Sequence diagram:
- Usually these are much more detailed (e.g., they show specific function calls and what kind of messages are passed around)
- Not sure the existing diagram adds much
- We should strive to improve this over time
- There may be more than one sequence diagram depending on the situation (e.g., reprojecting a very large raster may look different than subsetting a small vector dataset)
- Documentation developed for this CI board meeting can serve as a foundation for contributor docs that we will leverage near the end of year 2 when the developer workshop takes place.
- We think that we are close to an MVP dev deployment to the ADC cluster. We think achieving that before the CI board meeting would be good.
- Plan to meet with CI board sometime in mid-April. Matt Jones to schedule.