jinrongluo · jinrongluo · May 10, 2021 · Apr 16, 2021 · Apr 17, 2021 · Apr 19, 2021
diff --git a/.asf.yaml b/.asf.yaml
@@ -0,0 +1,45 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+github:
+  description: EventMesh is a dynamic cloud-native eventing infrastruture used to decouple the application and backend middleware layer, which supports a wide range of use cases that encompass complex multi-cloud, widely distributed topologies using diverse technology stacks.
+  homepage: https://eventmesh.apache.org/
+  labels:
+    - event-mesh
+    - event-gateway
+    - event-driven
+    - event-streaming
+    - event-sourcing
+    - event-governance
+    - event-routing
+    - cloud-native
+    - serverless
+    - serverless-workflow
+    - esb
+    - message-bus
+    - cqrs
+  enabled_merge_buttons:
+    squash:  true
+    merge:   false
+    rebase:  false
+  protected_branches:
+    master:
+      required_status_checks:
+        strict: true
+      required_pull_request_reviews:
+        dismiss_stale_reviews: true
+        required_approving_review_count: 2
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1 @@
+#TBD
diff --git a/.github/workflows/gitee-mirror.yml b/.github/workflows/gitee-mirror.yml
@@ -21,25 +21,25 @@ jobs:
 
     # Steps represent a sequence of tasks that will be executed as part of the job
     steps:
-    - name: Mirror the Github organization repos to Gitee.
-      uses: Yikun/hub-mirror-action@master
-      with:
-        src: github/WeBankFinTech
-        dst: gitee/webank
-        # 这里请填写与gitee上公钥匹配的的 ssh private key，参见：https://gitee.com/profile/sshkeys
-        # 填写地址：https://github.com/WeBankFinTech/fes.js/settings/secrets
-        dst_key: ${{ secrets.GITEE_PRIVATE_KEY }}
-        # 这里请填写 gitee的令牌，参见：https://gitee.com/profile/personal_access_tokens
-        # 填写地址：https://github.com/WeBankFinTech/fes.js/settings/secrets
-        dst_token: ${{ secrets.GITEE_TOKEN }}
-        # 项目同步白名单，可以选择填写多个，以英文逗号分割
-        static_list: "EventMesh"
-        # 是否强制同步
-        force_update: true
-        # 账号类型：对 luban-h5 而言是 user，因为是个人项目；如果是企业项目，请填写 org，因为是组织下的项目
-        account_type: org
-        clone_style: ssh
-        
+      - name: Mirror the Github organization repos to Gitee.
+        uses: Yikun/hub-mirror-action@master
+        with:
+          src: github/WeBankFinTech
+          dst: gitee/webank
+          # 这里请填写与gitee上公钥匹配的的 ssh private key，参见：https://gitee.com/profile/sshkeys
+          # 填写地址：https://github.com/WeBankFinTech/fes.js/settings/secrets
+          dst_key: ${{ secrets.GITEE_PRIVATE_KEY }}
+          # 这里请填写 gitee的令牌，参见：https://gitee.com/profile/personal_access_tokens
+          # 填写地址：https://github.com/WeBankFinTech/fes.js/settings/secrets
+          dst_token: ${{ secrets.GITEE_TOKEN }}
+          # 项目同步白名单，可以选择填写多个，以英文逗号分割
+          static_list: "EventMesh"
+          # 是否强制同步
+          force_update: true
+          # 账号类型：对 luban-h5 而言是 user，因为是个人项目；如果是企业项目，请填写 org，因为是组织下的项目
+          account_type: org
+          clone_style: ssh
+
   build-and-deploy:
     runs-on: ubuntu-latest
     steps:
@@ -56,5 +56,5 @@ jobs:
         uses: JamesIves/github-pages-deploy-action@3.7.1
         with:
           GITHUB_TOKEN: ${{ secrets.EVENTMESH }}
-          BRANCH: gh-pages 
+          BRANCH: gh-pages
           FOLDER: docs/.vuepress/dist # The folder the action should deploy.
diff --git a/.travis.yml b/.travis.yml
@@ -2,14 +2,14 @@ dist: trusty
 
 language: java
 jdk:
-- oraclejdk8
+  - oraclejdk8
 
 script:
