Re: [VOTE] Accept Gravitino into the ASF Incubator

[Jerry Shao]

+1 (binding)

Jerry Shao

Rui Fan  于2024年5月31日周五 13:03写道：

> +1 (non-binding)
>
> Rui Fan
>
> On Fri, May 31, 2024 at 12:02 PM ShaoFeng Shi 
> wrote:
>
> > +1 (binding)
> >
> > Best regards,
> >
> > Shaofeng Shi 史少锋
> > Apache Kylin PMC member,
> > Apache Incubator PMC member,
> > Email: shaofeng...@apache.org
> >
> >
> >
> >
> >
> >
> > Willem Jiang  于2024年5月31日周五 02:33写道：
> >
> > > +1 (binding)
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Wed, May 29, 2024 at 5:32 PM Jean-Baptiste Onofré 
> > > wrote:
> > > >
> > > > Hi folks,
> > > >
> > > > Following the discussion about Gravitino [1], I would like to start
> > > > the formal vote to accept Gravitino into the ASF Incubator.
> > > >
> > > >  As reminder, this is the Gravitino Proposal:
> > > >
> > > > Please cast your vote:
> > > >
> > > > [ ] +1, accept Gravitino into the ASF Incubator
> > > > [ ] 0, I don't care either way
> > > > [ ] -1, do not accept Gravitino into the ASF Incubator, because ...
> > > >
> > > > The vote will run for one week starting from today.
> > > >
> > > > Thanks !
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > -
> > > > 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: [VOTE] Graduate Apache Linkis(incubating) as an Apache Top Level Project

[Jerry Shao]

per
> > > applications and the underlying data engines.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > (PMC), to be known as the "Apache Linkis Project", be and hereby is
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache Linkis Project be and hereby is responsible
> > > for the creation and maintenance of software related to a computation
> > > middleware to facilitate connection, governance and orchestration
> > > between the upper applications and the underlying data engines; and be
> > > it further
> > >
> > > RESOLVED, that the office of "Vice President, Apache Linkis" 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 Linkis
> > > Project, and to have primary responsibility for management of the
> > > projects within the scope of responsibility of the Apache Linkis
> > > 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 Linkis
> > > Project:
> > >
> > >  ●  Alex Young 
> > >  ●  Deyi Hua 
> > >  ●  Duo Zhang 
> > >  ●  HuaJin Zhang 
> > >  ●  Hui Zhu 
> > >  ●  Jacky Xie 
> > >  ●  Jerry Shao 
> > >  ●  Junping Du 
> > >  ●  Ke Zhou 
> > >  ●  Kelu Tao 
> > >  ●  Le Bai 
> > >  ●  Lidong Dai 
> > >  ●  Ling Xu 
> > >  ●  Longping Jie 
> > >  ●  Peacewong 
> > >  ●  Qiang Yin 
> > >  ●  Rong Zhang 
> > >  ●  Shao Feng Shi 
> > >  ●  Shuai Di 
> > >  ●  Xiaogang Wang 
> > >  ●  Xiaohua Yi 
> > >  ●  Zhen Wang 
> > >  ●  Zhiyue Yang 
> > >
> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Shuai Di be appointed to
> > > the office of Vice President, Apache Linkis, to serve in accordance
> > > with and subject to the direction of the Board of Directors and the
> > > Bylaws of the Foundation until death, resignation, retirement, removal
> > > or disqualification, or until a successor is appointed; and be it
> > > further
> > >
> > > RESOLVED, that the Apache Linkis Project be and hereby is tasked with
> > > the migration and rationalization of the Apache Incubator Linkis
> > > podling; and be it further
> > >
> > > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > > Linkis podling encumbered upon the Apache Incubator PMC are hereafter
> > > discharged.
> > >
> > > --
> > > END OF DRAFT RESOLUTION
> > > --
> > >
> > > [1] https://lists.apache.org/thread/yvps9rwx8y1660t12o6034hczj05ko5o
> > > [2] https://lists.apache.org/thread/sc8vj2hqrsj6c1gp97n6x8hkscxo8pyj
> > > [3] https://lists.apache.org/thread/tnp165hs0k9rvntqz2f025sxsjlk6xsf
> > > [4] https://lists.apache.org/thread/7ovjddrpywg5yr97bqtc0ds0jffjztsx
> > > [5] https://cwiki.apache.org/confluence/display/LINKIS/Meetings
> > > [6] https://lists.apache.org/list.html?d...@linkis.apache.org
> > > [7] https://lists.apache.org/thread/m3ny1rwstr38do65ltcqyt4nl9mzhwdj
> > > [8]
> https://github.com/apache/incubator-linkis-website/blob/dev/maturity.md
> > > [9]
> https://cwiki.apache.org/confluence/display/INCUBATOR/LinkisProposal
> > > [10] https://github.com/apache/incubator-linkis/releases
> > > [11] https://github.com/apache/incubator-linkis/pulls and
> > > https://github.com/apache/incubator-linkis-website/pulls
> > > [12] https://github.com/apache/incubator-linkis/issues and
> > > https://github.com/apache/incubator-linkis-website/issues
> > > [13] https://incubator.apache.org/projects/linkis.html
> > > [14] https://incubator.apache.org/clutch/
> > > [15] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-192
> > > [16] https://github.com/apache/incubator-linkis/blob/master/LICENSE
> > > [17] https://linkis.apache.org/
> > > [18] https://whimsy.apache.org/pods/project/linkis
> > >
> > > Best regards,
> > > Shuai Di
> > >
> > > -
> > > 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
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Uniffle (incubating) 0.6.0 rc2

[Jerry Shao]

+1 (binding)

I checked:
- incubating is in the name
- hash and signatures are good
- LICENSE, NOTICE, DISCLAIMER-WIP look good
- ASF headers are present on source
- No binary files in the source distribution
- I built without problem (mvn clean install)

Thanks
Jerry

Jean-Baptiste Onofré  于2022年10月18日周二 14:33写道：

