You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-11Lines changed: 17 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ The [current release of the operator](https://github.com/oracle/weblogic-kuberne
29
29
This release was published on September 24, 2021.
30
30
***
31
31
32
-
# Documentation
32
+
##Documentation
33
33
34
34
Documentation for the operator is [available here](https://oracle.github.io/weblogic-kubernetes-operator).
35
35
@@ -38,7 +38,7 @@ information and a [Quick Start](https://oracle.github.io/weblogic-kubernetes-ope
38
38
39
39
Documentation for prior releases of the operator: [2.5.0](https://oracle.github.io/weblogic-kubernetes-operator/2.5/), [2.6.0](https://oracle.github.io/weblogic-kubernetes-operator/2.6/), [3.0.x](https://oracle.github.io/weblogic-kubernetes-operator/3.0/), [3.1.x](https://oracle.github.io/weblogic-kubernetes-operator/3.1/), and [3.2.x](https://oracle.github.io/weblogic-kubernetes-operator/3.2/).
40
40
41
-
# Backward compatibility guidelines
41
+
##Backward compatibility guidelines
42
42
43
43
The 2.0 release introduced some breaking changes and did not maintain compatibility with previous releases.
44
44
@@ -48,26 +48,24 @@ by the operator Helm chart, Kubernetes resources created by the operator, and th
48
48
maintain compatibility for three releases, except in the case of a clearly communicated deprecated feature, which will be
49
49
maintained for one release after a replacement is available.
50
50
51
-
# Need more help? Have a suggestion? Come and say, "Hello!"
51
+
##Need more help? Have a suggestion? Come and say, "Hello!"
52
52
53
53
We have a **public Slack channel** where you can get in touch with us to ask questions about using the operator or give us feedback
54
54
or suggestions about what features and improvements you would like to see. We would love to hear from you. To join our channel,
55
55
please [visit this site to get an invitation](https://weblogic-slack-inviter.herokuapp.com/). The invitation email will include
56
56
details of how to access our Slack workspace. After you are logged in, please come to `#operator` and say, "hello!"
57
57
58
-
# Contributing to the operator
58
+
##Contributing to the operator
59
59
60
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
61
62
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
63
64
-
If you have any questions about a possible submission, feel free to open an issue too.
64
+
### Contributing to the WebLogic Kubernetes Operator repository
65
65
66
-
## Contributing to the WebLogic Kubernetes Operator repository
66
+
Before submitting a pull request, please [review our contribution guide](./CONTRIBUTING.md).
67
67
68
-
Pull requests can be made under The Oracle Contributor Agreement (OCA), which is available at [https://www.oracle.com/technetwork/community/oca-486395.html](https://www.oracle.com/technetwork/community/oca-486395.html).
69
-
70
-
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.
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.
71
69
72
70
```
73
71
Signed-off-by: Your Name <you@example.org>
@@ -81,14 +79,22 @@ git commit --signoff
81
79
82
80
Only pull requests from committers that can be verified as having signed the OCA can be accepted.
83
81
84
-
## Pull request process
82
+
###Pull request process
85
83
86
84
* Fork the repository.
87
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`.
88
86
* Ensure that any documentation is updated with the changes that are required by your fix.
89
87
* Ensure that any samples are updated if the base image has been changed.
90
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.
91
89
92
-
## Introducing a new dependency
90
+
###Introducing a new dependency
93
91
94
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.
93
+
94
+
95
+
## License
96
+
97
+
Copyright (c) 2017, 2021 Oracle and/or its affiliates.
98
+
99
+
Released under the Universal Permissive License v1.0 as shown at
Oracle values the independent security research community and believes that responsible disclosure of security vulnerabilities helps us ensure the security and privacy of all our users.
4
-
5
-
Please do NOT raise a GitHub Issue to report a security vulnerability. If you believe you have found a security vulnerability, please submit a report to secalert_us@oracle.com preferably with a proof of concept. We provide additional information on [how to report security vulnerabilities to Oracle](https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html) which includes public encryption keys for secure email.
6
-
7
-
We ask that you do not use other channels or contact project contributors directly.
8
-
9
-
Non-vulnerability related security issues such as new great new ideas for security features are welcome on GitHub Issues.
10
-
11
-
## Security Updates, Alerts and Bulletins
12
-
13
-
Security updates will be released on a regular cadence. Many of our projects will typically release security fixes in conjunction with the [Oracle Critical Patch Update](https://www.oracle.com/security-alerts/) program. Security updates are released on the Tuesday closest to the 17th day of January, April, July and October. A pre-release announcement will be published on the Thursday preceding each release. Additional information, including past advisories, is available on our [Security Alerts](https://www.oracle.com/security-alerts/) page.
14
-
15
-
## Security-Related Information
16
-
17
-
We will provide security related information such as a threat model, considerations for secure use, or any known security issues in our documentation. Please note that labs and sample code are intended to demonstrate a concept and may not be sufficiently hardened for production use.
18
-
1
+
# Reporting security vulnerabilities
2
+
3
+
Oracle values the independent security research community and believes that
4
+
responsible disclosure of security vulnerabilities helps us ensure the security
5
+
and privacy of all our users.
6
+
7
+
Please do NOT raise a GitHub Issue to report a security vulnerability. If you
8
+
believe you have found a security vulnerability, please submit a report to
9
+
[secalert_us@oracle.com][1] preferably with a proof of concept. Please review
10
+
some additional information on [how to report security vulnerabilities to Oracle][2].
11
+
We encourage people who contact Oracle Security to use email encryption using
12
+
[our encryption key][3].
13
+
14
+
We ask that you do not use other channels or contact the project maintainers
15
+
directly.
16
+
17
+
Non-vulnerability related security issues including ideas for new or improved
18
+
security features are welcome on GitHub Issues.
19
+
20
+
## Security updates, alerts and bulletins
21
+
22
+
Security updates will be released on a regular cadence. Many of our projects
23
+
will typically release security fixes in conjunction with the
24
+
[Oracle Critical Patch Update][3] program. Security updates are released on the
25
+
Tuesday closest to the 17th day of January, April, July and October. A pre-release
26
+
announcement will be published on the Thursday preceding each release. Additional
27
+
information, including past advisories, is available on our [security alerts][4]
28
+
page.
29
+
30
+
## Security-related information
31
+
32
+
We will provide security related information such as a threat model, considerations
33
+
for secure use, or any known security issues in our documentation. Please note
34
+
that labs and sample code are intended to demonstrate a concept and may not be
0 commit comments