|
| 1 | +# Contributing |
| 2 | + |
| 3 | +## Contributing In General |
| 4 | + |
| 5 | +Our project welcomes external contributions. If you have an itch, please feel |
| 6 | +free to scratch it. |
| 7 | + |
| 8 | +To contribute code or documentation, please submit a [pull request](https://github.com/ibm/open-prediction-service-hub/pulls). |
| 9 | + |
| 10 | +A good way to familiarize yourself with the codebase and contribution process is |
| 11 | +to look for and tackle low-hanging fruit in the [issue tracker](https://github.com/ibm/open-prediction-service-hub/issues). |
| 12 | +Before embarking on a more ambitious contribution, please quickly [get in touch](#communication) with us. |
| 13 | + |
| 14 | +**Note: We appreciate your effort, and want to avoid a situation where a contribution |
| 15 | +requires extensive rework (by you or by us), sits in backlog for a long time, or |
| 16 | +cannot be accepted at all!** |
| 17 | + |
| 18 | +### Proposing new features |
| 19 | + |
| 20 | +If you would like to implement a new feature, please [raise an issue](https://github.com/ibm/open-prediction-service-hub/issues) |
| 21 | +before sending a pull request so the feature can be discussed. This is to avoid |
| 22 | +you wasting your valuable time working on a feature that the project developers |
| 23 | +are not interested in accepting into the code base. |
| 24 | + |
| 25 | +### Fixing bugs |
| 26 | + |
| 27 | +If you would like to fix a bug, please [raise an issue](https://github.com/ibm/open-prediction-service-hub/issues) before sending a |
| 28 | +pull request so it can be tracked. |
| 29 | + |
| 30 | +### Merge approval |
| 31 | + |
| 32 | +The project maintainers use LGTM (Looks Good To Me) in comments on the code |
| 33 | +review to indicate acceptance. A change requires LGTMs from one of the |
| 34 | +maintainers of each component affected. |
| 35 | + |
| 36 | +For a list of the maintainers, see the [MAINTAINERS.md](MAINTAINERS.md) page. |
| 37 | + |
| 38 | +## Legal |
| 39 | + |
| 40 | +Each source file must include a license header for the Apache |
| 41 | +Software License 2.0. Using the SPDX format is the simplest approach. |
| 42 | +e.g. |
| 43 | + |
| 44 | +```text |
| 45 | +/* |
| 46 | +Copyright <holder> All Rights Reserved. |
| 47 | +
|
| 48 | +SPDX-License-Identifier: Apache-2.0 |
| 49 | +*/ |
| 50 | +``` |
| 51 | + |
| 52 | +We have tried to make it as easy as possible to make contributions. This |
| 53 | +applies to how we handle the legal aspects of contribution. We use the |
| 54 | +same approach - the [Developer's Certificate of Origin 1.1 (DCO)](https://github.com/hyperledger/fabric/blob/master/docs/source/DCO1.1.txt) - that the Linux® Kernel [community](https://elinux.org/Developer_Certificate_Of_Origin) |
| 55 | +uses to manage code contributions. |
| 56 | + |
| 57 | +We simply ask that when submitting a patch for review, the developer |
| 58 | +must include a sign-off statement in the commit message. |
| 59 | + |
| 60 | +Here is an example Signed-off-by line, which indicates that the |
| 61 | +submitter accepts the DCO: |
| 62 | + |
| 63 | +```text |
| 64 | +Signed-off-by: John Doe <[email protected]> |
| 65 | +``` |
| 66 | + |
| 67 | +You can include this automatically when you commit a change to your |
| 68 | +local git repository using the following command: |
| 69 | + |
| 70 | +```shell |
| 71 | +git commit -s |
| 72 | +``` |
| 73 | + |
| 74 | +<!-- |
| 75 | +## Communication |
| 76 | +Please feel free to connect with us by entering an issue in our [issue tracker](https://github.com/ibm/open-prediction-service-hub/issues). |
| 77 | +
|
| 78 | +## Setup |
| 79 | +**FIXME** Please add any special setup instructions for your project to help the developer |
| 80 | +become productive quickly. |
| 81 | +
|
| 82 | +## Testing |
| 83 | +**FIXME** Please provide information that helps the developer test any changes they make |
| 84 | +before submitting. |
| 85 | +
|
| 86 | +## Coding style guidelines |
| 87 | +**FIXME** Optional, but recommended: please share any specific style guidelines you might |
| 88 | +have for your project. |
| 89 | +--> |
0 commit comments