Skip to content

Commit bda30b1

Browse files
author
Thomas Mahlberg
committed
Added mandatory files
1 parent 19bdb31 commit bda30b1

File tree

5 files changed

+132
-0
lines changed

5 files changed

+132
-0
lines changed

CODEOWNERS

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
@github/data-engineering

CODE_OF_CONDUCT.md

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, gender identity and expression, level of experience,
9+
nationality, personal appearance, race, religion, or sexual identity and
10+
orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at opensource@github.com. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at [http://contributor-covenant.org/version/1/4][version]
72+
73+
[homepage]: http://contributor-covenant.org
74+
[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
## Contributing
2+
3+
[fork]: https://github.com/github/KustoSchemaTools/fork
4+
[pr]: https://github.com/github/KustoSchemaTools/compare
5+
[style]: https://github.com/dotnet/runtime/blob/main/docs/coding-guidelines/coding-style.md
6+
[code-of-conduct]: CODE_OF_CONDUCT.md
7+
8+
Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
9+
10+
Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](LICENSE.md).
11+
12+
Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
13+
14+
## Prerequisites for running and testing code
15+
16+
These are one time installations required to be able to test your changes locally as part of the pull request (PR) submission process.
17+
18+
1. [Install .net 6](https://learn.microsoft.com/en-us/dotnet/core/install/)
19+
1. Get an IDE and set it up for C# development. We use [Visual Studio](https://visualstudio.microsoft.com/) or [VS Code](https://code.visualstudio.com/), but feel free to pick the IDE of your choice.
20+
21+
## Submitting a pull request
22+
23+
1. [Fork][fork] and clone the repository
24+
1. Make sure the tests pass on your machine
25+
1. Make sure you follow the style guide
26+
1. Create a new branch: `git checkout -b my-branch-name`
27+
1. Make your change, add tests, and make sure all tests still pass
28+
1. Make sure you follow the style guide
29+
1. Push to your fork and [submit a pull request][pr]
30+
1. Pat yourself on the back and wait for your pull request to be reviewed and merged.
31+
32+
Here are a few things you can do that will increase the likelihood of your pull request being accepted:
33+
34+
- Follow the [style guide][https://github.com/dotnet/runtime/blob/main/docs/coding-guidelines/coding-style.md].
35+
- Write tests.
36+
- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
37+
- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
38+
39+
## Resources
40+
41+
- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
42+
- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
43+
- [GitHub Help](https://help.github.com)

SECURITY.md

Whitespace-only changes.

SUPPORT.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
2+
# Support
3+
4+
## How to file issues and get help
5+
6+
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.
7+
8+
For help or questions about using this project, please use discussions.
9+
10+
KustoSchemaTools is under active development and maintained by GitHub staff and the community. We will do our best to respond to support, feature requests, and community questions in a timely manner.
11+
12+
## GitHub Support Policy
13+
14+
Support for this project is limited to the resources listed above.

0 commit comments

Comments
 (0)