Draft design doc for NetCDF/HDF5/geospatial

[mreekie]

@pdurbin this is a placeholder issue your next step that you talked about.

Title

• A clear and relevant title (Problem Statement)

Description

• A description of what the user will experience or how the system will do.

Context

• Any context that sheds more light on the what or why or the history.

Acceptance Criteria

• A description or how we will know when we have completed this deliverable.

Size: Small - this can be finished including testing in about a day. Medium - this can be finished including testing in 1 week. Large - STOP. this issue needs to be split in order to get pieces that can be completed in a week or less. (A large story is not "Ready")

---

Product backlog:

• https://github.com/orgs/IQSS/projects/32/views/22

[atrisovic]

Is this a paper for publication or internal?

[mreekie]

@atrisovic - This is a placeholder for future work. Phil mentioned that the next step would likely be a paper so I created a placeholder in the the NetCDF product backlog

I'm going to be working with you two on following the new process as I know you won't hang me out a window by my socks.
The first thing is getting future work into your deliverable backlog.

[pdurbin]

This may have gotten slightly lost in translation.

Here's what I propose:

• Step 1: Write down our ideas. Continue to brainstorm. I just created a doc for this: https://docs.google.com/document/d/1MtANhyun_X7wE7mwCLwYRu11bfh5hSAXpXKe0fJbxsc/edit?usp=sharing
• Step 2: Write a design doc with some more details for the ideas we hope to work on. I just created a doc for this too (but this one is empty): https://docs.google.com/document/d/1Ax_sMdgx5ROkIBA7-IC4_hySvgXkk6O8qTZLIvWWnqE/edit?usp=sharing

For the design doc I'd like to suggest that we draw inspiration from these design docs by @qqmyers:

• Embargo design doc (announcement)
• Multiple-license design doc (announcement)

[pdurbin]

@atrisovic and I discussed drafting a design doc based on the "ideas" doc. We plan to conduct a few more interviews first.

[pdurbin]

@atrisovic and I just discussed this during our weekly NetCDF/HDF5/geospatial meeting (notes).

We're giving this a size of 80 because we plan to incorporate some hacking around with different libraries, tools, and technologies along the way, to help determine what's realistic as deliverables.

[mreekie]

Priority review with Stefano:

• @pdurbin - I forget - is this ready to go? or still more discussions needed before you can start.

[pdurbin]

@mreekie this is ready to go.

[mreekie]

Priority Review with Stefano:

• Moved from NIH NetCDF to Ordered Backlog

[pdurbin]

@atrisovic and I plan to timebox this to a 33. Draft design doc is here: https://docs.google.com/document/d/1Ax_sMdgx5ROkIBA7-IC4_hySvgXkk6O8qTZLIvWWnqE/edit?usp=sharing

We'd like to post the doc on the google group and announce a date where we'd present it during a community call.

[pdurbin]

@atrisovic and I just published the design doc and announced it to the community.

Let's give the community two weeks to think about it and comment. Thanks, community! ❤️

[mreekie]

Grooming

• Looks like this is going to bleed over to March 15 sprint.
• needs resizing

[rtreacy]

Looks good. Lots of feedback

[rtreacy]

Closing

[mreekie]

Grooming

• Looks like this is going to bleed over to March 15 sprint.
• needs resizing

WAHOO!