[ISSUE #389] Support redis as event store

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,42 @@
+---
+name: 🐛 Bug Report
+about: If something isn't working as expected.
+labels: 'bug'
+---
+
+## Bug Report
+
+### Describe the bug
+<!--
+A clear and concise description of what the bug is.
+-->
+
+### Environment
+
+- OS: [e.g. Ubuntu 21.04 LTS]
+- EventMesh version(s): [e.g. 1.2.0]
+- RocketMQ version(s): [e.g. 4.7.1]
+- ...
+
+### Steps to reproduce
+<!--
+Describe the steps to reproduce the bug here.
+-->
+
+### Expected behavior
+<!--
+A clear and concise description of what you expected to happen.
+-->
+
+### Debug logs
+<!--
+Add your debug logs here.
+-->
+
+<details>
+<summary>Click to expand</summary>
+
+```
+replace this line with your debug logs
+```
+</details>

.github/ISSUE_TEMPLATE/documentation_related.md

@@ -0,0 +1,11 @@
+---
+name: ✏️ Documentation Related
+about: I find some issues related to the documentation.
+labels: 'doc'
+---
+
+## Documentation Related
+
+<!--
+Describe the issues here :D
+-->

.github/ISSUE_TEMPLATE/enhancement_request.md

@@ -0,0 +1,36 @@
+---
+name: ✨ Enhancement Request
+about: I want to suggest an enhancement for this project (and may want to implement it 🙂)!
+labels: 'enhancement'
+---
+
+## Enhancement Request
+
+<!-- 
+First of all: Have you checked the docs https://github.com/apache/incubator-eventmesh/tree/develop/docs, 
+or GitHub issues whether someone else has already reported your issue? 
+-->
+
+### Is your enhancement request related to a problem? Please describe
+
+<!-- 
+A clear and concise description of what the enhancement is.
+-->
+
+### Describe the solution you'd like
+
+<!-- 
+A clear and concise description of what you want to happen. Add any considered drawbacks.
+-->
+
+### Describe alternatives you've considered
+
+<!-- 
+A clear and concise description of any alternative solutions or features you've considered.
+-->
+
+### Additional context
+
+<!-- 
+Add any other context or screenshots about the enhancement request here.
+-->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,37 @@
+---
+name: 🚀 Feature Request
+about: I want to suggest a feature for this project (and may want to implement it 🙂)!
+labels: 'feature'
+---
+
+## Feature Request
+
+<!-- 
+First of all: Have you checked the docs https://github.com/apache/incubator-eventmesh/tree/develop/docs, 
+or GitHub issues whether someone else has already reported your issue? 
+Maybe the feature already exists?
+-->
+
+### Is your feature request related to a problem? Please describe
+
+<!-- 
+A clear and concise description of what the problem is.
+-->
+
+### Describe the solution you'd like
+
+<!-- 
+A clear and concise description of what you want to happen. Add any considered drawbacks.
+-->
+
+### Describe alternatives you've considered
+
+<!-- 
+A clear and concise description of any alternative solutions or features you've considered.
+-->
+
+### Additional context
+
+<!-- 
+Add any other context or screenshots about the feature request here.
+-->

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,11 @@
+---
+name: 🤔 Question
+about: I have a question that isn't answered in docs or discussions.
+labels: 'question'
+---
+
+## Question
+
+<!--
+Describe your question here :D
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1 +1,46 @@
-#TBD
+<!--
+### Contribution Checklist
+
+  - Name the pull request in the form "[ISSUE #XXXX] Title of the pull request", 
+    where *XXXX* should be replaced by the actual issue number.
+    Skip *[ISSUE #XXXX]* if there is no associated github issue for this pull request.
+
+  - Fill out the template below to describe the changes contributed by the pull request. 
+    That will give reviewers the context they need to do the review.
+
+  - Each pull request should address only one issue. 
+    Please do not mix up code from multiple issues.
+
+  - Each commit in the pull request should have a meaningful commit message.
+
+  - Once all items of the checklist are addressed, remove the above text and this checklist, 
+    leaving only the filled out template below.
+
+(The sections below can be removed for hotfixes of typos)
+-->
+
+<!--
+(If this PR fixes a GitHub issue, please add `Fixes ISSUE#<XXX>`.)
+-->
+
+Fixes ISSUE#<XXXX>.
+
+### Motivation
+
+*Explain the content here.*
+*Explain why you want to make the changes and what problem you're trying to solve.*
+
+
+
+### Modifications
+
+*Describe the modifications you've done.*
+
+
+
+### Documentation
+
+- Does this pull request introduce a new feature? (yes / no)
+- If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
+- If a feature is not applicable for documentation, explain why?
+- If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

.github/workflows/ci.yml

@@ -23,9 +23,11 @@ on:
   push:
     branches:
       - develop
+      - '[0-9]+.[0-9]+.[0-9]+**'
   pull_request:
     branches:
       - develop
+      - '[0-9]+.[0-9]+.[0-9]+**'
   workflow_dispatch:
 
 jobs:
@@ -69,6 +71,28 @@ jobs:
       - name: Upload coverage report to codecov.io
         run: bash <(curl -s https://codecov.io/bash) || echo 'Failed to upload coverage report!'
 
+  checkstyle:
+    name: Checkstyle
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2
+
+      - name: Download checkstyle exectable
+        run: wget -O - -q https://github.com/checkstyle/checkstyle/releases/download/checkstyle-8.44/checkstyle-8.44-all.jar > ./checkstyle.jar
+
+      - name: Download reviewdog exectable
+        run: wget -O - -q https://raw.githubusercontent.com/reviewdog/reviewdog/master/install.sh | sh -s -- -b . v0.12.0
+
+      - name: Check code style
+        env:
+          REVIEWDOG_GITHUB_API_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          java -jar ./checkstyle.jar -c ./style/checkStyle.xml -f xml ./eventmesh-* \
+               | ./reviewdog -f=checkstyle -reporter=github-pr-check -filter-mode=nofilter -fail-on-error
+
   license-check:
     name: License Check
 

.github/workflows/greetings.yml

@@ -19,7 +19,7 @@
 
 name: Greetings
 
-on: [pull_request, issues]
+on: [pull_request_target, issues]
 
 jobs:
   greeting:

README.md

@@ -48,20 +48,25 @@ The protocol of eventmesh is easier and more convenient, you can read more [here
 | v1.0.0  |Support java-sdk , tcp pub/sub, http pub|
 | v1.1.0  |Support RocketMQ as eventstore|
 | v1.1.1  |Support https|
-| v1.2.0  |Support EventMesh store layer pluggable by OpenMessaging Pub/Sub API, http sub, docker|
-| V1.3.0  |Support CloudEvents, Event Streaming|
-|         |Support Event function,triggers and bindings|
-|         |Support Event orchestration, Servelss workflow|
-|         |Support Event transaction|
-|         |Support Event schema|
-|         |Support Event governance, dashboard|
-|         |Support Event security|
-|         |Support multi language SDK(c\go\python\wasm)|
-|         |Support Promethus as metrics|
-|         |Support Skywalking as tracing|
-|         |Support streaming event store|
-|         |Support gRPC protocol|
-|         |Support MQTT protocol|
+| v1.2.0  |Support pluggable event store by OpenMessaging Pub/Sub API, http sub, docker|
+| V1.3.0  |Support CloudEvents, event streaming|
+|   WIP   |Support more pluggable event storage (Kafka, Pulsar, Redis, etc...)|
+|   WIP   |Support Event schema|
+|   WIP   |Support Event governance|
+|   WIP   |Support Event function,triggers and bindings|
+|   WIP   |Support Event orchestration, Servelss workflow|
+|   WIP   |Support in-memory event store|
+|   WIP   |Support Event transaction|
+|   WIP   |Support Event security|
+|   WIP   |Support multi language SDK(c\go\python\wasm)|
+|   WIP   |Support metrics exporter|
+|   WIP   |Support tracing exporter|
+|   WIP   |Support at-least-once/at-most-once delivery guarantees|
+|   WIP   |Support cold event storage (S3, Minio, SQL, key/value, etc...)|
+|   WIP   |Support gRPC protocol|
+|   WIP   |Support MQTT protocol|
+|   WIP   |Support reactive fisrt|
+
 
 ## Quick Start
 1. Build and deploy event-store(default RocketMQ), see [instruction](https://rocketmq.apache.org/docs/quick-start/).

README.zh-CN.md

@@ -44,20 +44,24 @@ eventmesh的通信协议更加简洁方便，详细内容，阅读更多[这里]
 | v1.0.0  |Support java-sdk , tcp pub/sub, http pub|
 | v1.1.0  |Support RocketMQ as eventstore|
 | v1.1.1  |Support https|
-| v1.2.0  |Support EventMesh store layer pluggable by OpenMessaging Pub/Sub API, http sub, docker|
-| V1.3.0  |Support CloudEvents, Event Streaming|
-|         |Support Event function,triggers and bindings|
-|         |Support Event orchestration, Servelss workflow|
-|         |Support Event transaction|
-|         |Support Event schema|
-|         |Support Event governance, dashboard|
-|         |Support Event security|
-|         |Support multi language SDK(c\go\python\wasm)|
-|         |Support Promethus as metrics|
-|         |Support Skywalking as tracing|
-|         |Support streaming event store|
-|         |Support gRPC protocol|
-|         |Support MQTT protocol|
+| v1.2.0  |Support pluggable event store by OpenMessaging Pub/Sub API, http sub, docker|
+| V1.3.0  |Support CloudEvents, event streaming|
+|   WIP   |Support more pluggable event storage (Kafka, Pulsar, Redis, etc...)|
+|   WIP   |Support Event schema|
+|   WIP   |Support Event governance|
+|   WIP   |Support Event function,triggers and bindings|
+|   WIP   |Support Event orchestration, Servelss workflow|
+|   WIP   |Support in-memory event store|
+|   WIP   |Support Event transaction|
+|   WIP   |Support Event security|
+|   WIP   |Support multi language SDK(c\go\python\wasm)|
+|   WIP   |Support metrics exporter|
+|   WIP   |Support tracing exporter|
+|   WIP   |Support at-least-once/at-most-once delivery guarantees|
+|   WIP   |Support cold event storage (S3, Minio, SQL, key/value, etc...)|
+|   WIP   |Support gRPC protocol|
+|   WIP   |Support MQTT protocol|
+|   WIP   |Support reactive fisrt|
 
 ## 快速开始
 1. 构建并部署event-store(RocketMQ), 请参见[说明](https://rocketmq.apache.org/docs/quick-start/)