github/zfssa-csi-driver
1
0
Fork 0
mirror of https://github.com/oracle/zfssa-csi-driver.git synced 2025-09-09 16:49:41 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #9 from oracle/spavlusieva-patch-1

Browse Source 
Update CONTRIBUTING.md and README.md
This commit is contained in:
Paul Monday
2023-02-09 06:10:59 -07:00
committed by GitHub
parent 01afd3ee01 ac5af51e7c
commit 3eff2a6463
3 changed files with 45 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
CONTRIBUTING.md
View File

@@ -5,7 +5,7 @@ Oracle welcomes contributions to this repository from anyone. If you want to sub
## Contributing to the zfssa-csi-driver repository ## Contributing to the zfssa-csi-driver repository
Pull requests can be made under Pull requests can be made under
[The Oracle Contributor Agreement](https://www.oracle.com/technetwork/community/oca-486395.html) (OCA). [The Oracle Contributor Agreement](https://oca.opensource.oracle.com) (OCA).
For pull requests to be accepted, the bottom of your commit message must have For pull requests to be accepted, the bottom of your commit message must have
the following line using your name and e-mail address as it appears in the the following line using your name and e-mail address as it appears in the
@@ -36,3 +36,10 @@ by your fix.
what your changes are meant to do and provide simple steps on how to validate 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. 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. We will assign the pull request to 2-3 people for review before it is merged.
## Code of conduct
Follow the [Golden Rule](https://en.wikipedia.org/wiki/Golden_Rule). If you'd
like more specific guidelines, see the [Contributor Covenant Code of Conduct][COC].
[COC]: https://www.contributor-covenant.org/version/1/4/code-of-conduct/

7
README.md
View File

@@ -104,3 +104,10 @@ this driver.
## Contributing ## Contributing
See [CONTRIBUTING](./CONTRIBUTING.md) for details. See [CONTRIBUTING](./CONTRIBUTING.md) for details.
## License
Copyright (c) 2021 Oracle and/or its affiliates.
Released under the Universal Permissive License v1.0 as shown at
<https://oss.oracle.com/licenses/upl/>.

39
SECURITY.md
View File

@@ -1,17 +1,38 @@
# Reporting Security Vulnerabilities # Reporting security vulnerabilities
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. 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.
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. 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][1] preferably with a proof of concept. Please review
some additional information on [how to report security vulnerabilities to Oracle][2].
We encourage people who contact Oracle Security to use email encryption using
[our encryption key][3].
We ask that you do not use other channels or contact project contributors directly. We ask that you do not use other channels or contact the project maintainers
directly.
Non-vulnerability related security issues such as new great new ideas for security features are welcome on GitHub Issues. Non-vulnerability related security issues including ideas for new or improved
security features are welcome on GitHub Issues.
## Security Updates, Alerts and Bulletins ## Security updates, alerts and bulletins
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. 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][3] program. Additional
information, including past advisories, is available on our [security alerts][4]
page.
## Security-Related Information ## Security-related information
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. 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.
[1]: mailto:secalert_us@oracle.com
[2]: https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html
[3]: https://www.oracle.com/security-alerts/encryptionkey.html
[4]: https://www.oracle.com/security-alerts/