Re: [VOTE] Release Apache Livy 0.7.1 (incubating) based on RC1

[Saisai Shao]

Thanks all for your votes, we already 3 binding +1 and 1 non-binding +1,
I'm going to close the vote and prepare for the release.

Best regards,
Saisai

Jean-Baptiste Onofre  于2021年2月10日周三 下午12:48写道：

> +1 (binding)
>
> Quickly check name, signature, DISCLAIMER, NOTICE and LICENSE.
>
> Regards
> JB
>
> > Le 7 févr. 2021 à 02:50, Saisai Shao  a écrit :
> >
> > The Livy PPMC has voted to release Livy 0.7.1 RC1 as the next Livy
> release.
> >
> > Livy enables programmatic, fault-tolerant, multi-tenant submission of
> > Spark jobs from web/mobile apps (no Spark client needed). So, multiple
> > users can interact with your Spark cluster concurrently and reliably.
> >
> > Vote thread:
> >
> https://lists.apache.org/thread.html/r9ac9717f267828028484a7b4aff63e9adbf0cdeca9ce6d674096bf71%40%3Cdev.livy.apache.org%3E
> >
> > Result thread:
> >
> https://lists.apache.org/thread.html/r083a6f1a5926df7441842a280f60c532c25a3eddc0e24416493814ae%40%3Cdev.livy.apache.org%3E
> >
> > The RC is based on tag v0.7.1-incubating-rc1:
> > https://github.com/apache/incubator-livy/commit/
> > 7c3d341926db69fb57a4978b15d4e96f06312267
> >
> > The release files can be found here:
> >
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.7.1-incubating-rc1/
> >
> > The staged maven artifacts can be found here:
> > https://repository.apache.org/content/repositories/orgapachelivy-1014
> >
> > This release is a hot-fix release, only added one commit compared to
> 0.7.0
> > -incubating
> > https://github.com/apache/incubator-livy
> > /commit/9f1ba47a2f0d8accc435b133b42c3a76aa9ac846
> >
> > Please help to vote. Thanks!
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

[Justin Mclean]

Hi,

> The reference [2] refers to the three different licenses for the three 
> different products. There are three links to three different license pages.
> 
> https://www.oracle.com/downloads/licenses/berkeleydb-oslicense.html
> https://www.oracle.com/downloads/licenses/berkeleydb-jeoslicense.html
> https://www.oracle.com/downloads/licenses/berkeleydb-xmloslicense.html
> 
> As I read it, the only license that would allow an Apache project to have a 
> hard dependency and to redistribute is the Berkeley DB Java Edition. 

I agree assuming no other conditions apply, but it unclear if that is the case. 
I assume this is intentional as Oracle wants you to use the commercial version.

I did see in the wikipedia page that other projects have use this [1] as a 
replacement due to the licensing issues. There's also a fork [2] but I not 
fully checked the licensing.

Thanks,
Justin

1. https://en.wikipedia.org/wiki/Lightning_Memory-Mapped_Database
2. https://github.com/bloomberg/comdb2
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

[Craig Russell]

The reference [2] refers to the three different licenses for the three 
different products. There are three links to three different license pages.

https://www.oracle.com/downloads/licenses/berkeleydb-oslicense.html
https://www.oracle.com/downloads/licenses/berkeleydb-jeoslicense.html
https://www.oracle.com/downloads/licenses/berkeleydb-xmloslicense.html

As I read it, the only license that would allow an Apache project to have a 
hard dependency and to redistribute is the Berkeley DB Java Edition. The others 
are unacceptable to Apache except as optional dependencies (in which case the 
user would have to install the dependencies and accept the conditions).

Craig

