Merge pull request #2 from telepace/feat/voiceflow

feat: init voiceflow project

.env.example

@@ -0,0 +1,16 @@
+# MinIO 配置
+MINIO_ENDPOINT=play.min.io
+MINIO_ACCESS_KEY=youraccesskey
+MINIO_SECRET_KEY=yoursecretkey
+MINIO_USE_SSL=false
+
+# Azure 配置
+AZURE_STT_KEY=yourazuresttkey
+AZURE_TTS_KEY=yourazurettskey
+
+# Google 配置
+GOOGLE_STT_KEY=yourgooglesttkey
+GOOGLE_TTS_KEY=yourgooglettskey
+
+# OpenAI 配置
+OPENAI_API_KEY=youropenaiapikey

.github/CODEOWNERS

@@ -21,7 +21,7 @@
 # Teams can be specified as code owners as well. Teams should
 # be identified in the format @org/team-name. Teams must have
 # explicit write access to the repository. In this example,
-# the kubecub team in the github organization owns all .txt files.
+# the telepace team in the github organization owns all .txt files.
 *.txt @cubxxw
 
 # In this example, @cubxxw owns any files in the build/

.github/CODE_OF_CONDUCT.md

@@ -4,42 +4,42 @@ We divide the problem into security and general problems:
 
 #### Reporting security issues
 
-Security issues are always treated seriously. As our usual principle, we discourage anyone to spread security issues. If you find a security issue of kubecub, please do not discuss it in public and even do not open a public issue.
+Security issues are always treated seriously. As our usual principle, we discourage anyone to spread security issues. If you find a security issue of telepace, please do not discuss it in public and even do not open a public issue.
 
 Instead we encourage you to send us a private email to [[email protected]](mailto:[email protected]) to report this.
 
 #### Reporting general issues
 
