Suborbital-Systems/ReadySetGit
2
0
Fork 0
Code Pull Requests Packages Projects Releases Activity

Fix linter warnings

Browse Source
This commit is contained in:
William Sandner 2021-08-01 14:47:55 +02:00
parent bd91fa808d
commit 70a43d171f
6 changed files with 19 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Feature-Set.md
View File

@ -1,3 +1,4 @@
<!-- markdownlint-disable-next-line MD041 -->
##### Project ##### Project
::PROJECT-NAME ::PROJECT-NAME
@ -70,7 +71,7 @@ consider estimated effort and risk.*
### Features by Release and Risk ### Features by Release and Risk
- ::Release 1.0 - ::Release 1.0
- ::[F-00](Features#f-00_site_configurtion) Safe : Site configuration - ::[F-00](Features#f-00_site_configuration) Safe : Site configuration
- ::[F-01](Features#f-01_user_registration) Safe : User registration - ::[F-01](Features#f-01_user_registration) Safe : User registration
- ::[F-21](Features#f-21_feature_name) Safe : NAME OF FEATURE - ::[F-21](Features#f-21_feature_name) Safe : NAME OF FEATURE
- ::[F-31](Features#f-31_feature_name) 1-Risk : NAME OF FEATURE - ::[F-31](Features#f-31_feature_name) 1-Risk : NAME OF FEATURE

1
Features.md
View File

@ -1,3 +1,4 @@
<!-- markdownlint-disable-next-line MD041 -->
##### Project ##### Project
::PROJECT-NAME ::PROJECT-NAME

1
Glossary-Standard-Terms.md
View File

@ -1,3 +1,4 @@
<!-- markdownlint-disable-next-line MD041 -->
**Process impact:** This file as a dictionary of standard terms defined **Process impact:** This file as a dictionary of standard terms defined
as they are used across projects. Individual projects should not need to as they are used across projects. Individual projects should not need to
edit this file. Writing out the definitions of terms and acronyms here edit this file. Writing out the definitions of terms and acronyms here

1
Glossary.md
View File

@ -1,3 +1,4 @@
<!-- markdownlint-disable-next-line MD041 -->
**Process impact:** This file as a dictionary of terms defined as they **Process impact:** This file as a dictionary of terms defined as they
are used during the project. Writing out the definitions of terms and are used during the project. Writing out the definitions of terms and
acronyms here helps keep other documents more concise and precise. A acronyms here helps keep other documents more concise and precise. A

2
Home.md
View File

@ -1,5 +1,7 @@
<!-- markdownlint-disable-next-line MD041 -->
### Mission and Scope ### Mission and Scope
<!-- markdownlint-disable-next-line MD036 -->
*TODO: Answer these questions in your own words by filling in each* *TODO: Answer these questions in your own words by filling in each*
#### What problem does this project address? #### What problem does this project address?

19
Implementation-Notes.md
View File

@ -1,14 +1,19 @@
<!-- markdownlint-disable-next-line MD041 -->
##### Project ##### Project
::[PROJECT-NAME](Home) ::[PROJECT-NAME](Home)
##### Release(s): ##### Internal Release Number
::X.Y.Z ::X.Y.Z
##### Related Documents ##### Related Documents
- [Software Requirements Specification](SRS) - [Software Requirements Specification](SRS)
- [Release notes](Release-Notes) - [Release notes](Release-Notes)
- [FAQ](FAQ) - [FAQ](FAQ)
- [Glossary](Glossary) - [Glossary](Glossary)
--- ---
**Process impact:** This document is a brief and fairly technical **Process impact:** This document is a brief and fairly technical
@ -198,11 +203,11 @@ Do these implementation notes provide enough information for operations engineer
- ::Yes, these notes have been reviewed by the operations team and - ::Yes, these notes have been reviewed by the operations team and
requested changes have been incorporated. requested changes have been incorporated.
- ::No, these notes only summarize parts of a larger - ::No, these notes only summarize parts of a larger
[operations manual](LINK-TO-OPERTIONS-MANUAL). [operations manual](LINK-TO-OPERATIONS-MANUAL).
- ::No, a member of the development team is available on-call whenever - ::No, a member of the development team is available on-call whenever
the operations team may need help. This is listed in the the operations team may need help. This is listed in the
[Resource Needs](Resource-Needs) document and in the [Resource Needs](Resource-Needs) document and in the
[on-call schedule](LINK-TO-ON-CALL-SCHEDULE). [on-call schedule](LINK-TO-ON-CALL-SCHEDULE).
Have these implementation notes been communicated to the operations and development teams and other stakeholders? Have these implementation notes been communicated to the operations and development teams and other stakeholders?
@ -210,6 +215,6 @@ Have these implementation notes been communicated to the operations and developm
- ::Yes, everyone has had a chance to review them. Feedback is welcome. - ::Yes, everyone has had a chance to review them. Feedback is welcome.
- ::Yes, it has been posted to the project website. - ::Yes, it has been posted to the project website.
- ::No, some developers or operations engineers are not aware of - ::No, some developers or operations engineers are not aware of
this document. This is a risk that is noted in the this document. This is a risk that is noted in the
[Risk Management](Project-Plan#risk-management) section of the [Risk Management](Project-Plan#risk-management) section of the
[Project Plan](Project-Plan). [Project Plan](Project-Plan).