> On Feb 18, 2021, at 4:35 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> Berkeley DB uses a Category X non-commercial license, which Justin points 
>> out is not an open source license.
>> 
>> Berkeley DB Java Edition uses a standard Apache License, v2.0 with an 
>> additional license that appears to be the 3-clause BSD license for an 
>> embedded third-party component; both of which are Category A licenses.
> 
> I'm not 100% sure this is the case, it’s not 100% clear from that page [1] 
> that Berkeley DB Java Edition is licensed differently. 
> 
> This page [2] has conflicting but non Apache compatible information:
> "The our open source license permits you to use Berkeley DB, Berkeley DB Java 
> Edition or Berkeley DB XML at no charge under the condition that if you use 
> the software in an application you redistribute, the complete source code for 
> your application must be available and freely redistributable under 
> reasonable conditions. If you do not want to release the source code for your 
> application, you may purchase a license from Oracle. For pricing information, 
> or if you have further questions on licensing, please contact us at 
> berkeleydb-info...@oracle.com."
> 
> 
> Thanks,
> Justin
> 
> 
> 1. 
> https://www.oracle.com/database/technologies/related/berkeleydb-downloads.html
> 2 
> https://www.oracle.com/database/technologies/related/berkeleydb/berkeleydb-licensing.html
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Craig L Russell
c...@apache.org


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

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

[Justin Mclean]

Hi,

> Berkeley DB uses a Category X non-commercial license, which Justin points out 
> is not an open source license.
> 
> Berkeley DB Java Edition uses a standard Apache License, v2.0 with an 
> additional license that appears to be the 3-clause BSD license for an 
> embedded third-party component; both of which are Category A licenses.

I'm not 100% sure this is the case, it’s not 100% clear from that page [1] that 
Berkeley DB Java Edition is licensed differently. 

This page [2] has conflicting but non Apache compatible information:
"The our open source license permits you to use Berkeley DB, Berkeley DB Java 
Edition or Berkeley DB XML at no charge under the condition that if you use the 
software in an application you redistribute, the complete source code for your 
application must be available and freely redistributable under reasonable 
conditions. If you do not want to release the source code for your application, 
you may purchase a license from Oracle. For pricing information, or if you have 
further questions on licensing, please contact us at 
berkeleydb-info...@oracle.com."


Thanks,
Justin


1. 
https://www.oracle.com/database/technologies/related/berkeleydb-downloads.html
2 
https://www.oracle.com/database/technologies/related/berkeleydb/berkeleydb-licensing.html
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

[Daniel B. Widdis]

Craig,

As Justin pointed out, while the "Java Edition" includes the AL 2.0
license, there are additional restrictions on the website [1]:

"The our open source license permits you to use Berkeley DB, Berkeley DB
Java Edition or Berkeley DB XML at no charge under the condition that if
you use the software in an application you redistribute, the complete
source code for your application must be available and freely
redistributable under reasonable conditions. "

[1] - Oracle Berkeley DB Licensing Information



On Thu, Feb 18, 2021 at 4:00 PM Craig Russell  wrote:

> Which Oracle product is TubeMQ dependent on?
>
> From what I see, there are two distinct Oracle products, with different
> licenses:
>
> Berkeley DB uses a Category X non-commercial license, which Justin points
> out is not an open source license.
>
> Berkeley DB Java Edition uses a standard Apache License, v2.0 with an
> additional license that appears to be the 3-clause BSD license for an
> embedded third-party component; both of which are Category A licenses.
>
> So if the project uses only Berkeley DB Java Edition, all is well. If it
> uses Berkeley DB then we have a problem.
>
> Regards,
> Craig
>
> > On Feb 18, 2021, at 1:46 PM, Daniel B. Widdis  wrote:
> >
> > Thank you for the clarification, Justin!  I missed that non-commercial
> > limitation.
> >
> > I agree that it would be better to replace that dependency,
> >
> > On Thu, Feb 18, 2021 at 1:41 PM Justin Mclean 
> > wrote:
> >
> >> Hi,
> >>
> >> My concern is that while it claims it is under the Apache license that
> is
> >> only for non-commercial use. Having a restriction like that means it’s
> not
> >> really under the Apache license.
> >>
> >> It states on that page [1]
> >> "Our open source license is OSI-certified and permits use of Berkeley DB
> >> in open source projects or in applications that are not distributed to
> >> third parties.”
> >> "Our commercial license permits closed-source distribution of an
> >> application to third parties and provides business assurance"
> >>
> >> ASF releases need to be distributed to third parties, ASF releases can’t
> >> have non-commercial restrictions.
> >>
> >> IMO It would be best if the project replaced this dependancy with
> >> something else.
> >>
> >> Thanks,
> >> Justin
> >>
> >> 1.
> >>
> https://www.oracle.com/database/technologies/related/berkeleydb-downloads.html
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
> >
> > --
> > Dan Widdis
>
> Craig L Russell
> c...@apache.org
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Dan Widdis

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

