diff --git a/.github/ISSUE_TEMPLATE/RFC.md b/.github/ISSUE_TEMPLATE/RFC.md
index de9e51b..4a6b111 100644
--- a/.github/ISSUE_TEMPLATE/RFC.md
+++ b/.github/ISSUE_TEMPLATE/RFC.md
@@ -1,15 +1,15 @@
---
name: RFC
-about: The OpenIM RFC design template, which you should use if you have a detailed and precise feature design in mind.
+about: The kubecub RFC design template, which you should use if you have a detailed and precise feature design in mind.
title: "🔮[RFC #0000]: "
labels: "proposal,RFC,kind/feature,enhancement"
---
-# [RFC #0000] OpenIMSDK proposal template
+# [RFC #0000] kubecub proposal template
## Meta
[meta]: #meta
@@ -18,13 +18,13 @@ labels: "proposal,RFC,kind/feature,enhancement"
- Author(s): (Github usernames)
- Status: Draft
- RFC Pull Request: (leave blank)
-- OpenIMSDK Pull Request: (leave blank)
-- OpenIMSDK Issue: (leave blank)
+- kubecub Pull Request: (leave blank)
+- kubecub Issue: (leave blank)
- Supersedes: (put "N/A" unless this replaces an existing RFC, then link to that RFC)
## 📇Topics
-- [\[RFC #0000\] OpenIMSDK proposal template](#rfc-0000-openimsdk-proposal-template)
+- [\[RFC #0000\] kubecub proposal template](#rfc-0000-kubecub-proposal-template)
- [Meta](#meta)
- [📇Topics](#topics)
- [Summary](#summary)
@@ -49,7 +49,7 @@ One paragraph explanation of the feature.
## Definitions
[definitions]: #definitions
-Make a list of the definitions that may be useful for those reviewing. Include phrases and words that OpenIMSDK authors or other interested parties may not be familiar with.
+Make a list of the definitions that may be useful for those reviewing. Include phrases and words that kubecub authors or other interested parties may not be familiar with.
## Motivation
[motivation]: #motivation
@@ -64,7 +64,7 @@ Make a list of the definitions that may be useful for those reviewing. Include p
This provides a high level overview of the feature.
- Define any new terminology.
-- Define the target persona: OpenIMSDK author, OpenIMSDK user, platform operator, platform implementor, and/or project contributor.
+- Define the target persona: kubecub author, kubecub user, platform operator, platform implementor, and/or project contributor.
- Explaining the feature largely in terms of examples.
- If applicable, provide sample error messages, deprecation warnings, or migration guidance.
- If applicable, describe the differences between teaching this to existing users and new users.
@@ -79,7 +79,7 @@ The section should return to the examples given in the previous section, and exp
## Migration
[migration]: #migration
-This section should document breaks to public API and breaks in compatibility due to this RFC's proposed changes. In addition, it should document the proposed steps that one would need to take to work through these changes. Care should be give to include all applicable personas, such as platform developers, OpenIMSDK developers, OpenIMSDK users and consumers of OpenIMSDK images.
+This section should document breaks to public API and breaks in compatibility due to this RFC's proposed changes. In addition, it should document the proposed steps that one would need to take to work through these changes. Care should be give to include all applicable personas, such as platform developers, kubecub developers, kubecub users and consumers of kubecub images.
## Drawbacks
[drawbacks]: #drawbacks
@@ -108,7 +108,7 @@ Discuss prior art, both the good and bad.
## Spec. Changes (OPTIONAL)
[spec-changes]: #spec-changes
Does this RFC entail any proposed changes to the core specifications or extensions? If so, please document changes here.
-Examples of a spec. change might be new lifecycle flags, new `OpenIMSDK.toml` fields, new fields in the OpenIMSDKage label, etc.
+Examples of a spec. change might be new lifecycle flags, new `kubecub.toml` fields, new fields in the kubecubage label, etc.
This section is not intended to be binding, but as discussion of an RFC unfolds, if spec changes are necessary, they should be documented here.
## History
diff --git a/.github/ISSUE_TEMPLATE/bug-report.yaml b/.github/ISSUE_TEMPLATE/bug-report.yaml
index 2bf45ea..af51c39 100644
--- a/.github/ISSUE_TEMPLATE/bug-report.yaml
+++ b/.github/ISSUE_TEMPLATE/bug-report.yaml
@@ -1,5 +1,5 @@
name: Bug Report
-description: Report a bug encountered while operating OpenIM
+description: Report a bug encountered while operating kubecub
title: "Bug: "
labels: ["kind/bug"]
body:
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index e251e43..adbdccd 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,5 +1,5 @@
contact_links:
- name: Connect on slack
url: https://join.slack.com/t/c-ub/shared_invite/zt-1se0k2bae-lkYzz0_T~BYh3rjkvlcUqQ
- about: Support OpenIM-related requests or issues, get in touch with developers and help on slack
+ about: Support kubecub-related requests or issues, get in touch with developers and help on slack
contact_links:
\ No newline at end of file
diff --git a/.github/ISSUE_TEMPLATE/failing-test.yaml b/.github/ISSUE_TEMPLATE/failing-test.yaml
index babc75b..8621098 100644
--- a/.github/ISSUE_TEMPLATE/failing-test.yaml
+++ b/.github/ISSUE_TEMPLATE/failing-test.yaml
@@ -1,5 +1,5 @@
name: Failing Test
-description: Report continuously failing tests or jobs in OpenIM CI
+description: Report continuously failing tests or jobs in kubecub CI
title: "🤖Failing test: "
labels: kind/failing-test
body:
@@ -8,7 +8,7 @@ body:
attributes:
label: Which job are failing?
placeholder: |
- Please only use this template for submitting reports about continuously failing tests or jobs in OpenIM CI.
+ Please only use this template for submitting reports about continuously failing tests or jobs in kubecub CI.
validations:
required: true
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 31b8994..440053a 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -3,7 +3,7 @@
🫰 Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
-📇 https://github.com/OpenIMSDK/community/blob/main/CONTRIBUTING.md
+📇 https://github.com/kubecub/community/blob/main/CONTRIBUTING.md
2. Ensure you have added or ran the appropriate tests for your PR:
-->
@@ -67,6 +67,6 @@ linking directly to the master branch. This ensures that links reference a
specific point in time, rather than a document that may change over time.
In the sharers Guide, we recommend the following documents:
-1. Using GitHub RFCs template: https://github.com/OpenIMSDK/community/blob/main/0000-template.md
+1. Using GitHub RFCs template: https://github.com/kubecub/community/blob/main/0000-template.md
2. Use Google Docs OR Notion and share it with the community.
-->
\ No newline at end of file
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index ee313f0..753ee12 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -358,7 +358,7 @@ Try your best to keep every function has been tested, it keeps the function beha
+ [README.md](https://github.com/kubecub/go-project-layout/blob/main/README.md): This file includes the basic information and instructions for getting started with go-project-layout.
+ [CONTRIBUTING.md](https://github.com/kubecub/go-project-layout/blob/main/CONTRIBUTING.md): This file contains guidelines for contributing to go-project-layout's codebase, such as how to submit issues, pull requests, and code reviews.
-+ [Official Documentation](nsddd.top): This is the official documentation for go-project-layout, which includes comprehensive information on all of its features, configuration options, and troubleshooting tips.
++ [Official Documentation](https://nsddd.top): This is the official documentation for go-project-layout, which includes comprehensive information on all of its features, configuration options, and troubleshooting tips.
**Please obey the following rules to better format the docs, which would greatly improve the reading experience.**
@@ -434,7 +434,7 @@ In addition to Slack, we also offer the following ways to get in touch:
+ 
: Get in touch with us on [Gmail]([3293172751nss@gmail.com](mailto:3293172751nss@gmail.com)). If you have any questions or issues that need resolving, or any suggestions and feedback for our open source projects, please feel free to contact us via email.
-+ 
: Read our [kubecub](nsddd.top). Our kubecub is a great place to stay up-to-date with kubecub projects and trends. On the kubecub, we share our latest developments, tech trends, and other interesting information.
++ : Read our [kubecub](https://nsddd.top). Our kubecub is a great place to stay up-to-date with kubecub projects and trends. On the kubecub, we share our latest developments, tech trends, and other interesting information.
+ 
: Add [Twitter]({twitter}) . If you prefer social media, our Twitter account is a great way to stay up-to-date with kubecub project news and trends. On Twitter, we share our latest tech and trends, as well as relevant news and events.
diff --git a/api/README.md b/api/README.md
index 126dcf8..3a4eaf3 100644
--- a/api/README.md
+++ b/api/README.md
@@ -1,106 +1,8 @@
-# go-project-layout
+# `/api`
-
-
- go-project-layout
-
- ⭐️ ESG Tracker: Automated Disclosure Monitoring ⭐️
-
+OpenAPI/Swagger specs, JSON schema files, protocol definition files.
-
-
-
-
-
-
-
-
+Examples:
-
-
-
- English •
- 中文
-
-
-
-
-## Awesome features
-
-A system that monitors and tracks ESG (Environmental, Social and Governance) disclosures and ratings from various public data sources. It collects ESG data points from sources like Feishu spreadsheets and makes them available through an administrative interface.
-
-## Quickstart
-
-> **Note**: You can get started quickly with go-project-layout.
-
-
-## Contributing & Development
-
-kubecub Our goal is to build a top-level open source community. We have a set of standards, in the [Community repository](https://github.com/kubecub/community).
-
-If you'd like to contribute to this go-project-layout repository, please read our [contributor documentation](https://github.com/kubecub/go-project-layout/blob/main/CONTRIBUTING.md).
-
-
-## architecture diagram
-```mermaid
-graph LR
-
-subgraph External Services
-feishuAPI --> sheetParser
-end
-
-subgraph Sheet Parser & Manager
-sheetParser[Sheet Parser] --> versionControl
-versionControl[Version Control] --> sheetDisplay
-end
-
-subgraph Display
-sheetDisplay[Sheet Display] --> UI
-end
-
-subgraph Backend
-versionControl --> API
-end
-
-subgraph Frontend
-UI[User Interface]
-end
-
-API --> UI
-UI --> feishuAPI
-```
-
-**MVC Architecture Design:**
-```mermaid
-graph LR
-A[View] -->|1. User interaction| B(Controller)
-B -->|2. Requests data| C(Model)
-C -->|3. Returns data| B
-B -->|4. Updates view| A
-```
-
-## File Directory Description
-
-
-
-## community meeting
-
-We welcome everyone to join us and contribute to go-project-layout, whether you are new to open source or professional. We are committed to promoting an open source culture, so we offer community members neighborhood prizes and reward money in recognition of their contributions. We believe that by working together, we can build a strong community and make valuable open source tools and resources available to more people. So if you are interested in go-project-layout, please join our community and start contributing your ideas and skills!
-
-We take notes of each [biweekly meeting](https://github.com/kubecub/go-project-layout/issues/2) in [GitHub discussions](https://github.com/kubecub/go-project-layout/discussions/categories/meeting), and our minutes are written in [Google Docs](https://docs.google.com/document/d/1nx8MDpuG74NASx081JcCpxPgDITNTpIIos0DS6Vr9GU/edit?usp=sharing).
-
-go-project-layout maintains a [public roadmap](https://github.com/kubecub/community/tree/main/roadmaps). It gives a a high-level view of the main priorities for the project, the maturity of different features and projects, and how to influence the project direction.
-
-
-## License
-
-Sealer is licensed under the Apache License, Version 2.0. See [LICENSE](https://github.com/kubecub/go-project-layout/tree/main/LICENSE) for the full license text.
-
-[](https://app.fossa.com/projects/git%2Bgithub.com%2Fkubecub%2Fgo-project-layout?ref=badge_large)
-
-
-## Thanks to our contributors!
-
-
- 
-
\ No newline at end of file
+* https://github.com/kubernetes/kubernetes/tree/master/api
+* https://github.com/moby/moby/tree/master/api
\ No newline at end of file
diff --git a/pkg/README.md b/pkg/README.md
index bccaccf..96aee39 100644
--- a/pkg/README.md
+++ b/pkg/README.md
@@ -19,7 +19,6 @@ Examples:
* https://github.com/google/gvisor/tree/master/pkg
* https://github.com/google/syzkaller/tree/master/pkg
* https://github.com/perkeep/perkeep/tree/master/pkg
-* https://github.com/minio/minio/tree/master/pkg
* https://github.com/heptio/ark/tree/master/pkg
* https://github.com/argoproj/argo/tree/master/pkg
* https://github.com/heptio/sonobuoy/tree/master/pkg
diff --git a/scripts/githooks/commit-msg b/scripts/githooks/commit-msg
index 11b1d2a..7050cfd 100644
--- a/scripts/githooks/commit-msg
+++ b/scripts/githooks/commit-msg
@@ -27,18 +27,18 @@ RED="\e[31m"
ENDCOLOR="\e[0m"
printMessage() {
- printf "${YELLOW}OpenIM : $1${ENDCOLOR}\n"
+ printf "${YELLOW}kubecub : $1${ENDCOLOR}\n"
}
printSuccess() {
- printf "${GREEN}OpenIM : $1${ENDCOLOR}\n"
+ printf "${GREEN}kubecub : $1${ENDCOLOR}\n"
}
printError() {
- printf "${RED}OpenIM : $1${ENDCOLOR}\n"
+ printf "${RED}kubecub : $1${ENDCOLOR}\n"
}
-printMessage "Running the OpenIM commit-msg hook."
+printMessage "Running the kubecub commit-msg hook."
# This example catches duplicate Signed-off-by lines.
@@ -58,7 +58,7 @@ test "" = "$(grep '^Signed-off-by: ' "$1" |
if [ $? -ne 0 ]
then
- printError "Please fix your commit message to match OpenIM coding standards"
+ printError "Please fix your commit message to match kubecub coding standards"
printError "https://gist.github.com/cubxxw/126b72104ac0b0ca484c9db09c3e5694#file-githook-md"
exit 1
fi
\ No newline at end of file
diff --git a/scripts/githooks/pre-commit b/scripts/githooks/pre-commit
index 0c88404..7d5d4c0 100644
--- a/scripts/githooks/pre-commit
+++ b/scripts/githooks/pre-commit
@@ -21,18 +21,18 @@ RED="\e[31m"
ENDCOLOR="\e[0m"
printMessage() {
- printf "${YELLOW}OpenIM : $1${ENDCOLOR}\n"
+ printf "${YELLOW}kubecub : $1${ENDCOLOR}\n"
}
printSuccess() {
- printf "${GREEN}OpenIM : $1${ENDCOLOR}\n"
+ printf "${GREEN}kubecub : $1${ENDCOLOR}\n"
}
printError() {
- printf "${RED}OpenIM : $1${ENDCOLOR}\n"
+ printf "${RED}kubecub : $1${ENDCOLOR}\n"
}
-printMessage "Running local OpenIM pre-commit hook."
+printMessage "Running local kubecub pre-commit hook."
# flutter format .
# https://gist.github.com/cubxxw/126b72104ac0b0ca484c9db09c3e5694#file-githook-md
diff --git a/scripts/githooks/pre-push b/scripts/githooks/pre-push
index 73c86e0..1d9d67c 100644
--- a/scripts/githooks/pre-push
+++ b/scripts/githooks/pre-push
@@ -11,18 +11,18 @@ RED="\e[31m"
ENDCOLOR="\e[0m"
printMessage() {
- printf "${YELLOW}OpenIM : $1${ENDCOLOR}\n"
+ printf "${YELLOW}kubecub : $1${ENDCOLOR}\n"
}
printSuccess() {
- printf "${GREEN}OpenIM : $1${ENDCOLOR}\n"
+ printf "${GREEN}kubecub : $1${ENDCOLOR}\n"
}
printError() {
- printf "${RED}OpenIM : $1${ENDCOLOR}\n"
+ printf "${RED}kubecub : $1${ENDCOLOR}\n"
}
-printMessage "Running local OpenIM pre-push hook."
+printMessage "Running local kubecub pre-push hook."
if [[ `git status --porcelain` ]]; then
printError "This script needs to run against committed code only. Please commit or stash you changes."
diff --git a/web/README.md b/web/README.md
index 126dcf8..a5cb800 100644
--- a/web/README.md
+++ b/web/README.md
@@ -1,106 +1,3 @@
-# go-project-layout
+# `/web`
-
-
- go-project-layout
-
- ⭐️ ESG Tracker: Automated Disclosure Monitoring ⭐️
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- English •
- 中文
-
-
-
-
-## Awesome features
-
-A system that monitors and tracks ESG (Environmental, Social and Governance) disclosures and ratings from various public data sources. It collects ESG data points from sources like Feishu spreadsheets and makes them available through an administrative interface.
-
-## Quickstart
-
-> **Note**: You can get started quickly with go-project-layout.
-
-
-## Contributing & Development
-
-kubecub Our goal is to build a top-level open source community. We have a set of standards, in the [Community repository](https://github.com/kubecub/community).
-
-If you'd like to contribute to this go-project-layout repository, please read our [contributor documentation](https://github.com/kubecub/go-project-layout/blob/main/CONTRIBUTING.md).
-
-
-## architecture diagram
-```mermaid
-graph LR
-
-subgraph External Services
-feishuAPI --> sheetParser
-end
-
-subgraph Sheet Parser & Manager
-sheetParser[Sheet Parser] --> versionControl
-versionControl[Version Control] --> sheetDisplay
-end
-
-subgraph Display
-sheetDisplay[Sheet Display] --> UI
-end
-
-subgraph Backend
-versionControl --> API
-end
-
-subgraph Frontend
-UI[User Interface]
-end
-
-API --> UI
-UI --> feishuAPI
-```
-
-**MVC Architecture Design:**
-```mermaid
-graph LR
-A[View] -->|1. User interaction| B(Controller)
-B -->|2. Requests data| C(Model)
-C -->|3. Returns data| B
-B -->|4. Updates view| A
-```
-
-## File Directory Description
-
-
-
-## community meeting
-
-We welcome everyone to join us and contribute to go-project-layout, whether you are new to open source or professional. We are committed to promoting an open source culture, so we offer community members neighborhood prizes and reward money in recognition of their contributions. We believe that by working together, we can build a strong community and make valuable open source tools and resources available to more people. So if you are interested in go-project-layout, please join our community and start contributing your ideas and skills!
-
-We take notes of each [biweekly meeting](https://github.com/kubecub/go-project-layout/issues/2) in [GitHub discussions](https://github.com/kubecub/go-project-layout/discussions/categories/meeting), and our minutes are written in [Google Docs](https://docs.google.com/document/d/1nx8MDpuG74NASx081JcCpxPgDITNTpIIos0DS6Vr9GU/edit?usp=sharing).
-
-go-project-layout maintains a [public roadmap](https://github.com/kubecub/community/tree/main/roadmaps). It gives a a high-level view of the main priorities for the project, the maturity of different features and projects, and how to influence the project direction.
-
-
-## License
-
-Sealer is licensed under the Apache License, Version 2.0. See [LICENSE](https://github.com/kubecub/go-project-layout/tree/main/LICENSE) for the full license text.
-
-[](https://app.fossa.com/projects/git%2Bgithub.com%2Fkubecub%2Fgo-project-layout?ref=badge_large)
-
-
-## Thanks to our contributors!
-
-
-
-
\ No newline at end of file
+Web application specific components: static web assets, server side templates and SPAs.
\ No newline at end of file