Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 07219cc

Browse files
author
Prakash Surya
committed
Initial commit
0 parents  commit 07219cc

File tree

7 files changed

+247
-0
lines changed

7 files changed

+247
-0
lines changed

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: '"[DATE] [BUG]"'
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
** Expected Behavior**
11+
Describe what should have happened.
12+
13+
** Actual Behavior**
14+
Describe what actually happened.
15+
16+
**Steps To Reproduce the Problem**
17+
Describe in as much detail as possible how to reproduce the problem.
18+
19+
Steps to reproduce the behavior:
20+
1. Go to '...'
21+
2. Click on '....'
22+
3. Scroll down to '....'
23+
4. See error
24+
25+
**Screenshots**
26+
If applicable, add screenshots to help explain your problem.
27+
28+
**Version**
29+
Indicate the relevant versions of components. This may include the package version, operating system version, or other components relevant to the project.
30+
31+
**Additional Context**
32+
Add any other context about the problem here, including additional logs or debugging information if appropriate.

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: '"[DATE]: [FEATURE NAME]"'
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is and why it is important. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen / how you might solve this problem.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any existing workarounds, alternative solutions or features you've considered, and why you think your solution is preferable.
18+
19+
20+
**Additional context**
21+
Add any other context or screenshots about the feature request here.

‎CODE_OF_CONDUCT.md‎

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

‎CONTRIBUTING.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
## Contributing
2+
1. Fork the project.
3+
1. Make your bug fix or new feature.
4+
1. Add tests for your code.
5+
1. Send a pull request.
6+
7+
Contributions must be signed as `User Name <[email protected]>`. Make sure to [set up Git with user name and email address](https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup). Bug fixes should branch from the current stable branch. New features should be based on the release branch.
8+
9+
## Contributor Agreement
10+
All contributors are required to sign the Delphix Contributor agreement prior to contributing code to an open source repository. This process is handled automatically by [cla-assistant](https://cla-assistant.io/). Simply open a pull request and a bot will automatically check to see if you have signed the latest agreement. If not, you will be prompted to do so as part of the pull request process.
11+
12+
## Code of Conduct
13+
This project operates under the Delphix Code of Conduct. By participating in this project you agree to abide by its terms.

‎README.md‎

Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
# Project Title
2+
3+
One Paragraph of project description goes here
4+
5+
## Getting Started
6+
7+
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
8+
9+
### Prerequisites
10+
11+
What things you need to install the software and how to install them
12+
13+
```
14+
Give examples
15+
```
16+
17+
### Installing
18+
19+
A step by step series of examples that tell you how to get a development env running
20+
21+
Say what the step will be
22+
23+
```
24+
Give the example
25+
```
26+
27+
And repeat
28+
29+
```
30+
until finished
31+
```
32+
33+
End with an example of getting some data out of the system or using it for a little demo
34+
35+
## Running the tests
36+
37+
Explain how to run the automated tests for this system
38+
39+
### Break down into end to end tests
40+
41+
Explain what these tests test and why
42+
43+
```
44+
Give an example
45+
```
46+
47+
### And coding style tests
48+
49+
Explain what these tests test and why
50+
51+
```
52+
Give an example
53+
```
54+
55+
## Deployment
56+
57+
Add additional notes about how to deploy this on a live system
58+
59+
## Built With
60+
61+
* [Dropwizard](http://www.dropwizard.io/1.0.2/docs/) - The web framework used
62+
* [Maven](https://maven.apache.org/) - Dependency Management
63+
* [ROME](https://rometools.github.io/rome/) - Used to generate RSS Feeds
64+
65+
## Contributing
66+
67+
Please read [CONTRIBUTING.md](https://github.com/delphix/.github/blob/master/CONTRIBUTING.md) for details on our code of conduct, and the process for submitting pull requests to us.
68+
69+
## Versioning
70+
71+
We use [SemVer](http://semver.org/) for versioning. For the versions available, see the [tags on this repository](https://github.com/your/project/tags).
72+
73+
## Authors
74+
75+
* **Joe Smith** - *Initial work* - [Company](https://github.com/Company)
76+
77+
See also the list of [contributors](https://github.com/your/project/contributors) who participated in this project.
78+
79+
## License
80+
81+
This project is licensed under the XX License - see the [LICENSE.md](LICENSE.md) file for details
82+
83+
## Acknowledgments
84+
85+
* Hat tip to anyone whose code was used
86+
* Inspiration
87+
* etc

‎SUPPORT.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
## Support
2+
This software is provided as-is, without warranty of any kind or commercial support through Delphix. See the associated license for additional details. Questions, issues, feature requests, and contributions should be directed to the community as outlined in the [Delphix Community Guidelines](https://delphix.github.io/community-guidelines.html).

‎pull_request_template.md‎

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
<!--
2+
# Context:
3+
A clear description of the high level effort that this pull request is
4+
a part of. Anyone in the organization can see this change and may not
5+
have the same context as you.
6+
-->
7+
# Problem:
8+
<!--
9+
A clear description of the problem. The problem statement should be
10+
written in terms of a specific symptom that affects users or the
11+
business. The problem statement should not be written in terms of the
12+
solution.
13+
-->
14+
# Solution:
15+
<!--
16+
A clear description of the high-level solution you have chosen. If
17+
there were other possible solutions that you considered and rejected,
18+
please mention those as well. Please do not describe implementation
19+
details when writing about the solution, those should go into the
20+
implementation section.
21+
-->
22+
# Testing
23+
<!--
24+
Describe explicitly how this change was tested. Were we able to
25+
recreate the issue? Were we able to write a test case that failed
26+
before that passes now?
27+
-->
28+
<!--
29+
# Implementation:
30+
The implementation details of the solution.
31+
-->
32+
<!--
33+
# Notes To Reviewers:
34+
Any extra information a reviewer may need to know before reviewing
35+
your change. For example here you might want to describe which files
36+
should be looked at first or which files are auto-generated.
37+
-->
38+
<!--
39+
# Deployment Plan:
40+
Some changes get more complicated and may need changes in multiple
41+
repositories or may require infrastructure changes. Describe how these
42+
changes will be smoothly deployed.
43+
-->
44+
<!--
45+
# Future work:
46+
A description of what follow up work is explicitly not being done in
47+
this change.
48+
-->
49+
<!--
50+
# Bonus:
51+
A description of extra problems you've solved in this change. Did you
52+
reformat an unrelated docstring? Point it out here
53+
-->

0 commit comments

Comments
 (0)