Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator

[Willem Jiang]

+1 (binding).


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Aug 23, 2019 at 9:39 AM Sheng Wu  wrote:
>
> Hi all,
>
> After the discussion of DolphinScheduler(was EasyScheduler) proposal
> (discussion thread:
> https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
> ),
> I would like to call a VOTE to accept it into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring DolphinScheduler into Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring DolphinScheduler into Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
>
> ==
> Abstract
>
> DolphinScheduler is a distributed ETL scheduling engine with powerful DAG
> visualization interface. DolphinScheduler focuses on solving the problem of
> 'complex task dependencies & triggers' in data processing. Just like its
> name, we dedicated to making the scheduling system out of the box.
>
> *Current project name of DolphinScheduler is EasyScheduler, will change it
> after it is accepted by Incubator.*
> Proposal
>
> DolphinScheduler provides many easy-to-use features to accelerate
> the engineering efficiency on data ETL workflow job. We propose a new
> concept of 'instance of process' and 'instance of task' to let developers
> to tuning their jobs on the running state of workflow instead of changing
> the task's template. Its main objectives are as follows:
>
>- Define the complex tasks' dependencies & triggers in a DAG graph by
>dragging and dropping.
>- Support cluster HA.
>- Support multi-tenant and parallel or serial backfilling data.
>- Support automatical failure job retry and recovery.
>- Support many data task types and process priority, task priority and
>relative task timeout alarm.
>
> For now, DolphinScheduler has a fairly huge community in China. It is also
> widely adopted by many companies and organizations
>  as its ETL scheduling
> tool.
>
> We believe that bringing DolphinScheduler into ASF could advance
> development of a much more stronger and more diverse open source community.
>
> Analysys submits this proposal to donate DolphinScheduler's source codes
> and all related documentations to Apache Software Foundation. The codes are
> already under Apache License Version 2.0.
>
>- Code base: https://www.github.com/analysys/easyscheduler
>- English Documentations: https://analysys.github.io/easyscheduler_docs
>- Chinese Documentations:
>https://analysys.github.io/easyscheduler_docs_cn
>
> Background
>
> We want to find a data processing tool with the following features:
>
>- Easy to use，developers can build a ETL process with a very simple drag
>and drop operation. not only for ETL developers，people who can't write code
>also can use this tool for ETL operation such as system adminitrator.
>- Solving the problem of "complex task dependencies" , and it can
>monitor the ETL running status.
>- Support multi-tenant.
>- Support many task types: Shell, MR, Spark, SQL (mysql, postgresql,
>hive, sparksql), Python, Sub_Process, Procedure, etc.
>- Support HA and linear scalability.
>
> For the above reasons, we realized that no existing product met our
> requirements, so we decided to develop this tool ourselves. We designed
> DolphinScheduler at the end of 2017. The first internal use version was
> completed in May 2018. We then iterated several internal versions and the
> system gradually became stabilized.
>
> Then we open the source code of DolphinScheduler on March 2019. It soon
> gained lot's of ETL developers interest and stars on github.
> Rationale
>
> Many organizations (>30) (refer to Who is using DolphinScheduler
>  ) already benefit
> from running DolphinScheduler to make data process pipelines more easier.
> More than 100 feature ideas
>  come from
> DolphinScheduler community. Some 3rd-party projects also plan to integrate
> with DolphinScheduler through task plugin, such as Scriptis
> , waterdrop
> . These will strengthen the
> features of DolphinScheduler.
> Current StatusMeritocracy
>
> DolphinScheduler was incubated at Analysys in 2017 and open sourced on
> GitHub in March 2019. Once open sourced, we have been quickly adopted by
> multiple organizations，DolphinScheduler has contributors and users from
> many companies; we have set up the Committer Team. New contributors are
> guided and reviewed by existed committer members. Contributions are always
> welcomed and highly valued.
> Community
>
> Now we have set development teams for DolphinScheduler in Analysys, and we
> already have external developers who contributed the 

Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator

[Liang Chen]

+1(binding), good luck.

Regards
Liang

Byung-Gon Chun  于2019年8月24日周六 上午9:38写道：

> +1 (binding)
>
> -Gon
>
>
> On Fri, Aug 23, 2019 at 10:39 AM Sheng Wu  wrote:
>
> > Hi all,
> >
> > After the discussion of DolphinScheduler(was EasyScheduler) proposal
> > (discussion thread:
> >
> >
> https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
> > ),
> > I would like to call a VOTE to accept it into the Apache Incubator.
> >
> > Please cast your vote:
> >
> >   [ ] +1, bring DolphinScheduler into Incubator
> >   [ ] +0, I don't care either way
> >   [ ] -1, do not bring DolphinScheduler into Incubator, because...
> >
> > The vote will open at least for 72 hours and only votes from the
> Incubator
> > PMC are binding.
> >
> > ==
> > Abstract
> >
> > DolphinScheduler is a distributed ETL scheduling engine with powerful DAG
> > visualization interface. DolphinScheduler focuses on solving the problem
> of
> > 'complex task dependencies & triggers' in data processing. Just like its
> > name, we dedicated to making the scheduling system out of the box.
> >
> > *Current project name of DolphinScheduler is EasyScheduler, will change
> it
> > after it is accepted by Incubator.*
> > Proposal
> >
> > DolphinScheduler provides many easy-to-use features to accelerate
> > the engineering efficiency on data ETL workflow job. We propose a new
> > concept of 'instance of process' and 'instance of task' to let developers
> > to tuning their jobs on the running state of workflow instead of changing
> > the task's template. Its main objectives are as follows:
> >
> >- Define the complex tasks' dependencies & triggers in a DAG graph by
> >dragging and dropping.
> >- Support cluster HA.
> >- Support multi-tenant and parallel or serial backfilling data.
> >- Support automatical failure job retry and recovery.
> >- Support many data task types and process priority, task priority and
> >relative task timeout alarm.
> >
> > For now, DolphinScheduler has a fairly huge community in China. It is
> also
> > widely adopted by many companies and organizations
> >  as its ETL
> > scheduling
> > tool.
> >
> > We believe that bringing DolphinScheduler into ASF could advance
> > development of a much more stronger and more diverse open source
> community.
> >
> > Analysys submits this proposal to donate DolphinScheduler's source codes
> > and all related documentations to Apache Software Foundation. The codes
> are
> > already under Apache License Version 2.0.
> >
> >- Code base: https://www.github.com/analysys/easyscheduler
> >- English Documentations:
> https://analysys.github.io/easyscheduler_docs
> >- Chinese Documentations:
> >https://analysys.github.io/easyscheduler_docs_cn
> >
> > Background
> >
> > We want to find a data processing tool with the following features:
> >
> >- Easy to use，developers can build a ETL process with a very simple
> drag
> >and drop operation. not only for ETL developers，people who can't write
> > code
> >also can use this tool for ETL operation such as system adminitrator.
> >- Solving the problem of "complex task dependencies" , and it can
> >monitor the ETL running status.
> >- Support multi-tenant.
> >- Support many task types: Shell, MR, Spark, SQL (mysql, postgresql,
> >hive, sparksql), Python, Sub_Process, Procedure, etc.
> >- Support HA and linear scalability.
> >
> > For the above reasons, we realized that no existing product met our
> > requirements, so we decided to develop this tool ourselves. We designed
> > DolphinScheduler at the end of 2017. The first internal use version was
> > completed in May 2018. We then iterated several internal versions and the
> > system gradually became stabilized.
> >
> > Then we open the source code of DolphinScheduler on March 2019. It soon
> > gained lot's of ETL developers interest and stars on github.
> > Rationale
> >
> > Many organizations (>30) (refer to Who is using DolphinScheduler
> >  ) already benefit
> > from running DolphinScheduler to make data process pipelines more easier.
> > More than 100 feature ideas
> >  come from
> > DolphinScheduler community. Some 3rd-party projects also plan to
> integrate
> > with DolphinScheduler through task plugin, such as Scriptis
> > , waterdrop
> > . These will strengthen the
> > features of DolphinScheduler.
> > Current StatusMeritocracy
> >
> > DolphinScheduler was incubated at Analysys in 2017 and open sourced on
> > GitHub in March 2019. Once open sourced, we have been quickly adopted by
> > multiple organizations，DolphinScheduler has contributors and users from
> > many companies; we have set up the Committer Team. 

Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator

