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. 

[GitHub] [incubator] justinmclean opened a new pull request #32: lists need * rather than -

[GitBox]

justinmclean opened a new pull request #32: lists need * rather than -
URL: https://github.com/apache/incubator/pull/32
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[GitHub] [incubator] justinmclean merged pull request #32: lists need * rather than -

[GitBox]

justinmclean merged pull request #32: lists need * rather than -
URL: https://github.com/apache/incubator/pull/32
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[GitHub] [incubator] justinmclean opened a new pull request #31: clarify and fix formatting

[GitBox]

justinmclean opened a new pull request #31: clarify and fix formatting
URL: https://github.com/apache/incubator/pull/31
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[GitHub] [incubator] justinmclean merged pull request #31: clarify and fix formatting

[GitBox]

justinmclean merged pull request #31: clarify and fix formatting
URL: https://github.com/apache/incubator/pull/31
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [MENTORS] New DISCLAIMER-WIP approved by board

[Justin Mclean]

Hi,

I’ve also updated [1], feedback as allways welcome. 

Thanks,
Justin

1. https://incubator.apache.org/guides/releasemanagement.html
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[GitHub] [incubator] justinmclean merged pull request #30: add information on disclaimer to release management page

[GitBox]

justinmclean merged pull request #30: add information on disclaimer to release 
management page
URL: https://github.com/apache/incubator/pull/30
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[GitHub] [incubator] justinmclean opened a new pull request #30: add information on disclaimer to release management page

[GitBox]

justinmclean opened a new pull request #30: add information on disclaimer to 
release management page
URL: https://github.com/apache/incubator/pull/30
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [MENTORS] Mentor guidance document

[Justin Mclean]

Hi,

I really don’t think there is a dialog happening here. I asked some questions 
and no-one answers. Other people seem to want to push some other tangental view 
and it’s not clear to me exactly what that is.

Perhaps I’m not making myself clear? The whole idea is not for me to write this 
document but have the 50+ people who have been mentors, to collaborate and 
produce this together. In coming up on the material I’m sure there will be some 
differences of opinion and useful discussion will happen and help clarify 
everyones understand of how the ASF values can be applied.  If no-one who is 
willing to help then new mentors will keep making the same mistakes.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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] Release Apache Milagro (incubating) Crypto Libraries v1.0.0

[Justin Mclean]

Hi,

+1 (binding) if a question below can be answered

I can see that the JS code includes a lot of standard algorithms, but the files 
have ASF headers and no 3rd party code is mentioned in LICENSE or in the files 
themselves that I can see. Was all of this code written entirely from scratch 
or do parts of the code base come from elsewhere and if so where? (I note that 
searching for some of the comments in the code points me to similar 3rd party 
code - although that may be a coincidence.)

I checked:
- incubating in name
- signatures and hashes are good
- DISCLAIMER exists
- LICENSE is fine but the copyright line in the appendix should not be changed
- NOTICE is good
- All source file has ASF headers
- No ungcpecte binary files in the release
- No need to compile

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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] Release Apache Superset (incubating) 0.34.0 [RC2]

[Jeff Feng]

+1 Binding

