Re: [VOTE] Release Apache DataSketches-cpp 2.0.0-incubating-rc4

[leerho]

Folks, Please!  We need one more IPMC member to vote on our C++ release,
which was posted 9 days ago.
Permalink

:

We do have customers that are waiting on this release.

Only one of our 5 mentors has voted, (Thank you Furkan!)

Please help us.

Thank you!

Lee.



On Sat, Jun 13, 2020 at 6:42 PM Justin Mclean 
wrote:

> Hi
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - signatures and hashes are fine
> - LICENSE and NOTICE are fine
> - No unexpected binary files
> - All source files have ASF headers
> - Don't have a suitable environment setup to compile
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[MENTORS] July 2020 Incubator report timeline

[Justin Mclean]

Hi,

The report timeline for July is:

Wed July 01 -- Podling reports due by end of day
Sun July 05 -- Shepherd reviews due by end of day
Sun July 05 -- Summary due by end of day
Tue July 07 -- Mentor signoff due by end of day
Wed July 08 -- Report submitted to Board
Wed July 15 -- Board meeting

Expected to report here [1] are:
- AGE 
- Annotator 
- APISIX 
- BlueMarlin 
- DLab 
- Flagon 
- Gobblin 
- Hivemall 
- Liminal 
- Livy 
- Milagro 
- MXNet 
- NuttX 
- Pony Mail 
- Spot 
- Teaclave 
- TubeMQ 
- TVM 
- Warble 
- Weex 
- YuniKorn 

Thanks,
Justin

1. https://cwiki.apache.org/confluence/display/INCUBATOR/July2020

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

Re: [VOTE]Release Apache DolphinScheduler (Incubating) 1.3.0

[lgcareer2...@outlook.com]

So thanks for your reply.



DolphinScheduler(Incubator) PPMC
Gang Li 李岗

lgcareer2...@outlook.com
 
From: Justin Mclean
Date: 2020-06-18 09:11
To: general
CC: tison
Subject: Re: [VOTE]Release Apache DolphinScheduler (Incubating) 1.3.0
Hi,
 
> I read over the [2] and [3],And I have a question on [1] to verify.
> Because the license of mybtis-3 is appache-2.0-license,So it needed to add in 
> the top-level NOTICE file.
 
ALv2 license code only need to be  added t NOTICE if it has a NOTICE file.
 
> If it is BSD or MIT license,it did'nt need to add in the top-level NOTICE 
> file.
 
Correct.
 
Thanks,
Justin
 

Re: [VOTE] Accept Pegasus into the Apache incubation

[Byung-Gon Chun]

+1 (binding)

Best,
Gon

On Thu, Jun 18, 2020 at 10:58 AM Gosling Von  wrote:

> +1, binding
>
>
> Best Regards,
> Von Gosling
>
> > On Jun 16, 2020, at 5:41 PM, Tao Wu 
> wrote:
> >
> > Hi,
> >
> > After [the discussion of Pegasus proposal](
> >
> https://lists.apache.org/thread.html/d2dc725389e1e6d0b525f85201c6219973a568ed075837601fd6bd0b%40%3Cgeneral.incubator.apache.org%3E
> ),
> > I would like to call a vote to accept this project into the Apache
> > Incubator.
> >
> > The proposal is here:
> > https://cwiki.apache.org/confluence/display/INCUBATOR/PegasusProposal
> >
> > Please cast your vote:
> >
> >  [ ] +1, bring Pegasus into Incubator
> >  [ ] +0, I don't care either way
> >  [ ] -1, do not bring Pegasus into Incubator, because...
> >
> > The vote will open for at least 72 hours and only votes from the IPMC
> > members are considered binding, but other votes are welcome!
> >
> > Thanks,
> > Wu Tao
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Byung-Gon Chun

[jira] [Updated] (INCUBATOR-253) Issues with MXNet releases and their distribution

