Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
  • Loading branch information
nutjob4life committed Sep 13, 2021
1 parent ea05d5e commit be353fd
Show file tree
Hide file tree
Showing 12 changed files with 435 additions and 267 deletions.
48 changes: 37 additions & 11 deletions .github/CODEOWNERS
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
@@ -1,20 +1,46 @@

# This is a comment.
# 📀 Code Owners
#
# Copyright © 2021, California Institute of Technology ("Caltech").
# U.S. Government sponsorship acknowledged.
#
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are met:
#
# • Redistributions of source code must retain the above copyright notice,
# this list of conditions and the following disclaimer.
# • Redistributions must reproduce the above copyright notice, this list of
# conditions and the following disclaimer in the documentation and/or other
# materials provided with the distribution.
# • Neither the name of Caltech nor its operating division, the Jet Propulsion
# Laboratory, nor the names of its contributors may be used to endorse or
# promote products derived from this software without specific prior written
# permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
# AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
# LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
# CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
# ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
# POSSIBILITY OF SUCH DAMAGE.
#
#
# Each line is a file pattern followed by one or more owners.

#
# These owners will be the default owners for everything in
# the repo. Unless a later match takes precedence,
# @global-owner1 and @global-owner2 will be requested for
# review when someone opens a pull request.

# ***************************************************************
#
# Go to https://github.com/orgs/pds-data-dictionaries/teams to
# find out more information about your applicable team

* @NASA-PDS/pds-registry-committers
# Go to https://github.com/orgs/NASA-PDS/teams to find out about our teams

# **************************************************************
* @NASA-PDS/pds-registry-committers

# For more information on populating this file, go to
# For more information on populating this file, check out
# https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners
43 changes: 43 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
---
name: Bug report
about: Create a report to help us improve
title: "<system feature> <is not/does not> <expected behaviour>"
labels: bug, needs:triage
assignees: jordanpadams

---

## 🐛 Describe the bug
<!-- A clear and concise description of what the bug is. -->

## 📜 To Reproduce
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

## 🕵️ Expected behavior
<!-- A clear and concise description of what you expected to happen -->

## 📚 Version of Software Used
<!-- Software should have a `-V` or `--version` flag to get this information. -->

## 🩺 Test Data / Additional context
<!-- If applicable, Add test data or any other context about the problem here -->

## 🏞Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->

## 🖥 System Info
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

---
<!-- FOR DEV TEAM USE -->

## 🦄 Related requirements


## ⚙️ Engineering Details
32 changes: 32 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
---
name: Feature request
about: Suggest a new idea or new requirement for this project
title: As a <what is the user's role?> I want to <what is the user trying to accomplish?>
labels: needs:triage, requirement
assignees: jordanpadams

---

<!--
For more information on how to populate this new feature request, see the PDS Wiki on User Story Development:
https://github.com/NASA-PDS/nasa-pds.github.io/wiki/Issue-Tracking#user-story-development
-->

## 💪 Motivation
...so that I can <!-- why do you want to do this? -->

## 📖 Additional Details
<!-- Please prove any additional details or information that could help provide some context for the user story. -->

## ⚖️ Acceptance Criteria
**Given** <!-- a condition -->
**When I perform** <!-- an action -->
**Then I expect** <!-- the result -->

<!-- For Internal Dev Team Use -->

## ⚙️ Engineering Details
<!--
Provide some design / implementation details and/or a sub-task checklist as needed.
Convert issue to Epic if estimate is outside the scope of 1 sprint.
-->
59 changes: 59 additions & 0 deletions .github/ISSUE_TEMPLATE/i-t-bug-report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,59 @@
---
name: I&T Bug Report
about: Report a bug found or test case failure during PDS System I&T
title: "<system feature> <is not/does not> <expected behaviour>"
labels: I&T, bug, needs:triage
assignees: jordanpadams

---

## 🐛 Describe the bug identified during I&T
<!-- A clear and concise description of what the bug is. -->


## 🥼 Related Test Case(s)
<!-- Document related test cases below -->


## 🔁 : Related issues
<!-- Reference related issues below, e.g.
* for issues in this repo: #1 (remove back ticks)
* for issues in other repos: NASA-PDS/my_repo#1, NASA-PDS/that_repo#2
-->

---

## ➕ Additional Details
<!-- Enter additional details to support the ticket if the info above is not sufficient to replicate -->

### 📜 To Reproduce
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

### 🕵️ Expected behavior
<!-- A clear and concise description of what you expected to happen -->

### 📚 Version of Software Used
<!-- Software should have a `-V` or `--version` flag to get this information. -->

### 🩺 Test Data / Additional context
<!-- If applicable, Add test data or any other context about the problem here -->

### 🏞Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->

### 🖥 System Info
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

---
<!-- FOR DEV TEAM USE -->

## 🦄 Related requirements


## ⚙️ Engineering Details
13 changes: 13 additions & 0 deletions .github/ISSUE_TEMPLATE/pds4-standards-change-request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
name: PDS4 Standards Change Request
about: Tasks related to PDS4 Standards Change Request in design and implementation
queue
title: 'CCB-xxx: Copy SCR title here'
labels: requirement, pending-scr, p.must-have, needs:triage
assignees: jordanpadams

---

**Link to SCR:** _Insert URL here to PDS CCB JIRA ticket, if available_

**SCR Details:** _Attach PDF export of issue details. If SCR design is not complete, leave blank for now_
14 changes: 14 additions & 0 deletions .github/ISSUE_TEMPLATE/vulnerability-issue.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
name: Vulnerability Issue
about: Describe security vulnerability
title: "[SECURITY] Title Here"
labels: bug, needs:triage, security
assignees: jordanpadams

---

## Vulnerability
_Describe the vulnerability_

## Software Version
_Version_
11 changes: 8 additions & 3 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,17 @@
**Summary***
## 📜 Summary

Brief summary of changes if not sufficiently described by commit messages.

**Test Data and/or Report**

## 🩺 Test Data and/or Report

One of the following should be included here:
* Reference to regression test included in code (preferred wherever reasonable)
* Attach test data here + outputs of tests

**Related Issues**

## 🧩 Related Issues

<!--
Reference related issues here and use `Fixes` or `Resolves` in order to automatically close the issue upon merge. For more information on autolinking to tickets see https://docs.github.com/en/github/writing-on-github/autolinked-references-and-urls.
Expand Down
Loading

0 comments on commit be353fd

Please sign in to comment.