Re: [HELP WANTED] Creating the next board report

[Jean-Baptiste Onofré]

Hi Justin,

I can help, just let me know the tasks you want me to do.

Thanks,
Regards
JB

On Thu, May 12, 2022 at 9:15 AM Justin Mclean  wrote:
>
> Hi,
>
> As noted here [2] the board report should not be the sole responsibility of 
> the chair to put together.
>
> Here's what is roughly needed for each board report.
>
> 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
>
> During the month:
> - Send out 2 or 3 reminders using report_reminders.py
>
> Before the report is due:
> - Write a summary of what has happened on the mailing list with anything of 
> interest
> - List all releases made during the month /  check if incubator votes match 
> with what’s in the release area
> - List who been added/removed to IPMC during the month
> - Check that PPMC members have been added correctly
> - Remove the non-reporting podlings sections from the report and note them as 
> not reporting
> - Note any podlings that didn’t get mentor sign off
> - Reflow the report and fix the report formatting including remove text 
> prompts for mentor activity and branding questions
> - Lock the wiki page so it can’t be edited
> - Send email to this list for review
> - Submit the report to the board
>
> If anyone would like to do any of these tasks just ask. If you need more 
> detail on how to do them just ask. The report run book report_reminders.py 
> and these pages [1][2] can also help. If no one volunteers then I’ll do them. 
> I’ll also check the report’s format and details if we do get volunteers.
>
> One thing it might be useful to look into is to see if we can automate 
> sending out the reminders each month rather than having it as a manual task.
>
> Kind Regards,
> Justin
>
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR
> 2. https://incubator.apache.org/guides/chair.html#board_report
> -
> 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

回复： [DISCUSSION] Incubating Proposal of Uniffle

[BLAST]

+1, Good Luck!




--原始邮件--
发件人:
"general"   
 
https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f),
we
 figured 
out a new project name "Uniffle" and created a new
  Thread.
 Please
 help to 
discuss.

 We would 
like to propose Uniffle[1] as a new Apache
 incubator
project,
 you
 can find 
the proposal here [2] for more details.

 Uniffle 
is a high performance, general purpose Remote
  Shuffle Service
 for
 
distributed compute engines like Apache Spark
 

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

[Sammi Chen]

+1 (non-binding)
Good luck to InLong!


Bests,
Sammi

On Wed, 25 May 2022 at 14:34, Charles Zhang  wrote:

