From 400e57e8ebcf4189a0589e787beb9f7f9f50928d Mon Sep 17 00:00:00 2001 From: Stefan Schmidt <stefan.schmidt@huawei.com> Date: Fri, 8 Oct 2021 22:17:04 +0200 Subject: [PATCH] README.md / CONTRIBUTING.md: Follow project rename Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com> --- CONTRIBUTING.md | 2 +- README.md | 2 +- meta-ohos-blueprints/README.md | 2 +- meta-ohos-core/README.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f926bac2..5ac8a4b0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -19,7 +19,7 @@ SPDX-License-Identifier: CC-BY-4.0 ## Overview -All Scenarios OS project handles contributions as [merge requests](https://docs.gitlab.com/ee/user/project/merge_requests/) to relevant repositories part of the All Scenarios OS [GitLab instance](https://git.ostc-eu.org/OSTC/OHOS). The flow for handling that is classic: fork-based merge requests. This means that once you have an account, you can fork any repository, create a branch with proposed changes and raise a merge request against the forked repository. More generic information you can find on the Gitlab's documentation as part of ["Merge requests workflow"](https://docs.gitlab.com/ee/development/contributing/merge_request_workflow.html). +Oniro Project handles contributions as [merge requests](https://docs.gitlab.com/ee/user/project/merge_requests/) to relevant repositories part of the Oniro Project [GitLab instance](https://git.ostc-eu.org/OSTC/OHOS). The flow for handling that is classic: fork-based merge requests. This means that once you have an account, you can fork any repository, create a branch with proposed changes and raise a merge request against the forked repository. More generic information you can find on the Gitlab's documentation as part of ["Merge requests workflow"](https://docs.gitlab.com/ee/development/contributing/merge_request_workflow.html). # REUSE compliance diff --git a/README.md b/README.md index c5de030c..3b3aca57 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ SPDX-License-Identifier: CC-BY-4.0 # meta-ohos **meta-ohos** is a collection of bitbake layers that implement the build system -support in All Scenarios OS. The build system documentation is available in the +support in Oniro Project. The build system documentation is available in the `docs` subdirectory. ## Contributing diff --git a/meta-ohos-blueprints/README.md b/meta-ohos-blueprints/README.md index d7e2e3f1..5a5dfc67 100644 --- a/meta-ohos-blueprints/README.md +++ b/meta-ohos-blueprints/README.md @@ -6,7 +6,7 @@ ## Description -This layer, `meta-ohos-blueprints`, contains build metadata for All Scenarios OS +This layer, `meta-ohos-blueprints`, contains build metadata for Oniro Project blueprints. ## Layer dependencies diff --git a/meta-ohos-core/README.md b/meta-ohos-core/README.md index fe53daa1..ab556f10 100644 --- a/meta-ohos-core/README.md +++ b/meta-ohos-core/README.md @@ -37,4 +37,4 @@ Run 'bitbake-layers add-layer /path/to/meta-ohos-core' III. Misc ========= -This layer provides recipes for the core elements of the All Scenarios OS distribution. +This layer provides recipes for the core elements of the Oniro Project distribution. -- GitLab