Skip to content

Commit aaa0a6d

Browse files
bkeryanbkeryan
authored
Initial commit
0 parents  commit aaa0a6d

File tree

6 files changed

+128
-0
lines changed

6 files changed

+128
-0
lines changed

‎.github/CODEOWNERS‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# Default code owner for \<reponame\>
2+
benmont #replace for \<reponame\>

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
### What does this Pull Request accomplish?
2+
3+
TODO: Include high-level description of the changes in this pull request.
4+
5+
### Why should this Pull Request be merged?
6+
7+
TODO: Justify why this contribution should be part of the project.
8+
9+
### What testing has been done?
10+
11+
TODO: Detail what testing has been done to ensure this submission meets requirements.

‎CONTRIBUTING.md‎

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
# Contributing to \<reponame\>
2+
3+
Contributions to \<reponame\> are welcome from all!
4+
5+
\<reponame\> is managed via [git](https://git-scm.com), with the canonical upstream
6+
repository hosted on [GitHub](https://github.com/ni/<reponame>/).
7+
8+
\<reponame\> follows a pull-request model for development. If you wish to
9+
contribute, you will need to create a GitHub account, fork this project, push a
10+
branch with your changes to your project, and then submit a pull request.
11+
12+
Please remember to sign off your commits (e.g., by using `git commit -s` if you
13+
are using the command line client). This amends your git commit message with a line
14+
of the form `Signed-off-by: Name Lastname <name.lastmail@emailaddress.com>`. Please
15+
include all authors of any given commit into the commit message with a
16+
`Signed-off-by` line. This indicates that you have read and signed the Developer
17+
Certificate of Origin (see below) and are able to legally submit your code to
18+
this repository.
19+
20+
See [GitHub's official documentation](https://help.github.com/articles/using-pull-requests/) for more details.
21+
22+
# Getting Started
23+
24+
- TODO: include build steps here.
25+
26+
# Testing
27+
28+
- TODO: include testing steps here.
29+
30+
# Developer Certificate of Origin (DCO)
31+
32+
Developer's Certificate of Origin 1.1
33+
34+
By making a contribution to this project, I certify that:
35+
36+
(a) The contribution was created in whole or in part by me and I
37+
have the right to submit it under the open source license
38+
indicated in the file; or
39+
40+
(b) The contribution is based upon previous work that, to the best
41+
of my knowledge, is covered under an appropriate open source
42+
license and I have the right under that license to submit that
43+
work with modifications, whether created in whole or in part
44+
by me, under the same open source license (unless I am
45+
permitted to submit under a different license), as indicated
46+
in the file; or
47+
48+
(c) The contribution was provided directly to me by some other
49+
person who certified (a), (b) or (c) and I have not modified
50+
it.
51+
52+
(d) I understand and agree that this project and the contribution
53+
are public and that a record of the contribution (including all
54+
personal information I submit with it, including my sign-off) is
55+
maintained indefinitely and may be redistributed consistent with
56+
this project or the open source license(s) involved.
57+
58+
(taken from [developercertificate.org](https://developercertificate.org/))
59+
60+
See [LICENSE](https://github.com/ni/<reponame>/blob/main/LICENSE)
61+
for details about how \<reponame\> is licensed.

‎LICENSE‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
Copyright (c) 2022, National Instruments Corp.
2+
3+
Permission is hereby granted, free of charge, to any person obtaining
4+
a copy of this software and associated documentation files (the
5+
"Software"), to deal in the Software without restriction, including
6+
without limitation the rights to use, copy, modify, merge, publish,
7+
distribute, sublicense, and/or sell copies of the Software, and to
8+
permit persons to whom the Software is furnished to do so, subject to
9+
the following conditions:
10+
11+
The above copyright notice and this permission notice shall be included
12+
in all copies or substantial portions of the Software.
13+
14+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
15+
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
16+
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
17+
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
18+
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
19+
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
20+
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

‎README.md‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# GitHub Repo Template
2+
3+
GitHub Repo Template is a template for creation of open source projects made
4+
available on GitHub. It includes a permissive open source license, a developer
5+
certificate of origin, and a pull request template. This provides everything
6+
necessary to have a properly licensed open source project.
7+
8+
## Using GitHub Repo Template
9+
10+
1. Clone or download this repository.
11+
2. Copy its contents into your project (including the hidden .github directory).
12+
3. Customize each file to suit your project's needs (including the README). Look through the files for "TODO" and \<reponame\>, and replace with content appropriate to your project.
13+
4. (Optional) Check out [GitHub Template Guidelines](https://github.com/cezaraugusto/github-template-guidelines) for ideas about how to customize your project.
14+
15+
TODO: describe a project in detail, what it does, how to use it, etc.

‎SECURITY.md‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
<!-- Begin NI SECURITY.md V1.0 -->
2+
3+
# Security
4+
5+
NI views the security of our software products as an important part of our commitment to our users. This includes source code repositories managed through the [NI](https://github.com/ni) GitHub organization.
6+
7+
## Reporting Security Issues
8+
9+
We encourage you to report security vulnerabilities to us privately so we can follow the principle of [Coordinated Vulnerability Disclosure (CVD)](https://vuls.cert.org/confluence/display/CVD). This allows us time to thoroughly investigate security issues and publicly disclose them when appropriate.
10+
11+
**Please do not report security vulnerabilities through public GitHub issues.**
12+
13+
Instead, please report them by sending an email to [security@ni.com](mailto:security@ni.com) with sufficient details about the type of issue, the impact of the issue, and how to reproduce the issue. You may use the [NI PGP key](https://www.ni.com/en/support/security/pgp.html) to encrypt any sensitive communications you send to us. When you notify us of a potential security issue, our remediation process includes acknowledging receipt and coordinating any necessary response activities with you.
14+
15+
## Learn More
16+
17+
To learn more about NI Security, please see [https://ni.com/security](https://ni.com/security)
18+
19+
<!-- End NI SECURITY.md -->

0 commit comments

Comments
 (0)