Skip to content

Commit 00c8bd5

Browse files
authored
Update README.md (#4103)
1 parent b084c07 commit 00c8bd5

File tree

1 file changed

+2
-34
lines changed

1 file changed

+2
-34
lines changed

README.md

Lines changed: 2 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -55,41 +55,9 @@ or suggestions about what features and improvements you would like to see. We w
5555
please [visit this site to get an invitation](https://join.slack.com/t/oracle-weblogic/shared_invite/zt-1lnz4kpci-WdY2gWfeJc5jS_a_1Z06MA). The invitation email will include
5656
details of how to access our Slack workspace. After you are logged in, please come to `#operator` and say, "hello!"
5757

58-
## Contributing to the operator
58+
## Contributing
5959

60-
Oracle welcomes contributions to this project from anyone. Contributions may be reporting an issue with the operator or submitting a pull request. Before embarking on significant development that may result in a large pull request, it is recommended that you create an issue and discuss the proposed changes with the existing developers first.
61-
62-
If you want to submit a pull request to fix a bug or enhance an existing feature, please first open an issue and link to that issue when you submit your pull request.
63-
64-
### Contributing to the WebLogic Kubernetes Operator repository
65-
66-
Before submitting a pull request, please [review our contribution guide](./CONTRIBUTING.md).
67-
68-
For pull requests to be accepted, the bottom of the commit message must have the following line, using the contributor’s name and e-mail address as it appears in the OCA Signatories List.
69-
70-
```
71-
Signed-off-by: Your Name <[email protected]>
72-
```
73-
74-
This can be automatically added to pull requests by committing with:
75-
76-
```
77-
git commit --signoff
78-
```
79-
80-
Only pull requests from committers that can be verified as having signed the OCA can be accepted.
81-
82-
### Pull request process
83-
84-
* Fork the repository.
85-
* Create a branch in your fork to implement the changes. We recommend using the issue number as part of your branch name, for example, `1234-fixes`.
86-
* Ensure that any documentation is updated with the changes that are required by your fix.
87-
* Ensure that any samples are updated if the base image has been changed.
88-
* Submit the pull request. Do not leave the pull request blank. Explain exactly what your changes are meant to do and provide simple steps on how to validate your changes. Ensure that you reference the issue you created as well. We will assign the pull request to 2-3 people for review before it is merged.
89-
90-
### Introducing a new dependency
91-
92-
Please be aware that pull requests that seek to introduce a new dependency will be subject to additional review. In general, contributors should avoid dependencies with incompatible licenses, and should try to use recent versions of dependencies. Standard security vulnerability checklists will be consulted before accepting a new dependency. Dependencies on closed-source code, including WebLogic Server, will most likely be rejected.
60+
This project welcomes contributions from the community. Before submitting a pull request, please [review our contribution guide](./CONTRIBUTING.md)
9361

9462
## Security
9563

0 commit comments

Comments
 (0)