[Craig Russell]

Which Oracle product is TubeMQ dependent on?

From what I see, there are two distinct Oracle products, with different 
licenses:

Berkeley DB uses a Category X non-commercial license, which Justin points out 
is not an open source license.

Berkeley DB Java Edition uses a standard Apache License, v2.0 with an 
additional license that appears to be the 3-clause BSD license for an embedded 
third-party component; both of which are Category A licenses.

So if the project uses only Berkeley DB Java Edition, all is well. If it uses 
Berkeley DB then we have a problem.

Regards,
Craig

> On Feb 18, 2021, at 1:46 PM, Daniel B. Widdis  wrote:
> 
> Thank you for the clarification, Justin!  I missed that non-commercial
> limitation.
> 
> I agree that it would be better to replace that dependency,
> 
> On Thu, Feb 18, 2021 at 1:41 PM Justin Mclean 
> wrote:
> 
>> Hi,
>> 
>> My concern is that while it claims it is under the Apache license that is
>> only for non-commercial use. Having a restriction like that means it’s not
>> really under the Apache license.
>> 
>> It states on that page [1]
>> "Our open source license is OSI-certified and permits use of Berkeley DB
>> in open source projects or in applications that are not distributed to
>> third parties.”
>> "Our commercial license permits closed-source distribution of an
>> application to third parties and provides business assurance"
>> 
>> ASF releases need to be distributed to third parties, ASF releases can’t
>> have non-commercial restrictions.
>> 
>> IMO It would be best if the project replaced this dependancy with
>> something else.
>> 
>> Thanks,
>> Justin
>> 
>> 1.
>> https://www.oracle.com/database/technologies/related/berkeleydb-downloads.html
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
> 
> -- 
> Dan Widdis

Craig L Russell
c...@apache.org


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

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

[Daniel B. Widdis]

Thank you for the clarification, Justin!  I missed that non-commercial
limitation.

I agree that it would be better to replace that dependency,

On Thu, Feb 18, 2021 at 1:41 PM Justin Mclean 
wrote:

> Hi,
>
> My concern is that while it claims it is under the Apache license that is
> only for non-commercial use. Having a restriction like that means it’s not
> really under the Apache license.
>
> It states on that page [1]
> "Our open source license is OSI-certified and permits use of Berkeley DB
> in open source projects or in applications that are not distributed to
> third parties.”
> "Our commercial license permits closed-source distribution of an
> application to third parties and provides business assurance"
>
> ASF releases need to be distributed to third parties, ASF releases can’t
> have non-commercial restrictions.
>
> IMO It would be best if the project replaced this dependancy with
> something else.
>
> Thanks,
> Justin
>
> 1.
> https://www.oracle.com/database/technologies/related/berkeleydb-downloads.html
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Dan Widdis

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

[Justin Mclean]

Hi,

My concern is that while it claims it is under the Apache license that is only 
for non-commercial use. Having a restriction like that means it’s not really 
under the Apache license. 

It states on that page [1]
"Our open source license is OSI-certified and permits use of Berkeley DB in 
open source projects or in applications that are not distributed to third 
parties.”
"Our commercial license permits closed-source distribution of an application to 
third parties and provides business assurance"

ASF releases need to be distributed to third parties, ASF releases can’t have 
non-commercial restrictions.

