IOOS DMAC Code Sprint 2019 Structure and Goals
Explore the proposed structure and goals of the IOOS DMAC Code Sprint 2019, including morning presentations on technical topics, work sessions, sprint ideas, and more. Get involved in advancing IOOS DMAC technology.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
2019 IOOS DMAC Code Sprint When: Tuesday, Oct 8 - Thursday Oct 10 Where: Cahoots, Ann Arbor, MI https://beincahoots.com/ Large meeting room/space reserved, capacity: ~50 or so Who: IOOS RA data managers, all Federal and non-Federal collaborators and partners, interested community members * travel available to cover IOOS grantee travel costs * Why: Get together in-person to fix issues discussed here and advance IOOS DMAC technology 2
Proposed Code Sprint Structure Each morning have an introductory 1 hour presentation on a relevant technical topic: GitHub workflow etiquette (PRs, branches, issues), Minimum viable python repository, Critical IOOS tools to improve workflows (pocean core, erddapy, CC) Morning and afternoon work sessions and/or tutorials (if available) Put ideas for sprint topics on public Trello board, gather interest and discuss/plan in advance We should have a rough idea of what areas have the most interest going into the event and identify individual goals for each by the end of week Daily recap/report out for each workgroup Celebrate! 3
Sprint Goals/Ideas/Things to work on Your ideas here: https://tinyurl.com/IOOS-Gathering ERDDAP configuration/ERDDAP development Library consolidation (3 QARTOD libraries, etc) Missing capabilities/libraries to build (eg. mapping Darwin Core -> CF) Existing client library updates (griddap for erddapy) Documentation updates (pocean core) ... 4
Tutorial Session Volunteers ESIP Pangeo HOWTO & pre-configured demonstration environments (Rich Signell) Other volunteers? 5
What else do we need to think about? Recommendations: ... 6
ETC (notes copied from agenda) What are the critical preparation steps in order to have a successful sprint? Get input from audience on what should/shouldn t be done ahead of time. Introductory talks at sprint: GitHub workflow etiquette (PRs, issues) Minimal viable Python repository (Travis CI, tests) Most important/common tools for IOOS (pocean, erddapy, Compliance Checker) Sprint goals/ideas/things to work on: ERDDAP configuration/ERDDAP development Library consolidation (QARTOD libraries - 3) New functionalities/libraries to be developed (biological datasets/Darwin Core -> CF and reverse). Client library updates: griddap support for erddapy Documentation (pocean core) - See former planning doc for more Put on Trello board for public input before sprint Volunteers to lead tutorial sessions: How to use Pangeo? Ask Rich about furnishing Pangeo instances/environments for code sprint users. ? Understand audience: different tracks for different members One presentation in the AM Make it clear it won t be tutorials 100% Do we need background/intro presentations to lead off? What should those include? How many tasks should we focus on? How do we define success? Volunteers to lead a sprint 7
