|
| 1 | + |
| 2 | +# Contributing to application support center |
| 3 | + |
| 4 | +Thank you for your interest in contributing to application support center. |
| 5 | + |
| 6 | +There are many ways in which you can contribute beyond writing code. The goal of this document is to provide a high-level overview of how you can get involved. |
| 7 | + |
| 8 | +## Asking Questions |
| 9 | + |
| 10 | +Have a question? Please create an issue and tag it appropriately. Your well-worded question will serve as a resource to others searching for help. |
| 11 | + |
1 | 12 | ## Code of Conduct |
2 | 13 |
|
3 | 14 | This project and everyone participating in it is governed by the [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [paul.aschmann@sap.com](mailto:paul.aschmann@sap.com). |
4 | 15 |
|
5 | 16 | ## Report Issues |
6 | 17 |
|
7 | | -To report an bug, or make a feature suggestion, please use the Issues section of this repository. |
| 18 | +To report a bug or make a feature suggestion, please use the Issues section of this repository. Here's how you can make reporting your issue as effective as possible. |
| 19 | + |
| 20 | + |
| 21 | +### Look For an Existing Issue |
| 22 | + |
| 23 | +Before you create a new issue, please search in [open issues](https://https://github.com/SAP/application-support-center/issues) to see if the issue or feature request has been created already. We have listed some "big ideas" in the [projects section](https://github.com/SAP/application-support-center/projects) of GitHub. |
| 24 | + |
| 25 | +If you find your issue already exists, make relevant comments and add your [reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). Use a reaction in place of a "+1" comment: |
| 26 | + |
| 27 | +* 👍 - upvote |
| 28 | +* 👎 - downvote |
| 29 | + |
| 30 | +If you cannot find an existing issue that describes your bug or feature, create a new issue using the guidelines below. |
| 31 | + |
| 32 | +### Writing Good Bug Reports and Feature Requests |
| 33 | + |
| 34 | +File a single issue per problem and feature request. Do not enumerate multiple bugs or feature requests in the same issue. |
| 35 | + |
| 36 | +Please do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar but have different causes. |
| 37 | + |
| 38 | +The more information you can provide, the more likely someone will be successful at reproducing the issue and finding a fix. |
| 39 | + |
| 40 | +Please include the following with each issue: |
| 41 | + |
| 42 | +* Your operating system |
| 43 | + |
| 44 | +* Browser and version |
| 45 | + |
| 46 | +* Reproducible steps (1... 2... 3...) that cause the issue |
| 47 | + |
| 48 | +* What you expected to see, versus what you actually saw |
| 49 | + |
| 50 | +* Images, animations, or a link to a video showing the issue occurring |
| 51 | + |
| 52 | +* A code snippet that demonstrates the issue or a link to a code repository the developers can easily pull down to recreate the issue locally |
| 53 | + |
| 54 | +* Errors from the Dev Tools Console (open from the menu: Help > Toggle Developer Tools) |
| 55 | + |
| 56 | +### Final Checklist |
| 57 | + |
| 58 | +Please remember to do the following: |
| 59 | + |
| 60 | +* [ ] Search the issue repository to ensure your report is a new issue |
| 61 | + |
| 62 | +* [ ] Recreate the issue |
| 63 | + |
| 64 | +* [ ] Simplify your code around the issue to better isolate the problem |
8 | 65 |
|
9 | 66 | ## Contribute Code |
10 | 67 |
|
11 | | -We welcome external contributions, please fork the code and submit a pull request. Please note: for legal reasons we request that contributers accept a DCO - Please see below. |
| 68 | +We welcome external contributions. Please fork the code and submit a pull request. Please note: for legal reasons, and we request that contributors accept a DCO - Please see below. |
12 | 69 |
|
13 | 70 | ## Developer Certificate of Origin (DCO) |
14 | 71 |
|
15 | | -Due to legal reasons, contributors will be asked to accept a DCO before they submit the first pull request to this projects, this happens in an automated fashion during the submission process. SAP uses [the standard DCO text of the Linux Foundation](https://developercertificate.org/). |
| 72 | +Due to legal reasons, contributors will be asked to accept a DCO before submitting the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses [the standard DCO text of the Linux Foundation](https://developercertificate.org/). |
| 73 | + |
| 74 | +## Thank You! |
| 75 | + |
| 76 | +Your contributions to open source, large or small, make great projects like this possible. Thank you for taking the time to contribute. |
0 commit comments