[Justin Mclean (Jira)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Mclean updated INCUBATOR-253:

Description: 
The main issues are:
1. Source and convenance binary releases containing Category X licensed code.
2. Website giving access to downloads of non released/unapproved code.
3. Website giving access to releases containing Category X licensed code.
4. Web site dent given enough warning to users of the issues with non (P)PMC 
releases or making it clear that these are not ASF releases.
5. Maven releases containing Category X licensed code.
6. PiPy releases containing Category X licensed code.
7. Docker releases containing Category X licensed code.
8 Docker releases containing unreleased/unapproved code.
9. Trademark and branding issues with PiPy and Docker releases. 
10. Trademark and brand issues with naming of releases. 
11. Developer releases available from public searchable https://repo.mxnet.io / 
https://dist.mxnet.io
12. Releases and other nightly builds on https://repo.mxnet.io / 
https://dist.mxnet.io containing category X licensed code.
13. Lack of clarity on all platforms for what is an ASF release and what is not.

For PiPy see:
https://pypi.org/project/mxnet/

For Docker see:
https://hub.docker.com/u/mxnet

For web site pages see:
https://mxnet.apache.org/get_started?
https://mxnet.apache.org/get_started/download

I may of missed something, if so please add it.

  was:
The main issues are:
1. Source and convenance binary releases containing Category X licensed code.
2. Website giving access to downloads of non released/unapproved code.
3. Website giving access to releases containing Category X licensed code.
4. Web site dent given enough warning to users of the issues with non (P)PMC 
releases or making it clear that these are not ASF releases.
5. Maven releases containing Category X licensed code.
6. PiPy releases containing Category X licensed code.
7. Docker releases containing Category X licensed code.
8 Docker releases containing unreleased/unapproved code.
9. Trademark and branding issues with PiPy and Docker releases. 
10. Trademark and brand issues with naming of releases. 
11. Developer releases available from public searchable https://repo.mxnet.io / 
https://dist.mxnet.io
12. Releases and other nightly builds on https://repo.mxnet.io containing 
category X licensed code.
13. Lack of clarity on all platforms for what is an ASF release and what is not.

For PiPy see:
https://pypi.org/project/mxnet/

For Docker see:
https://hub.docker.com/u/mxnet

For web site pages see:
https://mxnet.apache.org/get_started?
https://mxnet.apache.org/get_started/download

I may of missed something, if so please add it.


> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site dent given enough warning to users of the issues with non (P)PMC 
> releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available from public searchable https://repo.mxnet.io 
> / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Updated] (INCUBATOR-253) Issues with MXNet releases and their distribution

