Re: [MENTORS] Podling reports due June 1st

[justin]

Hi,

A report is due from Devlake but due to an issue with their entry in 
podlings.xml they are not included in this list or in the reminder that was 
sent out.

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

Re: [HELP WANTED] Creating the next board report

[Justin Mclean]

Hi,

> After the board meeting:
> - Update podlings.xml to mark podling that did not report, ones whose report 
> was missing but reported and podlings at the end of their monthly reporting 
> period
> - assign podling shepherds using assign_shepherds.py
> - run clutch script (./clutch2.sh) and generate report 
> template(clutch2report.py)
> - Update wiki report page to have correct podling listed (may need to remove 
> graduated and retired podlings and add new podlings) 
> - Add any new PPMCs to the wiki so they can edit their report
> - Send out email containing list of podlings to report and dates.

All of the above have been done and the first reminder sent out.

Do I have any volunteers for the other tasks?

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

Re: [MENTORS] Incubator reminder script minor issue

[Justin Mclean]

Hi,

The issue was the future assuagement of shepherds, so I fixed that and I’ll 
resend the reminders. This may mean that a couple of podlings got a reminder 
when they don’t need to report. If you are not listed in the wiki there no need 
to submit a report.

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

[MENTORS] Incubator reminder script minor issue

[Justin Mclean]

HI,

Look like there's a small issue with the Incubator reminder script and it send 
out some reminders to the wrong podlings. What was listed in the wiki is 
correct.

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

[MENTORS] Podling reports due June 1st

[Justin Mclean]

Hi,

Please submit your podling reports here [1]

Reporting timeline is:
Wed June 1st -- Podling reports due by end of day
Sun June 5th -- Shepherd reviews due by end of day
Sun June 5th -- Summary due by end of day
Tue June 7th -- Mentor signoff due by end of day
Wed June 8th -- Report submitted to Board
Wed June 15th -- Board meeting

Expected to report are:

BBRPC
Crail
Hivemall
Kvrocks
Kyuubi
Livy
Marvin-AI
Nemo
Pegasus
PonyMail
SDAP
Spot
StreamPipes
Wayang

Kind Regards,
Justin

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



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

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Saisai Shao]

I see, thanks Justin and Daniel for your inputs.

Best regards,
Jerry

Daniel Widdis  于2022年5月23日周一 11:32写道：

> Adding onto this, even if there may be no legal trademark issue, there is
> other software by this name which makes it less than desirable.  Quoted
> from [1]
>
> > Avoiding search-results confusion is important for another reason.
> Apache projects are often very quickly highly ranked. An Apache project
> with a similar name to another application in the same technical space may
> quickly come to dominate searches in that space. If someone else holds a
> related trademark, this may lead to a legal dispute. As a non-profit
> organization, the ASF and Apache projects have no business conflicting with
> an existing trademark for software products or related services.
>
> A current search for "firestorm software" reveals multiple sites related
> to [2]. Searching "firestorm download" links to [3].  Searching "apache
> firestorm" links to sites providing parts for remote control model cars, of
> which two models compatible with such parts are "Apache" and "Firestorm"
> [4].
>
> 1 - https://infra.apache.org/project-names.html
> 2 - https://www.zotac.com/us/page/firestorm
> 3 - https://www.firestormviewer.org/choose-your-platform/
> 4 - https://www.competitionx.com/hpi-racing-manuals/
>
> Not my call, I am not a lawyer and have no binding votes on the incubator,
> just adding my observations.
>
> On 5/22/22, 8:04 PM, "Justin Mclean"  wrote:
>
> HI,
>
> > According to the trademarks@ current cursory feedback, looks like
> project
> > name "Firestorm" is OK.
>
> I don’t this that is the case. Trademark checked “FlameStorm”, and
> said that if Firestorm was as issue then FlameStorm would also be an issue.
> I don’t believe they have checked FireStorm.
>
> Please don’t under estimate the cost of a project name change, I seen
> several project go through this and it it is always much more effort than
> you realise. Based on previous experience, Infra are not likely to make it
> a priority to help with a name change mid incubation or just before
> gradation.
>
> Kind Regards,
> 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
>
>

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Daniel Widdis]

Adding onto this, even if there may be no legal trademark issue, there is other 
software by this name which makes it less than desirable.  Quoted from [1]

> Avoiding search-results confusion is important for another reason. Apache 
> projects are often very quickly highly ranked. An Apache project with a 
> similar name to another application in the same technical space may quickly 
> come to dominate searches in that space. If someone else holds a related 
> trademark, this may lead to a legal dispute. As a non-profit organization, 
> the ASF and Apache projects have no business conflicting with an existing 
> trademark for software products or related services.

A current search for "firestorm software" reveals multiple sites related to 
[2]. Searching "firestorm download" links to [3].  Searching "apache firestorm" 
links to sites providing parts for remote control model cars, of which two 
models compatible with such parts are "Apache" and "Firestorm" [4].

1 - https://infra.apache.org/project-names.html 
2 - https://www.zotac.com/us/page/firestorm 
3 - https://www.firestormviewer.org/choose-your-platform/ 
4 - https://www.competitionx.com/hpi-racing-manuals/ 

