[Enhancement] Workflow Feature Implementation
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 658
- Avg merge
- 11h 29m
- Merged PRs (30d)
- 52
Description
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues.
### Enhancement Request
At present, Workflow has planned the next iterative feature list, and now we sincerely invite you to join our EventMesh community and help us implement some sub-feature. Once you finish the task successfully, you could become our 'Contributor of Apache EventMesh (Incubating)'。
The following links are issues which are not assigned yet. For more details, please refer to the specific issue link. Feel free to select one as your task~
Dashboard:
- [x] #2180
- [x] #2181
- [x] #2865
- [x] #2866
- [ ] #2182
Engine:
- [ ] #2183
Task:
- [ ] #2184
- [ ] #2185
- [ ] #2186
- [ ] #2187
Event:
- [ ] #2188
- [ ] #2189
- [x] #2190
Queue:
- [ ] #2191
- [x] #2192
Scheduler:
- [ ] #2193
- [ ] #2194
Observability:
- [ ] #2195
- [x] #2196
Others:
- [ ] #1650
### Describe the solution you'd like
Please comment something like "Hi, I want to contribute this feature and submit a PR" in the specific issue link, so that we could assign the task to you.
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Contributor guide
Research direction
This is an umbrella request rather than an implementation task. Start by choosing an unchecked linked issue, such as #2182, #2183, or #2184, and read that issue for its entry points and acceptance criteria. This issue is done only when a specific sub-feature is selected and completed through its linked issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100