[Byung-Gon Chun]

+1 (binding)

-Gon


On Fri, Aug 23, 2019 at 10:39 AM Sheng Wu  wrote:

> Hi all,
>
> After the discussion of DolphinScheduler(was EasyScheduler) proposal
> (discussion thread:
>
> https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
> ),
> I would like to call a VOTE to accept it into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring DolphinScheduler into Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring DolphinScheduler into Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
>
> ==
> Abstract
>
> DolphinScheduler is a distributed ETL scheduling engine with powerful DAG
> visualization interface. DolphinScheduler focuses on solving the problem of
> 'complex task dependencies & triggers' in data processing. Just like its
> name, we dedicated to making the scheduling system out of the box.
>
> *Current project name of DolphinScheduler is EasyScheduler, will change it
> after it is accepted by Incubator.*
> Proposal
>
> DolphinScheduler provides many easy-to-use features to accelerate
> the engineering efficiency on data ETL workflow job. We propose a new
> concept of 'instance of process' and 'instance of task' to let developers
> to tuning their jobs on the running state of workflow instead of changing
> the task's template. Its main objectives are as follows:
>
>- Define the complex tasks' dependencies & triggers in a DAG graph by
>dragging and dropping.
>- Support cluster HA.
>- Support multi-tenant and parallel or serial backfilling data.
>- Support automatical failure job retry and recovery.
>- Support many data task types and process priority, task priority and
>relative task timeout alarm.
>
> For now, DolphinScheduler has a fairly huge community in China. It is also
> widely adopted by many companies and organizations
>  as its ETL
> scheduling
> tool.
>
> We believe that bringing DolphinScheduler into ASF could advance
> development of a much more stronger and more diverse open source community.
>
> Analysys submits this proposal to donate DolphinScheduler's source codes
> and all related documentations to Apache Software Foundation. The codes are
> already under Apache License Version 2.0.
>
>- Code base: https://www.github.com/analysys/easyscheduler
>- English Documentations: https://analysys.github.io/easyscheduler_docs
>- Chinese Documentations:
>https://analysys.github.io/easyscheduler_docs_cn
>
> Background
>
> We want to find a data processing tool with the following features:
>
>- Easy to use，developers can build a ETL process with a very simple drag
>and drop operation. not only for ETL developers，people who can't write
> code
>also can use this tool for ETL operation such as system adminitrator.
>- Solving the problem of "complex task dependencies" , and it can
>monitor the ETL running status.
>- Support multi-tenant.
>- Support many task types: Shell, MR, Spark, SQL (mysql, postgresql,
>hive, sparksql), Python, Sub_Process, Procedure, etc.
>- Support HA and linear scalability.
>
> For the above reasons, we realized that no existing product met our
> requirements, so we decided to develop this tool ourselves. We designed
> DolphinScheduler at the end of 2017. The first internal use version was
> completed in May 2018. We then iterated several internal versions and the
> system gradually became stabilized.
>
> Then we open the source code of DolphinScheduler on March 2019. It soon
> gained lot's of ETL developers interest and stars on github.
> Rationale
>
> Many organizations (>30) (refer to Who is using DolphinScheduler
>  ) already benefit
> from running DolphinScheduler to make data process pipelines more easier.
> More than 100 feature ideas
>  come from
> DolphinScheduler community. Some 3rd-party projects also plan to integrate
> with DolphinScheduler through task plugin, such as Scriptis
> , waterdrop
> . These will strengthen the
> features of DolphinScheduler.
> Current StatusMeritocracy
>
> DolphinScheduler was incubated at Analysys in 2017 and open sourced on
> GitHub in March 2019. Once open sourced, we have been quickly adopted by
> multiple organizations，DolphinScheduler has contributors and users from
> many companies; we have set up the Committer Team. New contributors are
> guided and reviewed by existed committer members. Contributions are always
> welcomed and highly valued.
> Community
>
> Now we have set development teams for DolphinScheduler in Analysys, and we
> already have external developers who contributed the code. We already have
> a user group of more 

Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator

[Tan,Zhongyi]

+1, thanks

在 2019/8/23 上午9:39，“Sheng Wu” 写入:

Hi all,

After the discussion of DolphinScheduler(was EasyScheduler) proposal
(discussion thread:

https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
),
I would like to call a VOTE to accept it into the Apache Incubator.

Please cast your vote:

  [ ] +1, bring DolphinScheduler into Incubator
  [ ] +0, I don't care either way
  [ ] -1, do not bring DolphinScheduler into Incubator, because...

The vote will open at least for 72 hours and only votes from the Incubator
PMC are binding.

==
Abstract

DolphinScheduler is a distributed ETL scheduling engine with powerful DAG
visualization interface. DolphinScheduler focuses on solving the problem of
'complex task dependencies & triggers' in data processing. Just like its
name, we dedicated to making the scheduling system out of the box.

*Current project name of DolphinScheduler is EasyScheduler, will change it
after it is accepted by Incubator.*
Proposal