> +1 (binding)
>
> I checked:
> - incubating is in the name
> - hash and signatures are good
> - LICENSE, NOTICE, DISCLAIMER-WIP look good
> - ASF headers are present on source
> - No binary files in the source distribution
> - I built without problem (mvn clean install)
>
> Regards
> JB
>
> On Tue, Oct 18, 2022 at 5:06 AM roryqi  wrote:
> >
> > Hello Incubator Community,
> >This is a call for a vote to release Apache Uniffle (incubating)
> > version 0.6.0 rc2
> >The Apache Uniffle community has voted on and approved a proposal
> to
> > release Apache Uniffle (incubating) version 0.6.0 rc2
> > We now kindly request the Incubator PMC members review and vote
> on
> > this incubator release.
> >
> >  Uniffle community vote thread:
> >
> > https://lists.apache.org/thread/snhnx8hyzn1ogxjpxh3fh13jy1vl2d50
> >
> >  Vote result thread:
> >
> > https://lists.apache.org/thread/7ykhjdbn8dr16bmxgfp8c351rh3oyz5y
> >
> >  The release candidate:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.6.0-rc2/
> >
> >  Git tag for the release:
> >
> > https://github.com/apache/incubator-uniffle/commits/v0.6.0-rc2
> >
> >   The artifacts signed with PGP
> > key 95757CB677E6B5FA46C1760D0803111904129129 , corresponding to
> > ror...@apache.org, that can be found in key files:
> > https://downloads.apache.org/incubator/uniffle/KEYS
> >
> >Please vote accordingly:
> >
> >[ ] +1 approve
> >[ ] +0 no opinion
> >[ ] -1 disapprove with the reason
> >
> >More detail checklist  please refer:
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> >   Steps to validate the release, Please refer to:
> > https://linkis.apache.org/community/how-to-verify
> >
> > Thanks,
> > On behalf of Apache Uniffle (incubating) community
>

Re: [VOTE] Accept Uniffle into the Apache Incubator

[Jerry Shao]

Hi all,

Thanks everyone for your vote, greatly appreciated.
The vote now is closed, and it has passed with 11 binding +1, 12
non-binding + 1, no 0 and -1.

Binding votes:
tison, Xun Liu, Weiwei Yang, Devaraj Das, Justin Mclean, Willem Jiang,
Furkan Kamaci, Zhangkun Tang, Junping Du, Felix Cheung, Sunil Govindan.

Non-binding votes:
Goson Zhang, XiaoYu, Aloys Zhang, Xianjin Ye, Shui Di, Alexander
Alten-Lorenz, Yonglun Zhang, Eason Chen, Gang Li, Sammi Chen, Young Seung
Andrew Ko, Brahma Reddy Battula.

Best regards,
Jerry



Sunil Govindan  于2022年6月2日周四 10:05写道：

> +1 (binding)
>
> All the best!
>
> + Sunil
>
> On Mon, May 30, 2022 at 6:37 PM Jerry Shao  wrote:
>
> > Hi all,
> >
> > Following up the [DISCUSS] thread on Uniffle[1] and Firestorm[2], I would
> > like to
> > call a VOTE to accept Uniffle into the Apache Incubator, please check out
> > the Uniffle Proposal from the incubator wiki[3].
> >
> > Please cast your vote:
> >
> > [ ] +1, bring Uniffle into the Incubator
> > [ ] +0, I don't care either way
> > [ ] -1, do not bring Uniffle into the Incubator, because...
> >
> > The vote will open at least for 72 hours, and only votes from the
> > Incubator PMC are binding, but votes from everyone are welcome.
> >
> > [1] https://lists.apache.org/thread/fyyhkjvhzl4hpzr52hd64csh5lt2wm6h
> > [2] https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f
> > [3]
> https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal
> >
> > Best regards,
> > Jerry
> >
>

[VOTE] Accept Uniffle into the Apache Incubator

[Jerry Shao]

Hi all,

Following up the [DISCUSS] thread on Uniffle[1] and Firestorm[2], I would
like to
call a VOTE to accept Uniffle into the Apache Incubator, please check out
the Uniffle Proposal from the incubator wiki[3].

Please cast your vote:

[ ] +1, bring Uniffle into the Incubator
[ ] +0, I don't care either way
[ ] -1, do not bring Uniffle into the Incubator, because...

The vote will open at least for 72 hours, and only votes from the
Incubator PMC are binding, but votes from everyone are welcome.

[1] https://lists.apache.org/thread/fyyhkjvhzl4hpzr52hd64csh5lt2wm6h
[2] https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f
[3] https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal

Best regards,
Jerry

Re: [DISCUSSION] Incubating Proposal of Uniffle

[Jerry Shao]

Hi all,

Thanks a lot for your suggestions and supports. This thread is opened for
almost 7 days, I'm going to close it and create a new vote thread.

Thanks
Jerry

Aloys Zhang  于2022年5月27日周五 06:29写道：

> +1 (non-binding) good luck
>
> Zhang Yonglun  于2022年5月26日周四 20:52写道：
>
> > +1 (non-binding)
> >
> > --
> >
> > Zhang Yonglun
> > Apache ShenYu (Incubating)
> > Apache ShardingSphere
> >
> > Jerry Shao  于2022年5月25日周三 00:07写道：
> > >
> > > 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
> > > <https://spark.apache.org/>, Apache
> > > Hadoop MapReduce <https://hadoop.apache.org/>, Apache Flink
> > > <https://flink.apache.org/> 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

[Jerry Shao]

g
> >
> > 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 Onofré 
> >
> > * Jerry Shao 
> >
> > * Junjie Chen 
> >
> > * Junping Du 
> >
> > * Justin Mclean 
> >
> > * Lamber Liu 
> >
> > * Osgoo Li 
> >
> > * Peng Chen 
> >
> > * Zak Wu 
> >
> > * ZhongBo Wu 
> >
> > * Zili Chen 
> >
> > * Daniel Li 
> >
> > * Guo Jiwei 
> >
> > * Haiji Li 
> >
> > * Lizhen 
> >
> > * Yuanbo Liu 
> >
> > * Yuanhao Ji 
> >
> > * Zijie Lu 
> >
> > * Zirui Peng 
> >
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Charles Zhang be appointed
> >
> > to the office of Vice President, Apache InLong, to serve in accordance
> >
> > with and subject to the direction of the Board of Directors and the
> >
> > Bylaws of the Foundation until death, resignation, retirement, removal
> >
> > or disqualification, or until a successor is appointed; and be it
> >
> > further
> >
> > RESOLVED, that the Apache InLong Project be and hereby is tasked with
> >
> > the migration and rationalization of the Apache Incubator InLong
> >
> > podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> >
> > InLong podling encumbered upon the Apache Incubator PMC are hereafter
> >
> > discharged.
> >
> > --
> > Best wishes,
> > Charles Zhang
> >
>

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
> > > > > > >><https://spark.apache.org/>, Apache
> > > > > > >>Hadoop MapReduce <https://hadoop.apache.org/>, Apache
> > > Flink
> > > > > > >><https://flink.apache.org/> 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,
>

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Jerry Shao]

