You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dolphinscheduler.apache.org by Sheng Wu <wu...@gmail.com> on 2019/12/01 01:00:11 UTC
Re: [VOTE] Release Apache DolphinScheduler (Incubating) 1.2.0
Questions
1. For your frontend dist tar, why do you require Nginx in your
`install-dolphinscheduler-ui.sh`? Does the frontend depend on Nginx? If
logically yes, Nginx is your dependency lib, and license should be
included. Look like `BSD-2` from
https://github.com/nginx/nginx/blob/master/docs/text/LICENSE. As you are
Java based project, what do we need this? Spring boot should have already a
good container for webapp. Could someone explain this?
2. Where is the documentation for this release? Does every release have its
own doc? Or the documents are same for every release?
Suggestion
1. As you are using many Apache 2.0 licensed libs, if the license file is
standard Apache 2.0 license, you could add a new catalog like this, and no
LICENSE file required.
========================================================================
Apache 2.0 licenses
========================================================================
The following components are provided under the Apache License. See project
link for details.
The text of each license is the standard Apache 2.0 license.
Sheng Wu 吴晟
Twitter, wusheng1108
李 岗 <lg...@outlook.com> 于2019年12月1日周日 上午1:35写道:
> Hello DolphinScheduler Community,
>
> This is a call for vote to release Apache DolphinScheduler (Incubating)
> version 1.2.0
>
> Release notes:
>
> https://github.com/apache/incubator-dolphinscheduler/blob/1.2.0/ReleaseNotes.md
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/1.2.0/
>
> Maven 2 staging repository:
>
> https://repository.apache.org/content/repositories/orgapachedolphinscheduler-1012/org/apache/dolphinscheduler/
>
> Git tag for the release:
> https://github.com/apache/incubator-dolphinscheduler/tree/1.2.0
>
> Release Commit ID:
>
> https://github.com/apache/incubator-dolphinscheduler/commit/5ae23ccd237163807d078a4bbc8e71f9724f1d32
>
> Keys to verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/dolphinscheduler/KEYS
>
> Look at here for how to verify this release candidate:
>
> https://github.com/apache/incubator-dolphinscheduler/blob/1.2.0-release/README.md
>
> 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 DolphinScheduler repo.
>
> [ ] All files have license headers if necessary.
>
> [ ] No compiled archives bundled in source archive.
>
> ________________________________
> DolphinScheduler(Incubator) PPMC
> Gang Li 李岗
>
> lgcareer2019@outlook.com<ma...@outlook.com>
>
Re: [VOTE] Release Apache DolphinScheduler (Incubating) 1.2.0
Posted by lidong dai <da...@gmail.com>.
Front-end and back-end separation is just a development idea. The front-end
and back-end are developed by different people. As I know they usually want
to achieve decoupling. The front-end generally chooses nginx as the static
resource parser. but not only nginx, apache also can do this. And
back-end people generally chooses tomcat or jetty as application server.
Because I am not very familar with Front-end, I find some articles , here
is a Chinese article on front-end and back-end separation:
https://blog.csdn.net/weixin_37539378/article/details/79956760
This also some information about this on google:
https://www.google.com/search?q=front-end+and+back-end+separation&sxsrf=ACYBGNRoc1P3ql9ZMK5qp6kuH8eyYzC75w:1575212102993&ei=RtTjXf6VPIiroAS2-IuQAw&start=0&sa=N&ved=2ahUKEwj-0OCu2pTmAhWIFYgKHTb8AjI4ChDy0wN6BAgLEDE&biw=1638&bih=900
By the way, can we just provide a nginx or apache configuration file
instead of directly telling users that they need to install nginx, users
can choose to install nginx or apache or use jetty of the back-end
application according to their needs. In this case,is it not necessary to
add a license for nginx?
Best Regards
———————
DolphinScheduler(Incubator) PPMC
Lidong Dai 代立冬
dailidong66@gmail.com
———————
On December 1, 2019 at 22:30:54, Sheng Wu (wu.sheng.841108@gmail.com) wrote:
This is totally project option. Could you share why Nginx only? Is this
just document issue or really having tech related reason? Because they are
different cases.
lidong dai <da...@gmail.com>于2019年12月1日 周日下午9:47写道:
> Currently the front and back ends are deployed separately, using nginx as
> a static resource parser. In the next version, to reduce dependencies, we
> will consider removing nginx and use jetty to implement.
>
>
> Best Regards
>
> ---------------
> DolphinScheduler(Incubator) PPMC
> Lidong Dai 代立冬
> dailidong66@gmail.com
> ---------------
>
>
>
> On December 1, 2019 at 21:34:01, Sheng Wu (wu.sheng.841108@gmail.com)
> wrote:
>
> Why do you require Nginx? Why Spring Zuul container, or Tomcat can’t work?
>
> Sheng Wu <wu...@gmail.com>于2019年12月1日 周日下午9:32写道:
>
>> OK. Then you have this dependency implicitly.
>> But if you are really doing this, you need to get through all dependency
>> of Nginx too. Because you force users to use Nginx now.
>>
>> I would suggest the whole DS community could take part in this
>> discussion. What is the best and quick solution for us.
>>
>> lidong dai <da...@gmail.com>于2019年12月1日 周日下午9:28写道:
>>
>>>
>>>
>>>
>>> On December 1, 2019 at 21:02:21, Sheng Wu (wu.sheng.841108@gmail.com)
>>> wrote:
>>>
>>>
>>>
>>> lidong dai <da...@gmail.com>于2019年12月1日 周日下午7:06写道:
>>>
>>>> Thanks for seriously check and review.
>>>>
>>>> Questions
>>>> 1. For your frontend dist tar, why do you require Nginx in your
>>>> `install-dolphinscheduler-ui.sh`? Does the frontend depend on Nginx? If
>>>>
>>>> logically yes, Nginx is your dependency lib, and license should be
>>>> included. Look like `BSD-2` from
>>>> https://github.com/nginx/nginx/blob/master/docs/text/LICENSE. As you
>>>> are
>>>> Java based project, what do we need this? Spring boot should have
>>>> already a
>>>> good container for webapp. Could someone explain this?
>>>>
>>>>
>>>> As one more option, does nginx need to be written to the license file?
>>>>
>>>
>>> I just read your document of frontend deployment. Both ways(auto or
>>> manually), you are downloading Nginx. You said, this is one more option,
>>> but where are other options? How could user do if they don’t want Nginx,
>>> and whether it is working now?
>>>
>>> My point is, your release tar and your document make me feeling you need
>>> Nginx, rather than an option. If this is not wrong, I think you should
>>> describe it in your document.
>>>
>>>
>>>
>>> Thanks, for now we indeed need nginx, we will add nginx to ui-licenses
>>> directory.
>>>
>>>
>>>
>>>>
>>>> 2. Where is the documentation for this release? Does every release have
>>>> its
>>>> own doc? Or the documents are same for every release?
>>>>
>>>> the document address:https://
>>>> <https://dolphinscheduler.apache.org/en-us/docs/user_doc/quick-start.html>
>>>> dolphinscheduler.apache.org/en-us/docs/user_doc/quick-start.html ,every
>>>> document has its own doc
>>>>
>>>>
>>>>
>>>> Suggestion
>>>> 1. As you are using many Apache 2.0 licensed libs, if the license file
>>>> is
>>>> standard Apache 2.0 license, you could add a new catalog like this, and
>>>> no
>>>> LICENSE file required.
>>>> ========================================================================
>>>>
>>>> Apache 2.0 licenses
>>>> ========================================================================
>>>>
>>>>
>>>> The following components are provided under the Apache License. See
>>>> project
>>>> link for details.
>>>> The text of each license is the standard Apache 2.0 license.
>>>>
>>>> We will continue to remove third-party dependencies. Now the bloated
>>>> list display will always remind us to do it more firmly. In the near
>>>> future, we will remove a considerable part of the dependencies.
>>>>
>>>>
>>>> Best Regards
>>>> ---------------
>>>> DolphinScheduler(Incubator) PPMC
>>>> Lidong Dai 代立冬
>>>> dailidong66@gmail.com
>>>> ---------------
>>>>
>>>>
>>>> --
>>> Sheng Wu 吴晟
>>>
>>> Apache SkyWalking
>>> Apache Incubator
>>> Apache ShardingSphere, ECharts, DolphinScheduler podlings
>>> Zipkin
>>> Twitter, wusheng1108
>>>
>>> --
>> Sheng Wu 吴晟
>>
>> Apache SkyWalking
>> Apache Incubator
>> Apache ShardingSphere, ECharts, DolphinScheduler podlings
>> Zipkin
>> Twitter, wusheng1108
>>
> --
> Sheng Wu 吴晟
>
> Apache SkyWalking
> Apache Incubator
> Apache ShardingSphere, ECharts, DolphinScheduler podlings
> Zipkin
> Twitter, wusheng1108
>
> --
Sheng Wu 吴晟
Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108
Re: Re: [VOTE] Release Apache DolphinScheduler (Incubating) 1.2.0
Posted by 李 岗 <lg...@outlook.com>.
This is just document issue. Because the front-end support jetty deploy or nginx deploy.
User can choose one of the above two deployment methods, or can choose other deployment methods according to user production environment.
The official documentation also explains the front-end deployment.
https://dolphinscheduler.apache.org/en-us/docs/user_doc/frontend-deployment.html
________________________________
DolphinScheduler(Incubator) PPMC
Gang Li 李岗
lgcareer2019@outlook.com<ma...@outlook.com>
From: Sheng Wu<ma...@gmail.com>
Date: 2019-12-01 22:30
To: lidong dai<ma...@gmail.com>
CC: dev<ma...@dolphinscheduler.apache.org>
Subject: Re: [VOTE] Release Apache DolphinScheduler (Incubating) 1.2.0
This is totally project option. Could you share why Nginx only? Is this just document issue or really having tech related reason? Because they are different cases.
lidong dai <da...@gmail.com>>于2019年12月1日 周日下午9:47写道:
Currently the front and back ends are deployed separately, using nginx as a static resource parser. In the next version, to reduce dependencies, we will consider removing nginx and use jetty to implement.
Best Regards
---------------
DolphinScheduler(Incubator) PPMC
Lidong Dai 代立冬
dailidong66@gmail.com<ma...@gmail.com>
---------------
On December 1, 2019 at 21:34:01, Sheng Wu (wu.sheng.841108@gmail.com<ma...@gmail.com>) wrote:
Why do you require Nginx? Why Spring Zuul container, or Tomcat can’t work?
Sheng Wu <wu...@gmail.com>>于2019年12月1日周日下午9:32写道:
OK. Then you have this dependency implicitly.
But if you are really doing this, you need to get through all dependency of Nginx too. Because you force users to use Nginx now.
I would suggest the whole DS community could take part in this discussion. What is the best and quick solution for us.
lidong dai <da...@gmail.com>>于2019年12月1日周日下午9:28写道:
On December 1, 2019 at 21:02:21, Sheng Wu (wu.sheng.841108@gmail.com<ma...@gmail.com>) wrote:
lidong dai <da...@gmail.com>>于2019年12月1日周日下午7:06写道:
Thanks for seriously check and review.
Questions
1. For your frontend dist tar, why do you require Nginx in your
`install-dolphinscheduler-ui.sh`? Does the frontend depend on Nginx? If
logically yes, Nginx is your dependency lib, and license should be
included. Look like `BSD-2` from
https://github.com/nginx/nginx/blob/master/docs/text/LICENSE. As you are
Java based project, what do we need this? Spring boot should have already a
good container for webapp. Could someone explain this?
As one more option, does nginx need to be written to the license file?
I just read your document of frontend deployment. Both ways(auto or manually), you are downloading Nginx. You said, this is one more option, but where are other options? How could user do if they don’t want Nginx, and whether it is working now?
My point is, your release tar and your document make me feeling you need Nginx, rather than an option. If this is not wrong, I think you should describe it in your document.
Thanks, for now we indeed need nginx, we will add nginx to ui-licenses directory.
2. Where is the documentation for this release? Does every release have its
own doc? Or the documents are same for every release?
the document address:https://<https://dolphinscheduler.apache.org/en-us/docs/user_doc/quick-start.html>dolphinscheduler.apache.org/en-us/docs/user_doc/quick-start.html<http://dolphinscheduler.apache.org/en-us/docs/user_doc/quick-start.html> ,every document has its own doc
[cid:9f4fda0ae43e7c49_0.1.1]
Suggestion
1. As you are using many Apache 2.0 licensed libs, if the license file is
standard Apache 2.0 license, you could add a new catalog like this, and no
LICENSE file required.
========================================================================
Apache 2.0 licenses
========================================================================
The following components are provided under the Apache License. See project
link for details.
The text of each license is the standard Apache 2.0 license.
We will continue to remove third-party dependencies. Now the bloated list display will always remind us to do it more firmly. In the near future, we will remove a considerable part of the dependencies.
Best Regards
---------------
DolphinScheduler(Incubator) PPMC
Lidong Dai 代立冬
dailidong66@gmail.com<ma...@gmail.com>
---------------
--
Sheng Wu 吴晟
Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108
--
Sheng Wu 吴晟
Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108
--
Sheng Wu 吴晟
Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108
--
Sheng Wu 吴晟
Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108
Re: [VOTE] Release Apache DolphinScheduler (Incubating) 1.2.0
Posted by Sheng Wu <wu...@gmail.com>.
This is totally project option. Could you share why Nginx only? Is this
just document issue or really having tech related reason? Because they are
different cases.
lidong dai <da...@gmail.com>于2019年12月1日 周日下午9:47写道:
> Currently the front and back ends are deployed separately, using nginx as
> a static resource parser. In the next version, to reduce dependencies, we
> will consider removing nginx and use jetty to implement.
>
>
> Best Regards
>
> ---------------
> DolphinScheduler(Incubator) PPMC
> Lidong Dai 代立冬
> dailidong66@gmail.com
> ---------------
>
>
>
> On December 1, 2019 at 21:34:01, Sheng Wu (wu.sheng.841108@gmail.com)
> wrote:
>
> Why do you require Nginx? Why Spring Zuul container, or Tomcat can’t work?
>
> Sheng Wu <wu...@gmail.com>于2019年12月1日 周日下午9:32写道:
>
>> OK. Then you have this dependency implicitly.
>> But if you are really doing this, you need to get through all dependency
>> of Nginx too. Because you force users to use Nginx now.
>>
>> I would suggest the whole DS community could take part in this
>> discussion. What is the best and quick solution for us.
>>
>> lidong dai <da...@gmail.com>于2019年12月1日 周日下午9:28写道:
>>
>>>
>>>
>>>
>>> On December 1, 2019 at 21:02:21, Sheng Wu (wu.sheng.841108@gmail.com)
>>> wrote:
>>>
>>>
>>>
>>> lidong dai <da...@gmail.com>于2019年12月1日 周日下午7:06写道:
>>>
>>>> Thanks for seriously check and review.
>>>>
>>>> Questions
>>>> 1. For your frontend dist tar, why do you require Nginx in your
>>>> `install-dolphinscheduler-ui.sh`? Does the frontend depend on Nginx? If
>>>>
>>>> logically yes, Nginx is your dependency lib, and license should be
>>>> included. Look like `BSD-2` from
>>>> https://github.com/nginx/nginx/blob/master/docs/text/LICENSE. As you
>>>> are
>>>> Java based project, what do we need this? Spring boot should have
>>>> already a
>>>> good container for webapp. Could someone explain this?
>>>>
>>>>
>>>> As one more option, does nginx need to be written to the license file?
>>>>
>>>
>>> I just read your document of frontend deployment. Both ways(auto or
>>> manually), you are downloading Nginx. You said, this is one more option,
>>> but where are other options? How could user do if they don’t want Nginx,
>>> and whether it is working now?
>>>
>>> My point is, your release tar and your document make me feeling you need
>>> Nginx, rather than an option. If this is not wrong, I think you should
>>> describe it in your document.
>>>
>>>
>>>
>>> Thanks, for now we indeed need nginx, we will add nginx to ui-licenses
>>> directory.
>>>
>>>
>>>
>>>>
>>>> 2. Where is the documentation for this release? Does every release have
>>>> its
>>>> own doc? Or the documents are same for every release?
>>>>
>>>> the document address:https://
>>>> <https://dolphinscheduler.apache.org/en-us/docs/user_doc/quick-start.html>
>>>> dolphinscheduler.apache.org/en-us/docs/user_doc/quick-start.html ,every
>>>> document has its own doc
>>>>
>>>>
>>>>
>>>> Suggestion
>>>> 1. As you are using many Apache 2.0 licensed libs, if the license file
>>>> is
>>>> standard Apache 2.0 license, you could add a new catalog like this, and
>>>> no
>>>> LICENSE file required.
>>>> ========================================================================
>>>>
>>>> Apache 2.0 licenses
>>>> ========================================================================
>>>>
>>>>
>>>> The following components are provided under the Apache License. See
>>>> project
>>>> link for details.
>>>> The text of each license is the standard Apache 2.0 license.
>>>>
>>>> We will continue to remove third-party dependencies. Now the bloated
>>>> list display will always remind us to do it more firmly. In the near
>>>> future, we will remove a considerable part of the dependencies.
>>>>
>>>>
>>>> Best Regards
>>>> ---------------
>>>> DolphinScheduler(Incubator) PPMC
>>>> Lidong Dai 代立冬
>>>> dailidong66@gmail.com
>>>> ---------------
>>>>
>>>>
>>>> --
>>> Sheng Wu 吴晟
>>>
>>> Apache SkyWalking
>>> Apache Incubator
>>> Apache ShardingSphere, ECharts, DolphinScheduler podlings
>>> Zipkin
>>> Twitter, wusheng1108
>>>
>>> --
>> Sheng Wu 吴晟
>>
>> Apache SkyWalking
>> Apache Incubator
>> Apache ShardingSphere, ECharts, DolphinScheduler podlings
>> Zipkin
>> Twitter, wusheng1108
>>
> --
> Sheng Wu 吴晟
>
> Apache SkyWalking
> Apache Incubator
> Apache ShardingSphere, ECharts, DolphinScheduler podlings
> Zipkin
> Twitter, wusheng1108
>
> --
Sheng Wu 吴晟
Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108
Re: [VOTE] Release Apache DolphinScheduler (Incubating) 1.2.0
Posted by lidong dai <da...@gmail.com>.
Currently the front and back ends are deployed separately, using nginx as a
static resource parser. In the next version, to reduce dependencies, we
will consider removing nginx and use jetty to implement.
Best Regards
---------------
DolphinScheduler(Incubator) PPMC
Lidong Dai 代立冬
dailidong66@gmail.com
---------------
On December 1, 2019 at 21:34:01, Sheng Wu (wu.sheng.841108@gmail.com) wrote:
Why do you require Nginx? Why Spring Zuul container, or Tomcat can’t work?
Sheng Wu <wu...@gmail.com>于2019年12月1日 周日下午9:32写道:
> OK. Then you have this dependency implicitly.
> But if you are really doing this, you need to get through all dependency
> of Nginx too. Because you force users to use Nginx now.
>
> I would suggest the whole DS community could take part in this discussion.
> What is the best and quick solution for us.
>
> lidong dai <da...@gmail.com>于2019年12月1日 周日下午9:28写道:
>
>>
>>
>>
>> On December 1, 2019 at 21:02:21, Sheng Wu (wu.sheng.841108@gmail.com)
>> wrote:
>>
>>
>>
>> lidong dai <da...@gmail.com>于2019年12月1日 周日下午7:06写道:
>>
>>> Thanks for seriously check and review.
>>>
>>> Questions
>>> 1. For your frontend dist tar, why do you require Nginx in your
>>> `install-dolphinscheduler-ui.sh`? Does the frontend depend on Nginx? If
>>> logically yes, Nginx is your dependency lib, and license should be
>>> included. Look like `BSD-2` from
>>> https://github.com/nginx/nginx/blob/master/docs/text/LICENSE. As you are
>>>
>>> Java based project, what do we need this? Spring boot should have
>>> already a
>>> good container for webapp. Could someone explain this?
>>>
>>>
>>> As one more option, does nginx need to be written to the license file?
>>>
>>
>> I just read your document of frontend deployment. Both ways(auto or
>> manually), you are downloading Nginx. You said, this is one more option,
>> but where are other options? How could user do if they don’t want Nginx,
>> and whether it is working now?
>>
>> My point is, your release tar and your document make me feeling you need
>> Nginx, rather than an option. If this is not wrong, I think you should
>> describe it in your document.
>>
>>
>>
>> Thanks, for now we indeed need nginx, we will add nginx to ui-licenses
>> directory.
>>
>>
>>
>>>
>>> 2. Where is the documentation for this release? Does every release have
>>> its
>>> own doc? Or the documents are same for every release?
>>>
>>> the document address:https://
>>> <https://dolphinscheduler.apache.org/en-us/docs/user_doc/quick-start.html>
>>> dolphinscheduler.apache.org/en-us/docs/user_doc/quick-start.html ,every
>>> document has its own doc
>>>
>>>
>>>
>>> Suggestion
>>> 1. As you are using many Apache 2.0 licensed libs, if the license file is
>>>
>>> standard Apache 2.0 license, you could add a new catalog like this, and
>>> no
>>> LICENSE file required.
>>> ========================================================================
>>>
>>> Apache 2.0 licenses
>>> ========================================================================
>>>
>>>
>>> The following components are provided under the Apache License. See
>>> project
>>> link for details.
>>> The text of each license is the standard Apache 2.0 license.
>>>
>>> We will continue to remove third-party dependencies. Now the bloated
>>> list display will always remind us to do it more firmly. In the near
>>> future, we will remove a considerable part of the dependencies.
>>>
>>>
>>> Best Regards
>>> ---------------
>>> DolphinScheduler(Incubator) PPMC
>>> Lidong Dai 代立冬
>>> dailidong66@gmail.com
>>> ---------------
>>>
>>>
>>> --
>> Sheng Wu 吴晟
>>
>> Apache SkyWalking
>> Apache Incubator
>> Apache ShardingSphere, ECharts, DolphinScheduler podlings
>> Zipkin
>> Twitter, wusheng1108
>>
>> --
> Sheng Wu 吴晟
>
> Apache SkyWalking
> Apache Incubator
> Apache ShardingSphere, ECharts, DolphinScheduler podlings
> Zipkin
> Twitter, wusheng1108
>
--
Sheng Wu 吴晟
Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108
Re: [VOTE] Release Apache DolphinScheduler (Incubating) 1.2.0
Posted by lidong dai <da...@gmail.com>.
Thanks for seriously check and review.
Questions
1. For your frontend dist tar, why do you require Nginx in your
`install-dolphinscheduler-ui.sh`? Does the frontend depend on Nginx? If
logically yes, Nginx is your dependency lib, and license should be
included. Look like `BSD-2` from
https://github.com/nginx/nginx/blob/master/docs/text/LICENSE. As you are
Java based project, what do we need this? Spring boot should have already a
good container for webapp. Could someone explain this?
As one more option, does nginx need to be written to the license file?
2. Where is the documentation for this release? Does every release have its
own doc? Or the documents are same for every release?
the document address:https://
<https://dolphinscheduler.apache.org/en-us/docs/user_doc/quick-start.html>
dolphinscheduler.apache.org/en-us/docs/user_doc/quick-start.html ,every
document has its own doc
Suggestion
1. As you are using many Apache 2.0 licensed libs, if the license file is
standard Apache 2.0 license, you could add a new catalog like this, and no
LICENSE file required.
========================================================================
Apache 2.0 licenses
========================================================================
The following components are provided under the Apache License. See project
link for details.
The text of each license is the standard Apache 2.0 license.
We will continue to remove third-party dependencies. Now the bloated list
display will always remind us to do it more firmly. In the near future, we
will remove a considerable part of the dependencies.
Best Regards
---------------
DolphinScheduler(Incubator) PPMC
Lidong Dai 代立冬
dailidong66@gmail.com
---------------