DolphinScheduler provides many easy-to-use features to accelerate
the engineering efficiency on data ETL workflow job. We propose a new
concept of 'instance of process' and 'instance of task' to let developers
to tuning their jobs on the running state of workflow instead of changing
the task's template. Its main objectives are as follows:

   - Define the complex tasks' dependencies & triggers in a DAG graph by
   dragging and dropping.
   - Support cluster HA.
   - Support multi-tenant and parallel or serial backfilling data.
   - Support automatical failure job retry and recovery.
   - Support many data task types and process priority, task priority and
   relative task timeout alarm.

For now, DolphinScheduler has a fairly huge community in China. It is also
widely adopted by many companies and organizations
 as its ETL scheduling
tool.

We believe that bringing DolphinScheduler into ASF could advance
development of a much more stronger and more diverse open source community.

Analysys submits this proposal to donate DolphinScheduler's source codes
and all related documentations to Apache Software Foundation. The codes are
already under Apache License Version 2.0.

   - Code base: https://www.github.com/analysys/easyscheduler
   - English Documentations: https://analysys.github.io/easyscheduler_docs
   - Chinese Documentations:
   https://analysys.github.io/easyscheduler_docs_cn

Background

We want to find a data processing tool with the following features:

   - Easy to use，developers can build a ETL process with a very simple drag
   and drop operation. not only for ETL developers，people who can't write 
code
   also can use this tool for ETL operation such as system adminitrator.
   - Solving the problem of "complex task dependencies" , and it can
   monitor the ETL running status.
   - Support multi-tenant.
   - Support many task types: Shell, MR, Spark, SQL (mysql, postgresql,
   hive, sparksql), Python, Sub_Process, Procedure, etc.
   - Support HA and linear scalability.

For the above reasons, we realized that no existing product met our
requirements, so we decided to develop this tool ourselves. We designed
DolphinScheduler at the end of 2017. The first internal use version was
completed in May 2018. We then iterated several internal versions and the
system gradually became stabilized.

Then we open the source code of DolphinScheduler on March 2019. It soon
gained lot's of ETL developers interest and stars on github.
Rationale

Many organizations (>30) (refer to Who is using DolphinScheduler
 ) already benefit
from running DolphinScheduler to make data process pipelines more easier.
More than 100 feature ideas
 come from
DolphinScheduler community. Some 3rd-party projects also plan to integrate
with DolphinScheduler through task plugin, such as Scriptis
, waterdrop
. These will strengthen the
features of DolphinScheduler.
Current StatusMeritocracy

DolphinScheduler was incubated at Analysys in 2017 and open sourced on
GitHub in March 2019. Once open sourced, we have been quickly adopted by
multiple organizations，DolphinScheduler has contributors and users from
many companies; we have set up the Committer Team. New contributors are
guided and reviewed by existed committer members. Contributions are always
welcomed and highly 

Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator

[Michael Wall]

+1 binding

Mike Wall

On Fri, Aug 23, 2019 at 12:29 PM Felix Cheung 
wrote:

> +1
>
> On Fri, Aug 23, 2019 at 8:11 AM ShaoFeng Shi 
> wrote:
>
> > +1 (binding)
> >
> > I believe the DolphinScheduler project will bring value to ASF. The team
> is
> > very open and the community is already very active. Glad to see it to
> join
> > the incubator.
> >
> > Best regards,
> >
> > Shaofeng Shi 史少锋
> > Apache Kylin PMC
> > Email: shaofeng...@apache.org
> >
> > Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> > Join Kylin user mail group: user-subscr...@kylin.apache.org
> > Join Kylin dev mail group: dev-subscr...@kylin.apache.org
> >
> >
> >
> >
> > Furkan KAMACI  于2019年8月23日周五 下午5:32写道：
> >
> > > Hi,
> > >
> > > +1!
> > >
> > > Kind Regards,
> > > Furkan KAMACI
> > >
> > > 23 Ağu 2019 Cum, saat 12:25 tarihinde Sheng Wu <
> > wu.sheng.841...@gmail.com>
> > > şunu yazdı:
> > >
> > > > Julian Feinauer  于2019年8月23日周五
> 下午5:20写道：
> > > >
> > > > > Hi,
> > > > >
> > > > > Your proposal looks good and the initiual PPMC already looks
> > 'diverse'.
> > > > > Furthermore, it seems like you have a good mentoring team on board.
> > > > >
> > > > > One 'minor' concern is that I think it is best to use Apaches Infra
> > for
> > > > CI
> > > > > and Issue tracking.
> > > > > Which I would greatly prefer over using Github issues.
> > > > >
> > > >
> > > > Hi Julian
> > > >
> > > > Thanks for your supports.
> > > >
> > > > In the proposal, Jenkins means Apache INFRA Jenkins. I just changed
> the
> > > > proposal text to `Apache Jenkins`.
> > > >
> > > > I think GitHub Issue tracker is an open option, as many ASF projects
> > are
> > > > using it already, and GitHub issue notifications have been achieved
> in
> > > the
> > > > mail list.
> > > > Due to the team requires to use that, I think should be OK.
> > > >
> > > > Sheng Wu 吴晟
> > > >
> > > > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> > > > Twitter, wusheng1108
> > > >
> > > >
> > > >
> > > > >
> > > > > But overall, a clear +1 (binding) from my side.
> > > > >
> > > > > Julian
> > > > >
> > > > > Am 23.08.19, 11:14 schrieb "Kevin Ratnasekera" <
> > > djkevincr1...@gmail.com
> > > > >:
> > > > >
> > > > > +1
> > > > >
> > > > > On Fri, Aug 23, 2019 at 7:09 AM Sheng Wu 
> > > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > After the discussion of DolphinScheduler(was EasyScheduler)
> > > > proposal
> > > > > > (discussion thread:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
> > > > > > ),
> > > > > > I would like to call a VOTE to accept it into the Apache
> > > Incubator.
> > > > > >
> > > > > > Please cast your vote:
> > > > > >
> > > > > >   [ ] +1, bring DolphinScheduler into Incubator
> > > > > >   [ ] +0, I don't care either way
> > > > > >   [ ] -1, do not bring DolphinScheduler into Incubator,
> > > because...
> > > > > >
> > > > > > The vote will open at least for 72 hours and only votes from
> > the
> > > > > Incubator
> > > > > > PMC are binding.
> > > > > >
> > > > > > ==
> > > > > > Abstract
> > > > > >
> > > > > > DolphinScheduler is a distributed ETL scheduling engine with
> > > > > powerful DAG
> > > > > > visualization interface. DolphinScheduler focuses on solving
> > the
> > > > > problem of
> > > > > > 'complex task dependencies & triggers' in data processing.
> Just
> > > > like
> > > > > its
> > > > > > name, we dedicated to making the scheduling system out of the
> > > box.
> > > > > >
> > > > > > *Current project name of DolphinScheduler is EasyScheduler,
> > will
> > > > > change it
> > > > > > after it is accepted by Incubator.*
> > > > > > Proposal
> > > > > >
> > > > > > DolphinScheduler provides many easy-to-use features to
> > accelerate
> > > > > > the engineering efficiency on data ETL workflow job. We
> > propose a
> > > > new
> > > > > > concept of 'instance of process' and 'instance of task' to
> let
> > > > > developers
> > > > > > to tuning their jobs on the running state of workflow instead
> > of
> > > > > changing
> > > > > > the task's template. Its main objectives are as follows:
> > > > > >
> > > > > >- Define the complex tasks' dependencies & triggers in a
> DAG
> > > > > graph by
> > > > > >dragging and dropping.
> > > > > >- Support cluster HA.
> > > > > >- Support multi-tenant and parallel or serial backfilling
> > > data.
> > > > > >- Support automatical failure job retry and recovery.
> > > > > >- Support many data task types and process priority, task
> > > > > priority and
> > > > > >relative task timeout alarm.
> > > > > >
> > > > > > For now, DolphinScheduler has a fairly huge community in
> China.
> > > It
> > > 

Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator

[zhangli...@apache.org]

+1 (not binding), good luck

--

Liang Zhang (John)
Apache ShardingSphere & Dubbo


Felix Cheung  于2019年8月24日周六 上午12:29写道：

> +1
>
> On Fri, Aug 23, 2019 at 8:11 AM ShaoFeng Shi 
> wrote:
>
> > +1 (binding)
> >
> > I believe the DolphinScheduler project will bring value to ASF. The team
> is
> > very open and the community is already very active. Glad to see it to
> join
> > the incubator.
> >
> > Best regards,
> >
> > Shaofeng Shi 史少锋
> > Apache Kylin PMC
> > Email: shaofeng...@apache.org
> >
> > Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> > Join Kylin user mail group: user-subscr...@kylin.apache.org
> > Join Kylin dev mail group: dev-subscr...@kylin.apache.org
> >
> >
> >
> >
> > Furkan KAMACI  于2019年8月23日周五 下午5:32写道：
> >
> > > Hi,
> > >
> > > +1!
> > >
> > > Kind Regards,
> > > Furkan KAMACI
> > >
> > > 23 Ağu 2019 Cum, saat 12:25 tarihinde Sheng Wu <
> > wu.sheng.841...@gmail.com>
> > > şunu yazdı:
> > >
> > > > Julian Feinauer  于2019年8月23日周五
> 下午5:20写道：
> > > >
> > > > > Hi,
> > > > >
> > > > > Your proposal looks good and the initiual PPMC already looks
> > 'diverse'.
> > > > > Furthermore, it seems like you have a good mentoring team on board.
> > > > >
> > > > > One 'minor' concern is that I think it is best to use Apaches Infra
> > for
> > > > CI
> > > > > and Issue tracking.
> > > > > Which I would greatly prefer over using Github issues.
> > > > >
> > > >
> > > > Hi Julian
> > > >
> > > > Thanks for your supports.
> > > >
> > > > In the proposal, Jenkins means Apache INFRA Jenkins. I just changed
> the
> > > > proposal text to `Apache Jenkins`.
> > > >
> > > > I think GitHub Issue tracker is an open option, as many ASF projects
> > are
> > > > using it already, and GitHub issue notifications have been achieved
> in
> > > the
> > > > mail list.
> > > > Due to the team requires to use that, I think should be OK.
> > > >
> > > > Sheng Wu 吴晟
> > > >
> > > > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> > > > Twitter, wusheng1108
> > > >
> > > >
> > > >
> > > > >
> > > > > But overall, a clear +1 (binding) from my side.
> > > > >
> > > > > Julian
> > > > >
> > > > > Am 23.08.19, 11:14 schrieb "Kevin Ratnasekera" <
> > > djkevincr1...@gmail.com
> > > > >:
> > > > >
> > > > > +1
> > > > >
> > > > > On Fri, Aug 23, 2019 at 7:09 AM Sheng Wu 
> > > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > After the discussion of DolphinScheduler(was EasyScheduler)
> > > > proposal
> > > > > > (discussion thread:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
> > > > > > ),
> > > > > > I would like to call a VOTE to accept it into the Apache
> > > Incubator.
> > > > > >
> > > > > > Please cast your vote:
> > > > > >
> > > > > >   [ ] +1, bring DolphinScheduler into Incubator
> > > > > >   [ ] +0, I don't care either way
> > > > > >   [ ] -1, do not bring DolphinScheduler into Incubator,
> > > because...
> > > > > >
> > > > > > The vote will open at least for 72 hours and only votes from
> > the
> > > > > Incubator
> > > > > > PMC are binding.
> > > > > >
> > > > > > ==
> > > > > > Abstract
> > > > > >
> > > > > > DolphinScheduler is a distributed ETL scheduling engine with
> > > > > powerful DAG
> > > > > > visualization interface. DolphinScheduler focuses on solving
> > the
> > > > > problem of
> > > > > > 'complex task dependencies & triggers' in data processing.
> Just
> > > > like
> > > > > its
> > > > > > name, we dedicated to making the scheduling system out of the
> > > box.
> > > > > >
> > > > > > *Current project name of DolphinScheduler is EasyScheduler,
> > will
> > > > > change it
> > > > > > after it is accepted by Incubator.*
> > > > > > Proposal
> > > > > >
> > > > > > DolphinScheduler provides many easy-to-use features to
> > accelerate
> > > > > > the engineering efficiency on data ETL workflow job. We
> > propose a
> > > > new
> > > > > > concept of 'instance of process' and 'instance of task' to
> let
> > > > > developers
> > > > > > to tuning their jobs on the running state of workflow instead
> > of
> > > > > changing
> > > > > > the task's template. Its main objectives are as follows:
> > > > > >
> > > > > >- Define the complex tasks' dependencies & triggers in a
> DAG
> > > > > graph by
> > > > > >dragging and dropping.
> > > > > >- Support cluster HA.
> > > > > >- Support multi-tenant and parallel or serial backfilling
> > > data.
> > > > > >- Support automatical failure job retry and recovery.
> > > > > >- Support many data task types and process priority, task
> > > > > priority and
> > > > > >relative task timeout alarm.
> > > > > >
> > > > > > For now, 

Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator

[Felix Cheung]

+1

On Fri, Aug 23, 2019 at 8:11 AM ShaoFeng Shi  wrote:

> +1 (binding)
>
> I believe the DolphinScheduler project will bring value to ASF. The team is
> very open and the community is already very active. Glad to see it to join
> the incubator.
>
> Best regards,
>
> Shaofeng Shi 史少锋
> Apache Kylin PMC
> Email: shaofeng...@apache.org
>
> Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> Join Kylin user mail group: user-subscr...@kylin.apache.org
> Join Kylin dev mail group: dev-subscr...@kylin.apache.org
>
>
>
>
> Furkan KAMACI  于2019年8月23日周五 下午5:32写道：
>
> > Hi,
> >
> > +1!
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > 23 Ağu 2019 Cum, saat 12:25 tarihinde Sheng Wu <
> wu.sheng.841...@gmail.com>
> > şunu yazdı:
> >
> > > Julian Feinauer  于2019年8月23日周五 下午5:20写道：
> > >
> > > > Hi,
> > > >
> > > > Your proposal looks good and the initiual PPMC already looks
> 'diverse'.
> > > > Furthermore, it seems like you have a good mentoring team on board.
> > > >
> > > > One 'minor' concern is that I think it is best to use Apaches Infra
> for
> > > CI
> > > > and Issue tracking.
> > > > Which I would greatly prefer over using Github issues.
> > > >
> > >
> > > Hi Julian
> > >
> > > Thanks for your supports.
> > >
> > > In the proposal, Jenkins means Apache INFRA Jenkins. I just changed the
> > > proposal text to `Apache Jenkins`.
> > >
> > > I think GitHub Issue tracker is an open option, as many ASF projects
> are
> > > using it already, and GitHub issue notifications have been achieved in
> > the
> > > mail list.
> > > Due to the team requires to use that, I think should be OK.
> > >
> > > Sheng Wu 吴晟
> > >
> > > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> > > Twitter, wusheng1108
> > >
> > >
> > >
> > > >
> > > > But overall, a clear +1 (binding) from my side.
> > > >
> > > > Julian
> > > >
> > > > Am 23.08.19, 11:14 schrieb "Kevin Ratnasekera" <
> > djkevincr1...@gmail.com
> > > >:
> > > >
> > > > +1
> > > >
> > > > On Fri, Aug 23, 2019 at 7:09 AM Sheng Wu 
> > wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > After the discussion of DolphinScheduler(was EasyScheduler)
> > > proposal
> > > > > (discussion thread:
> > > > >
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
> > > > > ),
> > > > > I would like to call a VOTE to accept it into the Apache
> > Incubator.
> > > > >
> > > > > Please cast your vote:
> > > > >
> > > > >   [ ] +1, bring DolphinScheduler into Incubator
> > > > >   [ ] +0, I don't care either way
> > > > >   [ ] -1, do not bring DolphinScheduler into Incubator,
> > because...
> > > > >
> > > > > The vote will open at least for 72 hours and only votes from
> the
> > > > Incubator
> > > > > PMC are binding.
> > > > >
> > > > > ==
> > > > > Abstract
> > > > >
> > > > > DolphinScheduler is a distributed ETL scheduling engine with
> > > > powerful DAG
> > > > > visualization interface. DolphinScheduler focuses on solving
> the
> > > > problem of
> > > > > 'complex task dependencies & triggers' in data processing. Just
> > > like
> > > > its
> > > > > name, we dedicated to making the scheduling system out of the
> > box.
> > > > >
> > > > > *Current project name of DolphinScheduler is EasyScheduler,
> will
> > > > change it
> > > > > after it is accepted by Incubator.*
> > > > > Proposal
> > > > >
> > > > > DolphinScheduler provides many easy-to-use features to
> accelerate
> > > > > the engineering efficiency on data ETL workflow job. We
> propose a
> > > new
> > > > > concept of 'instance of process' and 'instance of task' to let
> > > > developers
> > > > > to tuning their jobs on the running state of workflow instead
> of
> > > > changing
> > > > > the task's template. Its main objectives are as follows:
> > > > >
> > > > >- Define the complex tasks' dependencies & triggers in a DAG
> > > > graph by
> > > > >dragging and dropping.
> > > > >- Support cluster HA.
> > > > >- Support multi-tenant and parallel or serial backfilling
> > data.
> > > > >- Support automatical failure job retry and recovery.
> > > > >- Support many data task types and process priority, task
> > > > priority and
> > > > >relative task timeout alarm.
> > > > >
> > > > > For now, DolphinScheduler has a fairly huge community in China.
> > It
> > > > is also
> > > > > widely adopted by many companies and organizations
> > > > >  as its
> ETL
> > > > > scheduling
> > > > > tool.
> > > > >
> > > > > We believe that bringing DolphinScheduler into ASF could
> advance
> > > > > development of a much more stronger and more diverse open
> source
> > > > community.
> > > > >
> > 

Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator

[ShaoFeng Shi]

+1 (binding)

I believe the DolphinScheduler project will bring value to ASF. The team is
very open and the community is already very active. Glad to see it to join
the incubator.

Best regards,

Shaofeng Shi 史少锋
Apache Kylin PMC
Email: shaofeng...@apache.org

Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
Join Kylin user mail group: user-subscr...@kylin.apache.org
Join Kylin dev mail group: dev-subscr...@kylin.apache.org




Furkan KAMACI  于2019年8月23日周五 下午5:32写道：

