apache / apache/dolphinscheduler

Wanted: Who is using DolphinScheduler

Open
#57 138 comments 4 reactions 0 assignees View on GitHub
community document FAQ
Dominant language
Java
Stars
14.5k
Forks
5.1k
Avg merge
1d 21h
Merged PRs (30d)
28

Description

Who is using DolphinScheduler
====
Sincerely thank everyone who constantly keeps on using and supporting DolphinScheduler. We will try our best to make DolphinScheduler better and make the DolphinScheduler community and ecology more prosperous.

The original intention of this issue
====
1. We’d like to listen to the community to make DolphinScheduler better.
1. We want to attract more partners to contribute to DolphinScheduler.
1. Learn more about the practical use scenarios of DolphinScheduler to facilitate the next step of planning.

What we expect from you
====
Please submit a comment in this issue to include the following infomation:

your company, school or organization, and homepage
your city and country.
your contact info: blog, email, twitter (at least one).
for what business scenario do you use DolphinScheduler.

You can refer to the following sample answer:

```html
* Organization: xueqiu
* Location: Beijing, China
* Contact: bianyulong@163.com
* Scenario: Data task and ETL scheduling platform
* WeChat/Slack:
* Logo Url:
```
Thanks again for your participation ! Your support is the motivation for us to move forward.
DolphinScheduler Community

Contributor guide

Open the contributing guide

Research direction

No source file, test, or entry point is named. Read the requested response fields and add a comment with the organization, location, contact, DolphinScheduler business scenario, and optional WeChat/Slack or logo details; done means the requested usage information is provided.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.