Skip to content

Commit a20ce81

Browse files
authored
Merge pull request #45 from oracle/LesiaChaban-patch-1
Update documentation with the OGHO requirements
2 parents b167722 + e071eec commit a20ce81

File tree

6 files changed

+131
-9
lines changed

6 files changed

+131
-9
lines changed

CONTRIBUTING.md

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

SECURITY.md

+38
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
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+
[[email protected]][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 program. Additional
25+
information, including past advisories, is available on our [security alerts][4]
26+
page.
27+
28+
## Security-related information
29+
30+
We will provide security related information such as a threat model, considerations
31+
for secure use, or any known security issues in our documentation. Please note
32+
that labs and sample code are intended to demonstrate a concept and may not be
33+
sufficiently hardened for production use.
34+
35+
[1]: mailto:[email protected]
36+
[2]: https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html
37+
[3]: https://www.oracle.com/security-alerts/encryptionkey.html
38+
[4]: https://www.oracle.com/security-alerts/

react-starter-sites/LICENSE.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Copyright (c) 2017,2018 Oracle and/or its affiliates
1+
Copyright (c) 2017,2024 Oracle and/or its affiliates
22

33

44

@@ -26,4 +26,4 @@ The above copyright notice and either this complete permission notice or at a mi
2626

2727

2828

29-
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
29+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

react-starter-sites/README.md

+21-6
Original file line numberDiff line numberDiff line change
@@ -47,8 +47,8 @@ To create a site to show CEC content, you need to specify the source of the cont
4747

4848
You can use command `cecss export-server-content` to export all published content items from a channel, then use the generated zip file to create a site.
4949

50-
3. The live content on a CEC server
51-
50+
3. The live content on a CEC server
51+
5252
Example content has been provided in `StarterBlog_export.zip`
5353

5454
# Set up CEC Server Connection
@@ -79,7 +79,7 @@ Run command `cecss create-site -h` to see the usage:
7979

8080
```
8181
Usage: cec create-site <name>
82-
```
82+
```
8383

8484
Creates the Site <name> for the content from local or from CEC server. By default, it creates a StarterSite. Optionally specify -f <source> to create from different source.
8585

@@ -92,14 +92,14 @@ Options:
9292
--locales, -l <locales> The comma separated list of locales, the first one in the list will be the default locale for the site
9393
--help, -h Show help [boolean]
9494

95-
Examples:
96-
95+
Examples:
96+
9797
```
9898
cecss create-site NewsSite -c StarterBlog_export.zip
9999
cecss create-site NewsSite -f ~/Downloads/ReactSiteTemplate.zip -c ~/Downloads/NewsTemplate.zip
100100
cecss create-site BlogSite -s -n Blog
101101
cecss create-site BlogSite -s -n Blog -t Blog,Author
102-
cecss create-site NewsSite -c ~/Downloads/NewsTemplate.zip -l fr-FR,it-IT,de-DE
102+
cecss create-site NewsSite -c ~/Downloads/NewsTemplate.zip -l fr-FR,it-IT,de-DE
103103
cecss create-site BlogSite -s -n Blog -l en-US,zh-CN
104104
```
105105

@@ -376,3 +376,18 @@ For each field object, we support following tags
376376
| `{{__render.reference}}` | a boolean flag to indicate the field is a reference to another item, you can render this field as a link pointing to the referenced item |
377377

378378
When create site template zip file, make sure not to include the top level folder.
379+
380+
## Contributing
381+
382+
This project welcomes contributions from the community. Before submitting a pull request, please [review our contribution guide](../CONTRIBUTING.md)
383+
384+
## Security
385+
386+
Please consult the [security guide](../SECURITY.md) for our responsible security vulnerability disclosure process
387+
388+
## License
389+
390+
Copyright (c) 2019, 2024 Oracle and/or its affiliates.
391+
392+
Released under the Universal Permissive License v1.0 as shown at
393+
<https://oss.oracle.com/licenses/upl/>.

sites/LICENSE.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Copyright (c) 2019, 2022 Oracle and/or its affiliates
1+
Copyright (c) 2019, 2024 Oracle and/or its affiliates
22

33

44

sites/README.MD

+14
Original file line numberDiff line numberDiff line change
@@ -102,4 +102,18 @@ Instructions on how to setup the IAM application for headless CLI are [here](doc
102102
## Using an IDCS Application to access CEC Instance to have a CLI without Chromium popup for Authentication
103103
Instructions on how to setup the IDCS application for headless CLI are [here](doc/IDCS-App.md)
104104

105+
## Contributing
106+
107+
This project welcomes contributions from the community. Before submitting a pull request, please [review our contribution guide](../CONTRIBUTING.md)
108+
109+
## Security
110+
111+
Please consult the [security guide](../SECURITY.md) for our responsible security vulnerability disclosure process
112+
113+
## License
114+
115+
Copyright (c) 2019, 2024 Oracle and/or its affiliates.
116+
117+
Released under the Universal Permissive License v1.0 as shown at
118+
<https://oss.oracle.com/licenses/upl/>.
105119

0 commit comments

Comments
 (0)