|
1 | 1 | # Contributing to the Oracle Cloud Infrastructure Java SDK |
2 | 2 |
|
3 | | -*Copyright (c) 2016, 2024, Oracle and/or its affiliates. All rights reserved. |
| 3 | +*Copyright (c) 2016, 2020, Oracle and/or its affiliates. All rights reserved. |
4 | 4 | This software is dual-licensed to you under the Universal Permissive License (UPL) 1.0 as shown at https://oss.oracle.com/licenses/upl |
5 | 5 | or Apache License 2.0 as shown at http://www.apache.org/licenses/LICENSE-2.0. You may choose either license.* |
6 | 6 |
|
7 | | -We welcome your contributions! There are multiple ways to contribute. |
| 7 | +Pull requests can be made under |
| 8 | +[The Oracle Contributor Agreement](https://www.oracle.com/technetwork/community/oca-486395.html) |
| 9 | +(OCA). |
8 | 10 |
|
9 | | -## Opening issues |
| 11 | +For pull requests to be accepted, the bottom of |
| 12 | +your commit message must have the following line using your name and |
| 13 | +e-mail address as it appears in the OCA Signatories list. |
10 | 14 |
|
11 | | -For bugs or enhancement requests, please file a GitHub issue unless it's |
12 | | -security related. When filing a bug remember that the better written the bug is, |
13 | | -the more likely it is to be fixed. If you think you've found a security |
14 | | -vulnerability, do not raise a GitHub issue and follow the instructions in our |
15 | | -[security policy](./SECURITY.md). |
16 | | - |
17 | | -## Contributing code |
18 | | - |
19 | | -We welcome your code contributions. Before submitting code via a pull request, |
20 | | -you will need to have signed the [Oracle Contributor Agreement][OCA] (OCA) and |
21 | | -your commits need to include the following line using the name and e-mail |
22 | | -address you used to sign the OCA: |
23 | | - |
24 | | -```text |
| 15 | +``` |
25 | 16 | Signed-off-by: Your Name <[email protected]> |
26 | 17 | ``` |
27 | 18 |
|
28 | | -This can be automatically added to pull requests by committing with `--sign-off` |
29 | | -or `-s`, e.g. |
| 19 | +This can be automatically added to pull requests by committing with: |
30 | 20 |
|
31 | | -```text |
32 | | -git commit --signoff |
33 | 21 | ``` |
| 22 | +git commit --signoff |
| 23 | +```` |
34 | 24 |
|
35 | | -Only pull requests from committers that can be verified as having signed the OCA |
36 | | -can be accepted. |
37 | | - |
38 | | -## Pull request process |
39 | | - |
40 | | -1. Ensure there is an issue created to track and discuss the fix or enhancement |
41 | | - you intend to submit. |
42 | | -1. Fork this repository. |
43 | | -1. Create a branch in your fork to implement the changes. We recommend using |
44 | | - the issue number as part of your branch name, e.g. `1234-fixes`. |
45 | | -1. Ensure that any documentation is updated with the changes that are required |
46 | | - by your change. |
47 | | -1. Ensure that any samples are updated if the base image has been changed. |
48 | | -1. Submit the pull request. *Do not leave the pull request blank*. Explain exactly |
49 | | - what your changes are meant to do and provide simple steps on how to validate. |
50 | | - your changes. Ensure that you reference the issue you created as well. |
51 | | -1. We will assign the pull request to 2-3 people for review before it is merged. |
52 | | - |
53 | | -## Code of conduct |
54 | | - |
55 | | -Follow the [Golden Rule](https://en.wikipedia.org/wiki/Golden_Rule). If you'd |
56 | | -like more specific guidelines, see the [Contributor Covenant Code of Conduct][COC]. |
57 | | - |
58 | | -[OCA]: https://oca.opensource.oracle.com |
59 | | -[COC]: https://www.contributor-covenant.org/version/1/4/code-of-conduct/ |
| 25 | +Only pull requests from committers that can be verified as having |
| 26 | +signed the OCA can be accepted. |
0 commit comments