Dear PPMC：
DolphinScheduler is in the early stages of incubation. At present, we have many
contributors who want to participate in the community, but they don't know how
to participate. We need to guide to generate the first community committer, so
I wrote a reference draft.
(Not considering non-code contributors for the time being)
Committer development draft for
code/document/feature/issue
First, the feature/bug is divided into three levels, we divide by cost time
(referred to as CT):
Level 1: hour level feature/bug (< 12 hours)
Level 2: Day level feature/bug (12 hours < CT <= 3 days)
Level 3: Week level feature/bug (3 days < CT < 2 weeks)
Second, the training time is calculated on a monthly basis
1~2 months, the introductory study period (community Q&A/issue reply, if you
don't know what to do, you can ask help from ppmc), it is best to fix small
bugs, and ppmc provides training for 5 times, mainly explaining the function of
each module and internal implementation
2~4 months, growth period (small function and big bug), understand the source
code of a module, complete 2 level 2 (or 1 level 3) feature/bug can apply for
committer
The above draft is regarded as a reference for the committer. Unwritten, we
will continue to encourage more partners to join the contributing team. The
above draft is only applicable to the first batch of committers.
Probably until March 2020
Do you have any suggestions?
Thank you！
2019-09-19
—————————————
DolphinScheduler(Incubator)
Lidong Dai 代立冬
[email protected]<mailto:[email protected]>
—————————————