IMO It would be best if the project replaced this dependancy with something 
else.

Thanks,
Justin

1. 
https://www.oracle.com/database/technologies/related/berkeleydb-downloads.html
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[NOTICE] Incubator and Clutch process for Website is Broken

[Dave Fisher]

Starting Wednesday ci-builds.apache.org has experienced issues which are being 
resolved.

Until they are clutch and website builds for the Incubator are broken.

I will kick them off once the builds configurations are restored.

Regards,
Dave


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

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

[Daniel B. Widdis]

Can you be clear on what you mean by "has no standard license file" and "no
open source code channel"?

I started at this download page [1].

On that page near the top is a link to "more details" on licensing, which
points to [2].

The link there for "Open source license for Berkeley DB Java Edition"
points to [3] which is the Apache License, 2.0.

>From [1], I downloaded the file Berkeley DB Java Edition je-7.5.11.zip and
extracted it.  It contains a LICENSE file exactly matching the license
shown in [3], the Apache License, 2.0.

The extracted zip file also contains a complete copy of the source code.

You are correct that it is not published on Maven, but is that a
requirement for a dependency?  The only "obstacle" to downloading is that
one has to create a (free) Oracle account to download it.  Is this a
disqualifying factor?

I am unclear on why this is not permitted as a dependency for an Apache
project.



[1] -
https://www.oracle.com/database/technologies/related/berkeleydb-downloads.html

[2] -
https://www.oracle.com/database/technologies/related/berkeleydb/berkeleydb-licensing.html
[3] - https://www.oracle.com/downloads/licenses/berkeleydb-jeoslicense.html



On Thu, Feb 18, 2021 at 3:31 AM Goson zhang  wrote:

> Hi all:
>
> We carefully analyzed the dependency package berkeleydb-je. I think
> what @Justin
> Mclean   said is correct: it has no standard
> license file, no open source code channel, and cannot be downloaded from
> the central repository. All off all , It does have a problem.
>
> I will restore the WIP label until it is replaced with the new scheme.
>
> Thanks all!
>
>
>
> Goson zhang  于2021年2月11日周四 下午9:07写道：
>
> > Hi all:
> >
> > I made the following adjustments according to your suggestions:
> >
> > 1. Sorted out and supplemented the LICENSE of each binary dependency
> > package.
> >
> > 2. Delete tubemq-manager and tubemq-web modules related content:
> > In the process of combing, it is found that tubemq-manager contains a
> > dependency package of the GNU GPL V2 LICENSE. This version deletes the
> > module, and then merges it into the official version after finishing the
> > relevant checks for dependency packages.
> > Since more than 60 files of tubemq-web module are not authorized by
> > LICENSE, they will be merged into the mainline version after finishing
> the
> > LICENSE information checks of the code and dependent packages.
> >
> > 3. Solved the problem of compiling:
> >  When compiling with the mvn compile command, the pom dependency of
> > tubemq-docker needs to obtain the dependency package of tubemq from the
> > warehouse instead of locally, so a compilation error occurs; this part
> > should be a pom problem, and solve the problem when the next version is
> > released(does not affect the main line).
> >
> > 4. LICENSE problem of bdb:
> > Through everyone's discussion and confirmation, the 7.3.7 version of
> > berkeleydb-je is authorized under Apache V2 LICENSE, which is explained
> in
> > detail in the LICENSE file of TubeMQ; subsequent project evolution will
> > consider gradually removing this component.
> >
> > 5. Modify the contents of the CHANGES.md file and add this modification
> > item.
> >
> > Please see if there are any other problems. If OK, we will launch a new
> > round of version release.
> >
> > Thanks!
> >
> >
> > Goson zhang  于2021年2月11日周四 下午2:55写道：
> >
> >> Ok, thanks Daniel!
> >>
> >>
> >>
> >> Daniel Widdis  于2021年2月11日周四 下午2:10写道：
> >>
> >>> To continue to provide clarity:
> >>>
> >>> The current version (7.5.11) still has AL2.0 licensing; I just
> >>> downloaded it to confirm.  Any version from 7.3.7 and newer (at this
> point
> >>> in time) is an acceptable dependency.
> >>>
> >>> If Oracle chooses to change the license again for future releases that
> >>> could pose a problem, but personally I don't think that's likely.
> >>>
> >>>
> >>> On 2/10/21, 9:58 PM, "Goson zhang"  wrote:
> >>>
> >>> Yes, restricting the use of its version number in the project is
> >>> still a
> >>> relatively passive solution: if we want to upgrade the version, but
> >>> the
> >>> corresponding version authorization is adjusted, our project still
> >>> has
> >>> restrictions.
> >>>
> >>> The biggest dependency of replacing this component lies in the
> >>> active/standby switching function: currently we are not considering
> >>> expanding its scope of use, and we are analyzing the new
> >>> active/standby
> >>> switching scheme, and want to temporarily maintain the existing
> >>> method
> >>> before completing this task, until the real-time active/standby
> >>> switching
> >>> is provided.
> >>>
> >>> I plan to explain this problem in detail in the supplementary
> binary
> >>> dependency package LICENSE, until the solution is adjusted to
> >>> completely
> >>> solve it.
> >>>
> >>> See if this is OK?
> >>>
> >>>
> >>> Justin Mclean  于2021年2月11日周四 下午1:46写道：
> >>>
> >>> > Hi,
> >>> >
> 

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.8.0-incubating RC2