On Fri, Aug 23, 2019 at 12:56 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Hi IPMC,
>
> The Apache Superset PPMC and IPMC recently voted and passed a vote on RC1
> recently, only to realize that there's was a minor blocking. The blocker
> was that the version was labelled `0.34.0rc1` inside the tarball, as
> opposed to `0.34.0`, meaning that when installing from source, the Python &
> npm packages would appear to be a `0.34.0rc1`. As you know, altering the
> tarball invalidates the MD5 / signature, so this is why we need this very
> minor tweak.
>
> 0.34.0rc2 addresses this, and uses `0.34.0` as the version number inside
> the tarball. I also addressed some of the [non-blocking] licensing comments
> surfaced during the RC1 process, and included the latest CHANGELOG in the
> tarball.
>
> Here are the 3 commits on top of RC1:
> 20e68c87 (HEAD -> 0.34, tag: 0.34.0rc2, origin/0.34, apache/0.34) Set
> version to 0.34.0 (no rcN)
> 6acd25d1 fix: minor release/license related issues (#8087)
> a13fb1d2 CHANGELOG for 0.30...0.34 (#8089)
>
> *This would be the first Apache release of Superset.*
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache Superset (incubating) is a business intelligence web application
>
> The community voting thread (for RC1) can be found here:
>
> https://lists.apache.org/thread.html/c9ad3ce592a695ceeabfa92969c00c0d7be8e3420b6a221c7e806f40@%3Cdev.superset.apache.org%3E
>
> The release candidate has been tagged in GitHub as tag 0.34.0rc2
> ,
> available here:
> https://github.com/apache/incubator-superset/releases/tag/0.34.0rc2
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/superset/
>
> Release artifacts are signed with the key located here:
> https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
>
> This vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast.
>
> [ ] +1 Release this package as Apache Superset (incubating)
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Thank you IPMC! We appreciate your efforts in helping the Apache Superset
> community to validate this release.
>
> On behalf of the Apache Superset Community,
>
> Max
>
> 
>
> Apache Superset (incubating) is an effort undergoing incubation at The
> Apache
> Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is
> required of all newly accepted projects until a further review indicates
> that the infrastructure, communications, and decision making process have
> stabilized in a manner consistent with other successful ASF projects. While
> incubation status is not necessarily a reflection of the completeness or
> stability of the code, it does indicate that the project has yet to be
> fully endorsed by the ASF.
>

[VOTE] Release Apache Superset (incubating) 0.34.0 [RC2]

[Maxime Beauchemin]

Hi IPMC,

The Apache Superset PPMC and IPMC recently voted and passed a vote on RC1
recently, only to realize that there's was a minor blocking. The blocker
was that the version was labelled `0.34.0rc1` inside the tarball, as
opposed to `0.34.0`, meaning that when installing from source, the Python &
npm packages would appear to be a `0.34.0rc1`. As you know, altering the
tarball invalidates the MD5 / signature, so this is why we need this very
minor tweak.

0.34.0rc2 addresses this, and uses `0.34.0` as the version number inside
the tarball. I also addressed some of the [non-blocking] licensing comments
surfaced during the RC1 process, and included the latest CHANGELOG in the
tarball.

Here are the 3 commits on top of RC1:
20e68c87 (HEAD -> 0.34, tag: 0.34.0rc2, origin/0.34, apache/0.34) Set
version to 0.34.0 (no rcN)
6acd25d1 fix: minor release/license related issues (#8087)
a13fb1d2 CHANGELOG for 0.30...0.34 (#8089)

*This would be the first Apache release of Superset.*

We now kindly request the Incubator PMC members review and vote on this
incubator release.

Apache Superset (incubating) is a business intelligence web application

The community voting thread (for RC1) can be found here:
https://lists.apache.org/thread.html/c9ad3ce592a695ceeabfa92969c00c0d7be8e3420b6a221c7e806f40@%3Cdev.superset.apache.org%3E

The release candidate has been tagged in GitHub as tag 0.34.0rc2
,
available here:
https://github.com/apache/incubator-superset/releases/tag/0.34.0rc2

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/incubator/superset/

Release artifacts are signed with the key located here:
https://dist.apache.org/repos/dist/release/incubator/superset/KEYS

This vote will be open for at least 72 hours. The vote will pass if a
majority of at least three +1 IPMC votes are cast.

[ ] +1 Release this package as Apache Superset (incubating)
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...

Thank you IPMC! We appreciate your efforts in helping the Apache Superset
community to validate this release.

On behalf of the Apache Superset Community,

Max



Apache Superset (incubating) is an effort undergoing incubation at The
Apache
Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is
required of all newly accepted projects until a further review indicates
that the infrastructure, communications, and decision making process have
stabilized in a manner consistent with other successful ASF projects. While
incubation status is not necessarily a reflection of the completeness or
stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

Re: [VOTE] Release Apache Superset (incubating) 0.34.0 [RC1]

[Maxime Beauchemin]

Ok, I have an RC2 ready to go with very minor changes, will kick off [only]
a general@ vote and tell dev@ & PPMC they can vote on general@

Max

On Thu, Aug 22, 2019 at 11:44 AM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hi,
>
> I agree with Alan that its really minor but as the signatures will change
> I would prefer another Vote to have this checked.
> If you (as Justin suggests) state your changes clearly in the thread I
> think everybody will easily carry over the vote from the previous thread so
> its just about waiting 72hrs but ensure that everything is alright.
>
> Julian
>
> Am 22.08.19, 19:21 schrieb "Alan Gates" :
>
> I would call a revote over that, it's not like you're changing
> anything of
> import.  I'd just regen the package with the change, create the new
> hash,
> and let everyone know.  I don't see any reason to drag back through the
> voting process on two lists over this.
>
> Alan.
>
> On Wed, Aug 21, 2019 at 10:43 PM Justin Mclean <
> jus...@classsoftware.com>
> wrote:
>
> > Hi,
> >
> > > Oh here's something. Somewhere inside the source release I have a
> version
> > > string that says "0.34.0rc1" and that now I'm realizing should
> really say
> > > "0.34.0" as it becomes an official release. Now changing that
> string will
> > > make for a different SHA.
> >
> > That's a bit awkward. It would be best to call a vote again if it
> needs to
> > be changed, given the changes shod be minor it shod be easy to
> review.
> >
> > Other IPMC members might have another view. Anyone?
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>
>

Re: [MENTORS] New DISCLAIMER-WIP approved by board

[John D. Ament]

This is a major incubator policy change.  It's worth a note to podlings@ at
a minimum.

On Fri, Aug 23, 2019, 00:29 Justin Mclean  wrote:

> Hi,
>
> Does anyone think we should mail this out to all incubating PMC? (e.g
> private@ or dev@). I'm not really sure that I want to spam 50 odd
> projects like that, but it woful be useful in getting this knowledge out
> there.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

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 A

[Liu Ted]

+1 binding.
Ted Liu, 
ASF Member, Incubator PMC Member
 
 
  2019 年 8 月 23 日周五 17:32，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,
> >    >    

Re: [MENTORS] Mentor guidance document

[Jim Jagielski]

Ross said everything that I would have said... only better.

> On Aug 18, 2019, at 5:35 PM, Ross Gardler  wrote:
> 
> Only replying because I'm called out explicitly.
> 
> Documentation does not solve the problem. If someone doesn't already "get" 
> this stuff then they should not be mentoring. Having a document does not 
> replace for selecting good mentors who have the time to do the job right.
> 
> It's a good effort in the broader context, but doesn't solve the problem I 
> see in the IPMC (insufficient high quality mentoring coupled with too much 
> application of rules in the process). The proposed doc is interesting but 
> it's just more words, We need more action.
> 
> How would I solve the problem? If I were championing another project into the 
> ASF I would carefully select mentors, just as I have in the past. I'd select 
> those who don't need the above document and who I'm confident will pay 
> attention and be constructive. I'd then work with those mentors and the 
> community to ensure people coming through the process are equipped to help me 
> on the next project I champion.
> 
> This is not new. It's how we setup the Incubator in the first place. But over 
> the years it has become a machine rather than personal relationships. More 
> words about the design of the machine won't change this.
> 
> I don't mean to say the effort you are putting in is wasted effort. Clarity 
> in what is expected can help the podlings, but I don't see how this can 
> really help those people I would already trust to be good mentors i.e. People 
> who have a vested interest in the success of the project and already know how 
> to apply the Apache Way to new communities so that they might flourish in 
> their own way.
> 
> Ross
> 
> 
> ---
> 
> Sent from my phone, you know what that means - sorry
> 
> 
> From: Justin Mclean 
> Sent: Saturday, August 17, 2019 6:26:32 PM
> To: general@incubator.apache.org 
> Subject: Re: [MENTORS] Mentor guidance document
> 
> Hi,
> 
> I've had hoped I'd get more of a response to the mentor guidance 
> documentation I suggested. Perhaps it got lost in the other noise?
> 
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FINCUBATOR%2FMentor%2BGuidancedata=02%7C01%7C%7C0e716c1bb8a74438cd0108d7237b24aa%7C84df9e7fe9f640afb435%7C1%7C0%7C637016884106582384sdata=9v85p9zRNDFHPp3yJgpVp7GUz%2F0NDNvC8vQuZjT4X50%3Dreserved=0
> 
> Jim and Ross, you have recently stated that you are concerned about the 
> erosion of our values and principles. It would be great to see your input on 
> this. If you have other idea one how these values can be better passed to 
> incubating incubation it would be great to hear.
> 
> I also welcome other IPMC members who have experience and can offer some 
> advice to other mentors.
> 
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Apache ShardingSphere (incubating) 4.0.0-RC2 available

[Zhang Yonglun]

Hi all,

Apache ShardingSphere (incubating) Team is glad to announce the release of
Apache ShardingSphere (incubating) 4.0.0-RC2.

ShardingSphere is an open-source ecosystem consisted of a set of
distributed database middleware solutions, including 2 independent
products, Sharding-JDBC & Sharding-Proxy.

Sharding-JDBC is an enhanced JDBC driver that provides in-process
transparent distributed database by connecting to multiple database back
ends. It supports many ORM frameworks and database connection pools and
supports many back end databases that have JDBC interfaces: MySQL, Oracle,
SQLServer and PostgreSQL.

Sharding-Proxy is a database proxy that runs in a separate process and
appears as a database server to multiple back end databases. It supports
multiple client front ends such as MySQL Command Client, MySQL Workbench,
Navicat etc. Current support is for MySQL and PostgreSQL.

Vote Thread:
https://lists.apache.org/thread.html/1625c938e62ae9146d290abf069335b977819323d2fc9978cc808d6c@%3Cgeneral.incubator.apache.org%3E

Download Links:
https://shardingsphere.apache.org/document/current/en/downloads/

Release Notes:
https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md

Website: https://shardingsphere.apache.org/

ShardingSphere Resources:

- Issue: https://github.com/apache/incubator-shardingsphere/issues
- Mailing list: d...@shardingsphere.apache.org
- Documents: https://shardingsphere.apache.org/document/current



- Apache ShardingSphere (incubating) Team


=
*Disclaimer*

Apache ShardingSphere (incubating) is an effort undergoing incubation at
The Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure,
communications, and decision making process have stabilized in a manner
consistent with other successful ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code,
it does indicate that the project has yet to be fully endorsed by the ASF.

-- 
Zhang Yonglun
Apache ShardingSphere

Re: [VOTE] Release Apache Myriad 0.4.0 (incubating) [rc1]

[Kevin Ratnasekera]

Hi all,

+1 ( Binding )

I checked the following,

1. Incubating in name

2. PGP Signature
myriad-0.4.0-incubating-rc1$ gpg --verify
myriad-0.4.0-incubating-rc1.tar.gz.asc myriad-0.4.0-incubating-rc1.tar.gz
gpg: Signature made 2019-08-07 12:34:41 +0530 +0530 using RSA key ID
64228691
gpg: Good signature from "Oscar Fernandez "
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 484E ABDA 4596 DD74 6C95  64C6 6533 EDB2 6422 8691

3. SHA512 Checksum
myriad-0.4.0-incubating-rc1$ sha512sum myriad-0.4.0-incubating-rc1.tar.gz
8031934e3e4f156bcf367f4a3787fa56605443b26bde5edac31bf3b83b0f5f641a26b944e9d46201e683b7e7c59e4adc57e2749c609aeac8ce7e6d44466f8ff8
 myriad-0.4.0-incubating-rc1.tar.gz

4. Build the sources on Ubuntu/Linux Environment
myriad-0.4.0-incubating-rc1$ ./gradlew build
BUILD SUCCESSFUL in 12m 17s
40 actionable tasks: 40 executed

Regards
Kevin

On Fri, Aug 23, 2019 at 12:46 AM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hi,
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - signatures and hashes match
> - checked DISCLAIMER, LICENSE and NOTICE
> - No unexpected binary
> - Can compile from source on macOS Mojave
>
> Julian
>
> Am 21.08.19, 05:15 schrieb "Justin Mclean" :
>
> Hi,
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - signatures and hashes fine
> - DISCLAIMER exists
> - LICENSE and NOTICE fine (but see below)
> - All source files have ASF header
> - No unexpected binary files
> - Can compile from source
>
> I think you may have the wrong license in LICENSE for bootstrap as the
> css file [1] refers to the Apache licensed version copyright twitter not
> the MIT licensed version?
>
> Thanks,
> Justin
>
> 1.
> ./myriad-scheduler/src/main/resources/webapp/css/bootstrap-myriad.css
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
>
>

Re: [VOTE] Release Apache ShardingSphere (Incubating) 4.0.0-RC2

[Zhang Yonglun]

We’ve received 4 +1 binding votes and 1 +1 non-binding vote:

+1 binding, Justin Mclean
+1 binding, Willen Jiang
+1 binding, Furkan KAMACI
+1 binding, Gosling Von

+1 non-binding, William Guo

Thank you everyone for taking the time to review the release and help us.
I will process to publish the release and send ANNOUNCE.

Gosling Von  于2019年8月22日周四 上午10:24写道：

> +1 (binding), forward my vote from PPMC.
>
> Best Regards,
> Von Gosling
>
> > On Aug 20, 2019, at 6:16 PM, Zhang Yonglun 
> wrote:
> >
> > Hello all,
> >
> > This is a call for vote to release Apache ShardingSphere (Incubating)
> > version 4.0.0-RC2.
> >
> > The Apache ShardingSphere community has voted on and approved a proposal
> to
> > release Apache ShardingSphere (Incubating) version 4.0.0-RC2.
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > ShardingSphere is an open-source ecosystem consisted of a set of
> > distributed database middleware solutions, including 2 independent
> > products, Sharding-JDBC & Sharding-Proxy.
> >
> > Sharding-JDBC is an enhanced JDBC driver that provides in-process
> > transparent distributed database by connecting to multiple database back
> > ends. It supports many ORM frameworks and database connection pools and
> > supports many back end databases that have JDBC interfaces: MySQL,
> Oracle,
> > SQLServer and PostgreSQL.
> >
> > Sharding-Proxy is a database proxy that runs in a separate process and
> > appears as a database server to multiple back end databases. It supports
> > multiple client front ends such as MySQL Command Client, MySQL Workbench,
> > Navicat etc. Current support is for MySQL and PostgreSQL.
> >
> > ShardingSphere community vote and result thread:
> >
> https://lists.apache.org/thread.html/4b29490f433dd26cc85d0e00340def3bd0f7b64e4bd2f3512e568bcd@%3Cdev.shardingsphere.apache.org%3E
> >
> > Release notes:
> >
> https://github.com/apache/incubator-shardingsphere/blob/dev/RELEASE-NOTES.md
> >
> > The release candidates:
> >
> https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/4.0.0-RC2/
> >
> > Maven 2 staging repository:
> >
> https://repository.apache.org/content/repositories/staging/org/apache/shardingsphere/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-shardingsphere/tree/4.0.0-RC2
> >
> > Release Commit ID:
> >
> https://github.com/apache/incubator-shardingsphere/commit/85f2ff877a7aaf122998964a0d03f7c9b2830e36
> >
> > Keys to verify the Release Candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/shardingsphere/KEYS
> > GPG username: zhangyonglun
> >
> > Look at here for how to verify this release candidate:
> > https://shardingsphere.apache.org/community/en/contribute/release/
> >
> > The vote will be open for at least 72 hours or until necessary number of
> > votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove with the reason
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> >
> > [ ] Checksums and PGP signatures are valid.
> >
> > [ ] DISCLAIMER is included.
> >
> > [ ] Source code artifacts have correct names matching the current
> release.
> >
> > [ ] LICENSE and NOTICE files are correct for each ShardingSphere repo.
> >
> > [ ] All files have license headers if necessary.
> >
> > [ ] No compiled archives bundled in source archive.
> >
> > --
> > Zhang Yonglun
> > Apache ShardingSphere
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Zhang Yonglun
Apache ShardingSphere

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 

Re: [IP CLEARANCE] Apache Celix - Websocket pubsub admin

[Roy Lenferink]

Thanks for your input as well Matt! Next time we'll discuss upfront whether
IP clearance is necessary or not.
Consider this case as a "better safe than sorry" one.

With that said, 72 hours have passed so the vote is closed with the
following results:

+1:
Furkan Kamaci
Matt Sicker
Roy Lenferink (hereby adding my +1)

No -1 votes have been cast.

Thanks all for your input,
Roy

Op wo 21 aug. 2019 om 20:21 schreef Matt Sicker :

> I would think that if the person who submits the PR has the rights to
> make that contribution, then their ICLA should cover that. See
> https://www.apache.org/licenses/contributor-agreements.html for more
> info.
>
> On Wed, 21 Aug 2019 at 11:49, Roy Lenferink 
> wrote:
> >
> > > Given it was already had a ASF license header and from a ASF project
> why
> > was IP clearance even needed? I assume the person involved has signed a
> > ICLA?
> >
> > The individual contributors all submitted an ICLA and a CCLA for the
> > company is already present. We were following IP clearance
> > because the written software was developed outside of the ASF version
> > control system (company internal VCS). After that, we squashed everything
> > into a single commit and submitted it as a PR to Celix.
> >
> > Would IP clearance be necessary in this case (duplication of an already
> > existing component)? Would IP clearance be necessary for new components
> > which already have ASF headers in place?
>
>
>
> --
> Matt Sicker 
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>