-- travis_retry gradle check
+  - travis_retry ./gradlew clean build
 
-after_success:
-- gradle clean test jacocoAllTestReport coveralls
+#after_success:
+#  - ./gradlew clean
 
 env:
   global:
-  - secure: "T1QAuaAzcB7K8YjAAVVb4P9+W0JAdOFbyBwRxliyyoSZUShlIqa0eE7ioXHXWBP/d5f3XtROse6lq2qILqcU9sFSncKE2vRJlwJ5p7R23WIsCXdV70A9AVE2gLJcIJiOTMwd/YYYzNDrGLp3CSJNcKo8t7t70V2j/11I9xPTOHnaZ8FHGC3d/7bjfR/+g/3d4EOCvV8Vm6ndEmmailmF8OJ/kcbuRbArKIehjUwNDyQZfwAc9+vvPZlHgnQvR1pJ/KiK6muEIi7RQohDq7lMTmcc2LZSYgy/+aqFrmBcQwXScABFmSwysQ4KMXfrCqqMsBdmvno/NoKVGofHHKdym/oauv/G3lxLx5sgM9A7ZSFBK08x08r7u/6TDsTFmQ9LzVFDNo/OLZhxs3dr9x2C9Pa2A7IP1i1oVbbYkwBJv4z6o3khWpQAAY/IWijlCZ9vkjFfqdIXbvlPqamEaFRAmK5I3MVqL2+eBF+2Or/zwv4rXjo+v5LUKTfmDl77QUshPv6J+hblbBR0cJ/ZTSh9rHgdqhEzPGSt3e0YrEefkKWfinBr8TjIsHgQgmfU8Kz7gf7tvioOuAgKj4WlgEQJs3dPp7J5zxFVNMM6teAMFy8c2MtAdzKrs13Ri1qZWtL6B7JWlH6yhHqhKghyJhRjUFNVZnBkA/z9gzDKZ+tz2m8="
+    - secure: "T1QAuaAzcB7K8YjAAVVb4P9+W0JAdOFbyBwRxliyyoSZUShlIqa0eE7ioXHXWBP/d5f3XtROse6lq2qILqcU9sFSncKE2vRJlwJ5p7R23WIsCXdV70A9AVE2gLJcIJiOTMwd/YYYzNDrGLp3CSJNcKo8t7t70V2j/11I9xPTOHnaZ8FHGC3d/7bjfR/+g/3d4EOCvV8Vm6ndEmmailmF8OJ/kcbuRbArKIehjUwNDyQZfwAc9+vvPZlHgnQvR1pJ/KiK6muEIi7RQohDq7lMTmcc2LZSYgy/+aqFrmBcQwXScABFmSwysQ4KMXfrCqqMsBdmvno/NoKVGofHHKdym/oauv/G3lxLx5sgM9A7ZSFBK08x08r7u/6TDsTFmQ9LzVFDNo/OLZhxs3dr9x2C9Pa2A7IP1i1oVbbYkwBJv4z6o3khWpQAAY/IWijlCZ9vkjFfqdIXbvlPqamEaFRAmK5I3MVqL2+eBF+2Or/zwv4rXjo+v5LUKTfmDl77QUshPv6J+hblbBR0cJ/ZTSh9rHgdqhEzPGSt3e0YrEefkKWfinBr8TjIsHgQgmfU8Kz7gf7tvioOuAgKj4WlgEQJs3dPp7J5zxFVNMM6teAMFy8c2MtAdzKrs13Ri1qZWtL6B7JWlH6yhHqhKghyJhRjUFNVZnBkA/z9gzDKZ+tz2m8="
diff --git a/CNAME b/CNAME
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,7 +1,7 @@
 # Contributing to EventMesh
 
-Welcome to EventMesh! This document is a guideline about how to contribute to EventMesh.
-If you find something incorrect or missing, please leave comments / suggestions.
+Welcome to EventMesh! This document is a guideline about how to contribute to EventMesh. If you find something incorrect
+or missing, please leave comments / suggestions.
 
 ## Before you get started
 
@@ -11,11 +11,11 @@ You should have JDK installed in your operating system.
 
 ## Contributing
 
-We are always very happy to have contributions, whether for typo fix, bug fix or big new features.
-Please do not ever hesitate to ask a question or send a pull request.
+We are always very happy to have contributions, whether for typo fix, bug fix or big new features. Please do not ever
+hesitate to ask a question or send a pull request.
 