Hi all,

I'm going to close this thread and create a new proposal thread (
https://lists.apache.org/thread/fyyhkjvhzl4hpzr52hd64csh5lt2wm6h) with
project name "Uniffle" . Please help to discuss.

Best regards,
Jerry

Daniel B. Widdis  于2022年5月24日周二 01:24写道：

> This conjures up a mental image of a unicorn with the Apache feather
> tickling its nose... I like it.
>
> On Mon, May 23, 2022 at 8:36 AM Jerry Shao  wrote:
>
> > Hi team,
> >
> > After discussing with the team, we figured out a new name "Uniffle"
> > (Unified/Universal Shuffle). And we did a name searching, seems there's
> no
> > conflict with this new name.
> >
> > So we'd go with "Uniffle" as new project name. What do you think?
> >
> > Best regards,
> > Jerry
> >
> > -
> > Uniffle Naming Search
> > Github:
> > Search for Uniffle returns 0 results
> > https://github.com/search?q=uniffle
> >
> > SF.net:
> > Search for Uniffle returns 0 results
> >
> >
> https://sourceforge.net/directory/os:mac/freshness:recently-updated/?q=Uniffle
> >
> > openhub.net
> > Search for Uniffle returns 0 results
> > https://www.openhub.net/p?ref=homepage=Uniffle
> >
> > Google code:
> > Search for Uniffle returns 0 results
> > https://opensource.google/s/results?q=Uniffle
> >
> > USPTO:
> >  I use ` Word and/or Design Mark Search (Free Form` of TESS. And type the
> > keyword '(uniffle)[BI,TI] and (software or computer)[GS] and (live)[LD]'
> .
> > There are 0 results
> > And I search
> >
> >
> https://search.uspto.gov/search?affiliate=web-sdmg-uspto.gov_by==uniffle
> > There are 0 results, too.
> >
> >
> > Trademarkia:
> > Search for Uniffle returns 0 results
> > https://www.trademarkia.com/trademarks-search.aspx?tn=uniffle
> >
> > EU Organization for Harmonization
> > Search for Uniffle returns 0 results
> > https://euipo.europa.eu/eSearch/#basic/1+1+1+1/uniffle
> >
> > Google:
> > Search for Uniffle returns 0 results
> > https://www.google.com/search?q=uniffle
> >
> > Bing:
> > Search for Uniffle returns 0 results
> > https://www.bing.com/search?q=uniffle
> >
> > Yahoo:
> > Search for Uniffle returns 0 results
> > https://search.yahoo.com/search?p=uniffle=1
> >
> > Stackoverflow:
> > Search for Uniffle returns 0 results
> > https://stackoverflow.com/search?q=uniffle
> >
> > Saisai Shao  于2022年5月23日周一 20:50写道：
> >
> > > Thanks Justin for the explanation.
> > >
> > > We discussed internally and think that a new name would be better to
> > avoid
> > > potential issue.
> > >
> > > Will figure out a new name.
> > >
> > > Best regards,
> > > Jerry
> > >
> > > Justin Mclean  于2022年5月23日周一 20:29写道：
> > >
> > >> Hi,
> > >>
> > >> > There’s a typo in this paragraph that makes it impossible to
> > >> > understand/changes the original meaning.
> > >>
> > >> Apologies I meant to say "I don’t think that is the case.”. From what
> I
> > >> can see trademarks have not approved FireStorm as a name. If the
> project
> > >> wants to enter the incubator with that name, and understands the risks
> > that
> > >> involves then that is OK. Just be aware there is a risk that this may
> > stop
> > >> the project from graduating from the Incubator under that name.
> > >>
> > >> Kind Regards,
> > >> Justin
> > >
> > >
> >
>
>
> --
> Dan Widdis
>

[DISCUSSION] Incubating Proposal of Uniffle

[Jerry Shao]

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

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Jerry Shao]

Hi team,

After discussing with the team, we figured out a new name "Uniffle"
(Unified/Universal Shuffle). And we did a name searching, seems there's no
conflict with this new name.

So we'd go with "Uniffle" as new project name. What do you think?

Best regards,
Jerry

-
Uniffle Naming Search
Github:
Search for Uniffle returns 0 results
https://github.com/search?q=uniffle

SF.net:
Search for Uniffle returns 0 results
https://sourceforge.net/directory/os:mac/freshness:recently-updated/?q=Uniffle

openhub.net
Search for Uniffle returns 0 results
https://www.openhub.net/p?ref=homepage=Uniffle

Google code:
Search for Uniffle returns 0 results
https://opensource.google/s/results?q=Uniffle

USPTO:
 I use ` Word and/or Design Mark Search (Free Form` of TESS. And type the
keyword '(uniffle)[BI,TI] and (software or computer)[GS] and (live)[LD]' .
There are 0 results
And I search
https://search.uspto.gov/search?affiliate=web-sdmg-uspto.gov_by==uniffle
There are 0 results, too.


Trademarkia:
Search for Uniffle returns 0 results
https://www.trademarkia.com/trademarks-search.aspx?tn=uniffle

EU Organization for Harmonization
Search for Uniffle returns 0 results
https://euipo.europa.eu/eSearch/#basic/1+1+1+1/uniffle

Google:
Search for Uniffle returns 0 results
https://www.google.com/search?q=uniffle

Bing:
Search for Uniffle returns 0 results
https://www.bing.com/search?q=uniffle

Yahoo:
Search for Uniffle returns 0 results
https://search.yahoo.com/search?p=uniffle=1

Stackoverflow:
Search for Uniffle returns 0 results
https://stackoverflow.com/search?q=uniffle

Saisai Shao  于2022年5月23日周一 20:50写道：

> Thanks Justin for the explanation.
>
> We discussed internally and think that a new name would be better to avoid
> potential issue.
>
> Will figure out a new name.
>
> Best regards,
> Jerry
>
> Justin Mclean  于2022年5月23日周一 20:29写道：
>
>> Hi,
>>
>> > There’s a typo in this paragraph that makes it impossible to
>> > understand/changes the original meaning.
>>
>> Apologies I meant to say "I don’t think that is the case.”. From what I
>> can see trademarks have not approved FireStorm as a name. If the project
>> wants to enter the incubator with that name, and understands the risks that
>> involves then that is OK. Just be aware there is a risk that this may stop
>> the project from graduating from the Incubator under that name.
>>
>> Kind Regards,
>> Justin
>
>

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Jerry Shao]