Not my call, I am not a lawyer and have no binding votes on the incubator, just 
adding my observations.

On 5/22/22, 8:04 PM, "Justin Mclean"  wrote:

HI,

> According to the trademarks@ current cursory feedback, looks like project
> name "Firestorm" is OK.

I don’t this that is the case. Trademark checked “FlameStorm”, and said 
that if Firestorm was as issue then FlameStorm would also be an issue. I don’t 
believe they have checked FireStorm.

Please don’t under estimate the cost of a project name change, I seen 
several project go through this and it it is always much more effort than you 
realise. Based on previous experience, Infra are not likely to make it a 
priority to help with a name change mid incubation or just before gradation.

Kind Regards,
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

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Justin Mclean]

HI,

> According to the trademarks@ current cursory feedback, looks like project
> name "Firestorm" is OK.

I don’t this that is the case. Trademark checked “FlameStorm”, and said that if 
Firestorm was as issue then FlameStorm would also be an issue. I don’t believe 
they have checked FireStorm.

Please don’t under estimate the cost of a project name change, I seen several 
project go through this and it it is always much more effort than you realise. 
Based on previous experience, Infra are not likely to make it a priority to 
help with a name change mid incubation or just before gradation.

Kind Regards,
Justin


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

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Jerry Shao]

Hi all,

Thanks for your feedbacks.

According to the trademarks@ current cursory feedback, looks like project
name "Firestorm" is OK.

After a quick search of registered US trademarks I don't see anything
> that would give me cause for concern.
>
> Note that if FIRESTORM was infringing, then I would not be prepared to
> approve FLAMESTORM either.
>


> I am saying having reviewed the registered marks at the USTPO for
> FIRESTORM I do not see any reason to reject FIRESTORM as a name for an

Apache podling.


I think maybe we could continue the proposal and do a PNS during podling.

What do you think?

Thanks
Jerry


Shuai Di  于2022年5月21日周六 22:51写道：

> +1 (non-binding)
> Interesting project, good luck!
>
> Shuai Di
> Best Regards.
>
> 俊平堵  于2022年5月21日周六 10:40写道：
>
> >
> > I cannot agree more.
> > In ASF, we have many SQLs, MQs, streamings, etc, and some projects among
> > them are really awesome. We (in ASF) should not be in the position to ask
> > projects to merge but leave it to community (users and developers) of
> > projects to decide if they want to.
> > Appreciate Jerry and Yu who spend time to discuss the possibilities of
> > working together in some way.
> > +1 on the proposal and good luck to Firestorm!
> >
> > Justin Mclean  于2022年5月18日周三 15:12写道：
> >
> > > Hi,
> > >
> > > It would be good if the project could work together, but there isn’t
> > > anything wrong with having two similar incubating projects. If the
> projects
> > > decide not to join forces, we would welcome an incubating proposal
> from the
> > > other project. The ASF doesn't pick projects to use, we let the wider
> user
> > > community decide what they want to use.
> > >
> > > Kind Regards,
> > > 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
>
>

Re: Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[Jerry Shao]

+1 binding. Good luck to Inlong project.

Best
Jerry

guo jiwei  于2022年5月23日周一 09:22写道：