-To be honest, we regard every user of kubecubas a very kind contributor. After experiencing kubecub, you may have some feedback for the project. Then feel free to open an issue via [NEW ISSUE](https://github.com/kubecub/kubecub/issues/new/choose).
+To be honest, we regard every user of telepaceas a very kind contributor. After experiencing telepace, you may have some feedback for the project. Then feel free to open an issue via [NEW ISSUE](https://github.com/telepace/telepace/issues/new/choose).
 
-Since we collaborate project kubecub in a distributed way, we appreciate **WELL-WRITTEN**, **DETAILED**, **EXPLICIT** issue reports. To make the communication more efficient, we wish everyone could search if your issue is an existing one in the searching list. If you find it existing, please add your details in comments under the existing issue instead of opening a brand new one.
+Since we collaborate project telepace in a distributed way, we appreciate **WELL-WRITTEN**, **DETAILED**, **EXPLICIT** issue reports. To make the communication more efficient, we wish everyone could search if your issue is an existing one in the searching list. If you find it existing, please add your details in comments under the existing issue instead of opening a brand new one.
 
-To make the issue details as standard as possible, we setup an [ISSUE TEMPLATE](https://github.com/kubecub/kubecub/tree/main/.github/ISSUE_TEMPLATE) for issue reporters. You can find three kinds of issue templates there: question, bug report and feature request. Please **BE SURE** to follow the instructions to fill fields in template.
+To make the issue details as standard as possible, we setup an [ISSUE TEMPLATE](https://github.com/telepace/telepace/tree/main/.github/ISSUE_TEMPLATE) for issue reporters. You can find three kinds of issue templates there: question, bug report and feature request. Please **BE SURE** to follow the instructions to fill fields in template.
 
 **There are a lot of cases when you could open an issue:**
 
 + bug report
 + feature request
-+ kubecub performance issues 
++ telepace performance issues 
 + feature proposal
 + feature design
 + help wanted
 + doc incomplete
 + test improvement
-+ any questions on kubecub project 
++ any questions on telepace project 
 + and so on 
 
-Also, we must be reminded when submitting a new question about kubecub, please remember to remove the sensitive data from your post. Sensitive data could be password, secret key, network locations, private business data and so on.
+Also, we must be reminded when submitting a new question about telepace, please remember to remove the sensitive data from your post. Sensitive data could be password, secret key, network locations, private business data and so on.
 
 #### Commit Rules
 
-Actually in kubecub, we take two rules serious when committing:
+Actually in telepace, we take two rules serious when committing:
 
 **🥇 Commit Message:**
 
 Commit message could help reviewers better understand what the purpose of submitted PR is. It could help accelerate the code review procedure as well. We encourage contributors to use **EXPLICIT** commit message rather than ambiguous message. In general, we advocate the following commit message type:
 
-We use [Semantic Commits](https://www.conventionalcommits.org/en/v1.0.0/) to make it easier to understand what a commit does and to build pretty change kubecub. Please use the following prefixes for your commits:
+We use [Semantic Commits](https://www.conventionalcommits.org/en/v1.0.0/) to make it easier to understand what a commit does and to build pretty change telepace. Please use the following prefixes for your commits:
 
 + `docs: xxxx`. For example, "docs: add docs about storage installation".
 + `feature: xxxx`.For example, "feature: make result show in sorted order".
@@ -76,9 +76,9 @@ An example for this could be:
 
 #### PR Description
 
-PR is the only way to make change to kubecub project files. To help reviewers better get your purpose, PR description could not be too detailed. We encourage contributors to follow the [PR template](https://github.com/kubecub) to finish the pull request.
+PR is the only way to make change to telepace project files. To help reviewers better get your purpose, PR description could not be too detailed. We encourage contributors to follow the [PR template](https://github.com/telepace) to finish the pull request.
 
-You can find some very formal PR in [RFC](https://github.com/kubecub/kubecub/issues) issues and learn about them.
+You can find some very formal PR in [RFC](https://github.com/telepace/telepace/issues) issues and learn about them.
 
 **📖 Opening PRs:**
 
@@ -124,12 +124,12 @@ git() {
 
 #### Docs Contribution
 
-The documentation for kubecub includes:
+The documentation for telepace includes:
 
-+ [README.md](https://github.com/kubecub/community/blob/main/README.md): This file includes the basic information and instructions for getting started with kubecub.
-+ [CONTRIBUTING.md](https://github.com/kubecub/community/blob/main/CONTRIBUTING.md): This file contains guidelines for contributing to kubecub's codebase, such as how to submit issues, pull requests, and code reviews.
-+ [DEVELOPGUIDE.md](https://github.com/kubecub/community/blob/main/DEVELOPGUIDE.md): This file provides a more in-depth guide to developing kubecub, including information on the project's architecture, coding conventions, and testing practices.
-+ [Official Documentation](nsddd.top): This is the official documentation for kubecub, which includes comprehensive information on all of its features, configuration options, and troubleshooting tips.
++ [README.md](https://github.com/telepace/community/blob/main/README.md): This file includes the basic information and instructions for getting started with telepace.
++ [CONTRIBUTING.md](https://github.com/telepace/community/blob/main/CONTRIBUTING.md): This file contains guidelines for contributing to telepace's codebase, such as how to submit issues, pull requests, and code reviews.
++ [DEVELOPGUIDE.md](https://github.com/telepace/community/blob/main/DEVELOPGUIDE.md): This file provides a more in-depth guide to developing telepace, including information on the project's architecture, coding conventions, and testing practices.
++ [Official Documentation](nsddd.top): This is the official documentation for telepace, 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.
 
@@ -142,20 +142,20 @@ Please obey the following rules to better format the docs, which would greatly i
 
 ## Engage to help anything
 
-We choose GitHub as the primary place for kubecub to collaborate. So the latest updates of kubecub are always here. Although contributions via PR is an explicit way to help, we still call for any other ways.
+We choose GitHub as the primary place for telepace to collaborate. So the latest updates of telepace are always here. Although contributions via PR is an explicit way to help, we still call for any other ways.
 
-+ reply to other's [issues](https://github.com/search?q=org%3Akubecub++&type=issues&s=comments&o=desc) if you could;
++ reply to other's [issues](https://github.com/search?q=org%3Atelepace++&type=issues&s=comments&o=desc) if you could;
 + help solve other user's problems;
-+ help review other's [PR](https://github.com/search?q=org%3Akubecub++&type=pullrequests&s=comments&o=desc) design; 
-+ discuss about kubecub to make things clearer;
-+ advocate [kubecub](google.com/search?q=kubecub) technokubecuby beyond GitHub;
-+ write kubecubs on kubecub and so on.
++ help review other's [PR](https://github.com/search?q=org%3Atelepace++&type=pullrequests&s=comments&o=desc) design; 
++ discuss about telepace to make things clearer;
++ advocate [telepace](google.com/search?q=telepace) technotelepacey beyond GitHub;
++ write telepaces on telepace and so on.
 
 In a word, **ANY HELP IS CONTRIBUTION.**
 
 ## Release version
 
-Releases of kubecub are done using [Release Please](https://github.com/googleapis/release-please) and [GoReleaser](https://goreleaser.com/). The workflow looks like this:
+Releases of telepace are done using [Release Please](https://github.com/googleapis/release-please) and [GoReleaser](https://goreleaser.com/). The workflow looks like this:
 
 🎯 A PR is merged to the `main` branch:
 
@@ -164,7 +164,7 @@ Releases of kubecub are done using [Release Please](https://github.com/googleapi
 
 🎯 Merging the 'release please' PR to `main`:
 
-+ Release please is triggered, creates a new release and updates the change kubecub based on the commit messages
++ Release please is triggered, creates a new release and updates the change telepace based on the commit messages
 + GoReleaser is triggered, builds the binaries and attaches them to the release
 + Containers are created and pushed to the container registry
 

.github/CONTRIBUTING.md

@@ -6,4 +6,4 @@ Read the [contributor documentation](../CONTRIBUTING.md), which will teach you h
 
 
 ## Join community meetings for discussion
-Keep a record of every discussion in [GitHub discussions](https://github.com/orgs/kubecub/discussions), and our minutes are written in [Google Docs](https://docs.google.com/document/d/1nx8MDpuG74NASx081JcCpxPgDITNTpIIos0DS6Vr9GU/edit?usp=sharing).
+Keep a record of every discussion in [GitHub discussions](https://github.com/orgs/telepace/discussions), and our minutes are written in [Google Docs](https://docs.google.com/document/d/1nx8MDpuG74NASx081JcCpxPgDITNTpIIos0DS6Vr9GU/edit?usp=sharing).

.github/FUNDING.yml

@@ -1,4 +1,4 @@
-# Copyright © 2023 KubeCub open source community. All rights reserved.
+# Copyright © 2023 telepace open source community. All rights reserved.
 # Licensed under the MIT License (the "License");
 # you may not use this file except in compliance with the License.
 

.github/ISSUE_TEMPLATE/RFC.md

@@ -1,15 +1,15 @@
 ---
 name: 📇 RFC
-about: The kubecub RFC design template, which you should use if you have a detailed and precise feature design in mind.
+about: The telepace 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] kubecub proposal template
+# [RFC #0000] telepace proposal template
 <!--
-🤖 design template: https://github.com/kubecub/community/blob/main/0000-template.md
-⚠️ Please submit a PR to https://github.com/kubecub/community/tree/main/RFC according to the specification after the design is completed
+🤖 design template: https://github.com/telepace/community/blob/main/0000-template.md
+⚠️ Please submit a PR to https://github.com/telepace/community/tree/main/RFC according to the specification after the design is completed
 -->
 ## Meta
 [meta]: #meta
@@ -18,13 +18,13 @@ labels: "proposal,RFC,kind/feature,enhancement"
 - Author(s): (Github usernames)
 - Status: Draft <!-- Acceptable values: Draft, Approved, On Hold, Superseded -->
 - RFC Pull Request: (leave blank)
-- kubecub Pull Request: (leave blank)
-- kubecub Issue: (leave blank)
+- telepace Pull Request: (leave blank)
+- telepace Issue: (leave blank)
 - Supersedes: (put "N/A" unless this replaces an existing RFC, then link to that RFC)
 
 
 ## 📇Topics
-- [\[RFC #0000\] kubecub proposal template](#rfc-0000-kubecub-proposal-template)
+- [\[RFC #0000\] telepace proposal template](#rfc-0000-telepace-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 kubecub 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 telepace 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: kubecub author, kubecub user, platform operator, platform implementor, and/or project contributor.
+- Define the target persona: telepace author, telepace 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, kubecub developers, kubecub users and consumers of kubecub 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, telepace developers, telepace users and consumers of telepace 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 `kubecub.toml` fields, new fields in the kubecubage label, etc.
+Examples of a spec. change might be new lifecycle flags, new `telepace.toml` fields, new fields in the telepaceage 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

.github/ISSUE_TEMPLATE/bug-report.yaml

@@ -1,9 +1,9 @@
-# Copyright © 2023 KubeCub open source community. All rights reserved.
+# Copyright © 2023 telepace open source community. All rights reserved.
 # Licensed under the MIT License (the "License");
 # you may not use this file except in compliance with the License.
 
 name: 🐛 Bug Report
-description: Report a bug encountered while operating kubecub
+description: Report a bug encountered while operating telepace
 title: "Bug: <describe the error>"
 labels: ["kind/bug"]
 body:

.github/ISSUE_TEMPLATE/config.yml

@@ -1,12 +1,12 @@
-# Copyright © 2023 KubeCub open source community. All rights reserved.
+# Copyright © 2023 telepace open source community. All rights reserved.
 # Licensed under the MIT License (the "License");
 # you may not use this file except in compliance with the License.
 
 blank_issues_enabled: false
 contact_links:
   - name: 📢 Connect on slack
-    url: https://join.slack.com/t/kubecub/shared_invite/zt-1se0k2bae-lkYzz0_T~BYh3rjkvlcUqQ
-    about: Support kubecub-related requests or issues, get in touch with developers and help on slack
-  - name: 🌐 kubecub Blog
-    url: https://kubecub.nsddd.top
-    about: Open the kubecub community blog
+    url: https://join.slack.com/t/telepace/shared_invite/zt-1se0k2bae-lkYzz0_T~BYh3rjkvlcUqQ
+    about: Support telepace-related requests or issues, get in touch with developers and help on slack
+  - name: 🌐 telepace Blog
+    url: https://telepace.nsddd.top
+    about: Open the telepace community blog

.github/ISSUE_TEMPLATE/docs.yml

@@ -1,4 +1,4 @@
-# Copyright © 2023 KubeCub open source community. All rights reserved.
+# Copyright © 2023 telepace open source community. All rights reserved.
 # Licensed under the MIT License (the "License");
 # you may not use this file except in compliance with the License.
 
@@ -31,5 +31,5 @@ body:
   - type: markdown
     attributes:
       value: |
-        You can also join our Slack community [here](https://join.slack.com/t/kubecub/shared_invite/zt-1se0k2bae-lkYzz0_T~BYh3rjkvlcUqQ)
-        Feel free to check out other cool repositories of the kubecub Community [here](https://github.com/kubecub)
+        You can also join our Slack community [here](https://join.slack.com/t/telepace/shared_invite/zt-1se0k2bae-lkYzz0_T~BYh3rjkvlcUqQ)
+        Feel free to check out other cool repositories of the telepace Community [here](https://github.com/telepace)

.github/ISSUE_TEMPLATE/failing-test.yaml

@@ -1,9 +1,9 @@
-# Copyright © 2023 KubeCub open source community. All rights reserved.
+# Copyright © 2023 telepace open source community. All rights reserved.
 # Licensed under the MIT License (the "License");
 # you may not use this file except in compliance with the License.
 
 name: 🚨 Failing Test
-description: Report continuously failing tests or jobs in kubecub CI
+description: Report continuously failing tests or jobs in telepace CI
 title: "🤖Failing-test: "
 labels: ["kind/failing-test"]
 body:
@@ -14,7 +14,7 @@ body:
       value: 
         <!-- ⚠️ Please ask questions in English. Thank you -->
       placeholder: |
-        Please only use this template for submitting reports about continuously failing tests or jobs in kubecub CI.
+        Please only use this template for submitting reports about continuously failing tests or jobs in telepace CI.
     validations:
       required: true