Hi John,

I'm a little confused for now. Is name "Firestorm" ok as an Apache podling
name?

Best regards,
Jerry


John D. Ament  于2022年5月23日周一 19:34写道：

> On Sun, May 22, 2022 at 23:32 Daniel Widdis  wrote:
>
> > Adding onto this, even if there may be no legal trademark issue, there is
> > other software by this name which makes it less than desirable.  Quoted
> > from [1]
> >
> > > Avoiding search-results confusion is important for another reason.
> > Apache projects are often very quickly highly ranked. An Apache project
> > with a similar name to another application in the same technical space
> may
> > quickly come to dominate searches in that space. If someone else holds a
> > related trademark, this may lead to a legal dispute. As a non-profit
> > organization, the ASF and Apache projects have no business conflicting
> with
> > an existing trademark for software products or related services.
> >
> > A current search for "firestorm software" reveals multiple sites related
> > to [2]. Searching "firestorm download" links to [3].  Searching "apache
> > firestorm" links to sites providing parts for remote control model cars,
> of
> > which two models compatible with such parts are "Apache" and "Firestorm"
> > [4].
> >
> > 1 - https://infra.apache.org/project-names.html
> > 2 - https://www.zotac.com/us/page/firestorm
> > 3 - https://www.firestormviewer.org/choose-your-platform/
> > 4 - https://www.competitionx.com/hpi-racing-manuals/
> >
>
>
> I don’t believe that’s what we search for here. What we search for is
> expected use of the name. I wonder if part of the skew is search results
> history. I use DuckDuckGo and the top results include this proposal, some
> military related content and a company named Firestorm’s viewer. When I
> search for Tencent Firestorm I only get this proposed project
>
> We wouldn’t expect Apache to get great hits right now.  Long run we would.
> The formal name would be Apache Firestorm.
>
>
> > Not my call, I am not a lawyer and have no binding votes on the
> incubator,
> > just adding my observations.
> >
> > On 5/22/22, 8:04 PM, "Justin Mclean"  wrote:
> >
> > HI,
> >
> > > According to the trademarks@ current cursory feedback, looks like
> > project
> > > name "Firestorm" is OK.
> >
> > I don’t this that is the case. Trademark checked “FlameStorm”, and
> > said that if Firestorm was as issue then FlameStorm would also be an
> issue.
> > I don’t believe they have checked FireStorm.
>
>
> There’s a typo in this paragraph that makes it impossible to
> understand/changes the original meaning.
>
>
>
> >
> > Please don’t under estimate the cost of a project name change, I seen
> > several project go through this and it it is always much more effort than
> > you realise. Based on previous experience, Infra are not likely to make
> it
> > a priority to help with a name change mid incubation or just before
> > gradation.
> >
> > Kind Regards,
> > Justin
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Jerry Shao]

Hi all,

Thanks for your feedbacks.

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

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


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

Apache podling.


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

What do you think?

Thanks
Jerry


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

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

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

[Jerry Shao]

d
> > > >
> > > > [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 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 Onofré 
> > > >
> > > > * Jerry Shao 
> > > >
> > > > * Junjie Chen 
> > > >
> > > > * Junping Du 
> > > >
> > > > * Justin Mclean 
> > > >
> > > > * Lamber Liu 
> > > >
> > > > * Osgoo Li 
> > > >
> > > > * Peng Chen 
> > > >
> > > > * Zak Wu 
> > > >
> > > > * ZhongBo Wu 
> > > >
> > > > * Zili Chen 
> > > >
> > > > * Daniel Li 
> > > >
> > > > * Guo Jiwei 
> > > >
> > > > * Haiji Li 
> > > >
> > > > * Lizhen 
> > > >
> > > > * Yuanbo Liu 
> > > >
> > > > * Yuanhao Ji 
> > > >
> > > > * Zijie Lu 
> > > >
> > > > * Zirui Peng 
> > > >
> > > >
> > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Charles Zhang be
> appointed
> > > >
> > > > to the office of Vice President, Apache InLong, to serve in
> accordance
> > > >
> > > > with and subject to the direction of the Board of Directors and the
> > > >
> > > > Bylaws of the Foundation until death, resignation, retirement,
> removal
> > > >
> > > > or disqualification, or until a successor is appointed; and be it
> > > >
> > > > further
> > > >
> > > >
> > > > RESOLVED, that the Apache InLong Project be and hereby is tasked with
> > > >
> > > > the migration and rationalization of the Apache Incubator InLong
> > > >
> > > > podling; and be it further
> > > >
> > > >
> > > > RESOLVED, that all responsibilities pertaining to the Apache
> Incubator
> > > >
> > > > InLong podling encumbered upon the Apache Incubator PMC are hereafter
> > > >
> > > > discharged.
> > > >
> > > >
> > > >
> > > > --
> > > > Best wishes,
> > > > Charles Zhang
> > > >
> > >
> > >
> >
>

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Jerry Shao]

Yes, I think we could discuss the possibilities offline.

But I would like to clarify that "merging these projects together" is
neither a "problem" (a "wish" indeed), nor a prerequisite for incubating.
In the heyday of Hadoop, there were so many similar or even same purpose
projects in ASF, the choice is made by user, not by ASF.

Best
Jerry

Willem Jiang  于2022年5月18日周三 17:17写道：