[Goson zhang]

Hi all:

We carefully analyzed the dependency package berkeleydb-je. I think
what @Justin
Mclean   said is correct: it has no standard
license file, no open source code channel, and cannot be downloaded from
the central repository. All off all , It does have a problem.

I will restore the WIP label until it is replaced with the new scheme.

Thanks all!



Goson zhang  于2021年2月11日周四 下午9:07写道：

> Hi all:
>
> I made the following adjustments according to your suggestions:
>
> 1. Sorted out and supplemented the LICENSE of each binary dependency
> package.
>
> 2. Delete tubemq-manager and tubemq-web modules related content:
> In the process of combing, it is found that tubemq-manager contains a
> dependency package of the GNU GPL V2 LICENSE. This version deletes the
> module, and then merges it into the official version after finishing the
> relevant checks for dependency packages.
> Since more than 60 files of tubemq-web module are not authorized by
> LICENSE, they will be merged into the mainline version after finishing the
> LICENSE information checks of the code and dependent packages.
>
> 3. Solved the problem of compiling:
>  When compiling with the mvn compile command, the pom dependency of
> tubemq-docker needs to obtain the dependency package of tubemq from the
> warehouse instead of locally, so a compilation error occurs; this part
> should be a pom problem, and solve the problem when the next version is
> released(does not affect the main line).
>
> 4. LICENSE problem of bdb:
> Through everyone's discussion and confirmation, the 7.3.7 version of
> berkeleydb-je is authorized under Apache V2 LICENSE, which is explained in
> detail in the LICENSE file of TubeMQ; subsequent project evolution will
> consider gradually removing this component.
>
> 5. Modify the contents of the CHANGES.md file and add this modification
> item.
>
> Please see if there are any other problems. If OK, we will launch a new
> round of version release.
>
> Thanks!
>
>
> Goson zhang  于2021年2月11日周四 下午2:55写道：
>
>> Ok, thanks Daniel!
>>
>>
>>
>> Daniel Widdis  于2021年2月11日周四 下午2:10写道：
>>
>>> To continue to provide clarity:
>>>
>>> The current version (7.5.11) still has AL2.0 licensing; I just
>>> downloaded it to confirm.  Any version from 7.3.7 and newer (at this point
>>> in time) is an acceptable dependency.
>>>
>>> If Oracle chooses to change the license again for future releases that
>>> could pose a problem, but personally I don't think that's likely.
>>>
>>>
>>> On 2/10/21, 9:58 PM, "Goson zhang"  wrote:
>>>
>>> Yes, restricting the use of its version number in the project is
>>> still a
>>> relatively passive solution: if we want to upgrade the version, but
>>> the
>>> corresponding version authorization is adjusted, our project still
>>> has
>>> restrictions.
>>>
>>> The biggest dependency of replacing this component lies in the
>>> active/standby switching function: currently we are not considering
>>> expanding its scope of use, and we are analyzing the new
>>> active/standby
>>> switching scheme, and want to temporarily maintain the existing
>>> method
>>> before completing this task, until the real-time active/standby
>>> switching
>>> is provided.
>>>
>>> I plan to explain this problem in detail in the supplementary binary
>>> dependency package LICENSE, until the solution is adjusted to
>>> completely
>>> solve it.
>>>
>>> See if this is OK?
>>>
>>>
>>> Justin Mclean  于2021年2月11日周四 下午1:46写道：
>>>
>>> > Hi,
>>> >
>>> > > 1. Can we meet the requirements of this open source agreement by
>>> > > restricting the version of this component to 7.X.Y?
>>> > > For Berkeley DB JE (Java Edition), this component itself is
>>> TubeMQ to
>>> > store
>>> > > metadata and switch between active and standby. It is not very
>>> deep, but
>>> > it
>>> > > need to take some time to adjust.
>>> >
>>> > Possibly if 7.X.Y is clearly Apache licensed, however as time goes
>>> on you
>>> > may need to move to a newer version (due to security concerns) and
>>> what
>>> > will be become an issue.
>>> >
>>> > > 2. Or have to switch to other components?
>>> > > If so, for this release,  do I restore the "WIP" label to
>>> complete the
>>> > > version release first?
>>> > > Then adjust the implementation plan later, and finally remove
>>> this
>>> > > component in the final version.
>>> >
>>> > That would be a valid path forward.
>>> >
>>> > Thanks,
>>> > Justin
>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>