> Hi,
>
> +1!
>
> Kind Regards,
> Furkan KAMACI
>
> 23 Ağu 2019 Cum, saat 12:25 tarihinde Sheng Wu 
> şunu yazdı:
>
> > Julian Feinauer  于2019年8月23日周五 下午5:20写道：
> >
> > > Hi,
> > >
> > > Your proposal looks good and the initiual PPMC already looks 'diverse'.
> > > Furthermore, it seems like you have a good mentoring team on board.
> > >
> > > One 'minor' concern is that I think it is best to use Apaches Infra for
> > CI
> > > and Issue tracking.
> > > Which I would greatly prefer over using Github issues.
> > >
> >
> > Hi Julian
> >
> > Thanks for your supports.
> >
> > In the proposal, Jenkins means Apache INFRA Jenkins. I just changed the
> > proposal text to `Apache Jenkins`.
> >
> > I think GitHub Issue tracker is an open option, as many ASF projects are
> > using it already, and GitHub issue notifications have been achieved in
> the
> > mail list.
> > Due to the team requires to use that, I think should be OK.
> >
> > Sheng Wu 吴晟
> >
> > Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> > Twitter, wusheng1108
> >
> >
> >
> > >
> > > But overall, a clear +1 (binding) from my side.
> > >
> > > Julian
> > >
> > > Am 23.08.19, 11:14 schrieb "Kevin Ratnasekera" <
> djkevincr1...@gmail.com
> > >:
> > >
> > > +1
> > >
> > > On Fri, Aug 23, 2019 at 7:09 AM Sheng Wu 
> wrote:
> > >
> > > > Hi all,
> > > >
> > > > After the discussion of DolphinScheduler(was EasyScheduler)
> > proposal
> > > > (discussion thread:
> > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
> > > > ),
> > > > I would like to call a VOTE to accept it into the Apache
> Incubator.
> > > >
> > > > Please cast your vote:
> > > >
> > > >   [ ] +1, bring DolphinScheduler into Incubator
> > > >   [ ] +0, I don't care either way
> > > >   [ ] -1, do not bring DolphinScheduler into Incubator,
> because...
> > > >
> > > > The vote will open at least for 72 hours and only votes from the
> > > Incubator
> > > > PMC are binding.
> > > >
> > > > ==
> > > > Abstract
> > > >
> > > > DolphinScheduler is a distributed ETL scheduling engine with
> > > powerful DAG
> > > > visualization interface. DolphinScheduler focuses on solving the
> > > problem of
> > > > 'complex task dependencies & triggers' in data processing. Just
> > like
> > > its
> > > > name, we dedicated to making the scheduling system out of the
> box.
> > > >
> > > > *Current project name of DolphinScheduler is EasyScheduler, will
> > > change it
> > > > after it is accepted by Incubator.*
> > > > Proposal
> > > >
> > > > DolphinScheduler provides many easy-to-use features to accelerate
> > > > the engineering efficiency on data ETL workflow job. We propose a
> > new
> > > > concept of 'instance of process' and 'instance of task' to let
> > > developers
> > > > to tuning their jobs on the running state of workflow instead of
> > > changing
> > > > the task's template. Its main objectives are as follows:
> > > >
> > > >- Define the complex tasks' dependencies & triggers in a DAG
> > > graph by
> > > >dragging and dropping.
> > > >- Support cluster HA.
> > > >- Support multi-tenant and parallel or serial backfilling
> data.
> > > >- Support automatical failure job retry and recovery.
> > > >- Support many data task types and process priority, task
> > > priority and
> > > >relative task timeout alarm.
> > > >
> > > > For now, DolphinScheduler has a fairly huge community in China.
> It
> > > is also
> > > > widely adopted by many companies and organizations
> > > >  as its ETL
> > > > scheduling
> > > > tool.
> > > >
> > > > We believe that bringing DolphinScheduler into ASF could advance
> > > > development of a much more stronger and more diverse open source
> > > community.
> > > >
> > > > Analysys submits this proposal to donate DolphinScheduler's
> source
> > > codes
> > > > and all related documentations to Apache Software Foundation. The
> > > codes are
> > > > already under Apache License Version 2.0.
> > > >
> > > >- Code base: https://www.github.com/analysys/easyscheduler
> > > >- English Documentations:
> > > 

Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator

[Furkan KAMACI]

Hi,

+1!

Kind Regards,
Furkan KAMACI

23 Ağu 2019 Cum, saat 12:25 tarihinde Sheng Wu 
şunu yazdı:

> Julian Feinauer  于2019年8月23日周五 下午5:20写道：
>
> > Hi,
> >
> > Your proposal looks good and the initiual PPMC already looks 'diverse'.
> > Furthermore, it seems like you have a good mentoring team on board.
> >
> > One 'minor' concern is that I think it is best to use Apaches Infra for
> CI
> > and Issue tracking.
> > Which I would greatly prefer over using Github issues.
> >
>
> Hi Julian
>
> Thanks for your supports.
>
> In the proposal, Jenkins means Apache INFRA Jenkins. I just changed the
> proposal text to `Apache Jenkins`.
>
> I think GitHub Issue tracker is an open option, as many ASF projects are
> using it already, and GitHub issue notifications have been achieved in the
> mail list.
> Due to the team requires to use that, I think should be OK.
>
> Sheng Wu 吴晟
>
> Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
> Twitter, wusheng1108
>
>
>
> >
> > But overall, a clear +1 (binding) from my side.
> >
> > Julian
> >
> > Am 23.08.19, 11:14 schrieb "Kevin Ratnasekera"  >:
> >
> > +1
> >
> > On Fri, Aug 23, 2019 at 7:09 AM Sheng Wu  wrote:
> >
> > > Hi all,
> > >
> > > After the discussion of DolphinScheduler(was EasyScheduler)
> proposal
> > > (discussion thread:
> > >
> > >
> >
> https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
> > > ),
> > > I would like to call a VOTE to accept it into the Apache Incubator.
> > >
> > > Please cast your vote:
> > >
> > >   [ ] +1, bring DolphinScheduler into Incubator
> > >   [ ] +0, I don't care either way
> > >   [ ] -1, do not bring DolphinScheduler into Incubator, because...
> > >
> > > The vote will open at least for 72 hours and only votes from the
> > Incubator
> > > PMC are binding.
> > >
> > > ==
> > > Abstract
> > >
> > > DolphinScheduler is a distributed ETL scheduling engine with
> > powerful DAG
> > > visualization interface. DolphinScheduler focuses on solving the
> > problem of
> > > 'complex task dependencies & triggers' in data processing. Just
> like
> > its
> > > name, we dedicated to making the scheduling system out of the box.
> > >
> > > *Current project name of DolphinScheduler is EasyScheduler, will
> > change it
> > > after it is accepted by Incubator.*
> > > Proposal
> > >
> > > DolphinScheduler provides many easy-to-use features to accelerate
> > > the engineering efficiency on data ETL workflow job. We propose a
> new
> > > concept of 'instance of process' and 'instance of task' to let
> > developers
> > > to tuning their jobs on the running state of workflow instead of
> > changing
> > > the task's template. Its main objectives are as follows:
> > >
> > >- Define the complex tasks' dependencies & triggers in a DAG
> > graph by
> > >dragging and dropping.
> > >- Support cluster HA.
> > >- Support multi-tenant and parallel or serial backfilling data.
> > >- Support automatical failure job retry and recovery.
> > >- Support many data task types and process priority, task
> > priority and
> > >relative task timeout alarm.
> > >
> > > For now, DolphinScheduler has a fairly huge community in China. It
> > is also
> > > widely adopted by many companies and organizations
> > >  as its ETL
> > > scheduling
> > > tool.
> > >
> > > We believe that bringing DolphinScheduler into ASF could advance
> > > development of a much more stronger and more diverse open source
> > community.
> > >
> > > Analysys submits this proposal to donate DolphinScheduler's source
> > codes
> > > and all related documentations to Apache Software Foundation. The
> > codes are
> > > already under Apache License Version 2.0.
> > >
> > >- Code base: https://www.github.com/analysys/easyscheduler
> > >- English Documentations:
> > https://analysys.github.io/easyscheduler_docs
> > >- Chinese Documentations:
> > >https://analysys.github.io/easyscheduler_docs_cn
> > >
> > > Background
> > >
> > > We want to find a data processing tool with the following features:
> > >
> > >- Easy to use，developers can build a ETL process with a very
> > simple drag
> > >and drop operation. not only for ETL developers，people who can't
> > write
> > > code
> > >also can use this tool for ETL operation such as system
> > adminitrator.
> > >- Solving the problem of "complex task dependencies" , and it
> can
> > >monitor the ETL running status.
> > >- Support multi-tenant.
> > >- Support many task types: Shell, MR, Spark, SQL (mysql,
> > postgresql,
> > >hive, sparksql), Python, 

Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator

[Sheng Wu]

Julian Feinauer  于2019年8月23日周五 下午5:20写道：

> Hi,
>
> Your proposal looks good and the initiual PPMC already looks 'diverse'.
> Furthermore, it seems like you have a good mentoring team on board.
>
> One 'minor' concern is that I think it is best to use Apaches Infra for CI
> and Issue tracking.
> Which I would greatly prefer over using Github issues.
>

Hi Julian

Thanks for your supports.

In the proposal, Jenkins means Apache INFRA Jenkins. I just changed the
proposal text to `Apache Jenkins`.

I think GitHub Issue tracker is an open option, as many ASF projects are
using it already, and GitHub issue notifications have been achieved in the
mail list.
Due to the team requires to use that, I think should be OK.

Sheng Wu 吴晟

Apache SkyWalking, Apache ShardingSphere(Incubating), Zipkin
Twitter, wusheng1108



>
> But overall, a clear +1 (binding) from my side.
>
> Julian
>
> Am 23.08.19, 11:14 schrieb "Kevin Ratnasekera" :
>
> +1
>
> On Fri, Aug 23, 2019 at 7:09 AM Sheng Wu  wrote:
>
> > Hi all,
> >
> > After the discussion of DolphinScheduler(was EasyScheduler) proposal
> > (discussion thread:
> >
> >
> https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
> > ),
> > I would like to call a VOTE to accept it into the Apache Incubator.
> >
> > Please cast your vote:
> >
> >   [ ] +1, bring DolphinScheduler into Incubator
> >   [ ] +0, I don't care either way
> >   [ ] -1, do not bring DolphinScheduler into Incubator, because...
> >
> > The vote will open at least for 72 hours and only votes from the
> Incubator
> > PMC are binding.
> >
> > ==
> > Abstract
> >
> > DolphinScheduler is a distributed ETL scheduling engine with
> powerful DAG
> > visualization interface. DolphinScheduler focuses on solving the
> problem of
> > 'complex task dependencies & triggers' in data processing. Just like
> its
> > name, we dedicated to making the scheduling system out of the box.
> >
> > *Current project name of DolphinScheduler is EasyScheduler, will
> change it
> > after it is accepted by Incubator.*
> > Proposal
> >
> > DolphinScheduler provides many easy-to-use features to accelerate
> > the engineering efficiency on data ETL workflow job. We propose a new
> > concept of 'instance of process' and 'instance of task' to let
> developers
> > to tuning their jobs on the running state of workflow instead of
> changing
> > the task's template. Its main objectives are as follows:
> >
> >- Define the complex tasks' dependencies & triggers in a DAG
> graph by
> >dragging and dropping.
> >- Support cluster HA.
> >- Support multi-tenant and parallel or serial backfilling data.
> >- Support automatical failure job retry and recovery.
> >- Support many data task types and process priority, task
> priority and
> >relative task timeout alarm.
> >
> > For now, DolphinScheduler has a fairly huge community in China. It
> is also
> > widely adopted by many companies and organizations
> >  as its ETL
> > scheduling
> > tool.
> >
> > We believe that bringing DolphinScheduler into ASF could advance
> > development of a much more stronger and more diverse open source
> community.
> >
> > Analysys submits this proposal to donate DolphinScheduler's source
> codes
> > and all related documentations to Apache Software Foundation. The
> codes are
> > already under Apache License Version 2.0.
> >
> >- Code base: https://www.github.com/analysys/easyscheduler
> >- English Documentations:
> https://analysys.github.io/easyscheduler_docs
> >- Chinese Documentations:
> >https://analysys.github.io/easyscheduler_docs_cn
> >
> > Background
> >
> > We want to find a data processing tool with the following features:
> >
> >- Easy to use，developers can build a ETL process with a very
> simple drag
> >and drop operation. not only for ETL developers，people who can't
> write
> > code
> >also can use this tool for ETL operation such as system
> adminitrator.
> >- Solving the problem of "complex task dependencies" , and it can
> >monitor the ETL running status.
> >- Support multi-tenant.
> >- Support many task types: Shell, MR, Spark, SQL (mysql,
> postgresql,
> >hive, sparksql), Python, Sub_Process, Procedure, etc.
> >- Support HA and linear scalability.
> >
> > For the above reasons, we realized that no existing product met our
> > requirements, so we decided to develop this tool ourselves. We
> designed
> > DolphinScheduler at the end of 2017. The first internal use version
> was
> > completed in May 2018. We then iterated 

Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator

[Julian Feinauer]

Hi,

Your proposal looks good and the initiual PPMC already looks 'diverse'.
Furthermore, it seems like you have a good mentoring team on board.

One 'minor' concern is that I think it is best to use Apaches Infra for CI and 
Issue tracking.
Which I would greatly prefer over using Github issues.

But overall, a clear +1 (binding) from my side.

Julian

Am 23.08.19, 11:14 schrieb "Kevin Ratnasekera" :

+1

On Fri, Aug 23, 2019 at 7:09 AM Sheng Wu  wrote:

> Hi all,
>
> After the discussion of DolphinScheduler(was EasyScheduler) proposal
> (discussion thread:
>
> 
https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
> ),
> I would like to call a VOTE to accept it into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring DolphinScheduler into Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring DolphinScheduler into Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
>
> ==
> Abstract
>
> DolphinScheduler is a distributed ETL scheduling engine with powerful DAG
> visualization interface. DolphinScheduler focuses on solving the problem 
of
> 'complex task dependencies & triggers' in data processing. Just like its
> name, we dedicated to making the scheduling system out of the box.
>
> *Current project name of DolphinScheduler is EasyScheduler, will change it
> after it is accepted by Incubator.*
> Proposal
>
> DolphinScheduler provides many easy-to-use features to accelerate
> the engineering efficiency on data ETL workflow job. We propose a new
> concept of 'instance of process' and 'instance of task' to let developers
> to tuning their jobs on the running state of workflow instead of changing
> the task's template. Its main objectives are as follows:
>
>- Define the complex tasks' dependencies & triggers in a DAG graph by
>dragging and dropping.
>- Support cluster HA.
>- Support multi-tenant and parallel or serial backfilling data.
>- Support automatical failure job retry and recovery.
>- Support many data task types and process priority, task priority and
>relative task timeout alarm.
>
> For now, DolphinScheduler has a fairly huge community in China. It is also
> widely adopted by many companies and organizations
>  as its ETL
> scheduling
> tool.
>
> We believe that bringing DolphinScheduler into ASF could advance
> development of a much more stronger and more diverse open source 
community.
>
> Analysys submits this proposal to donate DolphinScheduler's source codes
> and all related documentations to Apache Software Foundation. The codes 
are
> already under Apache License Version 2.0.
>
>- Code base: https://www.github.com/analysys/easyscheduler
>- English Documentations: https://analysys.github.io/easyscheduler_docs
>- Chinese Documentations:
>https://analysys.github.io/easyscheduler_docs_cn
>
> Background
>
> We want to find a data processing tool with the following features:
>
>- Easy to use，developers can build a ETL process with a very simple 
drag
>and drop operation. not only for ETL developers，people who can't write
> code
>also can use this tool for ETL operation such as system adminitrator.
>- Solving the problem of "complex task dependencies" , and it can
>monitor the ETL running status.
>- Support multi-tenant.
>- Support many task types: Shell, MR, Spark, SQL (mysql, postgresql,
>hive, sparksql), Python, Sub_Process, Procedure, etc.
>- Support HA and linear scalability.
>
> For the above reasons, we realized that no existing product met our
> requirements, so we decided to develop this tool ourselves. We designed
> DolphinScheduler at the end of 2017. The first internal use version was
> completed in May 2018. We then iterated several internal versions and the
> system gradually became stabilized.
>
> Then we open the source code of DolphinScheduler on March 2019. It soon
> gained lot's of ETL developers interest and stars on github.
> Rationale
>
> Many organizations (>30) (refer to Who is using DolphinScheduler
>  ) already benefit
> from running DolphinScheduler to make data process pipelines more easier.
> More than 100 feature ideas
>  come from
> DolphinScheduler community. Some 3rd-party projects also plan to integrate
> with DolphinScheduler through task plugin, such as Scriptis
   

Re: [VOTE] Accept DolphinScheduler(was EasyScheduler) into Apache Incubator

[Kevin Ratnasekera]

+1

On Fri, Aug 23, 2019 at 7:09 AM Sheng Wu  wrote:

> Hi all,
>
> After the discussion of DolphinScheduler(was EasyScheduler) proposal
> (discussion thread:
>
> https://lists.apache.org/thread.html/d3ac53bddf91391e54f63d042a0b3d60f2aecfbb99780bcc00b4db6e@%3Cgeneral.incubator.apache.org%3E
> ),
> I would like to call a VOTE to accept it into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring DolphinScheduler into Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring DolphinScheduler into Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
>
> ==
> Abstract
>
> DolphinScheduler is a distributed ETL scheduling engine with powerful DAG
> visualization interface. DolphinScheduler focuses on solving the problem of
> 'complex task dependencies & triggers' in data processing. Just like its
> name, we dedicated to making the scheduling system out of the box.
>
> *Current project name of DolphinScheduler is EasyScheduler, will change it
> after it is accepted by Incubator.*
> Proposal
>
> DolphinScheduler provides many easy-to-use features to accelerate
> the engineering efficiency on data ETL workflow job. We propose a new
> concept of 'instance of process' and 'instance of task' to let developers
> to tuning their jobs on the running state of workflow instead of changing
> the task's template. Its main objectives are as follows:
>
>- Define the complex tasks' dependencies & triggers in a DAG graph by
>dragging and dropping.
>- Support cluster HA.
>- Support multi-tenant and parallel or serial backfilling data.
>- Support automatical failure job retry and recovery.
>- Support many data task types and process priority, task priority and
>relative task timeout alarm.
>
> For now, DolphinScheduler has a fairly huge community in China. It is also
> widely adopted by many companies and organizations
>  as its ETL
> scheduling
> tool.
>
> We believe that bringing DolphinScheduler into ASF could advance
> development of a much more stronger and more diverse open source community.
>
> Analysys submits this proposal to donate DolphinScheduler's source codes
> and all related documentations to Apache Software Foundation. The codes are
> already under Apache License Version 2.0.
>
>- Code base: https://www.github.com/analysys/easyscheduler
>- English Documentations: https://analysys.github.io/easyscheduler_docs
>- Chinese Documentations:
>https://analysys.github.io/easyscheduler_docs_cn
>
> Background
>
> We want to find a data processing tool with the following features:
>
>- Easy to use，developers can build a ETL process with a very simple drag
>and drop operation. not only for ETL developers，people who can't write
> code
>also can use this tool for ETL operation such as system adminitrator.
>- Solving the problem of "complex task dependencies" , and it can
>monitor the ETL running status.
>- Support multi-tenant.
>- Support many task types: Shell, MR, Spark, SQL (mysql, postgresql,
>hive, sparksql), Python, Sub_Process, Procedure, etc.
>- Support HA and linear scalability.
>
> For the above reasons, we realized that no existing product met our
> requirements, so we decided to develop this tool ourselves. We designed
> DolphinScheduler at the end of 2017. The first internal use version was
> completed in May 2018. We then iterated several internal versions and the
> system gradually became stabilized.
>
> Then we open the source code of DolphinScheduler on March 2019. It soon
> gained lot's of ETL developers interest and stars on github.
> Rationale
>
> Many organizations (>30) (refer to Who is using DolphinScheduler
>  ) already benefit
> from running DolphinScheduler to make data process pipelines more easier.
> More than 100 feature ideas
>  come from
> DolphinScheduler community. Some 3rd-party projects also plan to integrate
> with DolphinScheduler through task plugin, such as Scriptis
> , waterdrop
> . These will strengthen the
> features of DolphinScheduler.
> Current StatusMeritocracy
>
> DolphinScheduler was incubated at Analysys in 2017 and open sourced on
> GitHub in March 2019. Once open sourced, we have been quickly adopted by
> multiple organizations，DolphinScheduler has contributors and users from
> many companies; we have set up the Committer Team. New contributors are
> guided and reviewed by existed committer members. Contributions are always
> welcomed and highly valued.
> Community
>
> Now we have set development teams for DolphinScheduler in Analysys, and we
> already have external developers who contributed the code. We already have
> a user group of more than 1,000