> On Wed, May 18, 2022 at 2:50 PM Sheng Wu 
> wrote:
> >
> > Hi Firestorm community
> >
> > Considering what Yu Li is proposing, I would recommend you could do
> > some discussions directly, maybe off the list if you want.
> > Both of the projects are young and very new to the community, it may
> > be not a concern from my perspective(may be concerned by some IPMC),
> > as one/both could fail in the incubating. But with you are going to
> > work on the similar things, the challenge would be for both of your
> > projects to establish the incubating process. Also, when we talk about
> > graduation in the future, it would be my concern of causing confusion
> > to users.
> >
> > Two TLPs are nearly the same is really not a good practice from the
> > foundation level.
> >
> > > We heartfully welcome you to join Firestorm project and community.
> >
> > So, I suggest not just saying joining Firestorm, this may be a simple
> > reaction, I hope you could do more.
> > This is an opportunity to do a bigger and more powerful project
> > supported by Tencent and Alibaba's initial teams.
> >
>
> After talking with LiYu and Jerry Shao,  I realized there could be
> some challenges we may face.
> But it would be great if we can work together to tackle the same problem.
> I'd like to help two teams to start a meeting to discuss the
> possibility of merging these projects together.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> > I know it is not easy to do a joint project, but it is actually much
> > better to see you two competing with each other in the next 1-2 years.
> > In the ASF, we hope to create a better project for the whole industry.
> >
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> > Jerry Shao  于2022年5月18日周三 14:38写道：
> > >
> > > Hi Yu，
> > >
> > > IMO, I think we're open and welcome all the contributions. We
> heartfully
> > > welcome you to join Firestorm project and community.
> > >
> > > Best regards,
> > > Jerry
> > >
> > > Yu Li  于2022年5月18日周三 13:36写道：
> > >
> > > > Hi Jerry,
> > > >
> > > > Good to see the proposal for incubating a uniform remote shuffle
> service.
> > > > Coincidently, we are preparing an incubating proposal for the same
> > > > direction based on two open source projects Alibaba is driving [1]
> [2], and
> > > > I'm the champion for that. Our proposal is still not fully prepared
> because
> > > > the merge of the two projects is still in progress, and I'm writing
> this
> > > > email to check whether it's possible that we have a joint force to
> achieve
> > > > the same goal. I believe it will be cool if we could do this
> together,
> > > > although there will be a lot (more) work to do to make this happen.
> > > >
> > > > Please let me know your thoughts and let's have more discussions if
> you're
> > > > also interested. Thanks.
> > > >
> > > > Best Regards,
> > > > Yu
> > > >
> > > > [1] https://github.com/flink-extended/flink-remote-shuffle
> > > > [2] https://github.com/alibaba/RemoteShuffleService
> > > >
> > > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Jerry Shao]

Thanks guys for your opinions, we will discuss the things off the list.

But AFAIK, this should not be the blocking issue here for incubating.

Best,
Jerry

Juan Pan  于2022年5月18日周三 15:31写道：

> Hello Justin,
>
>
> > If the projects decide not to join forces, we would welcome an
> incubating proposal from the other project. The ASF doesn't pick projects
> to use, we let the wider user community decide what they want to use.
>
>
> It’s a bit different from my impression, could I know it’s fine to have
> many projects sharing much similar functions or aiming in parallel here?
>
>
> Thanks,
> Trista
>
> --
> Trista Pan
> Twitter & Github: tristaZero
>
>
>
>
> On 05/18/2022 15:12，Justin Mclean wrote：
> Hi,
>
> It would be good if the project could work together, but there isn’t
> anything wrong with having two similar incubating projects. If the projects
> decide not to join forces, we would welcome an incubating proposal from the
> other project. The ASF doesn't pick projects to use, we let the wider user
> community decide what they want to use.
>
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Jerry Shao]

Hi Yu，

IMO, I think we're open and welcome all the contributions. We heartfully
welcome you to join Firestorm project and community.

Best regards,
Jerry

Yu Li  于2022年5月18日周三 13:36写道：

> Hi Jerry,
>
> Good to see the proposal for incubating a uniform remote shuffle service.
> Coincidently, we are preparing an incubating proposal for the same
> direction based on two open source projects Alibaba is driving [1] [2], and
> I'm the champion for that. Our proposal is still not fully prepared because
> the merge of the two projects is still in progress, and I'm writing this
> email to check whether it's possible that we have a joint force to achieve
> the same goal. I believe it will be cool if we could do this together,
> although there will be a lot (more) work to do to make this happen.
>
> Please let me know your thoughts and let's have more discussions if you're
> also interested. Thanks.
>
> Best Regards,
> Yu
>
> [1] https://github.com/flink-extended/flink-remote-shuffle
> [2] https://github.com/alibaba/RemoteShuffleService
>
>
> On Wed, 18 May 2022 at 12:15, Jerry Shao  wrote:
>
> > Sure Felix, let me add you to the list.
> >
> > Best,
> > Jerry
> >
> > Felix Cheung  于2022年5月18日周三 11:59写道：
> >
> > > Same here, would love to see if I can help, Jerry.
> > >
> > >
> > > On Mon, May 16, 2022 at 10:31 PM Saisai Shao 
> > > wrote:
> > >
> > > > Thanks Weiwei, let me add you to the mentor list.
> > > >
> > > > Best regards,
> > > > Jerry
> > > >
> > > > Weiwei Yang  于2022年5月17日周二 12:18写道：
> > > >
> > > > > +1
> > > > > This is an interesting project, I'd be happy to help the project's
> > > > > incubation process.
> > > > > Let me know if you need my help, Thanks
> > > > >
> > > > > On Mon, May 16, 2022 at 8:09 PM Saisai Shao <
> sai.sai.s...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Got it, thanks a lot Justin.
> > > > > >
> > > > > > Best regards,
> > > > > > Jerry
> > > > > >
> > > > > > Justin Mclean  于2022年5月17日周二 10:59写道：
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > The new project name doesn’t need to be a registered trademark,
> > but
> > > > you
> > > > > > > would still need to pick a name that is now likely to have any
> > > > > trademark
> > > > > > > issues.
> > > > > > >
> > > > > > > The project may want to get the ASF to register the mark at a
> > later
> > > > > date,
> > > > > > > but it wold be best to talk abut that on the trademarks@ list.
> > > > > > >
> > > > > > > Kind Regards,
> > > > > > > Justin
> > > > > > >
> > > > > > >
> > > > > > >
> > > -
> > > > > > > To unsubscribe, e-mail:
> general-unsubscr...@incubator.apache.org
> > > > > > > For additional commands, e-mail:
> > general-h...@incubator.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Jerry Shao]

Sure Felix, let me add you to the list.

Best,
Jerry

Felix Cheung  于2022年5月18日周三 11:59写道：