Re: [VOTE] Graduate Apache DolphinScheduler (incubating) as a TLP

[Willem Jiang]

+1 (binding).

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Feb 14, 2021 at 6:50 PM lidong dai  wrote:
>
> Hello all,
>
> We've got positive feedback on the DISCUSS thread [1], I'd like to start an
> official VOTE thread now.
>
> Please vote on the resolution pasted below to graduate Apache
> DolphinScheduler from the incubator to the Top Level Project.
>
> [ ] +1 Graduate Apache DolphinScheduler from the Incubator.
> [ ] +0 Don't care.
> [ ] -1 Don't graduate Apache DolphinScheduler from the Incubator because ...
>
> This vote will open for at least 72 hours.
>
> Many thanks to our mentors and everyone else for their support.
>
> [1]
> https://lists.apache.org/thread.html/r1d5f4e122c914b39a49a9ae5c39605e17c0b82b20de3966e989a9f21%40%3Cgeneral.incubator.apache.org%3E
>
>
> -
>
> Establish the Apache DolphinScheduler Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a distributed and extensible workflow scheduler platform with
> powerful DAG visual interfaces.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache DolphinScheduler Project", be and
> hereby is established pursuant to Bylaws of the Foundation; and be it
> further
>
> RESOLVED, that the Apache DolphinScheduler Project be and hereby is
> responsible for the creation and maintenance of software related to a
> distributed and extensible workflow scheduler platform with powerful DAG
> visual interfaces.; and be it further
>
> RESOLVED, that the office of "Vice President, Apache DolphinScheduler"
> be and hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache
> DolphinScheduler Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of the
> Apache DolphinScheduler Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache DolphinScheduler
> Project:
>
> * Furkan Kamaci 
> * Gang Li   
> * Guo Jiwei 
> * Guo William   
> * Jun Gao   
> * Kevin Ratnasekera 
> * Leon Bao  
> * Liang Chen
> * Lidong Dai
> * Qiao Zhanwei  
> * Shao Feng Shi 
> * Sheng Wu  
> * Wu Baoqi  
> * Xiaochun Liu  
> * ZijJian Gong  
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lidong Dai be appointed to
> the office of Vice President, Apache DolphinScheduler, to serve in
> accordance with and subject to the direction of the Board of Directors
> and the Bylaws of the Foundation until death, resignation, retirement,
> removal or disqualification, or until a successor is appointed; and be
> it further
>
> RESOLVED, that the Apache DolphinScheduler Project be and hereby is
> tasked with the migration and rationalization of the Apache Incubator
> DolphinScheduler podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> DolphinScheduler podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
>
>
>
> Best Regards
> ---
> DolphinScheduler(Incubator) PPMC
> Lidong Dai
> dailidon...@gmail.com
> ---

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