-We strongly value documentation and integration with other projects.
-We are very glad to accept improvements for these aspects.
+We strongly value documentation and integration with other projects. We are very glad to accept improvements for these
+aspects.
 
 ### GitHub workflow
 
@@ -31,29 +31,29 @@ Here are the workflow for contributors:
 6. Push your commits to your forked repository
 7. Create a pull request
 
-Please follow [the pull request template](./.github/PULL_REQUEST_TEMPLATE.md).
-Please make sure the PR has a corresponding issue. [GitHub Issues](https://github.com/WeBankFinTech/EventMesh/issues)
+Please follow [the pull request template](./.github/PULL_REQUEST_TEMPLATE.md). Please make sure the PR has a
+corresponding issue. [GitHub Issues](https://github.com/apache/incubator-eventmesh/issues)
 
-After creating a PR, one or more reviewers will be assigned to the pull request.
-The reviewers will review the code.
+After creating a PR, one or more reviewers will be assigned to the pull request. The reviewers will review the code.
 
-Before merging a PR, squash any fix review feedback, typo, merged, and rebased sorts of commits.
-The final commit message should be clear and concise.
+Before merging a PR, squash any fix review feedback, typo, merged, and rebased sorts of commits. The final commit
+message should be clear and concise.
 
 ### Open an issue / PR
 
-We use [GitHub Issues](https://github.com/WeBankFinTech/EventMesh/issues) and [Pull Requests](https://github.com/WeBankFinTech/EventMesh/pulls) for trackers.
+We use [GitHub Issues](https://github.com/apache/incubator-eventmesh/issues)
+and [Pull Requests](https://github.com/apache/incubator-eventmesh/pulls) for trackers.
 
-If you find a typo in a document, find a bug in code, or want new features, or want to give suggestions,
-you can [open an issue on GitHub](https://github.com/WeBankFinTech/EventMesh/issues/new) to report it.
-Please follow the guideline message in the issue template.
+If you find a typo in a document, find a bug in code, or want new features, or want to give suggestions, you
+can [open an issue on GitHub](https://github.com/apache/incubator-eventmesh/issues/new) to report it. Please follow the
+guideline message in the issue template.
 
-If you want to contribute, please follow the [contribution workflow](#github-workflow) and create a new pull request.
-If your PR contains large changes, e.g. component refactor or new components, please write detailed documents
-about its design and usage.
+If you want to contribute, please follow the [contribution workflow](#github-workflow) and create a new pull request. If
+your PR contains large changes, e.g. component refactor or new components, please write detailed documents about its
+design and usage.
 
-Note that a single pull request should not be too large. If heavy changes are required, it's better to separate the changes
-to a few individual PRs.
+Note that a single pull request should not be too large. If heavy changes are required, it's better to separate the
+changes to a few individual PRs.
 
 ### Code review
 

diff --git a/CONTRIBUTING.zh-CN.md b/CONTRIBUTING.zh-CN.md
@@ -1,7 +1,6 @@
 # 贡献给EventMesh
 
-欢迎使用EventMesh! 本文档是有关如何为EventMesh做出贡献的指南。
-如果发现不正确或缺失的内容，请留下评论/建议。
+欢迎使用EventMesh! 本文档是有关如何为EventMesh做出贡献的指南。 如果发现不正确或缺失的内容，请留下评论/建议。
 
 ## 开始之前
 
@@ -11,51 +10,43 @@
 
 ## 贡献
 
-无论是对于拼写错误，BUG修复还是重要的新功能，我们总是很乐意为您做出贡献。
-请不要犹豫，提出问题或发送请求请求。
+无论是对于拼写错误，BUG修复还是重要的新功能，我们总是很乐意为您做出贡献。 请不要犹豫，提出问题或发送请求请求。
 
-我们非常重视文档以及与其他项目的集成。
-我们很高兴接受这些方面的改进。
+我们非常重视文档以及与其他项目的集成。 我们很高兴接受这些方面的改进。
 
 ### GitHub工作流程
 
 我们将`develop`分支用作开发分支，这表明这是一个不稳定的分支。
 
 这是贡献者的工作流程 :
 
-1. Fork到您个人仓库 
-2. 克隆到本地存储库 
-3. 创建一个新分支并对其进行处理 
-4. 保持分支同步 
+1. Fork到您个人仓库
+2. 克隆到本地存储库
+3. 创建一个新分支并对其进行处理
+4. 保持分支同步
 5. 提交您的更改(确保您的提交消息简明扼要)
 6. 将您的提交推送到分叉的存储库
 7. 创建PR合并请求
 
 请遵循[Pull Requests模板](./.github/PULL_REQUEST_TEMPLATE.md).
-请确保PR对应有相应的问题. [GitHub Issues](https://github.com/WeBankFinTech/EventMesh/issues)
+请确保PR对应有相应的问题. [GitHub Issues](https://github.com/apache/incubator-eventmesh/issues)
 
-创建PR后，将为拉取请求分配一个或多个审阅者。
-审阅者将审阅代码。
+创建PR后，将为拉取请求分配一个或多个审阅者。 审阅者将审阅代码。
 
-在合并PR之前，请压缩所有修订审阅反馈，拼写错误，合并的内容和基于基础的提交内容。
-最终的提交消息应该清晰简洁。
+在合并PR之前，请压缩所有修订审阅反馈，拼写错误，合并的内容和基于基础的提交内容。 最终的提交消息应该清晰简洁。
 
 ### 打开问题/ PR
 
-我们将使用Issues和Pull Requests作为跟踪器 
-[GitHub Issues](https://github.com/WeBankFinTech/EventMesh/issues)
-[Pull Requests](https://github.com/WeBankFinTech/EventMesh/pulls)
+我们将使用Issues和Pull Requests作为跟踪器
+[GitHub Issues](https://github.com/apache/incubator-eventmesh/issues)
+[Pull Requests](https://github.com/apache/incubator-eventmesh/pulls)
 
-如果您在文档中发现拼写错误，在代码中发现错误，想要新功能或提出建议，
-您可以提出问题[在GitHub上打开问题](https://github.com/WeBankFinTech/EventMesh/issues/new)
+如果您在文档中发现拼写错误，在代码中发现错误，想要新功能或提出建议， 您可以提出问题[在GitHub上打开问题](https://github.com/apache/incubator-eventmesh/issues/new)
 请按照问题模板中的准则消息进行操作。
 
-如果您想贡献，请遵循[贡献工作流程](#github-workflow)并创建一个新的拉取请求。
-如果您的PR包含较大的更改，例如组件重构或新组件，请写详细文档
-有关其设计和使用的信息。
+如果您想贡献，请遵循[贡献工作流程](#github-workflow)并创建一个新的拉取请求。 如果您的PR包含较大的更改，例如组件重构或新组件，请写详细文档 有关其设计和使用的信息。
 
-请注意，单个拉取请求不应太大。如果需要进行重大更改，最好将更改分开
-到一些个人PR。
+请注意，单个拉取请求不应太大。如果需要进行重大更改，最好将更改分开 到一些个人PR。
 
 ### 代码审查
 

diff --git a/DISCLAIMER-WIP b/DISCLAIMER-WIP
@@ -0,0 +1,19 @@
+Apache EventMesh is an effort undergoing incubation at The Apache Software Foundation (ASF),
+sponsored by the Apache Incubator PMC.
+
+Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, 
+communications, and decision-making process have stabilized in a manner consistent with other successful ASF projects.
+
+While incubation status is not necessarily a reflection of the completeness or stability of the code, 
+it does indicate that the project has yet to be fully endorsed by the ASF.
+
+Some of the incubating project’s releases may not be fully compliant with ASF policy.
+For example, releases may have incomplete or un-reviewed licensing conditions. 
+What follows is a list of issues the project is currently aware of (this list is likely to be incomplete): 
+
+1- Releases may have incomplete licensing conditions
+
+
+If you are planning to incorporate this work into your product/project, 
+please be aware that you will need to conduct a thorough licensing review to determine the overall implications of including this work.
+For the current status of this project through the Apache Incubator, visit: https://incubator.apache.org/projects/eventmesh.html
diff --git a/NOTICE b/NOTICE
@@ -0,0 +1,5 @@
+Apache EventMesh (incubating)
+Copyright 2021 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).