> Same here, would love to see if I can help, Jerry.
>
>
> On Mon, May 16, 2022 at 10:31 PM Saisai Shao 
> wrote:
>
> > Thanks Weiwei, let me add you to the mentor list.
> >
> > Best regards,
> > Jerry
> >
> > Weiwei Yang  于2022年5月17日周二 12:18写道：
> >
> > > +1
> > > This is an interesting project, I'd be happy to help the project's
> > > incubation process.
> > > Let me know if you need my help, Thanks
> > >
> > > On Mon, May 16, 2022 at 8:09 PM Saisai Shao 
> > > wrote:
> > >
> > > > Got it, thanks a lot Justin.
> > > >
> > > > Best regards,
> > > > Jerry
> > > >
> > > > Justin Mclean  于2022年5月17日周二 10:59写道：
> > > >
> > > > > Hi,
> > > > >
> > > > > The new project name doesn’t need to be a registered trademark, but
> > you
> > > > > would still need to pick a name that is now likely to have any
> > > trademark
> > > > > issues.
> > > > >
> > > > > The project may want to get the ASF to register the mark at a later
> > > date,
> > > > > but it wold be best to talk abut that on the trademarks@ list.
> > > > >
> > > > > Kind Regards,
> > > > > Justin
> > > > >
> > > > >
> > > > >
> -
> > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Jerry Shao]

Thanks Justin,

Let me talk to trademarks@ first.

Best,
Jerry

Justin Mclean  于2022年5月17日周二 21:12写道：

> Hi,
>
> I’d run that past trademarks@ mailing list. It might be like calling your
> fast food restaurant McDoogles and hoping no-one notices the name is
> similar to McDonalds.
>
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Jerry Shao]

Hi,

We discussed internally and proposed a new name "flamestorm" as a
replacement.
If the community thinks this name "flamestorm" is OK, our proposal will go
with this new name.

Best regards,
Jerry


below is the search result for "flamestorm"
-
Github:
Search for Flamestorm returns 0 results
https://github.com/search?q=flamestorm

SF.net:
Search for Flamestorm returns 0 results
https://sourceforge.net/directory/os:mac/freshness:recently-updated/?q=Flamestorm

openhub.net
Search for Flamestorm returns 0 results
https://www.openhub.net/p?ref=homepage=Flamestorm

Google code:
Search for Flamestorm returns 0 results
https://opensource.google/projects?q=flamestorm


USPTO:
There are no effective results, the first page results only contain keyword
'flame'
https://search.uspto.gov/search?affiliate=web-sdmg-uspto.gov_by==flamestorm
And I search for 'Flamestorm software' returns 0 result
https://search.uspto.gov/search?affiliate=web-sdmg-uspto.gov_by==framestorm+software

Trademarkia:
Search for Flamestorm returns 0 results
https://www.trademarkia.com/trademarks-search.aspx?tn=flamestorm

EU Organization for Harmonization
Search for Flamestorm returns 0 results
https://euipo.europa.eu/eSearch/#basic/1+1+1+1/flamestorm

Google:
https://www.google.com/search?q=flamestorm
Bing:
https://www.bing.com/search?q=flamestorm
Yahoo
https://search.yahoo.com/search?p=flamestorm=1
Stackoverflow
https://stackoverflow.com/search?q=flamestorm

There are no results about software

Saisai Shao  于2022年5月17日周二 13:31写道：

> Thanks Weiwei, let me add you to the mentor list.
>
> Best regards,
> Jerry
>
> Weiwei Yang  于2022年5月17日周二 12:18写道：
>
>> +1
>> This is an interesting project, I'd be happy to help the project's
>> incubation process.
>> Let me know if you need my help, Thanks
>>
>> On Mon, May 16, 2022 at 8:09 PM Saisai Shao 
>> wrote:
>>
>> > Got it, thanks a lot Justin.
>> >
>> > Best regards,
>> > Jerry
>> >
>> > Justin Mclean  于2022年5月17日周二 10:59写道：
>> >
>> > > Hi,
>> > >
>> > > The new project name doesn’t need to be a registered trademark, but
>> you
>> > > would still need to pick a name that is now likely to have any
>> trademark
>> > > issues.
>> > >
>> > > The project may want to get the ASF to register the mark at a later
>> date,
>> > > but it wold be best to talk abut that on the trademarks@ list.
>> > >
>> > > Kind Regards,
>> > > Justin
>> > >
>> > >
>> > > -
>> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > > For additional commands, e-mail: general-h...@incubator.apache.org
>> > >
>> > >
>> >
>>
>

[DISCUSSION] Incubating Proposal of Firestorm

[Jerry Shao]

Hi all,

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

Firestorm 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 -  “Firestorm”  - is heavily
adopted in Tencent, and shows its advantages in production. Other
enterprises also adopted or prepared to adopt Firestorm in their
environments.

Firestorm’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 Firestorm 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:

   - Junping du (junping...@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/FirestormProposal

Best regards,
Jerry

Re: [VOTE] Release Apache InLong(Incubating) 1.0.0-incubating RC1

[Jerry Shao]

+1 (binding) from my side.

- Download links are valid
- DISCLAIMER files exists
- No unexpected binary files
- All source files have ASF headers

Thanks



Xun Liu  于2022年2月16日周三 20:12写道：

> Hi,
>
> +1 (binding) from me,
>
> I have checked the following items:
> - Incubating in name
> - LICENSE and NOTICE are fine
> - DISCLAIMER-WIP exists
> - All links are valid
> - No unexpected binary files
> - All ASF files have ASF headers
> - Can compile from source
>   `mvn clean install`
> - Checksums and PGP signatures are valid.
>
> I browsed InLong's website and found that there are some pictures on the
> English page[1][2][there may be others], showing Chinese,
> if there is time to unify it, it should be better. :-)
>
> [1] https://inlong.apache.org/docs/modules/tubemq/overview
> [2] https://inlong.apache.org/docs/modules/tubemq/quick_start
>
> Best regards
> Xun Liu
>
> On Wed, Feb 16, 2022 at 3:49 PM Lidong Dai  wrote:
>
> > +1(binding)
> >
> > I have checked the following items:
> > - Download links are valid
> > - DISCLAIMER files exists
> > - No unexpected binary files
> > - All source files have ASF headers
> > - Can compile from source
> >
> > Best Regards
> >
> >
> >
> > ---
> > Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
> > Lidong Dai
> > lidong...@apache.org
> > Linkedin: https://www.linkedin.com/in/dailidong
> > Twitter: @WorkflowEasy 
> >
> > ---
> >
> >
> > On Mon, Feb 14, 2022 at 4:36 PM dockerzhang 
> > wrote:
> >
> > > Hello Incubator Community,
> > >
> > > This is a call for a vote to release Apache InLong(Incubating)
> > version
> > > 1.0.0-incubating RC1
> > >
> > > The Apache InLong community has voted on and approved a proposal to
> > > release
> > > Apache InLong(Incubating) version 1.0.0-incubating RC1
> > >
> > > We now kindly request the Incubator PMC members review and vote on
> > this
> > > incubator release.
> > >
> > > InLong community vote thread:
> > > • https://lists.apache.org/thread/bp67bghmw480kff1olfbd655p9ct5f1k
> > >
> > > Vote result thread:
> > > • https://lists.apache.org/thread/jo58g880gxk6m4sjh7o1hvd11p6fwg1g
> > >
> > > The release candidate:
> > > •
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/inlong/1.0.0-incubating-RC1/
> > >
> > > Git tag for the release:
> > > •
> > >
> > >
> >
> https://github.com/apache/incubator-inlong/releases/tag/1.0.0-incubating-RC1
> > >
> > > Release notes:
> > > •
> > >
> > >
> >
> https://github.com/apache/incubator-inlong/blob/1.0.0-incubating-RC1/CHANGES.md
> > >
> > > The artifacts signed with PGP key A4D4D578, corresponding to
> > > dockerzh...@apache.org, can be found in the keys file:
> > > • https://downloads.apache.org/incubator/inlong/KEYS
> > >
> > > The vote will be open for at least 72 hours or until a necessary
> > number
> > > of votes is reached.
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > Thanks,
> > > On behalf of Apache InLong(Incubating) community
> > >
> >
>

Re: [VOTE] Graduate Apache Ratis as TLP Project

[Jerry Shao]

+1 binding.

Thanks
Jerry

Willem Jiang  于2021年2月1日周一 下午4:14写道：

> +1 binding.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sat, Jan 30, 2021 at 4:32 AM Uma gangumalla 
> wrote:
> >
> > Dear Incubator Community,
> >
> >  We have discussed Apache Ratis Podling graduation in the incubator
> general
> > DISCUSS thread[1] and We did not see any objections to proceed for
> voting.
> > Here is the official vote for graduating Apache Ratis project as TLP.
> >
> > Please provide your in the following options:
> > [ ] +1 - Recommend graduation of Apache Ratis as a TLP
> > [ ]  0 - I don't feel strongly about it, but don't object
> > [ ] -1 - Do not recommend graduation of Apache Ratis because...
> >
> > The VOTE will open for at least 72 hours.
> >
> > Just to summarize again:
> > Apache Ratis project is a very active project and the community has grown
> > well by following the Apache way in the process. It produced several
> > releases by having diverse people as release managers. I and the
> community
> > strongly believe that it's ready for graduation.
> >
> > The Apache Ratis project has been an Apache incubator project for nearly
> 3
> > year. Since then the community has grown and followed Apache Way. Some
> > highlights include:
> > * 7 releases given ( including 1.0.0 and 0.0.1 alpha ) by having
> > different people as release managers
> > * 50 contributors ( from report)
> > * 28 committers
> > * More than 1161 Jiras created, 905 resolved or closed
> > * > 293 pull requests in github
> > * One of the biggest positives for this community is that most of the
> > members in this community have a lot of experience in other Apache
> projects
> > already.
> >
> > Some additional note about the resolution below:
> > The current PPMC will be transitioned to the PMC. We have invited some of
> > the mentors in the current PPMC who like to stay involved.
> > We are also adding Siddharth and Jie Wang into PMC as we believe they are
> > committed to the project and a good addition to PMC.
> >
> > We have already voted for Ratis TLP in the Ratis Podling community.
> Please
> > find the voting threads for reference. Ratis PPMC DISCUSS thread: [2],
> > Ratis PPMC Vote: [3] and Ratis Community: [4]
> >
> > To make easy for you to review, here is the *resolution text*[5] copied:
> >
> ==
> > Establish the Apache Ratis 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 java implementation for RAFT consensus protocol.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Ratis Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Ratis Project be and hereby is responsible for
> > the creation and maintenance of software related to A java
> > implementation for RAFT consensus protocol; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Ratis" 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 Ratis
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache Ratis 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 Ratis Project:
> >
> >  * Anu Engineer  [Hadoop, Ozone PMC,
> > Incubator Committer]
> >  * Arpit Agarwal [ ASF Member, Hadoop, Ozone,
> > Incubator PMC]
> >  * Enis Soztutar [ASF Member, Hadoop, HBase,
> > Incubator PMC and also PMC in curator, gora, phoenix]
> >  * Hanisha Koneru[Hadoop, Ozone PMC,
> > Incubator Committer]
> >  * Jie Wang  [Incubator, Ozone
> Committer]
> >  * Jing Zhao [Hadoop PMC, Incubator
> Committer]
> >  * Jitendra Nath Pandey   [ASF Member, Hadoop,
> Ozone,
> > Incubator PMC and also PMC in ambari, atlas, tez]
> >  * Josh Elser [ASF Member, HBase,
> Incubator
> > PMC, and also PMC in accumulo, calcite, fluo, phoenix, rya]
> >  * Lokesh Jain   [Hadoop, Ozone PMC, Incubator
> > Committer]
> >  * Marton Elek[Hadoop, Ozone PMC, Incubator
> > Committer]
> >  * Mingliang Liu  [Hadoop PMC, Incubator
> > Committer]
> >  * Mukul Kumar Singh  [Hadoop, Ozone PMC,
> Incubator
> > Committer]
> >  * Shashikant Banerjee   [Hadoop, Ozone PMC,
> > Incubator Committer]
> >  * Siddharth Wagle[Ambari, Ozone PMC, Hadoop,
> > Incubator Committer]
> >  * Tsz-wo Sze [ASF Member, Hadoop,

Re: [VOTE] Release Apache TubeMQ (Incubating) 0.7.0-incubating RC0

[Jerry Shao]

+1 (binding)

Signatures, checksums are good.

Best Regards,
Jerry

Sijie Guo  于2020年12月2日周三 上午3:24写道：

> +1 (binding)
>
> Signatures, checksums, NOTICE, and LICENSE are good.
>
> - Sijie
>
> On Mon, Nov 30, 2020 at 6:27 PM Goson zhang  wrote:
>
> > @Dave Fisher, thank you!
> >
> > We will continue to improve it.
> >
> > Dave Fisher  于2020年12月1日周二 上午2:49写道：
> >
> > > +1 (binding)
> > >
> > > Signatures, Checksums, DISCLAIMER-WIP, NOTICE, and LICENSE checkout.
> > >
> > > Rat check looks ok on source. A .rat-excludes file would help as
> > licensing
> > > is further reviewed.
> > >
> > > Server binary spot check of license on mvnrepository.com shows proper
> > > license choices for selected dependency  jars.
> > >
> > > Likely the project should be able to attain proper LICENSE in binaries
> in
> > > next release.
> > >
> > > Best Regards,
> > > Dave
> > >
> > > >This is a call for a vote to release Apache TubeMQ (Incubating)
> > > version
> > > > 0.7.0-incubating-RC0
> > > >
> > > >The Apache TubeMQ community has voted on and approved a proposal
> to
> > > > release
> > > >Apache TubeMQ (Incubating) version 0.7.0-incubating-RC0
> > > >
> > > >We now kindly request the Incubator PMC members review and vote on
> > > this
> > > >incubator release.
> > > >
> > > >TubeMQ community vote thread:
> > > >•
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r6e3b8e42ad8adb7867780b6aec23cc44b7b55a6a19eecec83aa67b8d%40%3Cdev.tubemq.apache.org%3E
> > > >
> > > >Vote result thread:
> > > >•
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r459723d31c6f649dcaba6b81ffbccc94cbe53207248966bcc11d7343%40%3Cdev.tubemq.apache.org%3E
> > > >
> > > >The release candidate:
> > > >•
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/tubemq/0.7.0-incubating-RC0/
> > > >
> > > >Git tag for the release:
> > > >•
> > > https://github.com/apache/incubator-tubemq/tree/0.7.0-incubating-RC0
> > > >
> > > >Release notes:
> > > >•
> > > >
> > >
> >
> https://github.com/apache/incubator-tubemq/releases/tag/0.7.0-incubating-RC0
> > > >
> > > >The artifacts signed with PGP key [A4D4D578], corresponding to [
> > > > dockerzh...@apache.org], which can be found in the keys file:
> > > >• https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS
> > > >
> > > >The vote will be open for at least 72 hours or until the necessary
> > > > number of votes are reached.
> > > >
> > > >Please vote accordingly:
> > > >
> > > >[ ] +1 approve
> > > >[ ] +0 no opinion
> > > >[ ] -1 disapprove with the reason
> > > >
> > > > Thanks,
> > > > On behalf of the Apache TubeMQ (Incubating) community.
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: Process to rename the project

[Jerry Shao]

Thanks Dave for the reply, greatly appreciated!

Best regards,
Jerry

Dave Fisher  于2020年11月24日周二 上午11:03写道：

> If you are looking for the process.
>
> (1) Decide on new name in the podling.
>
> (2) Do a podling name search with trademarks.
>
> (3) let incubator know the new name
>
> (4) ask for Infra’s help changes resource names.
>
> Sent from my iPhone
>
> On Nov 23, 2020, at 6:02 PM, Saisai Shao  wrote:
>
> 
> Thanks all for the reply.
>
> Yes we will put into discussion in TubeMQ mail list. But just want know
> beforehand if it is possible to rename the project (I haven't seen this
> before)? if so, is there any documentation things to follow, if not, we
> will figure out other ways to do so.
>
> Thanks
> Jerry
>
> zhangli...@apache.org  于2020年11月23日周一 下午8:09写道：
>
>> Hi Jerry,
>>
>> It is better to discuss it in TubeMQ dev mail list first.
>>
>> --
>>
>> Sincerely,
>> Liang Zhang (John)
>> Apache ShardingSphere
>>
>>
>> Saisai Shao  于2020年11月23日周一 上午10:38写道：
>>
>> > The podling project is Apache TubeMQ. Currently the project is planning
>> to
>> > change the name, but haven't yet figured out a new name, neither did a
>> > podling name search. Just want to understand what is the process.
>> >
>> > CC @general@incubator.apache.org 
>> >
>> > Thanks
>> > Jerry
>> >
>> > Dave Fisher  于2020年11月23日周一 上午10:26写道：
>> >
>> > > Has the podling done a podling name search?
>> > >
>> > > What podling?
>> > >
>> > > What is the new name?
>> > >
>> > > Changing names is work for infrastructure so we want to be careful
>> not to
>> > > be spurious!
>> > >
>> > > Regards,
>> > > Dave
>> > >
>> > > Sent from my iPhone
>> > >
>> > > > On Nov 22, 2020, at 6:19 PM, Jerry Shao  wrote:
>> > > >
>> > > > 
>> > > > Hi Team,
>> > > >
>> > > > We have a podling project which wants to change its current name,
>> the
>> > > main reason of changing is to expand the scope of the project. I would
>> > like
>> > > to know if it is possible to change the project name? If so, what is
>> the
>> > > process, do we have any document about this?
>> > > >
>> > > > Thanks
>> > > > Jerry
>> > >
>> > >
>> > > -
>> > > To unsubscribe, e-mail: private-unsubscr...@incubator.apache.org
>> > > For additional commands, e-mail: private-h...@incubator.apache.org
>> > >
>> > >
>> >
>>
>

[VOTE] Release Livy 0.4.0-incubating based on Livy 0.4.0 RC2

[Jerry Shao]

Hello Incubator PMC’ers,

The Apache Livy community has decided to release Apache Livy
0.4.0-incubating based on 0.4.0-incubating Release Candidate 2. We now
kindly request the Incubator PMC members to review and vote on this incubator
release.

Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with
many Spark contexts.

Artifacts are available at
https://dist.apache.org/repos/dist/dev/incubator/livy/, public keys are
available at https://dist.apache.org/repos/dist/dev/incubator/livy/KEYS.

livy-0.4.0-incubating-src.zip <
https://dist.apache.org/repos/dist/dev/incubator/livy/0.4.0-incubating/livy-0.4.0-incubating-src-RC2.zip
> is a source release. Along with it, for convenience, please find the
binary release as livy-0.4.0-incubating-bin-RC2.zip <
https://dist.apache.org/repos/dist/dev/incubator/livy/0.4.0-incubating/livy-0.4.0-incubating-bin-RC2.zip
>.


Git tag:
*https://github.com/apache/incubator-livy/releases/tag/v0.4.0-incubating-rc2
*

The vote will be open for at least 72 hours or until necessary number of
votes are reached.

Members please be sure to indicate "(Binding)" with your vote which will
help in tallying the vote(s).

* Here is my +1 (non-binding) *

Cheers,
Jerry