apache / eventmesh-site Goto Github PK
View Code? Open in Web Editor NEWApache EventMesh Website
Home Page: https://eventmesh.apache.org
License: Apache License 2.0
Apache EventMesh Website
Home Page: https://eventmesh.apache.org
License: Apache License 2.0
The (completed in #152)Installation and deployment
and SDK
category should be in front of the Design documents
category.
Older versions of the documentation should remain as they were in the Git repository at the time of each release.
Related PR: apache/eventmesh#4675
Many image's paths in documents are incorrect, including design documents, explanatory documents, etc.
For example
https://github.com/apache/eventmesh-site/blob/master/docs/design-document/01-event-handling-and-integration/01-runtime-protocol.md
https://github.com/apache/eventmesh-site/blob/master/docs/design-document/02-stream.md
https://github.com/apache/eventmesh-site/blob/master/docs/design-document/03-schema-registry.md
......
The correct path for most images should be /static/images/...
instead of /images/...
.
This is a synchronised modification of apache/eventmesh#4336.
In the screenshots of the webhook documentation, the tasks are also failing.
Fix "填写webhook信息" image duplicate references.
Please see #170 (comment).
RocketMQProducerImpl
and org.apache.eventmesh.api.producer.Producer
are now files in eventmesh-storage-rocketmq
.
relevant pr: #108
Add v1.10.0 release doc
This is a subtask of GLCC Subject apache/eventmesh#4040.
Add RabbitMQ-Connector documents
Found in PR apache/eventmesh#4273
When inserting the config, the path contains manufacturerName
, and the same logic applies when querying. Therefore, if we follow the request example in the documentation, it will result in an NPE (NullPointerException).
There are two possible solutions, with no impact on users. One way is to retrieve manufacturerName
from callbackPath
when making a query on our end. However, this would require specifying in the documentation that manufacturerName
must be included in users' callbackPath
, which doesn't seem like a common practice.
A simpler solution is to include manufacturerName
in the request. Since there are likely no users for our webhook at the moment, I will go with the latter option.
Currently, after importing the checkStyle.xml
file, IntelliJ IDEA displays an error message in the bottom right corner stating "No header file found," which prevents new contributors from using the CheckStyle plugin.
To address this issue, I propose updating the contribution guidelines. This update should include step-by-step instructions on how to import the checkStyle.xml file in the plugin settings and how to enable the scanning in the Gradle options tab. This will ensure that new contributors can utilize the CheckStyle plugin seamlessly.
This issue is a document supplementation of Feat apache/eventmesh#4847.
(Related issue apache/eventmesh#4680. CC @VishalMCF.)
https://github.com/apache/eventmesh-site/blob/master/docs/instruction/03-runtime.md
Current EventMesh Connector is different from the initial EventMesh Connector, and it is a standalone service now. The initial EventMesh Connector was later changed to EventMesh Storage, but the relevant instructions in the documentation were not changed, resulting in users not knowing how to use Storage and Connector, and even attempting to use Storage or Connector in the wrong way.
For example:
The content of the file is the mapping from the plugin instance name to the plugin instance, see eventmesh-connector-rocketmq plugin module for details.
implementation project(":eventmesh-connectors:eventmesh-connector-rocketmq")
#connector plugin
eventMesh.connector.plugin.type=rocketmq
// Example: Load the RocketMQ plugin
implementation project(":eventmesh-connectors:eventmesh-connector-rocketmq")
Now eventmesh-connector-rocketmq as Connector, it does not run as a plugin, here they should be eventmesh-storage-rocketmq.
Additionally, all of the image paths in this document are incorrect. They should be /static/images/...
instead of /images/...
(Similar issue: #142 ).
I'd like to add myself to the committer list.
The documents of source/sink connectors can be synced to website for easier access of users.
Event Runtime 快速开始需要修改start.sh/stop.sh 为unix格式,否则在mac下报错无法直接执行
The http and grpc documents are included inside the tcp document, and the http and grpc documents should be split from the tcp document.
https://eventmesh.apache.org/zh/docs/design-document/event-handling-and-integration/runtime-protocol
eventmesh-operator needs documentation added.
Add release notes
This is a synchronised modification of this PR: apache/eventmesh#4291
#135 The documents before 1.7.0 seem to be inaccurate, and some relative references to images are outdated.
Currently, after EventMesh graduated from Incubator, all contributors who do not have write access to the repository need Maintainer approval for the CI to run after submitting a pull request. This has increased the workload for reviewers during the review process.
To address this issue, I propose adding an optional configuration to the contribution guidelines. This will kindly remind contributors to enable GitHub Actions in their forked repositories, allowing them to self-correct various errors and allowing reviewers to directly view the CI results on the right-hand side of commit message.
After clicking on "Detail," you will be redirected to the Actions page of the forked repository.
According to the existing document (https://docs.qq.com/doc/DRFBPcmNyZHlOQ2Nq), transcribe them into Markdown and translate into English.
Another document, available at https://docs.qq.com/doc/DRGx5U25jWnZXQXpT, seems to have no immediate value for transcription.
Add new Committer mxsm
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.