> Dear Apache Incubator Community,
>
>
> The InLong community has a discussion thread [1], passed the community vote
> [2], and the vote result is published [3]. We have discussed the graduation
> for InLong in the Incubator Community [4], where no issues were raised and
> lots of positive responses were received.
>
>
> I would like to start this voting thread to request graduating Apache
> InLong (incubating) from the incubator as a TLP. Please provide your vote
> as one of the following options:
>
> [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
>
> [ ] +0 No opinion.
>
> [ ] -1 No, the InLong project is not ready to graduate, because ...
>
>
> The VOTE will remain open for at least 72 hours.
>
>
> 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 [5].
>
>
> - 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 [6].
>
>
> - 101 unique code developers [7].
>
>
> - Closed more than 2200 issues, with an average of 200 issues per version
>
> [8].
>
>
> - All the dependencies were reviewed and ensured they do not bring any
>
> license issues [9].
>
>
> - Evaluated the InLong project and self-checked the InLong maturity model
>
> [10] and the pre-graduation Check [11].
>
>
> - Well and Complete documentation for contributors and users [12].
>
>
> - 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
>
> [13].
>
>
> [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
>
> [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
>
> [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
>
> [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
>
> [5] https://inlong.apache.org/download/main/
>
> [6] https://whimsy.apache.org/roster/ppmc/inlong
>
> [7] https://github.com/apache/incubator-inlong/graphs/contributors
>
> [8]
>
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
>
> [9] https://github.com/apache/incubator-inlong/tree/master/licenses
>
> [10]
>
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
>
> [11]
>
> https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
>
> [12] https://inlong.apache.org/docs/next/introduction
>
> [13] 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 

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

[Guangxu Cheng]

+1 (no-binding)


On 2022/05/25 06:33:22 Charles Zhang wrote:
> Dear Apache Incubator Community,
> 
> 
> The InLong community has a discussion thread [1], passed the community vote
> [2], and the vote result is published [3]. We have discussed the graduation
> for InLong in the Incubator Community [4], where no issues were raised and
> lots of positive responses were received.
> 
> 
> I would like to start this voting thread to request graduating Apache
> InLong (incubating) from the incubator as a TLP. Please provide your vote
> as one of the following options:
> 
> [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> 
> [ ] +0 No opinion.
> 
> [ ] -1 No, the InLong project is not ready to graduate, because ...
> 
> 
> The VOTE will remain open for at least 72 hours.
> 
> 
> 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 [5].
> 
> 
> - 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 [6].
> 
> 
> - 101 unique code developers [7].
> 
> 
> - Closed more than 2200 issues, with an average of 200 issues per version
> 
> [8].
> 
> 
> - All the dependencies were reviewed and ensured they do not bring any
> 
> license issues [9].
> 
> 
> - Evaluated the InLong project and self-checked the InLong maturity model
> 
> [10] and the pre-graduation Check [11].
> 
> 
> - Well and Complete documentation for contributors and users [12].
> 
> 
> - 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
> 
> [13].
> 
> 
> [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> 
> [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> 
> [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> 
> [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> 
> [5] https://inlong.apache.org/download/main/
> 
> [6] https://whimsy.apache.org/roster/ppmc/inlong
> 
> [7] https://github.com/apache/incubator-inlong/graphs/contributors
> 
> [8]
> 
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> 
> [9] https://github.com/apache/incubator-inlong/tree/master/licenses
> 
> [10]
> 
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> 
> [11]
> 
> https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> 
> [12] https://inlong.apache.org/docs/next/introduction
> 
> [13] 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 

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

[Aloys Zhang]

+1 (non-binding)

guo jiwei  于2022年5月26日周四 10:04写道：

> +1 (non-binding)
>
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Thu, May 26, 2022 at 9:59 AM XiaoYu  wrote:
>
> > + 1 (non-binding)
> >
> > Good luck for InLong~
> >
> > Furkan KAMACI  于2022年5月26日周四 03:14写道：
> > >
> > > Hi,
> > >
> > > +1 (binding)
> > >
> > > Good luck!
> > >
> > > Kind Regards,
> > > Furkan KAMACI
> > >
> > > On Wed, May 25, 2022 at 10:04 PM Mingshen Sun 
> wrote:
> > >
> > > > +1 (no-binding)
> > > >
> > > > Good luck!
> > > >
> > > > On Wed, May 25, 2022 at 10:18 AM Liang Chen  >
> > > > wrote:
> > > > >
> > > > > +1(binding)
> > > > >
> > > > > Regards
> > > > > Liang
> > > > >
> > > > > Lidong Dai  于2022年5月25日周三 23:07写道：
> > > > >
> > > > > > +1 (binding)
> > > > > > Good luck!
> > > > > >
> > > > > > Best Regards
> > > > > >
> > > > > >
> > > > > >
> > > > > > ---
> > > > > > Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
> > > > > > Lidong Dai
> > > > > > lidong...@apache.org
> > > > > > Linkedin: https://www.linkedin.com/in/dailidong
> > > > > > Twitter: @WorkflowEasy 
> > > > > >
> > > > > > ---
> > > > > >
> > > > > >
> > > > > > On Wed, May 25, 2022 at 10:09 PM Jean-Baptiste Onofré <
> > j...@nanthrax.net
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > +1 (binding)
> > > > > > >
> > > > > > > InLong is a great project, and mature to be a TLP. The team got
> > the
> > > > > > > Apache way and is executing smoothly.
> > > > > > >
> > > > > > > Thanks !
> > > > > > > Regards
> > > > > > > JB
> > > > > > >
> > > > > > > On Wed, May 25, 2022 at 8:33 AM Charles Zhang <
> > > > dockerzh...@apache.org>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Dear Apache Incubator Community,
> > > > > > > >
> > > > > > > >
> > > > > > > > The InLong community has a discussion thread [1], passed the
> > > > community
> > > > > > > vote
> > > > > > > > [2], and the vote result is published [3]. We have discussed
> > the
> > > > > > > graduation
> > > > > > > > for InLong in the Incubator Community [4], where no issues
> were
> > > > raised
> > > > > > > and
> > > > > > > > lots of positive responses were received.
> > > > > > > >
> > > > > > > >
> > > > > > > > I would like to start this voting thread to request
> graduating
> > > > Apache
> > > > > > > > InLong (incubating) from the incubator as a TLP. Please
> provide
> > > > your
> > > > > > vote
> > > > > > > > as one of the following options:
> > > > > > > >
> > > > > > > > [ ] +1 Yes, I support InLong to graduate from the Apache
> > incubator.
> > > > > > > >
> > > > > > > > [ ] +0 No opinion.
> > > > > > > >
> > > > > > > > [ ] -1 No, the InLong project is not ready to graduate,
> > because ...
> > > > > > > >
> > > > > > > >
> > > > > > > > The VOTE will remain open for at least 72 hours.
> > > > > > > >
> > > > > > > >
> > > > > > > > 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 [5].
> > > > > > > >
> > > > > > > >
> > > > > > > > - 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 [6].
> > > > > > > >
> > > > > > > >
> > > > > > > > - 101 unique code developers [7].
> > > > > > > >
> > > > > > > >
> > > > > > > > - Closed more than 2200 issues, with an average of 200 issues
> > per
> > > > > > version
> > > > > > > >
> > > > > > > > [8].
> > > > > > > >
> > > > > > > >
> > > > > > > > - All the dependencies were reviewed and ensured they do not
> > bring
> > > > any
> > > > > > > >
> > > > > > > > license issues [9].
> > > > > > > >
> > > > > > > >
> > > > > > > > - Evaluated the InLong project and self-checked the InLong
> > maturity
> > > > > > model
> > > > > > > >
> > > > > > > > [10] and the pre-graduation Check [11].
> > > > > > > >
> > > > > > > >
> > > > > > > > - Well and Complete documentation for contributors and users
> > [12].
> > > > > > > >
> > > > > > > >
> > > > > > > > - 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.
> > > > > > > >
> > > > > > > >
> > > > > > > > 

Re: [DISCUSSION] Incubating Proposal of Uniffle

[guo jiwei]

+1 non-binding
Good luck


Regards
Jiwei Guo (Tboy)


On Wed, May 25, 2022 at 9:54 PM Zhankun Tang  wrote:

> +1 (Non-binding).
> Looking forward to see it grows a bigger community and possibly cover more
> scenarios like public cloud. :D
>
> BR,
> Zhankun
>
> Willem Jiang 于2022年5月25日 周三下午8:59写道：
>
> > +1 （binding）.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Wed, May 25, 2022 at 12:05 AM Jerry Shao  wrote:
> > >
> > > Hi all,
> > >
> > > Due to the name issue in thread (
> > > https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f), we
> > > figured out a new project name "Uniffle" and created a new Thread.
> Please
> > > help to discuss.
> > >
> > > We would like to propose Uniffle[1] as a new Apache incubator project,
> > you
> > > can find the proposal here [2] for more details.
> > >
> > > Uniffle is a high performance, general purpose Remote Shuffle Service
> for
> > > distributed compute engines like Apache Spark
> > > , Apache
> > > Hadoop MapReduce , Apache Flink
> > >  and so on. We are aiming to make
> Firestorm a
> > > universal shuffle service for distributed compute engines.
> > >
> > > Shuffle is the key part for a distributed compute engine to exchange
> the
> > > data between distributed tasks, the performance and stability of
> shuffle
> > > will directly affect the whole job. Current “local file pull-like
> shuffle
> > > style” has several limitations:
> > >
> > >1. Current shuffle is hard to support super large workloads,
> > especially
> > >in a high load environment, the major problem is IO problem (random
> > disk IO
> > >issue, network congestion and timeout).
> > >2. Current shuffle is hard to deploy on the disaggregated compute
> > >storage environment, as disk capacity is quite limited on compute
> > nodes.
> > >3. The constraint of storing shuffle data locally makes it hard to
> > scale
> > >elastically.
> > >
> > > Remote Shuffle Service is the key technology for enterprises to build
> big
> > > data platforms, to expand big data applications to disaggregated,
> > > online-offline hybrid environments, and to solve above problems.
> > >
> > > The implementation of Remote Shuffle Service -  “Uniffle”  - is heavily
> > > adopted in Tencent, and shows its advantages in production. Other
> > > enterprises also adopted or prepared to adopt Firestorm in their
> > > environments.
> > >
> > > Uniffle's key idea is brought from Salfish shuffle
> > > <
> >
> https://www.researchgate.net/publication/262241541_Sailfish_a_framework_for_large_scale_data_processing
> > >,
> > > it has several key design goals:
> > >
> > >1. High performance. Firestorm’s performance is close enough to
> local
> > >file based shuffle style for small workloads. For large workloads,
> it
> > is
> > >far better than the current shuffle style.
> > >2. Fault tolerance. Firestorm provides high availability for
> > Coordinated
> > >nodes, and failover for Shuffle nodes.
> > >3. Pluggable. Firestorm is highly pluggable, which could be suited
> to
> > >different compute engines, different backend storages, and different
> > >wire-protocols.
> > >
> > > We believe that Uniffle project will provide the great value for the
> > > community if it is accepted by the Apache incubator.
> > >
> > > I will help this project as champion and many thanks to the 3 mentors:
> > >
> > >-
> > >
> > >Felix Cheung (felixche...@apache.org)
> > >- Junping du (junping...@apache.org)
> > >- Weiwei Yang (w...@apache.org)
> > >- Xun liu (liu...@apache.org)
> > >- Zhankun Tang (zt...@apache.org)
> > >
> > >
> > > [1] https://github.com/Tencent/Firestorm
> > > [2]
> > https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal
> > >
> > > Best regards,
> > > Jerry
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

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

[guo jiwei]

+1 (non-binding)


Regards
Jiwei Guo (Tboy)


On Thu, May 26, 2022 at 9:59 AM XiaoYu  wrote:

> + 1 (non-binding)
>
> Good luck for InLong~
>
> Furkan KAMACI  于2022年5月26日周四 03:14写道：
> >
> > Hi,
> >
> > +1 (binding)
> >
> > Good luck!
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > On Wed, May 25, 2022 at 10:04 PM Mingshen Sun  wrote:
> >
> > > +1 (no-binding)
> > >
> > > Good luck!
> > >
> > > On Wed, May 25, 2022 at 10:18 AM Liang Chen 
> > > wrote:
> > > >
> > > > +1(binding)
> > > >
> > > > Regards
> > > > Liang
> > > >
> > > > Lidong Dai  于2022年5月25日周三 23:07写道：
> > > >
> > > > > +1 (binding)
> > > > > Good luck!
> > > > >
> > > > > Best Regards
> > > > >
> > > > >
> > > > >
> > > > > ---
> > > > > Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
> > > > > Lidong Dai
> > > > > lidong...@apache.org
> > > > > Linkedin: https://www.linkedin.com/in/dailidong
> > > > > Twitter: @WorkflowEasy 
> > > > >
> > > > > ---
> > > > >
> > > > >
> > > > > On Wed, May 25, 2022 at 10:09 PM Jean-Baptiste Onofré <
> j...@nanthrax.net
> > > >
> > > > > wrote:
> > > > >
> > > > > > +1 (binding)
> > > > > >
> > > > > > InLong is a great project, and mature to be a TLP. The team got
> the
> > > > > > Apache way and is executing smoothly.
> > > > > >
> > > > > > Thanks !
> > > > > > Regards
> > > > > > JB
> > > > > >
> > > > > > On Wed, May 25, 2022 at 8:33 AM Charles Zhang <
> > > dockerzh...@apache.org>
> > > > > > wrote:
> > > > > > >
> > > > > > > Dear Apache Incubator Community,
> > > > > > >
> > > > > > >
> > > > > > > The InLong community has a discussion thread [1], passed the
> > > community
> > > > > > vote
> > > > > > > [2], and the vote result is published [3]. We have discussed
> the
> > > > > > graduation
> > > > > > > for InLong in the Incubator Community [4], where no issues were
> > > raised
> > > > > > and
> > > > > > > lots of positive responses were received.
> > > > > > >
> > > > > > >
> > > > > > > I would like to start this voting thread to request graduating
> > > Apache
> > > > > > > InLong (incubating) from the incubator as a TLP. Please provide
> > > your
> > > > > vote
> > > > > > > as one of the following options:
> > > > > > >
> > > > > > > [ ] +1 Yes, I support InLong to graduate from the Apache
> incubator.
> > > > > > >
> > > > > > > [ ] +0 No opinion.
> > > > > > >
> > > > > > > [ ] -1 No, the InLong project is not ready to graduate,
> because ...
> > > > > > >
> > > > > > >
> > > > > > > The VOTE will remain open for at least 72 hours.
> > > > > > >
> > > > > > >
> > > > > > > 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 [5].
> > > > > > >
> > > > > > >
> > > > > > > - 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 [6].
> > > > > > >
> > > > > > >
> > > > > > > - 101 unique code developers [7].
> > > > > > >
> > > > > > >
> > > > > > > - Closed more than 2200 issues, with an average of 200 issues
> per
> > > > > version
> > > > > > >
> > > > > > > [8].
> > > > > > >
> > > > > > >
> > > > > > > - All the dependencies were reviewed and ensured they do not
> bring
> > > any
> > > > > > >
> > > > > > > license issues [9].
> > > > > > >
> > > > > > >
> > > > > > > - Evaluated the InLong project and self-checked the InLong
> maturity
> > > > > model
> > > > > > >
> > > > > > > [10] and the pre-graduation Check [11].
> > > > > > >
> > > > > > >
> > > > > > > - Well and Complete documentation for contributors and users
> [12].
> > > > > > >
> > > > > > >
> > > > > > > - 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
> > > > > > >
> > > > > > > [13].
> > > > > > >
> > > > > > >
> > > > > > > [1]
> > > https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > > > > >
> > > > > > > [2]
> > > 

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

[XiaoYu]

+ 1 (non-binding)

Good luck for InLong~

Furkan KAMACI  于2022年5月26日周四 03:14写道：
>
> Hi,
>
> +1 (binding)
>
> Good luck!
>
> Kind Regards,
> Furkan KAMACI
>
> On Wed, May 25, 2022 at 10:04 PM Mingshen Sun  wrote:
>
> > +1 (no-binding)
> >
> > Good luck!
> >
> > On Wed, May 25, 2022 at 10:18 AM Liang Chen 
> > wrote:
> > >
> > > +1(binding)
> > >
> > > Regards
> > > Liang
> > >
> > > Lidong Dai  于2022年5月25日周三 23:07写道：
> > >
> > > > +1 (binding)
> > > > Good luck!
> > > >
> > > > Best Regards
> > > >
> > > >
> > > >
> > > > ---
> > > > Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
> > > > Lidong Dai
> > > > lidong...@apache.org
> > > > Linkedin: https://www.linkedin.com/in/dailidong
> > > > Twitter: @WorkflowEasy 
> > > >
> > > > ---
> > > >
> > > >
> > > > On Wed, May 25, 2022 at 10:09 PM Jean-Baptiste Onofré  > >
> > > > wrote:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > InLong is a great project, and mature to be a TLP. The team got the
> > > > > Apache way and is executing smoothly.
> > > > >
> > > > > Thanks !
> > > > > Regards
> > > > > JB
> > > > >
> > > > > On Wed, May 25, 2022 at 8:33 AM Charles Zhang <
> > dockerzh...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > Dear Apache Incubator Community,
> > > > > >
> > > > > >
> > > > > > The InLong community has a discussion thread [1], passed the
> > community
> > > > > vote
> > > > > > [2], and the vote result is published [3]. We have discussed the
> > > > > graduation
> > > > > > for InLong in the Incubator Community [4], where no issues were
> > raised
> > > > > and
> > > > > > lots of positive responses were received.
> > > > > >
> > > > > >
> > > > > > I would like to start this voting thread to request graduating
> > Apache
> > > > > > InLong (incubating) from the incubator as a TLP. Please provide
> > your
> > > > vote
> > > > > > as one of the following options:
> > > > > >
> > > > > > [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> > > > > >
> > > > > > [ ] +0 No opinion.
> > > > > >
> > > > > > [ ] -1 No, the InLong project is not ready to graduate, because ...
> > > > > >
> > > > > >
> > > > > > The VOTE will remain open for at least 72 hours.
> > > > > >
> > > > > >
> > > > > > 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 [5].
> > > > > >
> > > > > >
> > > > > > - 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 [6].
> > > > > >
> > > > > >
> > > > > > - 101 unique code developers [7].
> > > > > >
> > > > > >
> > > > > > - Closed more than 2200 issues, with an average of 200 issues per
> > > > version
> > > > > >
> > > > > > [8].
> > > > > >
> > > > > >
> > > > > > - All the dependencies were reviewed and ensured they do not bring
> > any
> > > > > >
> > > > > > license issues [9].
> > > > > >
> > > > > >
> > > > > > - Evaluated the InLong project and self-checked the InLong maturity
> > > > model
> > > > > >
> > > > > > [10] and the pre-graduation Check [11].
> > > > > >
> > > > > >
> > > > > > - Well and Complete documentation for contributors and users [12].
> > > > > >
> > > > > >
> > > > > > - 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
> > > > > >
> > > > > > [13].
> > > > > >
> > > > > >
> > > > > > [1]
> > https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > > > >
> > > > > > [2]
> > https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > > > >
> > > > > > [3]
> > https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > > > >
> > > > > > [4]
> > https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> > > > > >
> > > > > > [5] https://inlong.apache.org/download/main/
> > > > > >
> > > > > > [6] https://whimsy.apache.org/roster/ppmc/inlong
> > > > > >
> > > > > > [7] https://github.com/apache/incubator-inlong/graphs/contributors
> > > > > >
> > > > > > [8]
> > > > > 

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

[Furkan KAMACI]

Hi,

+1 (binding)

Good luck!

Kind Regards,
Furkan KAMACI

On Wed, May 25, 2022 at 10:04 PM Mingshen Sun  wrote:

> +1 (no-binding)
>
> Good luck!
>
> On Wed, May 25, 2022 at 10:18 AM Liang Chen 
> wrote:
> >
> > +1(binding)
> >
> > Regards
> > Liang
> >
> > Lidong Dai  于2022年5月25日周三 23:07写道：
> >
> > > +1 (binding)
> > > Good luck!
> > >
> > > Best Regards
> > >
> > >
> > >
> > > ---
> > > Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
> > > Lidong Dai
> > > lidong...@apache.org
> > > Linkedin: https://www.linkedin.com/in/dailidong
> > > Twitter: @WorkflowEasy 
> > >
> > > ---
> > >
> > >
> > > On Wed, May 25, 2022 at 10:09 PM Jean-Baptiste Onofré  >
> > > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > InLong is a great project, and mature to be a TLP. The team got the
> > > > Apache way and is executing smoothly.
> > > >
> > > > Thanks !
> > > > Regards
> > > > JB
> > > >
> > > > On Wed, May 25, 2022 at 8:33 AM Charles Zhang <
> dockerzh...@apache.org>
> > > > wrote:
> > > > >
> > > > > Dear Apache Incubator Community,
> > > > >
> > > > >
> > > > > The InLong community has a discussion thread [1], passed the
> community
> > > > vote
> > > > > [2], and the vote result is published [3]. We have discussed the
> > > > graduation
> > > > > for InLong in the Incubator Community [4], where no issues were
> raised
> > > > and
> > > > > lots of positive responses were received.
> > > > >
> > > > >
> > > > > I would like to start this voting thread to request graduating
> Apache
> > > > > InLong (incubating) from the incubator as a TLP. Please provide
> your
> > > vote
> > > > > as one of the following options:
> > > > >
> > > > > [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> > > > >
> > > > > [ ] +0 No opinion.
> > > > >
> > > > > [ ] -1 No, the InLong project is not ready to graduate, because ...
> > > > >
> > > > >
> > > > > The VOTE will remain open for at least 72 hours.
> > > > >
> > > > >
> > > > > 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 [5].
> > > > >
> > > > >
> > > > > - 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 [6].
> > > > >
> > > > >
> > > > > - 101 unique code developers [7].
> > > > >
> > > > >
> > > > > - Closed more than 2200 issues, with an average of 200 issues per
> > > version
> > > > >
> > > > > [8].
> > > > >
> > > > >
> > > > > - All the dependencies were reviewed and ensured they do not bring
> any
> > > > >
> > > > > license issues [9].
> > > > >
> > > > >
> > > > > - Evaluated the InLong project and self-checked the InLong maturity
> > > model
> > > > >
> > > > > [10] and the pre-graduation Check [11].
> > > > >
> > > > >
> > > > > - Well and Complete documentation for contributors and users [12].
> > > > >
> > > > >
> > > > > - 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
> > > > >
> > > > > [13].
> > > > >
> > > > >
> > > > > [1]
> https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > > >
> > > > > [2]
> https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > > >
> > > > > [3]
> https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > > >
> > > > > [4]
> https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> > > > >
> > > > > [5] https://inlong.apache.org/download/main/
> > > > >
> > > > > [6] https://whimsy.apache.org/roster/ppmc/inlong
> > > > >
> > > > > [7] https://github.com/apache/incubator-inlong/graphs/contributors
> > > > >
> > > > > [8]
> > > > >
> > > > >
> > > >
> > >
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > > > >
> > > > > [9]
> https://github.com/apache/incubator-inlong/tree/master/licenses
> > > > >
> > > > > [10]
> > > > >
> > > > >
> > > >
> > >
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > > > >
> > > > > [11]
> > > > >
> > > > >
> > >
> 

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

[Mingshen Sun]

+1 (no-binding)

Good luck!

On Wed, May 25, 2022 at 10:18 AM Liang Chen  wrote:
>
> +1(binding)
>
> Regards
> Liang
>
> Lidong Dai  于2022年5月25日周三 23:07写道：
>
> > +1 (binding)
> > Good luck!
> >
> > Best Regards
> >
> >
> >
> > ---
> > Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
> > Lidong Dai
> > lidong...@apache.org
> > Linkedin: https://www.linkedin.com/in/dailidong
> > Twitter: @WorkflowEasy 
> >
> > ---
> >
> >
> > On Wed, May 25, 2022 at 10:09 PM Jean-Baptiste Onofré 
> > wrote:
> >
> > > +1 (binding)
> > >
> > > InLong is a great project, and mature to be a TLP. The team got the
> > > Apache way and is executing smoothly.
> > >
> > > Thanks !
> > > Regards
> > > JB
> > >
> > > On Wed, May 25, 2022 at 8:33 AM Charles Zhang 
> > > wrote:
> > > >
> > > > Dear Apache Incubator Community,
> > > >
> > > >
> > > > The InLong community has a discussion thread [1], passed the community
> > > vote
> > > > [2], and the vote result is published [3]. We have discussed the
> > > graduation
> > > > for InLong in the Incubator Community [4], where no issues were raised
> > > and
> > > > lots of positive responses were received.
> > > >
> > > >
> > > > I would like to start this voting thread to request graduating Apache
> > > > InLong (incubating) from the incubator as a TLP. Please provide your
> > vote
> > > > as one of the following options:
> > > >
> > > > [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> > > >
> > > > [ ] +0 No opinion.
> > > >
> > > > [ ] -1 No, the InLong project is not ready to graduate, because ...
> > > >
> > > >
> > > > The VOTE will remain open for at least 72 hours.
> > > >
> > > >
> > > > 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 [5].
> > > >
> > > >
> > > > - 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 [6].
> > > >
> > > >
> > > > - 101 unique code developers [7].
> > > >
> > > >
> > > > - Closed more than 2200 issues, with an average of 200 issues per
> > version
> > > >
> > > > [8].
> > > >
> > > >
> > > > - All the dependencies were reviewed and ensured they do not bring any
> > > >
> > > > license issues [9].
> > > >
> > > >
> > > > - Evaluated the InLong project and self-checked the InLong maturity
> > model
> > > >
> > > > [10] and the pre-graduation Check [11].
> > > >
> > > >
> > > > - Well and Complete documentation for contributors and users [12].
> > > >
> > > >
> > > > - 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
> > > >
> > > > [13].
> > > >
> > > >
> > > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > >
> > > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > >
> > > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > >
> > > > [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> > > >
> > > > [5] https://inlong.apache.org/download/main/
> > > >
> > > > [6] https://whimsy.apache.org/roster/ppmc/inlong
> > > >
> > > > [7] https://github.com/apache/incubator-inlong/graphs/contributors
> > > >
> > > > [8]
> > > >
> > > >
> > >
> > https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > > >
> > > > [9] https://github.com/apache/incubator-inlong/tree/master/licenses
> > > >
> > > > [10]
> > > >
> > > >
> > >
> > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > > >
> > > > [11]
> > > >
> > > >
> > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > > >
> > > > [12] https://inlong.apache.org/docs/next/introduction
> > > >
> > > > [13] 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
> > > >
> > > > 

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

[Liang Chen]

+1(binding)

Regards
Liang

Lidong Dai  于2022年5月25日周三 23:07写道：

> +1 (binding)
> Good luck!
>
> Best Regards
>
>
>
> ---
> Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
> Lidong Dai
> lidong...@apache.org
> Linkedin: https://www.linkedin.com/in/dailidong
> Twitter: @WorkflowEasy 
>
> ---
>
>
> On Wed, May 25, 2022 at 10:09 PM Jean-Baptiste Onofré 
> wrote:
>
> > +1 (binding)
> >
> > InLong is a great project, and mature to be a TLP. The team got the
> > Apache way and is executing smoothly.
> >
> > Thanks !
> > Regards
> > JB
> >
> > On Wed, May 25, 2022 at 8:33 AM Charles Zhang 
> > wrote:
> > >
> > > Dear Apache Incubator Community,
> > >
> > >
> > > The InLong community has a discussion thread [1], passed the community
> > vote
> > > [2], and the vote result is published [3]. We have discussed the
> > graduation
> > > for InLong in the Incubator Community [4], where no issues were raised
> > and
> > > lots of positive responses were received.
> > >
> > >
> > > I would like to start this voting thread to request graduating Apache
> > > InLong (incubating) from the incubator as a TLP. Please provide your
> vote
> > > as one of the following options:
> > >
> > > [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> > >
> > > [ ] +0 No opinion.
> > >
> > > [ ] -1 No, the InLong project is not ready to graduate, because ...
> > >
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > >
> > > 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 [5].
> > >
> > >
> > > - 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 [6].
> > >
> > >
> > > - 101 unique code developers [7].
> > >
> > >
> > > - Closed more than 2200 issues, with an average of 200 issues per
> version
> > >
> > > [8].
> > >
> > >
> > > - All the dependencies were reviewed and ensured they do not bring any
> > >
> > > license issues [9].
> > >
> > >
> > > - Evaluated the InLong project and self-checked the InLong maturity
> model
> > >
> > > [10] and the pre-graduation Check [11].
> > >
> > >
> > > - Well and Complete documentation for contributors and users [12].
> > >
> > >
> > > - 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
> > >
> > > [13].
> > >
> > >
> > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > >
> > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > >
> > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > >
> > > [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> > >
> > > [5] https://inlong.apache.org/download/main/
> > >
> > > [6] https://whimsy.apache.org/roster/ppmc/inlong
> > >
> > > [7] https://github.com/apache/incubator-inlong/graphs/contributors
> > >
> > > [8]
> > >
> > >
> >
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > >
> > > [9] https://github.com/apache/incubator-inlong/tree/master/licenses
> > >
> > > [10]
> > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > >
> > > [11]
> > >
> > >
> https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > >
> > > [12] https://inlong.apache.org/docs/next/introduction
> > >
> > > [13] 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 

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

[Lidong Dai]

+1 (binding)
Good luck!

Best Regards



---
Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
Lidong Dai
lidong...@apache.org
Linkedin: https://www.linkedin.com/in/dailidong
Twitter: @WorkflowEasy 

---


On Wed, May 25, 2022 at 10:09 PM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> InLong is a great project, and mature to be a TLP. The team got the
> Apache way and is executing smoothly.
>
> Thanks !
> Regards
> JB
>
> On Wed, May 25, 2022 at 8:33 AM Charles Zhang 
> wrote:
> >
> > Dear Apache Incubator Community,
> >
> >
> > The InLong community has a discussion thread [1], passed the community
> vote
> > [2], and the vote result is published [3]. We have discussed the
> graduation
> > for InLong in the Incubator Community [4], where no issues were raised
> and
> > lots of positive responses were received.
> >
> >
> > I would like to start this voting thread to request graduating Apache
> > InLong (incubating) from the incubator as a TLP. Please provide your vote
> > as one of the following options:
> >
> > [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> >
> > [ ] +0 No opinion.
> >
> > [ ] -1 No, the InLong project is not ready to graduate, because ...
> >
> >
> > The VOTE will remain open for at least 72 hours.
> >
> >
> > 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 [5].
> >
> >
> > - 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 [6].
> >
> >
> > - 101 unique code developers [7].
> >
> >
> > - Closed more than 2200 issues, with an average of 200 issues per version
> >
> > [8].
> >
> >
> > - All the dependencies were reviewed and ensured they do not bring any
> >
> > license issues [9].
> >
> >
> > - Evaluated the InLong project and self-checked the InLong maturity model
> >
> > [10] and the pre-graduation Check [11].
> >
> >
> > - Well and Complete documentation for contributors and users [12].
> >
> >
> > - 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
> >
> > [13].
> >
> >
> > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> >
> > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> >
> > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> >
> > [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> >
> > [5] https://inlong.apache.org/download/main/
> >
> > [6] https://whimsy.apache.org/roster/ppmc/inlong
> >
> > [7] https://github.com/apache/incubator-inlong/graphs/contributors
> >
> > [8]
> >
> >
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> >
> > [9] https://github.com/apache/incubator-inlong/tree/master/licenses
> >
> > [10]
> >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> >
> > [11]
> >
> > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> >
> > [12] https://inlong.apache.org/docs/next/introduction
> >
> > [13] 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
> >
> > 

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

[Jean-Baptiste Onofré]

+1 (binding)

InLong is a great project, and mature to be a TLP. The team got the
Apache way and is executing smoothly.

Thanks !
Regards
JB

On Wed, May 25, 2022 at 8:33 AM Charles Zhang  wrote:
>
> Dear Apache Incubator Community,
>
>
> The InLong community has a discussion thread [1], passed the community vote
> [2], and the vote result is published [3]. We have discussed the graduation
> for InLong in the Incubator Community [4], where no issues were raised and
> lots of positive responses were received.
>
>
> I would like to start this voting thread to request graduating Apache
> InLong (incubating) from the incubator as a TLP. Please provide your vote
> as one of the following options:
>
> [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
>
> [ ] +0 No opinion.
>
> [ ] -1 No, the InLong project is not ready to graduate, because ...
>
>
> The VOTE will remain open for at least 72 hours.
>
>
> 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 [5].
>
>
> - 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 [6].
>
>
> - 101 unique code developers [7].
>
>
> - Closed more than 2200 issues, with an average of 200 issues per version
>
> [8].
>
>
> - All the dependencies were reviewed and ensured they do not bring any
>
> license issues [9].
>
>
> - Evaluated the InLong project and self-checked the InLong maturity model
>
> [10] and the pre-graduation Check [11].
>
>
> - Well and Complete documentation for contributors and users [12].
>
>
> - 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
>
> [13].
>
>
> [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
>
> [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
>
> [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
>
> [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
>
> [5] https://inlong.apache.org/download/main/
>
> [6] https://whimsy.apache.org/roster/ppmc/inlong
>
> [7] https://github.com/apache/incubator-inlong/graphs/contributors
>
> [8]
>
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
>
> [9] https://github.com/apache/incubator-inlong/tree/master/licenses
>
> [10]
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
>
> [11]
>
> https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
>
> [12] https://inlong.apache.org/docs/next/introduction
>
> [13] 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 

Re: [DISCUSSION] Incubating Proposal of Uniffle

[Zhankun Tang]

+1 (Non-binding).
Looking forward to see it grows a bigger community and possibly cover more
scenarios like public cloud. :D

BR,
Zhankun

Willem Jiang 于2022年5月25日 周三下午8:59写道：

> +1 （binding）.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, May 25, 2022 at 12:05 AM Jerry Shao  wrote:
> >
> > Hi all,
> >
> > Due to the name issue in thread (
> > https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f), we
> > figured out a new project name "Uniffle" and created a new Thread. Please
> > help to discuss.
> >
> > We would like to propose Uniffle[1] as a new Apache incubator project,
> you
> > can find the proposal here [2] for more details.
> >
> > Uniffle is a high performance, general purpose Remote Shuffle Service for
> > distributed compute engines like Apache Spark
> > , Apache
> > Hadoop MapReduce , Apache Flink
> >  and so on. We are aiming to make Firestorm a
> > universal shuffle service for distributed compute engines.
> >
> > Shuffle is the key part for a distributed compute engine to exchange the
> > data between distributed tasks, the performance and stability of shuffle
> > will directly affect the whole job. Current “local file pull-like shuffle
> > style” has several limitations:
> >
> >1. Current shuffle is hard to support super large workloads,
> especially
> >in a high load environment, the major problem is IO problem (random
> disk IO
> >issue, network congestion and timeout).
> >2. Current shuffle is hard to deploy on the disaggregated compute
> >storage environment, as disk capacity is quite limited on compute
> nodes.
> >3. The constraint of storing shuffle data locally makes it hard to
> scale
> >elastically.
> >
> > Remote Shuffle Service is the key technology for enterprises to build big
> > data platforms, to expand big data applications to disaggregated,
> > online-offline hybrid environments, and to solve above problems.
> >
> > The implementation of Remote Shuffle Service -  “Uniffle”  - is heavily
> > adopted in Tencent, and shows its advantages in production. Other
> > enterprises also adopted or prepared to adopt Firestorm in their
> > environments.
> >
> > Uniffle's key idea is brought from Salfish shuffle
> > <
> https://www.researchgate.net/publication/262241541_Sailfish_a_framework_for_large_scale_data_processing
> >,
> > it has several key design goals:
> >
> >1. High performance. Firestorm’s performance is close enough to local
> >file based shuffle style for small workloads. For large workloads, it
> is
> >far better than the current shuffle style.
> >2. Fault tolerance. Firestorm provides high availability for
> Coordinated
> >nodes, and failover for Shuffle nodes.
> >3. Pluggable. Firestorm is highly pluggable, which could be suited to
> >different compute engines, different backend storages, and different
> >wire-protocols.
> >
> > We believe that Uniffle project will provide the great value for the
> > community if it is accepted by the Apache incubator.
> >
> > I will help this project as champion and many thanks to the 3 mentors:
> >
> >-
> >
> >Felix Cheung (felixche...@apache.org)
> >- Junping du (junping...@apache.org)
> >- Weiwei Yang (w...@apache.org)
> >- Xun liu (liu...@apache.org)
> >- Zhankun Tang (zt...@apache.org)
> >
> >
> > [1] https://github.com/Tencent/Firestorm
> > [2]
> https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal
> >
> > Best regards,
> > Jerry
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

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

[Sheng Wu]

+1 binding

Enjoy your TLP journey.

Sheng Wu 吴晟
Twitter, wusheng1108

Eason Chen  于2022年5月25日周三 17:22写道：
>
> +1 (no-binding)
>
> Good luck!!
>
> On Wed, May 25, 2022 at 4:27 PM Goson zhang  wrote:
> >
> > +1 (no-binding)
> >
> > Good luck!!
> >
> > tison  于2022年5月25日周三 16:18写道：
> >
> > > +1 (binding)
> > >
> > > Good luck!
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > Jerry Shao  于2022年5月25日周三 16:12写道：
> > >
> > > > +1 (binding).
> > > >
> > > > Good luck to Inlong.
> > > >
> > > > Best
> > > > Jerry
> > > >
> > > > 俊平堵  于2022年5月25日周三 14:50写道：
> > > >
> > > > > +1, good luck to InLong.:)
> > > > >
> > > > > Charles Zhang 于2022年5月25日 周三下午2:34写道：
> > > > >
> > > > > > Dear Apache Incubator Community,
> > > > > >
> > > > > >
> > > > > > The InLong community has a discussion thread [1], passed the
> > > community
> > > > > vote
> > > > > > [2], and the vote result is published [3]. We have discussed the
> > > > > graduation
> > > > > > for InLong in the Incubator Community [4], where no issues were
> > > raised
> > > > > and
> > > > > > lots of positive responses were received.
> > > > > >
> > > > > >
> > > > > > I would like to start this voting thread to request graduating 
> > > > > > Apache
> > > > > > InLong (incubating) from the incubator as a TLP. Please provide your
> > > > vote
> > > > > > as one of the following options:
> > > > > >
> > > > > > [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> > > > > >
> > > > > > [ ] +0 No opinion.
> > > > > >
> > > > > > [ ] -1 No, the InLong project is not ready to graduate, because ...
> > > > > >
> > > > > >
> > > > > > The VOTE will remain open for at least 72 hours.
> > > > > >
> > > > > >
> > > > > > 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 [5].
> > > > > >
> > > > > >
> > > > > > - 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 [6].
> > > > > >
> > > > > >
> > > > > > - 101 unique code developers [7].
> > > > > >
> > > > > >
> > > > > > - Closed more than 2200 issues, with an average of 200 issues per
> > > > version
> > > > > >
> > > > > > [8].
> > > > > >
> > > > > >
> > > > > > - All the dependencies were reviewed and ensured they do not bring
> > > any
> > > > > >
> > > > > > license issues [9].
> > > > > >
> > > > > >
> > > > > > - Evaluated the InLong project and self-checked the InLong maturity
> > > > model
> > > > > >
> > > > > > [10] and the pre-graduation Check [11].
> > > > > >
> > > > > >
> > > > > > - Well and Complete documentation for contributors and users [12].
> > > > > >
> > > > > >
> > > > > > - 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
> > > > > >
> > > > > > [13].
> > > > > >
> > > > > >
> > > > > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > > > >
> > > > > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > > > >
> > > > > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > > > >
> > > > > > [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> > > > > >
> > > > > > [5] https://inlong.apache.org/download/main/
> > > > > >
> > > > > > [6] https://whimsy.apache.org/roster/ppmc/inlong
> > > > > >
> > > > > > [7] https://github.com/apache/incubator-inlong/graphs/contributors
> > > > > >
> > > > > > [8]
> > > > > >
> > > > > >
> > > > >
> > > >
> > > https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > > > > >
> > > > > > [9] https://github.com/apache/incubator-inlong/tree/master/licenses
> > > > > >
> > > > > > [10]
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > > > > >
> > > > > > [11]
> > > > > >
> > > > > >
> > > > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > > > > >
> > > > > > [12] 

Re: [HELP WANTED] Creating the next board report

[Willem Jiang]

Hi, Justin,

I can give a hand on it.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, May 23, 2022 at 2:23 PM Justin Mclean  wrote:
>
> 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
>

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

Re: [DISCUSSION] Incubating Proposal of Uniffle

[Willem Jiang]

+1 （binding）.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, May 25, 2022 at 12:05 AM Jerry Shao  wrote:
>
> Hi all,
>
> Due to the name issue in thread (
> https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f), we
> figured out a new project name "Uniffle" and created a new Thread. Please
> help to discuss.
>
> We would like to propose Uniffle[1] as a new Apache incubator project, you
> can find the proposal here [2] for more details.
>
> Uniffle is a high performance, general purpose Remote Shuffle Service for
> distributed compute engines like Apache Spark
> , Apache
> Hadoop MapReduce , Apache Flink
>  and so on. We are aiming to make Firestorm a
> universal shuffle service for distributed compute engines.
>
> Shuffle is the key part for a distributed compute engine to exchange the
> data between distributed tasks, the performance and stability of shuffle
> will directly affect the whole job. Current “local file pull-like shuffle
> style” has several limitations:
>
>1. Current shuffle is hard to support super large workloads, especially
>in a high load environment, the major problem is IO problem (random disk IO
>issue, network congestion and timeout).
>2. Current shuffle is hard to deploy on the disaggregated compute
>storage environment, as disk capacity is quite limited on compute nodes.
>3. The constraint of storing shuffle data locally makes it hard to scale
>elastically.
>
> Remote Shuffle Service is the key technology for enterprises to build big
> data platforms, to expand big data applications to disaggregated,
> online-offline hybrid environments, and to solve above problems.
>
> The implementation of Remote Shuffle Service -  “Uniffle”  - is heavily
> adopted in Tencent, and shows its advantages in production. Other
> enterprises also adopted or prepared to adopt Firestorm in their
> environments.
>
> Uniffle's key idea is brought from Salfish shuffle
> ,
> it has several key design goals:
>
>1. High performance. Firestorm’s performance is close enough to local
>file based shuffle style for small workloads. For large workloads, it is
>far better than the current shuffle style.
>2. Fault tolerance. Firestorm provides high availability for Coordinated
>nodes, and failover for Shuffle nodes.
>3. Pluggable. Firestorm is highly pluggable, which could be suited to
>different compute engines, different backend storages, and different
>wire-protocols.
>
> We believe that Uniffle project will provide the great value for the
> community if it is accepted by the Apache incubator.
>
> I will help this project as champion and many thanks to the 3 mentors:
>
>-
>
>Felix Cheung (felixche...@apache.org)
>- Junping du (junping...@apache.org)
>- Weiwei Yang (w...@apache.org)
>- Xun liu (liu...@apache.org)
>- Zhankun Tang (zt...@apache.org)
>
>
> [1] https://github.com/Tencent/Firestorm
> [2] https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal
>
> Best regards,
> Jerry

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

Re: [DISCUSSION] Incubating Proposal of Uniffle

[Charles Zhang]

+1 (non-binding)

Good luck

Brahma Reddy Battula  于2022年5月25日周三 17:24写道：

> + 1 ( non binding)
>
> Good luck
>
> On Wed, 25 May 2022 at 1:55 PM, Sammi Chen  wrote:
>
> > +1  (non-binding)
> >
> > Good luck to Uniffle.
> >
> > Bests,
> > Sammi
> >
> > On Wed, 25 May 2022 at 00:05, Jerry Shao  wrote:
> >
> > > Hi all,
> > >
> > > Due to the name issue in thread (
> > > https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f), we
> > > figured out a new project name "Uniffle" and created a new Thread.
> Please
> > > help to discuss.
> > >
> > > We would like to propose Uniffle[1] as a new Apache incubator project,
> > you
> > > can find the proposal here [2] for more details.
> > >
> > > Uniffle is a high performance, general purpose Remote Shuffle Service
> for
> > > distributed compute engines like Apache Spark
> > > , Apache
> > > Hadoop MapReduce , Apache Flink
> > >  and so on. We are aiming to make
> Firestorm a
> > > universal shuffle service for distributed compute engines.
> > >
> > > Shuffle is the key part for a distributed compute engine to exchange
> the
> > > data between distributed tasks, the performance and stability of
> shuffle
> > > will directly affect the whole job. Current “local file pull-like
> shuffle
> > > style” has several limitations:
> > >
> > >1. Current shuffle is hard to support super large workloads,
> > especially
> > >in a high load environment, the major problem is IO problem (random
> > > disk IO
> > >issue, network congestion and timeout).
> > >2. Current shuffle is hard to deploy on the disaggregated compute
> > >storage environment, as disk capacity is quite limited on compute
> > nodes.
> > >3. The constraint of storing shuffle data locally makes it hard to
> > scale
> > >elastically.
> > >
> > > Remote Shuffle Service is the key technology for enterprises to build
> big
> > > data platforms, to expand big data applications to disaggregated,
> > > online-offline hybrid environments, and to solve above problems.
> > >
> > > The implementation of Remote Shuffle Service -  “Uniffle”  - is heavily
> > > adopted in Tencent, and shows its advantages in production. Other
> > > enterprises also adopted or prepared to adopt Firestorm in their
> > > environments.
> > >
> > > Uniffle's key idea is brought from Salfish shuffle
> > > <
> > >
> >
> https://www.researchgate.net/publication/262241541_Sailfish_a_framework_for_large_scale_data_processing
> > > >,
> > > it has several key design goals:
> > >
> > >1. High performance. Firestorm’s performance is close enough to
> local
> > >file based shuffle style for small workloads. For large workloads,
> it
> > is
> > >far better than the current shuffle style.
> > >2. Fault tolerance. Firestorm provides high availability for
> > Coordinated
> > >nodes, and failover for Shuffle nodes.
> > >3. Pluggable. Firestorm is highly pluggable, which could be suited
> to
> > >different compute engines, different backend storages, and different
> > >wire-protocols.
> > >
> > > We believe that Uniffle project will provide the great value for the
> > > community if it is accepted by the Apache incubator.
> > >
> > > I will help this project as champion and many thanks to the 3 mentors:
> > >
> > >-
> > >
> > >Felix Cheung (felixche...@apache.org)
> > >- Junping du (junping...@apache.org)
> > >- Weiwei Yang (w...@apache.org)
> > >- Xun liu (liu...@apache.org)
> > >- Zhankun Tang (zt...@apache.org)
> > >
> > >
> > > [1] https://github.com/Tencent/Firestorm
> > > [2]
> > https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal
> > >
> > > Best regards,
> > > Jerry
> > >
> >
> --
>
>
>
> --Brahma Reddy Battula
>


-- 
Best wishes,
Charles Zhang

[ANNOUNCE] Apache Linkis (Incubating) 1.1.1 available

[peacewong]

  Hi all,

Apache Linkis (Incubating) Team is glad to announce the new release of
Apache Linkis (Incubating) 1.1.1

Apache Linkis (Incubating) builds a computation middleware layer to
decouple the upper applications and the underlying data engines,
provides standardized interfaces (REST, JDBC, WebSocket etc.) to
easily connect to various underlying engines (Spark, Presto, Flink,
etc.), while enables cross engine context sharing, unified job& engine
governance and orchestration.

Download Links: https://linkis.apache.org/download/main/

Release Notes: https://linkis.apache.org/download/release-notes-1.1.1

Website: https://linkis.apache.org/

Linkis Resources:
- Issue: https://github.com/apache/incubator-linkis/issues
- Mailing list: d...@linkis.apache.org

- Apache Linkis (Incubating) Team

Re: [DISCUSSION] Incubating Proposal of Uniffle

[Brahma Reddy Battula]

+ 1 ( non binding)

Good luck

On Wed, 25 May 2022 at 1:55 PM, Sammi Chen  wrote:

> +1  (non-binding)
>
> Good luck to Uniffle.
>
> Bests,
> Sammi
>
> On Wed, 25 May 2022 at 00:05, Jerry Shao  wrote:
>
> > Hi all,
> >
> > Due to the name issue in thread (
> > https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f), we
> > figured out a new project name "Uniffle" and created a new Thread. Please
> > help to discuss.
> >
> > We would like to propose Uniffle[1] as a new Apache incubator project,
> you
> > can find the proposal here [2] for more details.
> >
> > Uniffle is a high performance, general purpose Remote Shuffle Service for
> > distributed compute engines like Apache Spark
> > , Apache
> > Hadoop MapReduce , Apache Flink
> >  and so on. We are aiming to make Firestorm a
> > universal shuffle service for distributed compute engines.
> >
> > Shuffle is the key part for a distributed compute engine to exchange the
> > data between distributed tasks, the performance and stability of shuffle
> > will directly affect the whole job. Current “local file pull-like shuffle
> > style” has several limitations:
> >
> >1. Current shuffle is hard to support super large workloads,
> especially
> >in a high load environment, the major problem is IO problem (random
> > disk IO
> >issue, network congestion and timeout).
> >2. Current shuffle is hard to deploy on the disaggregated compute
> >storage environment, as disk capacity is quite limited on compute
> nodes.
> >3. The constraint of storing shuffle data locally makes it hard to
> scale
> >elastically.
> >
> > Remote Shuffle Service is the key technology for enterprises to build big
> > data platforms, to expand big data applications to disaggregated,
> > online-offline hybrid environments, and to solve above problems.
> >
> > The implementation of Remote Shuffle Service -  “Uniffle”  - is heavily
> > adopted in Tencent, and shows its advantages in production. Other
> > enterprises also adopted or prepared to adopt Firestorm in their
> > environments.
> >
> > Uniffle's key idea is brought from Salfish shuffle
> > <
> >
> https://www.researchgate.net/publication/262241541_Sailfish_a_framework_for_large_scale_data_processing
> > >,
> > it has several key design goals:
> >
> >1. High performance. Firestorm’s performance is close enough to local
> >file based shuffle style for small workloads. For large workloads, it
> is
> >far better than the current shuffle style.
> >2. Fault tolerance. Firestorm provides high availability for
> Coordinated
> >nodes, and failover for Shuffle nodes.
> >3. Pluggable. Firestorm is highly pluggable, which could be suited to
> >different compute engines, different backend storages, and different
> >wire-protocols.
> >
> > We believe that Uniffle project will provide the great value for the
> > community if it is accepted by the Apache incubator.
> >
> > I will help this project as champion and many thanks to the 3 mentors:
> >
> >-
> >
> >Felix Cheung (felixche...@apache.org)
> >- Junping du (junping...@apache.org)
> >- Weiwei Yang (w...@apache.org)
> >- Xun liu (liu...@apache.org)
> >- Zhankun Tang (zt...@apache.org)
> >
> >
> > [1] https://github.com/Tencent/Firestorm
> > [2]
> https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal
> >
> > Best regards,
> > Jerry
> >
>
-- 



--Brahma Reddy Battula

Re: [DISCUSSION] Incubating Proposal of Uniffle

[Eason Chen]

+1 (non-binding)

Good luck!

On Wed, May 25, 2022 at 4:25 PM Sammi Chen  wrote:
>
> +1  (non-binding)
>
> Good luck to Uniffle.
>
> Bests,
> Sammi
>
> On Wed, 25 May 2022 at 00:05, Jerry Shao  wrote:
>
> > Hi all,
> >
> > Due to the name issue in thread (
> > https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f), we
> > figured out a new project name "Uniffle" and created a new Thread. Please
> > help to discuss.
> >
> > We would like to propose Uniffle[1] as a new Apache incubator project, you
> > can find the proposal here [2] for more details.
> >
> > Uniffle is a high performance, general purpose Remote Shuffle Service for
> > distributed compute engines like Apache Spark
> > , Apache
> > Hadoop MapReduce , Apache Flink
> >  and so on. We are aiming to make Firestorm a
> > universal shuffle service for distributed compute engines.
> >
> > Shuffle is the key part for a distributed compute engine to exchange the
> > data between distributed tasks, the performance and stability of shuffle
> > will directly affect the whole job. Current “local file pull-like shuffle
> > style” has several limitations:
> >
> >1. Current shuffle is hard to support super large workloads, especially
> >in a high load environment, the major problem is IO problem (random
> > disk IO
> >issue, network congestion and timeout).
> >2. Current shuffle is hard to deploy on the disaggregated compute
> >storage environment, as disk capacity is quite limited on compute nodes.
> >3. The constraint of storing shuffle data locally makes it hard to scale
> >elastically.
> >
> > Remote Shuffle Service is the key technology for enterprises to build big
> > data platforms, to expand big data applications to disaggregated,
> > online-offline hybrid environments, and to solve above problems.
> >
> > The implementation of Remote Shuffle Service -  “Uniffle”  - is heavily
> > adopted in Tencent, and shows its advantages in production. Other
> > enterprises also adopted or prepared to adopt Firestorm in their
> > environments.
> >
> > Uniffle's key idea is brought from Salfish shuffle
> > <
> > https://www.researchgate.net/publication/262241541_Sailfish_a_framework_for_large_scale_data_processing
> > >,
> > it has several key design goals:
> >
> >1. High performance. Firestorm’s performance is close enough to local
> >file based shuffle style for small workloads. For large workloads, it is
> >far better than the current shuffle style.
> >2. Fault tolerance. Firestorm provides high availability for Coordinated
> >nodes, and failover for Shuffle nodes.
> >3. Pluggable. Firestorm is highly pluggable, which could be suited to
> >different compute engines, different backend storages, and different
> >wire-protocols.
> >
> > We believe that Uniffle project will provide the great value for the
> > community if it is accepted by the Apache incubator.
> >
> > I will help this project as champion and many thanks to the 3 mentors:
> >
> >-
> >
> >Felix Cheung (felixche...@apache.org)
> >- Junping du (junping...@apache.org)
> >- Weiwei Yang (w...@apache.org)
> >- Xun liu (liu...@apache.org)
> >- Zhankun Tang (zt...@apache.org)
> >
> >
> > [1] https://github.com/Tencent/Firestorm
> > [2] https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal
> >
> > Best regards,
> > Jerry
> >

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

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

[Eason Chen]

+1 (no-binding)

Good luck!!

On Wed, May 25, 2022 at 4:27 PM Goson zhang  wrote:
>
> +1 (no-binding)
>
> Good luck!!
>
> tison  于2022年5月25日周三 16:18写道：
>
> > +1 (binding)
> >
> > Good luck!
> >
> > Best,
> > tison.
> >
> >
> > Jerry Shao  于2022年5月25日周三 16:12写道：
> >
> > > +1 (binding).
> > >
> > > Good luck to Inlong.
> > >
> > > Best
> > > Jerry
> > >
> > > 俊平堵  于2022年5月25日周三 14:50写道：
> > >
> > > > +1, good luck to InLong.:)
> > > >
> > > > Charles Zhang 于2022年5月25日 周三下午2:34写道：
> > > >
> > > > > Dear Apache Incubator Community,
> > > > >
> > > > >
> > > > > The InLong community has a discussion thread [1], passed the
> > community
> > > > vote
> > > > > [2], and the vote result is published [3]. We have discussed the
> > > > graduation
> > > > > for InLong in the Incubator Community [4], where no issues were
> > raised
> > > > and
> > > > > lots of positive responses were received.
> > > > >
> > > > >
> > > > > I would like to start this voting thread to request graduating Apache
> > > > > InLong (incubating) from the incubator as a TLP. Please provide your
> > > vote
> > > > > as one of the following options:
> > > > >
> > > > > [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> > > > >
> > > > > [ ] +0 No opinion.
> > > > >
> > > > > [ ] -1 No, the InLong project is not ready to graduate, because ...
> > > > >
> > > > >
> > > > > The VOTE will remain open for at least 72 hours.
> > > > >
> > > > >
> > > > > 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 [5].
> > > > >
> > > > >
> > > > > - 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 [6].
> > > > >
> > > > >
> > > > > - 101 unique code developers [7].
> > > > >
> > > > >
> > > > > - Closed more than 2200 issues, with an average of 200 issues per
> > > version
> > > > >
> > > > > [8].
> > > > >
> > > > >
> > > > > - All the dependencies were reviewed and ensured they do not bring
> > any
> > > > >
> > > > > license issues [9].
> > > > >
> > > > >
> > > > > - Evaluated the InLong project and self-checked the InLong maturity
> > > model
> > > > >
> > > > > [10] and the pre-graduation Check [11].
> > > > >
> > > > >
> > > > > - Well and Complete documentation for contributors and users [12].
> > > > >
> > > > >
> > > > > - 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
> > > > >
> > > > > [13].
> > > > >
> > > > >
> > > > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > > >
> > > > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > > >
> > > > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > > >
> > > > > [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> > > > >
> > > > > [5] https://inlong.apache.org/download/main/
> > > > >
> > > > > [6] https://whimsy.apache.org/roster/ppmc/inlong
> > > > >
> > > > > [7] https://github.com/apache/incubator-inlong/graphs/contributors
> > > > >
> > > > > [8]
> > > > >
> > > > >
> > > >
> > >
> > https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > > > >
> > > > > [9] https://github.com/apache/incubator-inlong/tree/master/licenses
> > > > >
> > > > > [10]
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > > > >
> > > > > [11]
> > > > >
> > > > >
> > > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > > > >
> > > > > [12] https://inlong.apache.org/docs/next/introduction
> > > > >
> > > > > [13]
> > 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
> > > > >

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

[Goson zhang]

+1 (no-binding)

Good luck!!

tison  于2022年5月25日周三 16:18写道：

> +1 (binding)
>
> Good luck!
>
> Best,
> tison.
>
>
> Jerry Shao  于2022年5月25日周三 16:12写道：
>
> > +1 (binding).
> >
> > Good luck to Inlong.
> >
> > Best
> > Jerry
> >
> > 俊平堵  于2022年5月25日周三 14:50写道：
> >
> > > +1, good luck to InLong.:)
> > >
> > > Charles Zhang 于2022年5月25日 周三下午2:34写道：
> > >
> > > > Dear Apache Incubator Community,
> > > >
> > > >
> > > > The InLong community has a discussion thread [1], passed the
> community
> > > vote
> > > > [2], and the vote result is published [3]. We have discussed the
> > > graduation
> > > > for InLong in the Incubator Community [4], where no issues were
> raised
> > > and
> > > > lots of positive responses were received.
> > > >
> > > >
> > > > I would like to start this voting thread to request graduating Apache
> > > > InLong (incubating) from the incubator as a TLP. Please provide your
> > vote
> > > > as one of the following options:
> > > >
> > > > [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> > > >
> > > > [ ] +0 No opinion.
> > > >
> > > > [ ] -1 No, the InLong project is not ready to graduate, because ...
> > > >
> > > >
> > > > The VOTE will remain open for at least 72 hours.
> > > >
> > > >
> > > > 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 [5].
> > > >
> > > >
> > > > - 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 [6].
> > > >
> > > >
> > > > - 101 unique code developers [7].
> > > >
> > > >
> > > > - Closed more than 2200 issues, with an average of 200 issues per
> > version
> > > >
> > > > [8].
> > > >
> > > >
> > > > - All the dependencies were reviewed and ensured they do not bring
> any
> > > >
> > > > license issues [9].
> > > >
> > > >
> > > > - Evaluated the InLong project and self-checked the InLong maturity
> > model
> > > >
> > > > [10] and the pre-graduation Check [11].
> > > >
> > > >
> > > > - Well and Complete documentation for contributors and users [12].
> > > >
> > > >
> > > > - 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
> > > >
> > > > [13].
> > > >
> > > >
> > > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > > >
> > > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > > >
> > > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > > >
> > > > [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> > > >
> > > > [5] https://inlong.apache.org/download/main/
> > > >
> > > > [6] https://whimsy.apache.org/roster/ppmc/inlong
> > > >
> > > > [7] https://github.com/apache/incubator-inlong/graphs/contributors
> > > >
> > > > [8]
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > > >
> > > > [9] https://github.com/apache/incubator-inlong/tree/master/licenses
> > > >
> > > > [10]
> > > >
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > > >
> > > > [11]
> > > >
> > > >
> > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > > >
> > > > [12] https://inlong.apache.org/docs/next/introduction
> > > >
> > > > [13]
> 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
> > > >
> > 

Re: [DISCUSSION] Incubating Proposal of Uniffle

[Sammi Chen]

+1  (non-binding)

Good luck to Uniffle.

Bests,
Sammi

On Wed, 25 May 2022 at 00:05, Jerry Shao  wrote:

> Hi all,
>
> Due to the name issue in thread (
> https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f), we
> figured out a new project name "Uniffle" and created a new Thread. Please
> help to discuss.
>
> We would like to propose Uniffle[1] as a new Apache incubator project, you
> can find the proposal here [2] for more details.
>
> Uniffle is a high performance, general purpose Remote Shuffle Service for
> distributed compute engines like Apache Spark
> , Apache
> Hadoop MapReduce , Apache Flink
>  and so on. We are aiming to make Firestorm a
> universal shuffle service for distributed compute engines.
>
> Shuffle is the key part for a distributed compute engine to exchange the
> data between distributed tasks, the performance and stability of shuffle
> will directly affect the whole job. Current “local file pull-like shuffle
> style” has several limitations:
>
>1. Current shuffle is hard to support super large workloads, especially
>in a high load environment, the major problem is IO problem (random
> disk IO
>issue, network congestion and timeout).
>2. Current shuffle is hard to deploy on the disaggregated compute
>storage environment, as disk capacity is quite limited on compute nodes.
>3. The constraint of storing shuffle data locally makes it hard to scale
>elastically.
>
> Remote Shuffle Service is the key technology for enterprises to build big
> data platforms, to expand big data applications to disaggregated,
> online-offline hybrid environments, and to solve above problems.
>
> The implementation of Remote Shuffle Service -  “Uniffle”  - is heavily
> adopted in Tencent, and shows its advantages in production. Other
> enterprises also adopted or prepared to adopt Firestorm in their
> environments.
>
> Uniffle's key idea is brought from Salfish shuffle
> <
> https://www.researchgate.net/publication/262241541_Sailfish_a_framework_for_large_scale_data_processing
> >,
> it has several key design goals:
>
>1. High performance. Firestorm’s performance is close enough to local
>file based shuffle style for small workloads. For large workloads, it is
>far better than the current shuffle style.
>2. Fault tolerance. Firestorm provides high availability for Coordinated
>nodes, and failover for Shuffle nodes.
>3. Pluggable. Firestorm is highly pluggable, which could be suited to
>different compute engines, different backend storages, and different
>wire-protocols.
>
> We believe that Uniffle project will provide the great value for the
> community if it is accepted by the Apache incubator.
>
> I will help this project as champion and many thanks to the 3 mentors:
>
>-
>
>Felix Cheung (felixche...@apache.org)
>- Junping du (junping...@apache.org)
>- Weiwei Yang (w...@apache.org)
>- Xun liu (liu...@apache.org)
>- Zhankun Tang (zt...@apache.org)
>
>
> [1] https://github.com/Tencent/Firestorm
> [2] https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal
>
> Best regards,
> Jerry
>

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

[谭中意]

+1 （no binding）
good luck

On Wed, May 25, 2022 at 2:27 PM Charles Zhang 
wrote:

>   Thanks,
> everyone, I think we have received enough feedback. I will close this
> discussion and prepare for the next vote process.
>
> Charles Zhang  于2022年5月24日周二 11:48写道：
>
> > Thank you all for participating in the discussion.  Sincerely remind you
> > that this discussion will be closed after 24 hours.
> >
> > Juan Pan  于2022年5月24日周二 10:57写道：
> >
> >> +1 binding, looks good.
> >>
> >>
> >>
> >>
> >>
> --
> >> Trista Pan
> >> Twitter & Github: tristaZero
> >>
> >>
> >>
> >>
> >> On 05/19/2022 17:09，Charles Zhang wrote：
> >> 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=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 

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

[tison]

+1 (binding)

Good luck!

Best,
tison.


Jerry Shao  于2022年5月25日周三 16:12写道：

> +1 (binding).
>
> Good luck to Inlong.
>
> Best
> Jerry
>
> 俊平堵  于2022年5月25日周三 14:50写道：
>
> > +1, good luck to InLong.:)
> >
> > Charles Zhang 于2022年5月25日 周三下午2:34写道：
> >
> > > Dear Apache Incubator Community,
> > >
> > >
> > > The InLong community has a discussion thread [1], passed the community
> > vote
> > > [2], and the vote result is published [3]. We have discussed the
> > graduation
> > > for InLong in the Incubator Community [4], where no issues were raised
> > and
> > > lots of positive responses were received.
> > >
> > >
> > > I would like to start this voting thread to request graduating Apache
> > > InLong (incubating) from the incubator as a TLP. Please provide your
> vote
> > > as one of the following options:
> > >
> > > [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> > >
> > > [ ] +0 No opinion.
> > >
> > > [ ] -1 No, the InLong project is not ready to graduate, because ...
> > >
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > >
> > > 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 [5].
> > >
> > >
> > > - 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 [6].
> > >
> > >
> > > - 101 unique code developers [7].
> > >
> > >
> > > - Closed more than 2200 issues, with an average of 200 issues per
> version
> > >
> > > [8].
> > >
> > >
> > > - All the dependencies were reviewed and ensured they do not bring any
> > >
> > > license issues [9].
> > >
> > >
> > > - Evaluated the InLong project and self-checked the InLong maturity
> model
> > >
> > > [10] and the pre-graduation Check [11].
> > >
> > >
> > > - Well and Complete documentation for contributors and users [12].
> > >
> > >
> > > - 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
> > >
> > > [13].
> > >
> > >
> > > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> > >
> > > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> > >
> > > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> > >
> > > [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> > >
> > > [5] https://inlong.apache.org/download/main/
> > >
> > > [6] https://whimsy.apache.org/roster/ppmc/inlong
> > >
> > > [7] https://github.com/apache/incubator-inlong/graphs/contributors
> > >
> > > [8]
> > >
> > >
> >
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> > >
> > > [9] https://github.com/apache/incubator-inlong/tree/master/licenses
> > >
> > > [10]
> > >
> > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> > >
> > > [11]
> > >
> > >
> https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> > >
> > > [12] https://inlong.apache.org/docs/next/introduction
> > >
> > > [13] 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; 

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

[Jerry Shao]

+1 (binding).

Good luck to Inlong.

Best
Jerry

俊平堵  于2022年5月25日周三 14:50写道：

> +1, good luck to InLong.:)
>
> Charles Zhang 于2022年5月25日 周三下午2:34写道：
>
> > Dear Apache Incubator Community,
> >
> >
> > The InLong community has a discussion thread [1], passed the community
> vote
> > [2], and the vote result is published [3]. We have discussed the
> graduation
> > for InLong in the Incubator Community [4], where no issues were raised
> and
> > lots of positive responses were received.
> >
> >
> > I would like to start this voting thread to request graduating Apache
> > InLong (incubating) from the incubator as a TLP. Please provide your vote
> > as one of the following options:
> >
> > [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> >
> > [ ] +0 No opinion.
> >
> > [ ] -1 No, the InLong project is not ready to graduate, because ...
> >
> >
> > The VOTE will remain open for at least 72 hours.
> >
> >
> > 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 [5].
> >
> >
> > - 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 [6].
> >
> >
> > - 101 unique code developers [7].
> >
> >
> > - Closed more than 2200 issues, with an average of 200 issues per version
> >
> > [8].
> >
> >
> > - All the dependencies were reviewed and ensured they do not bring any
> >
> > license issues [9].
> >
> >
> > - Evaluated the InLong project and self-checked the InLong maturity model
> >
> > [10] and the pre-graduation Check [11].
> >
> >
> > - Well and Complete documentation for contributors and users [12].
> >
> >
> > - 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
> >
> > [13].
> >
> >
> > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> >
> > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> >
> > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> >
> > [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> >
> > [5] https://inlong.apache.org/download/main/
> >
> > [6] https://whimsy.apache.org/roster/ppmc/inlong
> >
> > [7] https://github.com/apache/incubator-inlong/graphs/contributors
> >
> > [8]
> >
> >
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> >
> > [9] https://github.com/apache/incubator-inlong/tree/master/licenses
> >
> > [10]
> >
> >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> >
> > [11]
> >
> > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> >
> > [12] https://inlong.apache.org/docs/next/introduction
> >
> > [13] 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
> >
> > 

Re: [DISCUSSION] Incubating Proposal of Uniffle

[Jerry Shao]

Sorry for the copy-paste issue, +1 from my own side.

Best
Jerry

Heal Chow  于2022年5月25日周三 15:16写道：

> +1 (non-binding).
>
> Looking forward to the outstanding performance of the Uniffle on Shuffle.
> Good luck.
>
> Regards,
> HealChow
>
> On 2022/05/25 06:26:53 tison wrote:
> > +1 (binding)
> >
> > An interesting project. Good luck!
> >
> > Best,
> > tison.
> >
> >
> > Jungtaek Lim  于2022年5月25日周三 14:22写道：
> >
> > > +1 (non-binding)
> > >
> > > Good luck!
> > >
> > > On Wed, May 25, 2022 at 2:42 PM Daniel Widdis 
> wrote:
> > >
> > > > This was stated in the other thread: Unified/Universal Shuffle
> > > >
> > > > On 5/24/22, 10:04 PM, "XiaoYu"  wrote:
> > > >
> > > > Hi
> > > >
> > > > Uniffle  as a project name， What does he mean~
> > > >
> > > > thanks
> > > >
> > > > Weiwei Yang  于2022年5月25日周三 12:57写道：
> > > > >
> > > > > +1 (binding)
> > > > > Good luck!
> > > > >
> > > > > On Tue, May 24, 2022 at 8:49 PM Ye Xianjin <
> advance...@gmail.com>
> > > > wrote:
> > > > >
> > > > > > +1 (non-binding).
> > > > > >
> > > > > > Sent from my iPhone
> > > > > >
> > > > > > > On May 25, 2022, at 9:59 AM, Goson zhang <
> > > gosonzh...@apache.org>
> > > > wrote:
> > > > > > >
> > > > > > > +1 (non-binding)
> > > > > > >
> > > > > > > Good luck!
> > > > > > >
> > > > > > > Daniel Widdis  于2022年5月25日周三 09:53写道：
> > > > > > >
> > > > > > >> +1 (non-binding) from me!  Good luck!
> > > > > > >>
> > > > > > >> On 5/24/22, 9:05 AM, "Jerry Shao" 
> wrote:
> > > > > > >>
> > > > > > >>Hi all,
> > > > > > >>
> > > > > > >>Due to the name issue in thread (
> > > > > > >>
> > > > https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f),
> > > > > > we
> > > > > > >>figured out a new project name "Uniffle" and created a
> new
> > > > Thread.
> > > > > > >> Please
> > > > > > >>help to discuss.
> > > > > > >>
> > > > > > >>We would like to propose Uniffle[1] as a new Apache
> > > incubator
> > > > > > project,
> > > > > > >> you
> > > > > > >>can find the proposal here [2] for more details.
> > > > > > >>
> > > > > > >>Uniffle is a high performance, general purpose Remote
> > > > Shuffle Service
> > > > > > >> for
> > > > > > >>distributed compute engines like Apache Spark
> > > > > > >>, Apache
> > > > > > >>Hadoop MapReduce , Apache
> > > Flink
> > > > > > >> and so on. We are aiming
> to
> > > make
> > > > > > >> Firestorm a
> > > > > > >>universal shuffle service for distributed compute
> engines.
> > > > > > >>
> > > > > > >>Shuffle is the key part for a distributed compute
> engine to
> > > > exchange
> > > > > > >> the
> > > > > > >>data between distributed tasks, the performance and
> > > > stability of
> > > > > > >> shuffle
> > > > > > >>will directly affect the whole job. Current “local file
> > > > pull-like
> > > > > > >> shuffle
> > > > > > >>style” has several limitations:
> > > > > > >>
> > > > > > >>   1. Current shuffle is hard to support super large
> > > > workloads,
> > > > > > >> especially
> > > > > > >>   in a high load environment, the major problem is IO
> > > > problem
> > > > > > (random
> > > > > > >> disk IO
> > > > > > >>   issue, network congestion and timeout).
> > > > > > >>   2. Current shuffle is hard to deploy on the
> > > disaggregated
> > > > compute
> > > > > > >>   storage environment, as disk capacity is quite
> limited
> > > on
> > > > compute
> > > > > > >> nodes.
> > > > > > >>   3. The constraint of storing shuffle data locally
> makes
> > > > it hard to
> > > > > > >> scale
> > > > > > >>   elastically.
> > > > > > >>
> > > > > > >>Remote Shuffle Service is the key technology for
> > > enterprises
> > > > to build
> > > > > > >> big
> > > > > > >>data platforms, to expand big data applications to
> > > > disaggregated,
> > > > > > >>online-offline hybrid environments, and to solve above
> > > > problems.
> > > > > > >>
> > > > > > >>The implementation of Remote Shuffle Service -
> “Uniffle”
> > > -
> > > > is
> > > > > > heavily
> > > > > > >>adopted in Tencent, and shows its advantages in
> production.
> > > > Other
> > > > > > >>enterprises also adopted or prepared to adopt
> Firestorm in
> > > > their
> > > > > > >>environments.
> > > > > > >>
> > > > > > >>Uniffle's key idea is brought from Salfish shuffle
> > > > > > >><
> > > > > > >>
> > > > > >
> > > >
> > >
> https://www.researchgate.net/publication/262241541_Sailfish_a_framework_for_large_scale_data_processing
> > > > > > >>> ,
> > > > > > >>it has several 

Re: [DISCUSSION] Incubating Proposal of Uniffle

[Heal Chow]

+1 (non-binding).

Looking forward to the outstanding performance of the Uniffle on Shuffle. Good 
luck.

Regards,
HealChow

On 2022/05/25 06:26:53 tison wrote:
> +1 (binding)
> 
> An interesting project. Good luck!
> 
> Best,
> tison.
> 
> 
> Jungtaek Lim  于2022年5月25日周三 14:22写道：
> 
> > +1 (non-binding)
> >
> > Good luck!
> >
> > On Wed, May 25, 2022 at 2:42 PM Daniel Widdis  wrote:
> >
> > > This was stated in the other thread: Unified/Universal Shuffle
> > >
> > > On 5/24/22, 10:04 PM, "XiaoYu"  wrote:
> > >
> > > Hi
> > >
> > > Uniffle  as a project name， What does he mean~
> > >
> > > thanks
> > >
> > > Weiwei Yang  于2022年5月25日周三 12:57写道：
> > > >
> > > > +1 (binding)
> > > > Good luck!
> > > >
> > > > On Tue, May 24, 2022 at 8:49 PM Ye Xianjin 
> > > wrote:
> > > >
> > > > > +1 (non-binding).
> > > > >
> > > > > Sent from my iPhone
> > > > >
> > > > > > On May 25, 2022, at 9:59 AM, Goson zhang <
> > gosonzh...@apache.org>
> > > wrote:
> > > > > >
> > > > > > +1 (non-binding)
> > > > > >
> > > > > > Good luck!
> > > > > >
> > > > > > Daniel Widdis  于2022年5月25日周三 09:53写道：
> > > > > >
> > > > > >> +1 (non-binding) from me!  Good luck!
> > > > > >>
> > > > > >> On 5/24/22, 9:05 AM, "Jerry Shao"  wrote:
> > > > > >>
> > > > > >>Hi all,
> > > > > >>
> > > > > >>Due to the name issue in thread (
> > > > > >>
> > > https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f),
> > > > > we
> > > > > >>figured out a new project name "Uniffle" and created a new
> > > Thread.
> > > > > >> Please
> > > > > >>help to discuss.
> > > > > >>
> > > > > >>We would like to propose Uniffle[1] as a new Apache
> > incubator
> > > > > project,
> > > > > >> you
> > > > > >>can find the proposal here [2] for more details.
> > > > > >>
> > > > > >>Uniffle is a high performance, general purpose Remote
> > > Shuffle Service
> > > > > >> for
> > > > > >>distributed compute engines like Apache Spark
> > > > > >>, Apache
> > > > > >>Hadoop MapReduce , Apache
> > Flink
> > > > > >> and so on. We are aiming to
> > make
> > > > > >> Firestorm a
> > > > > >>universal shuffle service for distributed compute engines.
> > > > > >>
> > > > > >>Shuffle is the key part for a distributed compute engine to
> > > exchange
> > > > > >> the
> > > > > >>data between distributed tasks, the performance and
> > > stability of
> > > > > >> shuffle
> > > > > >>will directly affect the whole job. Current “local file
> > > pull-like
> > > > > >> shuffle
> > > > > >>style” has several limitations:
> > > > > >>
> > > > > >>   1. Current shuffle is hard to support super large
> > > workloads,
> > > > > >> especially
> > > > > >>   in a high load environment, the major problem is IO
> > > problem
> > > > > (random
> > > > > >> disk IO
> > > > > >>   issue, network congestion and timeout).
> > > > > >>   2. Current shuffle is hard to deploy on the
> > disaggregated
> > > compute
> > > > > >>   storage environment, as disk capacity is quite limited
> > on
> > > compute
> > > > > >> nodes.
> > > > > >>   3. The constraint of storing shuffle data locally makes
> > > it hard to
> > > > > >> scale
> > > > > >>   elastically.
> > > > > >>
> > > > > >>Remote Shuffle Service is the key technology for
> > enterprises
> > > to build
> > > > > >> big
> > > > > >>data platforms, to expand big data applications to
> > > disaggregated,
> > > > > >>online-offline hybrid environments, and to solve above
> > > problems.
> > > > > >>
> > > > > >>The implementation of Remote Shuffle Service -  “Uniffle”
> > -
> > > is
> > > > > heavily
> > > > > >>adopted in Tencent, and shows its advantages in production.
> > > Other
> > > > > >>enterprises also adopted or prepared to adopt Firestorm in
> > > their
> > > > > >>environments.
> > > > > >>
> > > > > >>Uniffle's key idea is brought from Salfish shuffle
> > > > > >><
> > > > > >>
> > > > >
> > >
> > https://www.researchgate.net/publication/262241541_Sailfish_a_framework_for_large_scale_data_processing
> > > > > >>> ,
> > > > > >>it has several key design goals:
> > > > > >>
> > > > > >>   1. High performance. Firestorm’s performance is close
> > > enough to
> > > > > >> local
> > > > > >>   file based shuffle style for small workloads. For large
> > > workloads,
> > > > > >> it is
> > > > > >>   far better than the current shuffle style.
> > > > > >>   2. Fault tolerance. Firestorm provides high availability
> > > for
> > > > 

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

[俊平堵]

+1, good luck to InLong.:)

Charles Zhang 于2022年5月25日 周三下午2:34写道：

> Dear Apache Incubator Community,
>
>
> The InLong community has a discussion thread [1], passed the community vote
> [2], and the vote result is published [3]. We have discussed the graduation
> for InLong in the Incubator Community [4], where no issues were raised and
> lots of positive responses were received.
>
>
> I would like to start this voting thread to request graduating Apache
> InLong (incubating) from the incubator as a TLP. Please provide your vote
> as one of the following options:
>
> [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
>
> [ ] +0 No opinion.
>
> [ ] -1 No, the InLong project is not ready to graduate, because ...
>
>
> The VOTE will remain open for at least 72 hours.
>
>
> 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 [5].
>
>
> - 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 [6].
>
>
> - 101 unique code developers [7].
>
>
> - Closed more than 2200 issues, with an average of 200 issues per version
>
> [8].
>
>
> - All the dependencies were reviewed and ensured they do not bring any
>
> license issues [9].
>
>
> - Evaluated the InLong project and self-checked the InLong maturity model
>
> [10] and the pre-graduation Check [11].
>
>
> - Well and Complete documentation for contributors and users [12].
>
>
> - 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
>
> [13].
>
>
> [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
>
> [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
>
> [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
>
> [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
>
> [5] https://inlong.apache.org/download/main/
>
> [6] https://whimsy.apache.org/roster/ppmc/inlong
>
> [7] https://github.com/apache/incubator-inlong/graphs/contributors
>
> [8]
>
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
>
> [9] https://github.com/apache/incubator-inlong/tree/master/licenses
>
> [10]
>
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
>
> [11]
>
> https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
>
> [12] https://inlong.apache.org/docs/next/introduction
>
> [13] 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 

[VOTE] Graduate Apache InLong(Incubating) as a TLP

[Charles Zhang]

Dear Apache Incubator Community,


The InLong community has a discussion thread [1], passed the community vote
[2], and the vote result is published [3]. We have discussed the graduation
for InLong in the Incubator Community [4], where no issues were raised and
lots of positive responses were received.


I would like to start this voting thread to request graduating Apache
InLong (incubating) from the incubator as a TLP. Please provide your vote
as one of the following options:

[ ] +1 Yes, I support InLong to graduate from the Apache incubator.

[ ] +0 No opinion.

[ ] -1 No, the InLong project is not ready to graduate, because ...


The VOTE will remain open for at least 72 hours.


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 [5].


- 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 [6].


- 101 unique code developers [7].


- Closed more than 2200 issues, with an average of 200 issues per version

[8].


- All the dependencies were reviewed and ensured they do not bring any

license issues [9].


- Evaluated the InLong project and self-checked the InLong maturity model

[10] and the pre-graduation Check [11].


- Well and Complete documentation for contributors and users [12].


- 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

[13].


[1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro

[2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20

[3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9

[4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t

[5] https://inlong.apache.org/download/main/

[6] https://whimsy.apache.org/roster/ppmc/inlong

[7] https://github.com/apache/incubator-inlong/graphs/contributors

[8]

https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed

[9] https://github.com/apache/incubator-inlong/tree/master/licenses

[10]

https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong

[11]

https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List

[12] https://inlong.apache.org/docs/next/introduction

[13] 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 persons listed immediately below be and hereby are

appointed to serve as the initial members of the Apache InLong Project:


* Aloys Zhang 

* Charles Zhang 

* Guangxu Cheng 

* Guocheng Zhang 

* Heal Chow 

* Jean-Baptiste 

Re: [DISCUSSION] Incubating Proposal of Uniffle

[tison]

+1 (binding)

An interesting project. Good luck!

Best,
tison.


Jungtaek Lim  于2022年5月25日周三 14:22写道：

> +1 (non-binding)
>
> Good luck!
>
> On Wed, May 25, 2022 at 2:42 PM Daniel Widdis  wrote:
>
> > This was stated in the other thread: Unified/Universal Shuffle
> >
> > On 5/24/22, 10:04 PM, "XiaoYu"  wrote:
> >
> > Hi
> >
> > Uniffle  as a project name， What does he mean~
> >
> > thanks
> >
> > Weiwei Yang  于2022年5月25日周三 12:57写道：
> > >
> > > +1 (binding)
> > > Good luck!
> > >
> > > On Tue, May 24, 2022 at 8:49 PM Ye Xianjin 
> > wrote:
> > >
> > > > +1 (non-binding).
> > > >
> > > > Sent from my iPhone
> > > >
> > > > > On May 25, 2022, at 9:59 AM, Goson zhang <
> gosonzh...@apache.org>
> > wrote:
> > > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > Good luck!
> > > > >
> > > > > Daniel Widdis  于2022年5月25日周三 09:53写道：
> > > > >
> > > > >> +1 (non-binding) from me!  Good luck!
> > > > >>
> > > > >> On 5/24/22, 9:05 AM, "Jerry Shao"  wrote:
> > > > >>
> > > > >>Hi all,
> > > > >>
> > > > >>Due to the name issue in thread (
> > > > >>
> > https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f),
> > > > we
> > > > >>figured out a new project name "Uniffle" and created a new
> > Thread.
> > > > >> Please
> > > > >>help to discuss.
> > > > >>
> > > > >>We would like to propose Uniffle[1] as a new Apache
> incubator
> > > > project,
> > > > >> you
> > > > >>can find the proposal here [2] for more details.
> > > > >>
> > > > >>Uniffle is a high performance, general purpose Remote
> > Shuffle Service
> > > > >> for
> > > > >>distributed compute engines like Apache Spark
> > > > >>, Apache
> > > > >>Hadoop MapReduce , Apache
> Flink
> > > > >> and so on. We are aiming to
> make
> > > > >> Firestorm a
> > > > >>universal shuffle service for distributed compute engines.
> > > > >>
> > > > >>Shuffle is the key part for a distributed compute engine to
> > exchange
> > > > >> the
> > > > >>data between distributed tasks, the performance and
> > stability of
> > > > >> shuffle
> > > > >>will directly affect the whole job. Current “local file
> > pull-like
> > > > >> shuffle
> > > > >>style” has several limitations:
> > > > >>
> > > > >>   1. Current shuffle is hard to support super large
> > workloads,
> > > > >> especially
> > > > >>   in a high load environment, the major problem is IO
> > problem
> > > > (random
> > > > >> disk IO
> > > > >>   issue, network congestion and timeout).
> > > > >>   2. Current shuffle is hard to deploy on the
> disaggregated
> > compute
> > > > >>   storage environment, as disk capacity is quite limited
> on
> > compute
> > > > >> nodes.
> > > > >>   3. The constraint of storing shuffle data locally makes
> > it hard to
> > > > >> scale
> > > > >>   elastically.
> > > > >>
> > > > >>Remote Shuffle Service is the key technology for
> enterprises
> > to build
> > > > >> big
> > > > >>data platforms, to expand big data applications to
> > disaggregated,
> > > > >>online-offline hybrid environments, and to solve above
> > problems.
> > > > >>
> > > > >>The implementation of Remote Shuffle Service -  “Uniffle”
> -
> > is
> > > > heavily
> > > > >>adopted in Tencent, and shows its advantages in production.
> > Other
> > > > >>enterprises also adopted or prepared to adopt Firestorm in
> > their
> > > > >>environments.
> > > > >>
> > > > >>Uniffle's key idea is brought from Salfish shuffle
> > > > >><
> > > > >>
> > > >
> >
> https://www.researchgate.net/publication/262241541_Sailfish_a_framework_for_large_scale_data_processing
> > > > >>> ,
> > > > >>it has several key design goals:
> > > > >>
> > > > >>   1. High performance. Firestorm’s performance is close
> > enough to
> > > > >> local
> > > > >>   file based shuffle style for small workloads. For large
> > workloads,
> > > > >> it is
> > > > >>   far better than the current shuffle style.
> > > > >>   2. Fault tolerance. Firestorm provides high availability
> > for
> > > > >> Coordinated
> > > > >>   nodes, and failover for Shuffle nodes.
> > > > >>   3. Pluggable. Firestorm is highly pluggable, which could
> > be suited
> > > > >> to
> > > > >>   different compute engines, different backend storages,
> and
> > > > different
> > > > >>   wire-protocols.
> > > > >>
> > > > >>We believe that Uniffle project will provide the great
> value
> > for the
> > > > >>

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

[Charles Zhang]

  Thanks,
everyone, I think we have received enough feedback. I will close this
discussion and prepare for the next vote process.

Charles Zhang  于2022年5月24日周二 11:48写道：

> Thank you all for participating in the discussion.  Sincerely remind you
> that this discussion will be closed after 24 hours.
>
> Juan Pan  于2022年5月24日周二 10:57写道：
>
>> +1 binding, looks good.
>>
>>
>>
>>
>> --
>> Trista Pan
>> Twitter & Github: tristaZero
>>
>>
>>
>>
>> On 05/19/2022 17:09，Charles Zhang wrote：
>> 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=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 

Re: [DISCUSSION] Incubating Proposal of Uniffle

[Jungtaek Lim]

+1 (non-binding)

Good luck!

On Wed, May 25, 2022 at 2:42 PM Daniel Widdis  wrote:

> This was stated in the other thread: Unified/Universal Shuffle
>
> On 5/24/22, 10:04 PM, "XiaoYu"  wrote:
>
> Hi
>
> Uniffle  as a project name， What does he mean~
>
> thanks
>
> Weiwei Yang  于2022年5月25日周三 12:57写道：
> >
> > +1 (binding)
> > Good luck!
> >
> > On Tue, May 24, 2022 at 8:49 PM Ye Xianjin 
> wrote:
> >
> > > +1 (non-binding).
> > >
> > > Sent from my iPhone
> > >
> > > > On May 25, 2022, at 9:59 AM, Goson zhang 
> wrote:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > Good luck!
> > > >
> > > > Daniel Widdis  于2022年5月25日周三 09:53写道：
> > > >
> > > >> +1 (non-binding) from me!  Good luck!
> > > >>
> > > >> On 5/24/22, 9:05 AM, "Jerry Shao"  wrote:
> > > >>
> > > >>Hi all,
> > > >>
> > > >>Due to the name issue in thread (
> > > >>
> https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f),
> > > we
> > > >>figured out a new project name "Uniffle" and created a new
> Thread.
> > > >> Please
> > > >>help to discuss.
> > > >>
> > > >>We would like to propose Uniffle[1] as a new Apache incubator
> > > project,
> > > >> you
> > > >>can find the proposal here [2] for more details.
> > > >>
> > > >>Uniffle is a high performance, general purpose Remote
> Shuffle Service
> > > >> for
> > > >>distributed compute engines like Apache Spark
> > > >>, Apache
> > > >>Hadoop MapReduce , Apache Flink
> > > >> and so on. We are aiming to make
> > > >> Firestorm a
> > > >>universal shuffle service for distributed compute engines.
> > > >>
> > > >>Shuffle is the key part for a distributed compute engine to
> exchange
> > > >> the
> > > >>data between distributed tasks, the performance and
> stability of
> > > >> shuffle
> > > >>will directly affect the whole job. Current “local file
> pull-like
> > > >> shuffle
> > > >>style” has several limitations:
> > > >>
> > > >>   1. Current shuffle is hard to support super large
> workloads,
> > > >> especially
> > > >>   in a high load environment, the major problem is IO
> problem
> > > (random
> > > >> disk IO
> > > >>   issue, network congestion and timeout).
> > > >>   2. Current shuffle is hard to deploy on the disaggregated
> compute
> > > >>   storage environment, as disk capacity is quite limited on
> compute
> > > >> nodes.
> > > >>   3. The constraint of storing shuffle data locally makes
> it hard to
> > > >> scale
> > > >>   elastically.
> > > >>
> > > >>Remote Shuffle Service is the key technology for enterprises
> to build
> > > >> big
> > > >>data platforms, to expand big data applications to
> disaggregated,
> > > >>online-offline hybrid environments, and to solve above
> problems.
> > > >>
> > > >>The implementation of Remote Shuffle Service -  “Uniffle”  -
> is
> > > heavily
> > > >>adopted in Tencent, and shows its advantages in production.
> Other
> > > >>enterprises also adopted or prepared to adopt Firestorm in
> their
> > > >>environments.
> > > >>
> > > >>Uniffle's key idea is brought from Salfish shuffle
> > > >><
> > > >>
> > >
> https://www.researchgate.net/publication/262241541_Sailfish_a_framework_for_large_scale_data_processing
> > > >>> ,
> > > >>it has several key design goals:
> > > >>
> > > >>   1. High performance. Firestorm’s performance is close
> enough to
> > > >> local
> > > >>   file based shuffle style for small workloads. For large
> workloads,
> > > >> it is
> > > >>   far better than the current shuffle style.
> > > >>   2. Fault tolerance. Firestorm provides high availability
> for
> > > >> Coordinated
> > > >>   nodes, and failover for Shuffle nodes.
> > > >>   3. Pluggable. Firestorm is highly pluggable, which could
> be suited
> > > >> to
> > > >>   different compute engines, different backend storages, and
> > > different
> > > >>   wire-protocols.
> > > >>
> > > >>We believe that Uniffle project will provide the great value
> for the
> > > >>community if it is accepted by the Apache incubator.
> > > >>
> > > >>I will help this project as champion and many thanks to the 3
> > > mentors:
> > > >>
> > > >>   -
> > > >>
> > > >>   Felix Cheung (felixche...@apache.org)
> > > >>   - Junping du (junping...@apache.org)
> > > >>   - Weiwei Yang (w...@apache.org)
> > > >>   - Xun liu (liu...@apache.org)
> > > >>