Re: [VOTE] Graduate Apache DolphinScheduler (incubating) as a TLP

[Yu Li]

+1 (non-binding). Good luck!

Best Regards,
Yu


On Mon, 15 Feb 2021 at 13:54, Jean-Baptiste Onofre  wrote:

> +1 (binding)
>
> Regards
> JB
>
> > Le 14 févr. 2021 à 11:49, lidong dai  a écrit :
> >
> > Hello all,
> >
> > We've got positive feedback on the DISCUSS thread [1], I'd like to start
> an
> > official VOTE thread now.
> >
> > Please vote on the resolution pasted below to graduate Apache
> > DolphinScheduler from the incubator to the Top Level Project.
> >
> > [ ] +1 Graduate Apache DolphinScheduler from the Incubator.
> > [ ] +0 Don't care.
> > [ ] -1 Don't graduate Apache DolphinScheduler from the Incubator because
> ...
> >
> > This vote will open for at least 72 hours.
> >
> > Many thanks to our mentors and everyone else for their support.
> >
> > [1]
> >
> https://lists.apache.org/thread.html/r1d5f4e122c914b39a49a9ae5c39605e17c0b82b20de3966e989a9f21%40%3Cgeneral.incubator.apache.org%3E
> >
> >
> > -
> >
> > Establish the Apache DolphinScheduler Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to a distributed and extensible workflow scheduler platform with
> > powerful DAG visual interfaces.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache DolphinScheduler Project", be and
> > hereby is established pursuant to Bylaws of the Foundation; and be it
> > further
> >
> > RESOLVED, that the Apache DolphinScheduler Project be and hereby is
> > responsible for the creation and maintenance of software related to a
> > distributed and extensible workflow scheduler platform with powerful DAG
> > visual interfaces.; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache DolphinScheduler"
> > be and hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache
> > DolphinScheduler Project, and to have primary responsibility for
> > management of the projects within the scope of responsibility of the
> > Apache DolphinScheduler Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache DolphinScheduler
> > Project:
> >
> > * Furkan Kamaci 
> > * Gang Li   
> > * Guo Jiwei 
> > * Guo William   
> > * Jun Gao   
> > * Kevin Ratnasekera 
> > * Leon Bao  
> > * Liang Chen
> > * Lidong Dai
> > * Qiao Zhanwei  
> > * Shao Feng Shi 
> > * Sheng Wu  
> > * Wu Baoqi  
> > * Xiaochun Liu  
> > * ZijJian Gong  
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lidong Dai be appointed to
> > the office of Vice President, Apache DolphinScheduler, to serve in
> > accordance with and subject to the direction of the Board of Directors
> > and the Bylaws of the Foundation until death, resignation, retirement,
> > removal or disqualification, or until a successor is appointed; and be
> > it further
> >
> > RESOLVED, that the Apache DolphinScheduler Project be and hereby is
> > tasked with the migration and rationalization of the Apache Incubator
> > DolphinScheduler podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > DolphinScheduler podling encumbered upon the Apache Incubator PMC are
> > hereafter discharged.
> >
> >
> >
> > Best Regards
> > ---
> > DolphinScheduler(Incubator) PPMC
> > Lidong Dai
> > dailidon...@gmail.com
> > ---
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>