Skip to content
This repository was archived by the owner on Jul 19, 2024. It is now read-only.

Commit 4e0ebfa

Browse files
bartrbartr
committed
added template files
1 parent 704c621 commit 4e0ebfa

File tree

9 files changed

+219
-0
lines changed

9 files changed

+219
-0
lines changed

‎.github/CHANGELOG.md

+4
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
# Change Log
2+
3+
- July 2021
4+
- Initial release for Spark

‎.github/CODE_OF_CONDUCT.md

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# Microsoft Open Source Code of Conduct
2+
3+
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
4+
5+
Resources:
6+
7+
- [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/)
8+
- [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/)
9+
- Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns

‎.github/CONTRIBUTING.md

+83
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
# Contributing
2+
3+
This project welcomes contributions and suggestions. Most contributions require you to agree to a
4+
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
5+
the rights to use your contribution. For details, visit [Microsoft CLA](https://cla.microsoft.com).
6+
7+
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide
8+
a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions
9+
provided by the bot. You will only need to do this once across all repos using our CLA.
10+
11+
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
12+
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
13+
contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
14+
15+
- [Code of Conduct](#coc)
16+
- [Issues and Bugs](#issue)
17+
- [Feature Requests](#feature)
18+
- [Submission Guidelines](#submit)
19+
20+
## Code of Conduct
21+
22+
Help us keep this project open and inclusive. Please read and follow our [Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
23+
24+
## Found an Issue
25+
26+
If you find a bug in the source code or a mistake in the documentation, you can help us by
27+
[submitting an issue](#submit-issue) to the GitHub Repository. Even better, you can
28+
[submit a Pull Request](#submit-pr) with a fix.
29+
30+
## Want a Feature
31+
32+
You can *request* a new feature by [submitting an issue](#submit-issue) to the GitHub
33+
Repository. If you would like to *implement* a new feature, please submit an issue with
34+
a proposal for your work first, to be sure that we can use it.
35+
36+
- **Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).
37+
38+
## Submission Guidelines
39+
40+
### Submitting an Issue
41+
42+
Before you submit an issue, search the archive, maybe your question was already answered.
43+
44+
If your issue appears to be a bug, and hasn't been reported, open a new issue.
45+
Help us to maximize the effort we can spend fixing issues and adding new
46+
features, by not reporting duplicate issues. Providing the following information will increase the
47+
chances of your issue being dealt with quickly:
48+
49+
- **Overview of the Issue** - if an error is being thrown a non-minified stack trace helps
50+
- **Version** - what version is affected (e.g. 0.1.2)
51+
- **Motivation for or Use Case** - explain what are you trying to do and why the current behavior is a bug for you
52+
- **Browsers and Operating System** - is this a problem with all browsers?
53+
- **Reproduce the Error** - provide a live example or a unambiguous set of steps
54+
- **Related Issues** - has a similar issue been reported before?
55+
- **Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point to what might be
56+
causing the problem (line of code or commit)
57+
58+
You can file new issues by providing the above information at the corresponding repository's issues link: `https://github.com/[organization-name]/[repository-name]/issues/new]`
59+
60+
### Submitting a Pull Request (PR)
61+
62+
Before you submit your Pull Request (PR) consider the following guidelines:
63+
64+
- Search the repository `https://github.com/[organization-name]/[repository-name]/pulls` for an open or closed PR
65+
that relates to your submission. You don't want to duplicate effort.
66+
67+
- Make your changes in a new git fork:
68+
69+
- Commit your changes using a descriptive commit message
70+
- Push your fork to GitHub:
71+
- In GitHub, create a pull request
72+
- If we suggest changes then:
73+
- Make the required updates.
74+
- Rebase your fork and force push to your GitHub repository (this will update your Pull Request):
75+
76+
```shell
77+
78+
git rebase main -i
79+
git push -f
80+
81+
```
82+
83+
That's it! Thank you for your contribution!

‎.github/ISSUE_TEMPLATE/bug.md

+16
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
name: Bug report
3+
about: For reporting an issue in code or documentation for improvement
4+
title: ''
5+
labels: Bug
6+
assignees: ''
7+
8+
---
9+
10+
## Description
11+
12+
-
13+
14+
## Expected Behavior
15+
16+
-

‎.github/ISSUE_TEMPLATE/feature.md

+26
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
name: Feature Request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: Design Review, Enhancement
6+
assignees: ''
7+
8+
---
9+
10+
## Problem Statement
11+
12+
-
13+
14+
## Proposed Solution
15+
16+
-
17+
18+
## Alternative Proposals
19+
20+
-
21+
22+
## Next Steps
23+
24+
- [ ] Team consensus to proceed
25+
- [ ] Complete Design Review Template (if applicable)
26+
- [ ] Schedule Design Session

‎.github/PULL_REQUEST_TEMPLATE.md

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# Type of PR
2+
3+
- [ ] Documentation changes
4+
- [ ] Code changes
5+
- [ ] Test changes
6+
- [ ] CI-CD changes
7+
- [ ] GitHub Template changes
8+
9+
## Purpose of PR
10+
11+
## Issues Closed or Referenced
12+
13+
- Closes #issue_number (this will automatically close the issue when the PR closes)
14+
- References #issue_number (this references the issue but does not close with PR)

‎.github/SECURITY.md

+35
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
<!-- BEGIN MICROSOFT SECURITY.MD V0.0.1 BLOCK -->
2+
3+
# Security
4+
5+
Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [many more](https://opensource.microsoft.com/).
6+
7+
If you believe you have found a security vulnerability in any Microsoft-owned repository that meets Microsoft's [definition](https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383(v=technet.10)) of a security vulnerability, please report it to us as described below.
8+
9+
## Reporting Security Issues
10+
11+
**Please do not report security vulnerabilities through public GitHub issues.** Instead, please report them to the Microsoft Security Response Center at [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://technet.microsoft.com/en-us/security/dn606155).
12+
13+
You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc).
14+
15+
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
16+
17+
* Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
18+
* Full paths of source file(s) related to the manifestation of the issue
19+
* The location of the affected source code (tag/branch/commit or direct URL)
20+
* Any special configuration required to reproduce the issue
21+
* Step-by-step instructions to reproduce the issue
22+
* Proof-of-concept or exploit code (if possible)
23+
* Impact of the issue, including how an attacker might exploit the issue
24+
25+
This information will help us triage your report more quickly.
26+
27+
## Preferred Languages
28+
29+
We prefer all communications to be in English.
30+
31+
## Policy
32+
33+
Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd).
34+
35+
<!-- END MICROSOFT SECURITY.MD BLOCK -->

‎.github/SUPPORT.md

+11
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# Support
2+
3+
## How to file issues and get help
4+
5+
This project uses GitHub Issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new issue.
6+
7+
For help and questions about using this project, please open a GitHub issue.
8+
9+
## Microsoft Support Policy
10+
11+
Support for this project is limited to the resources listed above.

‎LICENSE

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

0 commit comments

Comments
 (0)