Merge in nr-spar-data

nr-spar-data/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Overview
+
+Act in the best interests of the community, the government of British Columbia and your fellow collaborators.  We welcome and appreciate your contributions, in any capacity.
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

nr-spar-data/COMPLIANCE.yaml

@@ -0,0 +1,11 @@
+name: compliance
+description: |
+  This document is used to track a projects PIA and STRA
+  compliance.
+spec:
+  - name: PIA
+    status: in-progress
+    last-updated: '2023-12-14T10:00:00.000Z'
+  - name: STRA
+    status: in-progress
+    last-updated: '2023-12-14T10:00:00.000Z'

nr-spar-data/CONTRIBUTING.md

@@ -0,0 +1,9 @@
+# How to contribute
+
+Government employees, public and members of the private sector are encouraged to contribute to the repository by **creating a branch and submitting a pull request**.  Outside forks come with permissions complications, but can still be accepted.
+
+(If you are new to GitHub, you might start with a [basic tutorial](https://help.github.com/articles/set-up-git) and check out a more detailed guide to [pull requests](https://help.github.com/articles/using-pull-requests/).)
+
+Pull requests will be evaluated by the repository guardians on a schedule and if deemed beneficial will be committed to the main branch.
+
+All contributors retain the original copyright to their stuff, but by contributing to this project, you grant a world-wide, royalty-free, perpetual, irrevocable, non-exclusive, transferable license to all users **under the terms of the [license](./LICENSE.md) under which this project is distributed**.

nr-spar-data/DOTgithub/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,35 @@
+---
+name: Bug
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the Bug**
+A clear and concise description of what the bug is.
+
+**Expected Behaviour**
+A clear and concise description of what you expected to happen.
+
+**Actual Behaviour**
+A clear and concise description of what you expected to happen.
+
+** Steps To Reproduce**
+Steps to reproduce the behaviour:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

nr-spar-data/DOTgithub/ISSUE_TEMPLATE/custom.md

@@ -0,0 +1,8 @@
+---
+name: Custom issue template
+about: Describe this issue template's purpose here
+title: ''
+labels: ''
+assignees: ''
+
+---

nr-spar-data/DOTgithub/ISSUE_TEMPLATE/decision.md

@@ -0,0 +1,8 @@
+---
+name: Decision
+about: This is a big decision that has been made or raised to PO
+title: ''
+labels: decision
+assignees: ''
+
+---

nr-spar-data/DOTgithub/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,26 @@
+---
+name: Documentation
+about: Documentation for a specific area or need
+title: ''
+labels: documentation
+assignees: ''
+
+---
+
+**As a** *(User Type/Persona)* **I want** *(Feature/enhancement)* **So That** *(Value, why is this wanted, what is the user trying to accomplish)*
+
+**Additional Context**
+- enter text here
+- enter text here
+
+**Acceptance Criteria**
+- [ ] Given (Context), When (action carried out), Then (expected outcome)
+- [ ] Given (Context), When (action carried out), Then (expected outcome)
+
+**Definition of Done**
+- [ ] Ready to Demo in Sprint Review
+- [ ] Does what I have made have appropriate test coverage?
+- [ ] Documentation and/or scientific documentation exists and can be found
+- [ ] Peer Reviewed by 2 people on the team
+- [ ] Manual testing of all PRs in Dev and Prod
+- [ ] Merged

nr-spar-data/DOTgithub/ISSUE_TEMPLATE/epic.md

@@ -0,0 +1,21 @@
+---
+name: Epic
+about: A User Story Large enough that it cannot be completed in a single sprint, the
+  desired end state of a feature
+title: ''
+labels: epic
+assignees: ''
+
+---
+
+**As a** *(User Type/Persona)* **I want** *(Feature/enhancement)* **So That** *(Value, why is this wanted, what is the user trying to accomplish)*
+
+**Additional Context**
+
+- enter text here
+- enter text here
+
+**Acceptance Criteria**
+
+- [ ] Given (Context), When (action carried out), Then (expected outcome)
+- [ ] Given (Context), When (action carried out), Then (expected outcome)

nr-spar-data/DOTgithub/ISSUE_TEMPLATE/feature.md

@@ -0,0 +1,26 @@
+---
+name: Feature request / user story
+about: Suggest an idea from the perspective of a user
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+**As a** *(User Type/Persona)* **I want** *(Feature/enhancement)* **So That** *(Value, why is this wanted, what is the user trying to accomplish)*
+
+**Additional Context**
+- enter text here
+- enter text here
+
+**Acceptance Criteria**
+- [ ] Given (Context), When (action carried out), Then (expected outcome)
+- [ ] Given (Context), When (action carried out), Then (expected outcome)
+
+**Definition of Done**
+- [ ] Ready to Demo in Sprint Review
+- [ ] Does what I have made have appropriate test coverage?
+- [ ] Documentation and/or scientific documentation exists and can be found
+- [ ] Peer Reviewed by 2 people on the team
+- [ ] Manual testing of all PRs in Dev and Prod
+- [ ] Merged

nr-spar-data/DOTgithub/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,22 @@
+---
+name: Question
+about: Ask us a question!
+title: ''
+labels: question
+assignees: ''
+
+---
+
+**Describe the task**
+basic description of the task, is it focuse on research with users or the business area? is it design focused on either co-design or wireframing? is it User Testing or compiling results?
+
+**Acceptance Criteria**
+- [ ] what is required for this task to be complete?
+- what is the finishing point or end state of this task?
+- [ ] what is the output of this task?
+
+**SME/User Contact**
+(may want to use a persona to fill this in)
+
+**Additional context**
+- any additional details that could not be captured above

nr-spar-data/DOTgithub/ISSUE_TEMPLATE/task.md

@@ -0,0 +1,20 @@
+---
+name: Task
+about: Work for the team that cannot be written as a user story
+title: ''
+labels: task
+assignees: ''
+
+---
+
+**Describe the task**
+A clear and concise description of what the task is.
+
+**Acceptance Criteria**
+- [ ] first
+- [ ] second
+- [ ] third
+
+**Additional context**
+- Add any other context about the task here.
+- Or here

nr-spar-data/DOTgithub/ISSUE_TEMPLATE/ux.md

@@ -0,0 +1,22 @@
+---
+name: UX Task
+about: This is a Task for UX Research, Design or Testing
+title: ''
+labels: ux
+assignees: ''
+
+---
+
+**Describe the task**
+basic description of the task, is it focuse on research with users or the business area? is it design focused on either co-design or wireframing? is it User Testing or compiling results?
+
+**Acceptance Criteria**
+- [ ] what is required for this task to be complete?
+- what is the finishing point or end state of this task?
+- [ ] what is the output of this task?
+
+**SME/User Contact**
+(may want to use a persona to fill this in)
+
+**Additional context**
+- any additional details that could not be captured above

nr-spar-data/DOTgithub/codeowners

@@ -0,0 +1,4 @@
+# Matched against repo root (asterisk)
+*                         @marcionemec-daitan @craigyu @rmcampos @paulushcgcj @derekroberts @sldonnelly
+
+# See https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners