Risk register

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Start by reading minutes/minutes_2022-03-17.md to recover the context and intended scope of the proposed register. Define what storage and compute risks each ACS work unit should record, then document a usable register and completion process; done means work units can fill it out consistently.

Written by the indexing model from the issue text.

Description

action item

At the meeting on 17 March 2022 we discussed the idea of creating a storage/compute risk register for ACS work units to fill out.

This seemed more manageable than trying to continually monitor storage and compute requirements across the project.

Dominant language
Jupyter Notebook
Stars
1
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AusClimateService/data-code-group

All issues in AusClimateService/data-code-group

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.