search

ioos / marine_life_data_network

Planning efforts relevant to IOOS Marine Life and IOOS DMAC.
https://ioos.github.io/marine_life_data_network/
Other
1 stars 2 forks source link

New Task: collect and document requirements for future work. #23

Open MathewBiddle opened 5 months ago

MathewBiddle commented 5 months ago

Who is requesting this?

@ioos/marine-life

What is being requested?

To further understand what the IOOS community needs to meet their stakeholders, the Marine Life effort needs to collect and document requirements for future work.

What is the requested deadline and why?

2024-11-30

What is the current status quo (i.e., what happens if this does not get done)?

We will build stuff that no one needs.

What indicates this is done (i.e., how do we know this is complete)?

Provide a description or any other important information.

Could be related to https://github.com/ioos/marine_life_data_network/issues/21

laurabrenskelle commented 5 months ago

Is this repo a good place to document user requirements, or is there another option that might be better? We could have a different issue template for submitting a user story.

laurabrenskelle commented 5 months ago

Relating to this, as I am writing the contributing guide, I think we need to determine what other issue templates we may need and create those. Do we need three? New Dataset, New User Story, New Task? Or do we think Dataset can be combined with New Task? Currently we do have one example of that in #5.

MathewBiddle commented 5 months ago

I think New Task and New User Story would be sufficient. I like the addition of tags to call out that a task is a dataset and I think that suffices for now. We should consider is New User Story is appropriate. I'm thinking along the lines of User Request, but maybe that's different?

I think https://github.com/ioos/marine_life_data_network/blob/main/.github/ISSUE_TEMPLATE/custom.md should be updated to be the New User Story template, or whatever we call it.

We will have to iterate on the information to collect for a user story. Mainly; who is requesting the thing, what is the thing, and how can we get in contact. Keeping the bar low at the outset will be key.