> +1 (non-binding). good luck
>
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Mon, May 23, 2022 at 8:46 AM Xiangdong Huang 
> wrote:
>
> > +1 binding. Good luck.
> > ---
> > Xiangdong Huang
> >
> >
> >
> > Liu Ted  于2022年5月22日周日 23:41写道：
> >
> > > +1 (binding). Good luck!
> > >
> > > Ted Liu
> > >
> > >   2022 年 5 月 22 日周日 22:09，俊平堵 写道：   +1 (binding).
> > > Good luck to InLong!
> > >
> > > Thanks,
> > >
> > > Junping
> > >
> > > Charles Zhang  于2022年5月19日周四 17:10写道：
> > >
> > > > Dear Apache Incubator Community,
> > > >
> > > >
> > > > The InLong Project has been incubating since 2019-11-03. In the past
> > two
> > > > and a half years, the project has been renamed from TubeMQ to InLong,
> > and
> > > > expanded its scope from a message queue service to a one-stop
> > integration
> > > > framework for massive data.
> > > >
> > > >
> > > > The InLong community has a discussion thread [1], passed the
> community
> > > vote
> > > > [2], and the vote result is published [3]. Our assessment is that
> > Apache
> > > > InLong(Incubating) is ready to graduate as a TLP. We would like to
> > raise
> > > > the discussion to IPMC and collect more feedback towards graduation.
> > > >
> > > >
> > > > Since incubating in ASF, the project itself has become more mature
> and
> > > > stable. The following is a brief summary of the project and community
> > > > during the incubation:
> > > >
> > > >
> > > > - 11 versions were released by 6 different release managers, of
> which 5
> > > > versions are the original TubeMQ, and 6 versions are after the name
> was
> > > > changed to InLong. The release cadence is about 2 months [4].
> > > >
> > > >
> > > > - 10 new Committers and 3 PPMCs were added during incubating, they
> are
> > > from
> > > > 4 different organizations. All PPMCs and Committers are spread
> across 8
> > > > different organizations [5].
> > > >
> > > >
> > > > - 101 unique code developers [6].
> > > >
> > > >
> > > > - Closed more than 2200 issues, with an average of 200 issues per
> > version
> > > > [7].
> > > >
> > > >
> > > > - All the dependencies were reviewed and ensured they do not bring
> any
> > > > license issues [8].
> > > >
> > > >
> > > > - Evaluated the InLong project and self-checked the InLong maturity
> > model
> > > > [9] and the pre-graduation Check [10].
> > > >
> > > >
> > > > - Well and Complete documentation for contributors and users [11].
> > > >
> > > >
> > > > - Created channels like Email, Slack, Twitter, WeChat, and GitHub
> > > > Discussions to communicate, with more than 650 subscribers.
> > > >
> > > >
> > > > - Actively participated in or held more than 15 meetups to increase
> > > > community influence.
> > > >
> > > >
> > > > Please see the proposed board resolution below and let us know what
> you
> > > > think. The initial PMC members were passed by the discussion and
> > > invitation
> > > > [12].
> > > >
> > > >
> > > > The discussion will remain open for at least 72 hours, looking
> forward
> > to
> > > > your feedback.
> > > >
> > > >
> > > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > >
> > > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > >
> > > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > >
> > > > [4] https://inlong.apache.org/download/main/
> > > >
> > > > [5] https://whimsy.apache.org/roster/ppmc/inlong
> > > >
> > > > [6] https://github.com/apache/incubator-inlong/graphs/contributors
> > > >
> > > > [7]
> > > >
> > >
> >
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > > >
> > > > [8] https://github.com/apache/incubator-inlong/tree/master/licenses
> > > >
> > > > [9]
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG&title=Maturity+Assessment+for+InLong
> > > >
> > > > [10]
> > > >
> > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > > >
> > > > [11] https://inlong.apache.org/docs/next/introduction
> > > >
> > > > [12]
> https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
> > > >
> > > >
> > > >
> > > >
> > >
> >
> --
> > > >
> > > > Establish the Apache InLong 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 one-stop data integration framework that provides
> > > >
> > > > automatic, secure, and reliable data transmission capabilities.
> InLong
> > > >
> > > > s

Re: Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[guo jiwei]

+1 (non-binding). good luck


Regards
Jiwei Guo (Tboy)


On Mon, May 23, 2022 at 8:46 AM Xiangdong Huang  wrote:

> +1 binding. Good luck.
> ---
> Xiangdong Huang
>
>
>
> Liu Ted  于2022年5月22日周日 23:41写道：
>
> > +1 (binding). Good luck!
> >
> > Ted Liu
> >
> >   2022 年 5 月 22 日周日 22:09，俊平堵 写道：   +1 (binding).
> > Good luck to InLong!
> >
> > Thanks,
> >
> > Junping
> >
> > Charles Zhang  于2022年5月19日周四 17:10写道：
> >
> > > Dear Apache Incubator Community,
> > >
> > >
> > > The InLong Project has been incubating since 2019-11-03. In the past
> two
> > > and a half years, the project has been renamed from TubeMQ to InLong,
> and
> > > expanded its scope from a message queue service to a one-stop
> integration
> > > framework for massive data.
> > >
> > >
> > > The InLong community has a discussion thread [1], passed the community
> > vote
> > > [2], and the vote result is published [3]. Our assessment is that
> Apache
> > > InLong(Incubating) is ready to graduate as a TLP. We would like to
> raise
> > > the discussion to IPMC and collect more feedback towards graduation.
> > >
> > >
> > > Since incubating in ASF, the project itself has become more mature and
> > > stable. The following is a brief summary of the project and community
> > > during the incubation:
> > >
> > >
> > > - 11 versions were released by 6 different release managers, of which 5
> > > versions are the original TubeMQ, and 6 versions are after the name was
> > > changed to InLong. The release cadence is about 2 months [4].
> > >
> > >
> > > - 10 new Committers and 3 PPMCs were added during incubating, they are
> > from
> > > 4 different organizations. All PPMCs and Committers are spread across 8
> > > different organizations [5].
> > >
> > >
> > > - 101 unique code developers [6].
> > >
> > >
> > > - Closed more than 2200 issues, with an average of 200 issues per
> version
> > > [7].
> > >
> > >
> > > - All the dependencies were reviewed and ensured they do not bring any
> > > license issues [8].
> > >
> > >
> > > - Evaluated the InLong project and self-checked the InLong maturity
> model
> > > [9] and the pre-graduation Check [10].
> > >
> > >
> > > - Well and Complete documentation for contributors and users [11].
> > >
> > >
> > > - Created channels like Email, Slack, Twitter, WeChat, and GitHub
> > > Discussions to communicate, with more than 650 subscribers.
> > >
> > >
> > > - Actively participated in or held more than 15 meetups to increase
> > > community influence.
> > >
> > >
> > > Please see the proposed board resolution below and let us know what you
> > > think. The initial PMC members were passed by the discussion and
> > invitation
> > > [12].
> > >
> > >
> > > The discussion will remain open for at least 72 hours, looking forward
> to
> > > your feedback.
> > >
> > >
> > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > >
> > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > >
> > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > >
> > > [4] https://inlong.apache.org/download/main/
> > >
> > > [5] https://whimsy.apache.org/roster/ppmc/inlong
> > >
> > > [6] https://github.com/apache/incubator-inlong/graphs/contributors
> > >
> > > [7]
> > >
> >
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > >
> > > [8] https://github.com/apache/incubator-inlong/tree/master/licenses
> > >
> > > [9]
> > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG&title=Maturity+Assessment+for+InLong
> > >
> > > [10]
> > >
> https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > >
> > > [11] https://inlong.apache.org/docs/next/introduction
> > >
> > > [12] https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
> > >
> > >
> > >
> > >
> >
> --
> > >
> > > Establish the Apache InLong 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 one-stop data integration framework that provides
> > >
> > > automatic, secure, and reliable data transmission capabilities. InLong
> > >
> > > supports both batch and stream data processing at the same time, which
> > >
> > > offers great power to build data analysis, modeling, and other
> real-time
> > >
> > > applications based on streaming data.
> > >
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > >
> > > (PMC), to be known as the "Apache InLong Project", be and hereby is
> > >
> > > established pursuant to Bylaws of the Foundation; and be 