[Justin Mclean (Jira)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Mclean updated INCUBATOR-253:

Description: 
The main issues are:
1. Source and convenance binary releases containing Category X licensed code.
2. Website giving access to downloads of non released/unapproved code.
3. Website giving access to releases containing Category X licensed code.
4. Web site dent given enough warning to users of the issues with non (P)PMC 
releases or making it clear that these are not ASF releases.
5. Maven releases containing Category X licensed code.
6. PiPy releases containing Category X licensed code.
7. Docker releases containing Category X licensed code.
8 Docker releases containing unreleased/unapproved code.
9. Trademark and branding issues with PiPy and Docker releases. 
10. Trademark and brand issues with naming of releases. 
11. Developer releases available from public searchable https://repo.mxnet.io / 
https://dist.mxnet.io
12. Releases and other nightly builds on https://repo.mxnet.io containing 
category X licensed code.
13. Lack of clarity on all platforms for what is an ASF release and what is not.

For PiPy see:
https://pypi.org/project/mxnet/

For Docker see:
https://hub.docker.com/u/mxnet

For web site pages see:
https://mxnet.apache.org/get_started?
https://mxnet.apache.org/get_started/download

I may of missed something, if so please add it.

  was:
The main issues are:
1. Source and convenance binary releases containing Category X licensed code.
2. Website giving access to downloads of non released/unapproved code.
3. Website giving access to releases containing Category X licensed code.
4. Web site dent given enough warning to users of the issues with non (P)PMC 
releases or making it clear that these are not ASF releases.
5. Maven releases containing Category X licensed code.
6. PiPy releases containing Category X licensed code.
7. Docker releases containing Category X licensed code.
8 Docker releases containing unreleased/unapproved code.
9. Trademark and branding issues with PiPy and Docker releases.
10. Trademark and brand issues with naming of releases. 
11. Developer releases available from public searchable https://repo.mxnet.io
12. Releases and other nightly builds on https://repo.mxnet.io containing 
category X licensed code.
13. Lack of clarity on all platforms for what is an ASF release and what is not.

I may of missed something, if so please add it.


> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site dent given enough warning to users of the issues with non (P)PMC 
> releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available from public searchable https://repo.mxnet.io 
> / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io containing 
> category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[jira] [Created] (INCUBATOR-253) Issues with MXNet releases and their distribution

[Justin Mclean (Jira)]

Justin Mclean created INCUBATOR-253:
---

 Summary: Issues with MXNet releases and their distribution
 Key: INCUBATOR-253
 URL: https://issues.apache.org/jira/browse/INCUBATOR-253
 Project: Incubator
  Issue Type: Improvement
Reporter: Justin Mclean
Assignee: Justin Mclean


The main issues are:
1. Source and convenance binary releases containing Category X licensed code.
2. Website giving access to downloads of non released/unapproved code.
3. Website giving access to releases containing Category X licensed code.
4. Web site dent given enough warning to users of the issues with non (P)PMC 
releases or making it clear that these are not ASF releases.
5. Maven releases containing Category X licensed code.
6. PiPy releases containing Category X licensed code.
7. Docker releases containing Category X licensed code.
8 Docker releases containing unreleased/unapproved code.
9. Trademark and branding issues with PiPy and Docker releases.
10. Trademark and brand issues with naming of releases. 
11. Developer releases available from public searchable https://repo.mxnet.io
12. Releases and other nightly builds on https://repo.mxnet.io containing 
category X licensed code.
13. Lack of clarity on all platforms for what is an ASF release and what is not.

I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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

[Gosling Von]

Hi,


+1, binding

I really feel the same way, It seems that everyone is very positive in 
promoting the rapid development of the whole community, we could catch a 
glimpse of case from more than 200 emails everyday. 

Best Regards,
Von Gosling

> On Jun 18, 2020, at 9:31 AM, Justin Mclean  wrote:
> 
> I'll also note that has been one of the easiest podling I've mentored as they 
> have from the start proactively seek out how to comply with ASF policy and 
> how to develop their community under the Apache Way. They have set a low 
> committer bar and continue to grow their community.

Re: [VOTE] Accept Pegasus into the Apache incubation

[Gosling Von]

+1, binding


Best Regards,
Von Gosling

> On Jun 16, 2020, at 5:41 PM, Tao Wu  wrote:
> 
> Hi,
> 
> After [the discussion of Pegasus proposal](
> https://lists.apache.org/thread.html/d2dc725389e1e6d0b525f85201c6219973a568ed075837601fd6bd0b%40%3Cgeneral.incubator.apache.org%3E),
> I would like to call a vote to accept this project into the Apache
> Incubator.
> 
> The proposal is here:
> https://cwiki.apache.org/confluence/display/INCUBATOR/PegasusProposal
> 
> Please cast your vote:
> 
>  [ ] +1, bring Pegasus into Incubator
>  [ ] +0, I don't care either way
>  [ ] -1, do not bring Pegasus into Incubator, because...
> 
> The vote will open for at least 72 hours and only votes from the IPMC
> members are considered binding, but other votes are welcome!
> 
> Thanks,
> Wu Tao


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

Re: [VOTE] Release Apache Annotator (incubating) version 0.1.0 (-rc.4)

[Justin Mclean]

Hi,

> The build should work on macOS with the requirements listed in the README. 
> Node.js and Yarn are the two required tools.

I had both of them installed but is seem to be expected something else, I can 
try again if you want the exact error.

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

Re: [VOTE] Accept Pegasus into the Apache incubation

[Duo Zhang]

+1(binding)

I think you'd better let the initial commiters to show up here and vote.

Thanks.

Justin Mclean  于2020年6月18日周四 上午9:27写道：

> HI,
>
> +1 (binding) and good luck
>
> I do notice an issue that will need to be fixed is that rapidjson may
> contain code under the JSON license which is not compatible with the ASF
> license. The license of XiaoMi/galaxy-fds-sdk-cpp will also need to be
> sorted.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] When to add Apache Headers to Third Party Code [WAS] Re: [MENTORS] PPMC case-by-case decision for major modifications of third-party work guidance

[Justin Mclean]

HI,

> In addition, Justin stated that converting the code from one program language 
> to another one should **NOT** be considered as a major modification.

INAL but my understanding is that translation from one language to another is 
considered a fairly trivial task and may not be novel enough for a copyright to 
apply and it would not considered an original work.

> So it seems more appropriate to remove the ASF header and just keep the Numpy 
> license header and claim it at the top level LICENSE, or do we need to vote 
> on the two options as Bob stated below, thanks!

I think the safest think to do would be to leave the original header on and 
remove the ASF one.Version control will show what lines have been modified if 
anyone is stressed in the history.

Thanks,
Justin

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

[Justin Mclean]

Hi,

+1 (binding) and all the best.

I'll also note that has been one of the easiest podling I've mentored as they 
have from the start proactively seek out how to comply with ASF policy and how 
to develop their community under the Apache Way. They have set a low committer 
bar and continue to grow their community.

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

Re: [VOTE] Accept Pegasus into the Apache incubation

[Justin Mclean]

HI,

+1 (binding) and good luck

I do notice an issue that will need to be fixed is that rapidjson may contain 
code under the JSON license which is not compatible with the ASF license. The 
license of XiaoMi/galaxy-fds-sdk-cpp will also need to be sorted.

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

Re: [VOTE]Release Apache DolphinScheduler (Incubating) 1.3.0

[Justin Mclean]

Hi,

> Could you show us how to check NOTICE files? It seems manually checking 
> content often misses information and causes more release cycles.

I suggest you ask your mentors for help as they will be familiar with how to do 
this.

Thanks,
Justin


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

Re: [VOTE]Release Apache DolphinScheduler (Incubating) 1.3.0

[Justin Mclean]

Hi,

> I read over the [2] and [3],And I have a question on [1] to verify.
> Because the license of mybtis-3 is appache-2.0-license,So it needed to add in 
> the top-level NOTICE file.

ALv2 license code only need to be  added t NOTICE if it has a NOTICE file.

> If it is BSD or MIT license,it did'nt need to add in the top-level NOTICE 
> file.

Correct.

Thanks,
Justin

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

[Willem Jiang]

+1 (binding).

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Jun 16, 2020 at 5:22 PM Ming Wen  wrote:
>
> Hello all,
>
> We've got positive feedback on the DISCUSS thread, I'd like to start
> an official VOTE thread now.
>
> Please vote on the resolution pasted below to graduate Apache APISIX from the
> incubator to a Top Level Project.
>
> [ ] +1 Graduate Apache APISIX from the Incubator.
> [ ] +0
> [ ] -1 Don't graduate Apache APISIX from the Incubator because ...
>
> This vote will open for at least 72 hours.
> ---
>
> Establish the Apache APISIX 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 Apache APISIX is a cloud-native microservices API gateway,
> delivering the ultimate performance, security and scalable platform
> for APIs and microservices...
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache APISIX Project", be and hereby
> is established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache APISIX Project be and hereby is
> responsible for the creation and maintenance of software related to
>  Apache APISIX is a cloud-native microservices API gateway,
> delivering the ultimate performance, security and scalable platform
> for APIs and microservices; and be it further
>
> RESOLVED, that the office of "Vice President, Apache APISIX" 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 ApacheAPISIX
> Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of the
> Apache APISIX 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 APISIX Project:
> * agile6v 
> * Ayeshmantha Perera  
> * Jarvis.Qiu 
> * jinwei 
> * junxu chen 
> * Justin Mclean 
> * Kevin Ratnasekera 
> * Lang Wang 
> * liling 
> * linsir 
> * Ming Wen 
> * Nirojan Selvanathan 
> * sheng wu 
> * spacewander 
> * Von Gosling  
> * Willem Ning Jiang 
> * yousa 
> * YuanSheng Wang 
> * Zhiyuan Ju  
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ming Wen be appointed to
> the office of Vice President, Apache APISIX, 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 APISIX Project be and hereby is tasked
> with the migration and rationalization of the Apache IncubatorAPISIX
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> IncubatorAPISIX podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
>
> ---
>
> Thanks,
> Ming Wen, Apache APISIX & Apache SkyWalking
> Twitter: _WenMing

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

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

[lgcareer2...@outlook.com]

+1 (non-binding)
Good luck.



DolphinScheduler(Incubator) PPMC
Gang Li 李岗

lgcareer2...@outlook.com
 
From: Ming Wen
Date: 2020-06-16 17:22
To: general
Subject: [VOTE] Graduate Apache APISIX (incubating) as a TLP
Hello all,
 
We've got positive feedback on the DISCUSS thread, I'd like to start
an official VOTE thread now.
 
Please vote on the resolution pasted below to graduate Apache APISIX from the
incubator to a Top Level Project.
 
[ ] +1 Graduate Apache APISIX from the Incubator.
[ ] +0
[ ] -1 Don't graduate Apache APISIX from the Incubator because ...
 
This vote will open for at least 72 hours.
---
 
Establish the Apache APISIX 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 Apache APISIX is a cloud-native microservices API gateway,
delivering the ultimate performance, security and scalable platform
for APIs and microservices...
 
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache APISIX Project", be and hereby
is established pursuant to Bylaws of the Foundation; and be it further
 
RESOLVED, that the Apache APISIX Project be and hereby is
responsible for the creation and maintenance of software related to
Apache APISIX is a cloud-native microservices API gateway,
delivering the ultimate performance, security and scalable platform
for APIs and microservices; and be it further
 
RESOLVED, that the office of "Vice President, Apache APISIX" 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 ApacheAPISIX
Project, and to have primary responsibility for
management of the projects within the scope of responsibility of the
Apache APISIX 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 APISIX Project:
* agile6v 
* Ayeshmantha Perera  
* Jarvis.Qiu 
* jinwei 
* junxu chen 
* Justin Mclean 
* Kevin Ratnasekera 
* Lang Wang 
* liling 
* linsir 
* Ming Wen 
* Nirojan Selvanathan 
* sheng wu 
* spacewander 
* Von Gosling  
* Willem Ning Jiang 
* yousa 
* YuanSheng Wang 
* Zhiyuan Ju  
 
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ming Wen be appointed to
the office of Vice President, Apache APISIX, 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 APISIX Project be and hereby is tasked
with the migration and rationalization of the Apache IncubatorAPISIX
podling; and be it further
 
RESOLVED, that all responsibilities pertaining to the Apache
IncubatorAPISIX podling encumbered upon the Apache Incubator PMC are
hereafter discharged.
 
---
 
Thanks,
Ming Wen, Apache APISIX & Apache SkyWalking
Twitter: _WenMing