Re: Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[Xiangdong Huang]

+1 binding. Good luck.
---
Xiangdong Huang



Liu Ted  于2022年5月22日周日 23:41写道：

> +1 (binding). Good luck!
>
> Ted Liu
>
>   2022 年 5 月 22 日周日 22:09，俊平堵 写道：   +1 (binding).
> Good luck to InLong!
>
> Thanks,
>
> Junping
>
> Charles Zhang  于2022年5月19日周四 17:10写道：
>
> > Dear Apache Incubator Community,
> >
> >
> > The InLong Project has been incubating since 2019-11-03. In the past two
> > and a half years, the project has been renamed from TubeMQ to InLong, and
> > expanded its scope from a message queue service to a one-stop integration
> > framework for massive data.
> >
> >
> > The InLong community has a discussion thread [1], passed the community
> vote
> > [2], and the vote result is published [3]. Our assessment is that Apache
> > InLong(Incubating) is ready to graduate as a TLP. We would like to raise
> > the discussion to IPMC and collect more feedback towards graduation.
> >
> >
> > Since incubating in ASF, the project itself has become more mature and
> > stable. The following is a brief summary of the project and community
> > during the incubation:
> >
> >
> > - 11 versions were released by 6 different release managers, of which 5
> > versions are the original TubeMQ, and 6 versions are after the name was
> > changed to InLong. The release cadence is about 2 months [4].
> >
> >
> > - 10 new Committers and 3 PPMCs were added during incubating, they are
> from
> > 4 different organizations. All PPMCs and Committers are spread across 8
> > different organizations [5].
> >
> >
> > - 101 unique code developers [6].
> >
> >
> > - Closed more than 2200 issues, with an average of 200 issues per version
> > [7].
> >
> >
> > - All the dependencies were reviewed and ensured they do not bring any
> > license issues [8].
> >
> >
> > - Evaluated the InLong project and self-checked the InLong maturity model
> > [9] and the pre-graduation Check [10].
> >
> >
> > - Well and Complete documentation for contributors and users [11].
> >
> >
> > - Created channels like Email, Slack, Twitter, WeChat, and GitHub
> > Discussions to communicate, with more than 650 subscribers.
> >
> >
> > - Actively participated in or held more than 15 meetups to increase
> > community influence.
> >
> >
> > Please see the proposed board resolution below and let us know what you
> > think. The initial PMC members were passed by the discussion and
> invitation
> > [12].
> >
> >
> > The discussion will remain open for at least 72 hours, looking forward to
> > your feedback.
> >
> >
> > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> >
> > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> >
> > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> >
> > [4] https://inlong.apache.org/download/main/
> >
> > [5] https://whimsy.apache.org/roster/ppmc/inlong
> >
> > [6] https://github.com/apache/incubator-inlong/graphs/contributors
> >
> > [7]
> >
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> >
> > [8] https://github.com/apache/incubator-inlong/tree/master/licenses
> >
> > [9]
> >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG&title=Maturity+Assessment+for+InLong
> >
> > [10]
> > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> >
> > [11] https://inlong.apache.org/docs/next/introduction
> >
> > [12] https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
> >
> >
> >
> >
> --
> >
> > Establish the Apache InLong 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 one-stop data integration framework that provides
> >
> > automatic, secure, and reliable data transmission capabilities. InLong
> >
> > supports both batch and stream data processing at the same time, which
> >
> > offers great power to build data analysis, modeling, and other real-time
> >
> > applications based on streaming data.
> >
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >
> > (PMC), to be known as the "Apache InLong Project", be and hereby is
> >
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> >
> > RESOLVED, that the Apache InLong Project be and hereby is responsible
> >
> > for the creation and maintenance of software related to a one-stop data
> >
> > integration framework that provides automatic, secure, and reliable data
> >
> > transmission capabilities. InLong supports both batch and stream data
> >
> > processing at the same time, which offers great power to build data
> >
> > analysis, modeling, and ot

回复：Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[Liu Ted]

+1 (binding). Good luck!

Ted Liu 
 
  2022 年 5 月 22 日周日 22:09，俊平堵 写道：   +1 (binding). Good 
luck to InLong!

Thanks,

Junping

Charles Zhang  于2022年5月19日周四 17:10写道：

> Dear Apache Incubator Community,
>
>
> The InLong Project has been incubating since 2019-11-03. In the past two
> and a half years, the project has been renamed from TubeMQ to InLong, and
> expanded its scope from a message queue service to a one-stop integration
> framework for massive data.
>
>
> The InLong community has a discussion thread [1], passed the community vote
> [2], and the vote result is published [3]. Our assessment is that Apache
> InLong(Incubating) is ready to graduate as a TLP. We would like to raise
> the discussion to IPMC and collect more feedback towards graduation.
>
>
> Since incubating in ASF, the project itself has become more mature and
> stable. The following is a brief summary of the project and community
> during the incubation:
>
>
> - 11 versions were released by 6 different release managers, of which 5
> versions are the original TubeMQ, and 6 versions are after the name was
> changed to InLong. The release cadence is about 2 months [4].
>
>
> - 10 new Committers and 3 PPMCs were added during incubating, they are from
> 4 different organizations. All PPMCs and Committers are spread across 8
> different organizations [5].
>
>
> - 101 unique code developers [6].
>
>
> - Closed more than 2200 issues, with an average of 200 issues per version
> [7].
>
>
> - All the dependencies were reviewed and ensured they do not bring any
> license issues [8].
>
>
> - Evaluated the InLong project and self-checked the InLong maturity model
> [9] and the pre-graduation Check [10].
>
>
> - Well and Complete documentation for contributors and users [11].
>
>
> - Created channels like Email, Slack, Twitter, WeChat, and GitHub
> Discussions to communicate, with more than 650 subscribers.
>
>
> - Actively participated in or held more than 15 meetups to increase
> community influence.
>
>
> Please see the proposed board resolution below and let us know what you
> think. The initial PMC members were passed by the discussion and invitation
> [12].
>
>
> The discussion will remain open for at least 72 hours, looking forward to
> your feedback.
>
>
> [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
>
> [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
>
> [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
>
> [4] https://inlong.apache.org/download/main/
>
> [5] https://whimsy.apache.org/roster/ppmc/inlong
>
> [6] https://github.com/apache/incubator-inlong/graphs/contributors
>
> [7]
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
>
> [8] https://github.com/apache/incubator-inlong/tree/master/licenses
>
> [9]
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG&title=Maturity+Assessment+for+InLong
>
> [10]
> https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
>
> [11] https://inlong.apache.org/docs/next/introduction
>
> [12] https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
>
>
>
> --
>
> Establish the Apache InLong 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 one-stop data integration framework that provides
>
> automatic, secure, and reliable data transmission capabilities. InLong
>
> supports both batch and stream data processing at the same time, which
>
> offers great power to build data analysis, modeling, and other real-time
>
> applications based on streaming data.
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>
> (PMC), to be known as the "Apache InLong Project", be and hereby is
>
> established pursuant to Bylaws of the Foundation; and be it further
>
>
> RESOLVED, that the Apache InLong Project be and hereby is responsible
>
> for the creation and maintenance of software related to a one-stop data
>
> integration framework that provides automatic, secure, and reliable data
>
> transmission capabilities. InLong supports both batch and stream data
>
> processing at the same time, which offers great power to build data
>
> analysis, modeling, and other real-time applications based on streaming
>
> data; and be it further
>
>
> RESOLVED, that the office of "Vice President, Apache InLong" 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 InLong
>
> Project, and to have primary responsibility for management of the
>
> projects within the scope of responsibility of t

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[俊平堵]

+1 (binding). Good luck to InLong!

Thanks,

Junping

Charles Zhang  于2022年5月19日周四 17:10写道：

> Dear Apache Incubator Community,
>
>
> The InLong Project has been incubating since 2019-11-03. In the past two
> and a half years, the project has been renamed from TubeMQ to InLong, and
> expanded its scope from a message queue service to a one-stop integration
> framework for massive data.
>
>
> The InLong community has a discussion thread [1], passed the community vote
> [2], and the vote result is published [3]. Our assessment is that Apache
> InLong(Incubating) is ready to graduate as a TLP. We would like to raise
> the discussion to IPMC and collect more feedback towards graduation.
>
>
> Since incubating in ASF, the project itself has become more mature and
> stable. The following is a brief summary of the project and community
> during the incubation:
>
>
> - 11 versions were released by 6 different release managers, of which 5
> versions are the original TubeMQ, and 6 versions are after the name was
> changed to InLong. The release cadence is about 2 months [4].
>
>
> - 10 new Committers and 3 PPMCs were added during incubating, they are from
> 4 different organizations. All PPMCs and Committers are spread across 8
> different organizations [5].
>
>
> - 101 unique code developers [6].
>
>
> - Closed more than 2200 issues, with an average of 200 issues per version
> [7].
>
>
> - All the dependencies were reviewed and ensured they do not bring any
> license issues [8].
>
>
> - Evaluated the InLong project and self-checked the InLong maturity model
> [9] and the pre-graduation Check [10].
>
>
> - Well and Complete documentation for contributors and users [11].
>
>
> - Created channels like Email, Slack, Twitter, WeChat, and GitHub
> Discussions to communicate, with more than 650 subscribers.
>
>
> - Actively participated in or held more than 15 meetups to increase
> community influence.
>
>
> Please see the proposed board resolution below and let us know what you
> think. The initial PMC members were passed by the discussion and invitation
> [12].
>
>
> The discussion will remain open for at least 72 hours, looking forward to
> your feedback.
>
>
> [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
>
> [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
>
> [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
>
> [4] https://inlong.apache.org/download/main/
>
> [5] https://whimsy.apache.org/roster/ppmc/inlong
>
> [6] https://github.com/apache/incubator-inlong/graphs/contributors
>
> [7]
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
>
> [8] https://github.com/apache/incubator-inlong/tree/master/licenses
>
> [9]
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG&title=Maturity+Assessment+for+InLong
>
> [10]
> https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
>
> [11] https://inlong.apache.org/docs/next/introduction
>
> [12] https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
>
>
>
> --
>
> Establish the Apache InLong 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 one-stop data integration framework that provides
>
> automatic, secure, and reliable data transmission capabilities. InLong
>
> supports both batch and stream data processing at the same time, which
>
> offers great power to build data analysis, modeling, and other real-time
>
> applications based on streaming data.
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>
> (PMC), to be known as the "Apache InLong Project", be and hereby is
>
> established pursuant to Bylaws of the Foundation; and be it further
>
>
> RESOLVED, that the Apache InLong Project be and hereby is responsible
>
> for the creation and maintenance of software related to a one-stop data
>
> integration framework that provides automatic, secure, and reliable data
>
> transmission capabilities. InLong supports both batch and stream data
>
> processing at the same time, which offers great power to build data
>
> analysis, modeling, and other real-time applications based on streaming
>
> data; and be it further
>
>
> RESOLVED, that the office of "Vice President, Apache InLong" 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 InLong
>
> Project, and to have primary responsibility for management of the
>
> projects within the scope of responsibility of the Apache InLong
>
> Project; and be it further
>
>
> RESOLVED, that the p

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[张家峰]

1，good luck！

Zirui Peng 于2022年5月22日 周日20:02写道：

> +1, all the best, great work !
>
> On 2022/05/21 05:03:39 Aloys Zhang wrote:
> > +1, good luck
> >
> > Liang Chen  于2022年5月21日周六 00:04写道：
> >
> > > +1, good luck.
> > >
> > > Regards
> > > Liang
> > >
> > > tison  于2022年5月20日周五 18:13写道：
> > >
> > > > +1 good luck
> > > >
> > > > Young Seung Andrew Ko 于2022年5月20日
> > > 周五17:36写道：
> > > >
> > > > > +1  (non-binding)
> > > > >
> > > > > Well done :)
> > > > >
> > > > > On Fri, May 20, 2022 at 6:32 PM wangxiaogang <
> wangxiaog...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > +1, good luck；
> > > > > >
> > > > > >
> > > > > > Eason Chen  于2022年5月20日周五 16:34写道：
> > > > > >
> > > > > > > + 1  （non-binding）
> > > > > > >
> > > > > > > Good luck!
> > > > > > >
> > > > > > > On Fri, May 20, 2022 at 3:43 PM XiaoYu 
> wrote:
> > > > > > > >
> > > > > > > > + 1  （non-binding）
> > > > > > > >
> > > > > > > > Good luck!
> > > > > > > >
> > > > > > > > Heal Chow  于2022年5月20日周五 15:16写道：
> > > > > > > > >
> > > > > > > > > +1.
> > > > > > > > >
> > > > > > > > > I've learned a lot about community collaboration and
> > > maintaining
> > > > > open
> > > > > > > source projects in the InLong project. Looking forward to
> InLong
> > > > doing
> > > > > > > better in data integration.
> > > > > > > > >
> > > > > > > > > Good luck!
> > > > > > > > > HealChow
> > > > > > > > >
> > > > > > > > > On 2022/05/19 10:47:52 Goson zhang wrote:
> > > > > > > > > > +1
> > > > > > > > > >
> > > > > > > > > > Since the InLong project entered the incubation pool, the
> > > team
> > > > > has
> > > > > > > > > > continued to grow, with the help of community
> contributors,
> > > the
> > > > > > > project has
> > > > > > > > > > developed from a single module to a mature data
> integration
> > > > > > > framework, and
> > > > > > > > > > has implemented the application of the project in
> multiple
> > > > > > > environments.
> > > > > > > > > >
> > > > > > > > > > Looking forward to the continuous improvement of the
> InLong
> > > > > project
> > > > > > > to
> > > > > > > > > > become a global community of contributors to better
> serve the
> > > > big
> > > > > > > data
> > > > > > > > > > business.
> > > > > > > > > >
> > > > > > > > > > Thanks!
> > > > > > > > > >
> > > > > > > > > > Kent Yao  于2022年5月19日周四 17:25写道：
> > > > > > > > > >
> > > > > > > > > > > +1, good luck to InLong community
> > > > > > > > > > >
> > > > > > > > > > > Charles Zhang  于2022年5月19日周四
> > > > 17:09写道：
> > > > > > > > > > > >
> > > > > > > > > > > > Dear Apache Incubator Community,
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > The InLong Project has been incubating since
> 2019-11-03.
> > > In
> > > > > the
> > > > > > > past two
> > > > > > > > > > > > and a half years, the project has been renamed from
> > > TubeMQ
> > > > to
> > > > > > > InLong, and
> > > > > > > > > > > > expanded its scope from a message queue service to a
> > > > one-stop
> > > > > > > integration
> > > > > > > > > > > > framework for massive data.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > The InLong community has a discussion thread [1],
> passed
> > > > the
> > > > > > > community
> > > > > > > > > > > vote
> > > > > > > > > > > > [2], and the vote result is published [3]. Our
> assessment
> > > > is
> > > > > > > that Apache
> > > > > > > > > > > > InLong(Incubating) is ready to graduate as a TLP. We
> > > would
> > > > > like
> > > > > > > to raise
> > > > > > > > > > > > the discussion to IPMC and collect more feedback
> towards
> > > > > > > graduation.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > Since incubating in ASF, the project itself has
> become
> > > more
> > > > > > > mature and
> > > > > > > > > > > > stable. The following is a brief summary of the
> project
> > > and
> > > > > > > community
> > > > > > > > > > > > during the incubation:
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > - 11 versions were released by 6 different release
> > > > managers,
> > > > > of
> > > > > > > which 5
> > > > > > > > > > > > versions are the original TubeMQ, and 6 versions are
> > > after
> > > > > the
> > > > > > > name was
> > > > > > > > > > > > changed to InLong. The release cadence is about 2
> months
> > > > [4].
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > - 10 new Committers and 3 PPMCs were added during
> > > > incubating,
> > > > > > > they are
> > > > > > > > > > > from
> > > > > > > > > > > > 4 different organizations. All PPMCs and Committers
> are
> > > > > spread
> > > > > > > across 8
> > > > > > > > > > > > different organizations [5].
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > - 101 unique code developers [6].
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > - Closed more than 2200 issues, with an average of
> 200
> > > > issues
> > > > > > > per version
> > > > > > > > > > > > [7].

Re: [DISCUSS] Graduate Apache InLong(Incubating) as a TLP

[Zirui Peng]

+1, all the best, great work !

On 2022/05/21 05:03:39 Aloys Zhang wrote:
> +1, good luck
> 
> Liang Chen  于2022年5月21日周六 00:04写道：
> 
> > +1, good luck.
> >
> > Regards
> > Liang
> >
> > tison  于2022年5月20日周五 18:13写道：
> >
> > > +1 good luck
> > >
> > > Young Seung Andrew Ko 于2022年5月20日
> > 周五17:36写道：
> > >
> > > > +1  (non-binding)
> > > >
> > > > Well done :)
> > > >
> > > > On Fri, May 20, 2022 at 6:32 PM wangxiaogang 
> > > > wrote:
> > > >
> > > > > +1, good luck；
> > > > >
> > > > >
> > > > > Eason Chen  于2022年5月20日周五 16:34写道：
> > > > >
> > > > > > + 1  （non-binding）
> > > > > >
> > > > > > Good luck!
> > > > > >
> > > > > > On Fri, May 20, 2022 at 3:43 PM XiaoYu  wrote:
> > > > > > >
> > > > > > > + 1  （non-binding）
> > > > > > >
> > > > > > > Good luck!
> > > > > > >
> > > > > > > Heal Chow  于2022年5月20日周五 15:16写道：
> > > > > > > >
> > > > > > > > +1.
> > > > > > > >
> > > > > > > > I've learned a lot about community collaboration and
> > maintaining
> > > > open
> > > > > > source projects in the InLong project. Looking forward to InLong
> > > doing
> > > > > > better in data integration.
> > > > > > > >
> > > > > > > > Good luck!
> > > > > > > > HealChow
> > > > > > > >
> > > > > > > > On 2022/05/19 10:47:52 Goson zhang wrote:
> > > > > > > > > +1
> > > > > > > > >
> > > > > > > > > Since the InLong project entered the incubation pool, the
> > team
> > > > has
> > > > > > > > > continued to grow, with the help of community contributors,
> > the
> > > > > > project has
> > > > > > > > > developed from a single module to a mature data integration
> > > > > > framework, and
> > > > > > > > > has implemented the application of the project in multiple
> > > > > > environments.
> > > > > > > > >
> > > > > > > > > Looking forward to the continuous improvement of the InLong
> > > > project
> > > > > > to
> > > > > > > > > become a global community of contributors to better serve the
> > > big
> > > > > > data
> > > > > > > > > business.
> > > > > > > > >
> > > > > > > > > Thanks!
> > > > > > > > >
> > > > > > > > > Kent Yao  于2022年5月19日周四 17:25写道：
> > > > > > > > >
> > > > > > > > > > +1, good luck to InLong community
> > > > > > > > > >
> > > > > > > > > > Charles Zhang  于2022年5月19日周四
> > > 17:09写道：
> > > > > > > > > > >
> > > > > > > > > > > Dear Apache Incubator Community,
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > The InLong Project has been incubating since 2019-11-03.
> > In
> > > > the
> > > > > > past two
> > > > > > > > > > > and a half years, the project has been renamed from
> > TubeMQ
> > > to
> > > > > > InLong, and
> > > > > > > > > > > expanded its scope from a message queue service to a
> > > one-stop
> > > > > > integration
> > > > > > > > > > > framework for massive data.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > The InLong community has a discussion thread [1], passed
> > > the
> > > > > > community
> > > > > > > > > > vote
> > > > > > > > > > > [2], and the vote result is published [3]. Our assessment
> > > is
> > > > > > that Apache
> > > > > > > > > > > InLong(Incubating) is ready to graduate as a TLP. We
> > would
> > > > like
> > > > > > to raise
> > > > > > > > > > > the discussion to IPMC and collect more feedback towards
> > > > > > graduation.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Since incubating in ASF, the project itself has become
> > more
> > > > > > mature and
> > > > > > > > > > > stable. The following is a brief summary of the project
> > and
> > > > > > community
> > > > > > > > > > > during the incubation:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > - 11 versions were released by 6 different release
> > > managers,
> > > > of
> > > > > > which 5
> > > > > > > > > > > versions are the original TubeMQ, and 6 versions are
> > after
> > > > the
> > > > > > name was
> > > > > > > > > > > changed to InLong. The release cadence is about 2 months
> > > [4].
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > - 10 new Committers and 3 PPMCs were added during
> > > incubating,
> > > > > > they are
> > > > > > > > > > from
> > > > > > > > > > > 4 different organizations. All PPMCs and Committers are
> > > > spread
> > > > > > across 8
> > > > > > > > > > > different organizations [5].
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > - 101 unique code developers [6].
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > - Closed more than 2200 issues, with an average of 200
> > > issues
> > > > > > per version
> > > > > > > > > > > [7].
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > - All the dependencies were reviewed and ensured they do
> > > not
> > > > > > bring any
> > > > > > > > > > > license issues [8].
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > - Evaluated the InLong project and self-checked the
> > InLong
> > > > > > maturity model
> > > > > > > > > > > [9] and the pre-graduation Check [10].
> >

Re: [VOTE] Release Apache Linkis (Incubating) 1.1.1-RC2

[Zhen Wang]

+1 (non-binding)

I checked:
[OK] Download links are valid.
[OK] Checksums and PGP signatures are valid.
[OK] Source code distributions have correct names matching the current
release.
[OK] LICENSE and NOTICE files are correct for each Linkis repo.
[OK] All files have license headers if necessary.
[OK] Build successfully on Win11

Kind Regards,
Zhen Wang

ShaoFeng Shi  于2022年5月21日周六 21:22写道：

> Forward my vote in the dev@ list:
>
> +1 (binding)
>
> Best regards,
>
> Shaofeng Shi 史少锋
> Apache Kylin PMC,
> Apache Incubator 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
>
>
>
>
> peacewong  于2022年5月20日周五 17:46写道：
>
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache Linkis(Incubating)
> version
> > 1.1.1-RC2
> >
> > The Apache Linkis community has voted on and approved a proposal to
> > release
> > Apache Linkis(Incubating) version  1.1.1-RC2
> >
> > We now kindly request the Incubator PMC members review and vote on
> this
> > incubator release.
> >
> > The RC2 version mainly optimizes the problems reported by Justin in
> RC1
> > 1. Removed maven-wrapper.jar from source release and fix mvnw the
> > wrong line endings
> > 2. Upgrade py4j version to py4j-0.10.9.5 solve the license issue.
> > 3. In addition, the current compilation instructions in the
> readme
> > are to jump to the linkis official website 'Compile Guide', and the
> Linkis
> > community will pay attention to the validity of the link. And in the
> > future, it will be optimized to give compilation instructions directly in
> >   the readme.
> >
> > Linkis community vote thread:
> > •
> > 
> > https://lists.apache.org/thread/fokdzv8q8yq6r0kyodjgzcvsfl2t44r7
> >
> > Vote result thread:
> > •
> https://lists.apache.org/thread/g2jkwxck8scl584vk39glwbkhokszhxl
> >
> > The release candidate:
> > •
> > https://dist.apache.org/repos/dist/dev/incubator/linkis/1.1.1-RC2/
> >
> > Git tag for the release:
> > •
> >
> https://github.com/apache/incubator-linkis/releases/tag/release-1.1.1-rc2
> >
> > Release notes:
> > •  https://linkis.apache.org/docs/1.1.1/release-notes-1.1.1/
> >
> > The artifacts signed with PGP key [ 38C76105 ], corresponding to [
> > peacew...@apache.com], that can be found in keys file:
> > • https://downloads.apache.org/incubator/linkis/KEYS
> >
> >
> >
> > This is the first non DISCLAIMER-WIP version after joining the ASF
> > incubator
> >
> >
> > 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
> >
> > More detail checklist  please refer:
> > •
> >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > Steps to validate the release，Please refer to:
> > • https://linkis.apache.org/community/how-to-verify
> >
> > Thanks,
> > On behalf of Apache Linkis(Incubating) community
> >
>