Re: [VOTE] Drop the incubator- prefix for podling's GitHub repo name

[Xinyu Zhou]

+1 binding

The GitHub repo name usually matches the project name. Dropping 'incubator'
makes it cleaner.

We'll just make sure to highlight the 'Incubating' status on our website,
in the GitHub description, the README, and all release versions. I think
it's very clear to the developers of the project.

Regards,
Xinyu Zhou

On Wed, May 8, 2024 at 10:56 AM Wilfred Spiegelenburg 
wrote:

> +1 not binding from wilfreds
>
> On 2024/05/08 00:31:23 tison wrote:
> > Hi,
> >
> > Following the discussion thread [1], I'd start a vote on the following
> > proposals:
> >
> > 1. Establish a consensus to allow and finally converge podling's GitHub
> repo to
> > have a name without the incubator- prefix.
> > 2. Allow existing ongoing podlings to ask the INFRA to drop their
> > incubator- prefix by now, not MUST during the graduation.
> > 3. Update the docs on incubator.apache.org everywhere if the description
> > can conflict with this consensus.
> > 4. Update the docs on incubator.apache.org to guide how to describe
> > podling's incubating status on the GitHub repo (namely, including
> > "incubating" in the repo description and README, point to the DISCLAIMER
> > content).
> >
> > [1] https://lists.apache.org/thread/kxvdkrf8g8yr6hww1n08r21xdy67y4ok
> >
> > +1 allow podling's GitHub repo to have a name without the incubator-
> > prefix, and other items above
> > +0 do not care strongly
> > -1 disagree the proposals above, because ...
> >
> > Please vote with your ASF ID followed by (binding) if you are a member of
> > the Incubator PMC or (not binding) if not.
> >
> > Vote will be open for at least 72 hours.
> >
> > Best,
> > tison.
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo

[Xinyu Zhou]

If the `incubator-` prefix significantly burdens the graduation process or
introduces inconveniences in package or dependency management, its removal
might be considered.

However, IMO, maintaining incubating in the description, and website,
especially in the *release version*, clearly signals that this is an
incubator release of an Apache project, which should be sufficient to
alleviate most ambiguity.

I mean, `incubating` is just a temporary status label, it's changeable,
while the project or product name usually is immutable.

Regards,
Xinyu Zhou

On Mon, Apr 29, 2024 at 5:40 PM tison  wrote:

> Before starting the vote, I found (perhaps) a final question: Shall we thus
> guide all the new podlings to enter the incubator without incubator- prefix
> and thus converge all the current podlings are in form apache/foo?
>
> I'm afraid that if new podling can still have the incubator- prefix, it can
> give a confusing impression to end-users.
>
> I can't find a good place to document this point but perhaps we spread the
> consensus when reviewing new podling proposal's "Git Repositories" section.
>
> Best,
> tison.
>
>
> ConradJam  于2024年4月29日周一 14:17写道：
>
> > As a developer on the Apache Amoro project, I believe it's crucial to
> > prominently display the project's status as an incubator, whether by
> > attaching it to the project prefix or featuring it on the website. Most
> > individuals typically recognize that a project is in incubation through
> the
> > project's website or GitHub description (including myself when initially
> > encountering or learning about a project). Every project developer has an
> > obligation to indicate the project's incubation status when promoting or
> > publicizing it. Additionally, displaying a clear logo on the website
> > indicating its incubation status is essential. As a user, simply having
> > that incubator logo or description suffices for me. Therefore,  I’m +0
> for
> > incubator- prefix .
> >
> > tison  于2024年4月24日周三 19:49写道：
> >
> > > Thanks for your participation!
> > >
> > > For people who support drop the incubator- prefix, please describe you
> > > opinion on:
> > >
> > > > 3. It's still significant to make it clear that a podling is in the
> > > incubating status and thus a DISCLAIMER to protect the ASF branding.
> > > > I'd propose to add the "incubating" words to each repo's README. This
> > can
> > > be regarded as treating those READMEs a homepage for the repo and,
> > > >
> > > > 1. Name the project as "Apache Foo (Incubating)" in its first and
> most
> > > prominent uses, hopefully and H1 heading.
> > > > 2. Add a footer including the Incubator logo and DISCLAIMER, like the
> > > current footer of Apache Answer (Incubating) [3]
> > > > [3] https://answer.apache.org/
> > >
> > > Be sure that you know we don't barely drop the prefix, but we need a
> > formal
> > > way to "make it clear that a podling's repo is in the incubating
> status",
> > > which can be achieved currently by  its prefix.
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > Wilfred Spiegelenburg  于2024年4月23日周二 13:12写道：
> > >
> > > > For Go based projects dropping the incubator reference in the git
> repo
> > > > makes things easier also when graduating. Packages and dependencies
> are
> > > > referenced based on the repository name. Renaming the repository
> either
> > > > requires changes throughout the code base to remove the incubator
> > > reference
> > > > or the packages will always have the incubator reference in them.
> > > >
> > > > Wilfred
> > > >
> > > > On 2024/04/23 01:22:02 tison wrote:
> > > > > Hi,
> > > > >
> > > > > Recently, the new added podlings, namely Amoro and Hertzbeat, have
> > > their
> > > > > GitHub repo in the names:
> > > > >
> > > > > * https://github.com/apache/amoro
> > > > > * https://github.com/apache/hertzbeat
> > > > >
> > > > > ... which is different to the other 20+ podlings and 200+ repos [1]
> > > > > existing (this number counts retired ones and those for the
> Incubator
> > > PMC
> > > > > itself, but it's approximate).
> > > > >
> > > > > [1]
> > > > >
> > > >
> > >
> >
> https://github.com/orgs/apa

Re: [VOTE] Accept HertzBeat Into the ASF Incubator

[Xinyu Zhou]

+1 binding.

Good Luck!

Regards,
Xinyu Zhou



On Wed, Apr 3, 2024 at 10:19 AM roryqi  wrote:

> +1, Thanks.
>
> Xin Wang  于2024年4月3日周三 09:43写道：
>
> > +1, binding
> >
> > Xun Liu  于2024年4月3日周三 08:58写道：
> >
> > > +1 (binding)
> > >
> > > Best regards,
> > > Xun Liu
> > >
> > > On Wed, Apr 3, 2024 at 7:33 AM zhongyi tan 
> > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > Good luck
> > > >
> > > >
> > > >
> > > > 在 2024/4/2 20:15，“Zhang Yonglun” > > > zhangyong...@apache.org>> 写入:
> > > >
> > > >
> > > > Hi,
> > > >
> > > >
> > > > Thanks to everyone who has already taken the time to vote.
> > > >
> > > >
> > > > I just wanted to gently remind that our voting process is nearing its
> > > > deadline, and we're still hoping to gather more input. Your thoughts
> > > > and opinions truly matter to us.
> > > >
> > > >
> > > > Your participation in the vote will not only shape our decisions but
> > > > also ensure that we consider a diverse range of perspectives. We
> value
> > > > every voice and want to make sure everyone has the opportunity to
> > > > contribute.
> > > >
> > > >
> > > > If you haven't already, please take a moment to cast your vote. And
> if
> > > > you have any questions or need assistance, feel free to reach out to
> > > > me anytime.
> > > >
> > > >
> > > > Thank you for your time and consideration.
> > > >
> > > >
> > > > Best Regards,
> > > > Zhang Yonglun
> > > >
> > > >
> > > > Zhang Yonglun  zhangyong...@apache.org
> > >>
> > > > 于2024年3月29日周五 14:24写道：
> > > > >
> > > > > Hi Incubator,
> > > > >
> > > > > Following the discussion [DISCUSS] Incubating Proposal for
> > > HertzBeat[1],
> > > > > I am starting this official vote for the HertzBeat project.
> > > > >
> > > > > Here is their proposal:
> > > > >
> > >
> https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal
> > > > <
> > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal
> > > >
> > > > >
> > > > > Please cast your vote:
> > > > >
> > > > > [ ] +1, bring into the Incubator
> > > > > [ ] +0, I don't care either way
> > > > > [ ] -1, do not bring HertzBeat into the Incubator, because...
> > > > >
> > > > > The vote will open for one week from today.
> > > > >
> > > > > [1]
> https://lists.apache.org/thread/snxcdyvqgvhgjdmfv4l192g9tdf8w7rn
> > <
> > > > https://lists.apache.org/thread/snxcdyvqgvhgjdmfv4l192g9tdf8w7rn>
> > > > >
> > > > > Best Regards,
> > > > > Zhang Yonglun
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >  > > > general-unsubscr...@incubator.apache.org>
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > > <mailto:general-h...@incubator.apache.org>
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> > --
> > Thanks,
> > Xin
> >
>

Re: [VOTE] Graduate Apache Paimon (Incubating) as a Top Level Project

[Xinyu Zhou]

+1 binding

Regards,
Xinyu Zhou

On Mon, Mar 11, 2024 at 9:34 AM Willem Jiang  wrote:

> +1 binding.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Mar 8, 2024 at 6:51 PM Yu Li  wrote:
> >
> > Hi All,
> >
> > We've got positive feedback on the DISCUSS thread for graduation [1],
> > and would like to start an official VOTE thread now.
> >
> > Below are some facts and project highlights from the incubation phase
> > as well as the draft resolution:
> >
> > - Currently, our community consists of 18 committers (including
> > mentors) from ~10 different companies, with 11 serving as PPMC
> > members.
> > - So far, we have boasted 132 contributors.
> > - Throughout the incubation period, we've made 5 releases in 12
> > months, at a stable pace.
> > - We've had 3 different release managers to date.
> > - Our software is used in production by 20+ well known entities.
> > - As yet, we have opened 1,363 issues with 1,083 successfully
> > resolved, including the period as a sub-project of Apache Flink.
> > - We have submitted a total of 2,166 PRs, out of which 2,091 have been
> > merged or closed.
> > - We have met all maturity criteria as outlined in [2].
> >
> > Please vote on the resolution pasted below to graduate Apache Paimon
> > from the Incubator to the Top Level Project.
> >
> >  [ ] +1 Graduate Apache Paimon from the Incubator.
> >  [ ] +0 No opinion.
> >  [ ] -1 Don't graduate Apache Paimon from the Incubator because ...
> >
> > This vote will open for at least 72 hours.
> >
> > We would like to thank everyone who has participated in the Apache
> > Paimon community. We would also like to thank the Apache Incubator
> > community as well as Apache Infrastructure team and general ASF
> > community for your support.
> >
> > [1] https://lists.apache.org/thread/012rfy2zvnhqh39foncwvdpvy9fzry1q
> > [2]
> https://cwiki.apache.org/confluence/display/PAIMON/Apache+Maturity+Model+Assessment+for+Paimon
> >
> > ---
> >
> > Establish the Apache Paimon 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 unified lake storage to build dynamic tables for both
> > stream and batch processing with big data compute engines, supporting
> > high-speed data ingestion and real-time data query.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Paimon Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Paimon Project be and hereby is responsible
> > for the creation and maintenance of software related to a unified lake
> > storage to build dynamic tables for both stream and batch processing
> > with big data compute engines, supporting high-speed data ingestion and
> > real-time data query; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Paimon" 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 Paimon
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache Paimon
> > 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 Paimon Project:
> >
> > * Becket Qin 
> > * Caizhi Weng 
> > * Fang Yong 
> > * Feng Wang 
> > * Jingsong Lee 
> > * Nicholas Jiang 
> > * Robert Metzger 
> > * Stephan Ewen 
> > * Timo Walther 
> > * Yann Byron (Bi Yan) 
> > * Yu Li 
> > * Zelin Yu 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jingsong Lee be appointed
> > to the office of Vice President, Apache Paimon, 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 Paimon Project be and hereby is tasked wi

Re: [VOTE] Graduate Apache Celeborn (Incubating) as a Top Level Project

[Xinyu Zhou]

+1 binding

Regards,
Xinyu Zhou

On Mon, Mar 11, 2024 at 9:23 AM Willem Jiang  wrote:

> +1 (binding)
> Good luck!
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Mar 8, 2024 at 6:45 PM Yu Li  wrote:
> >
> > Hi All,
> >
> > We've got positive feedback on the DISCUSS thread for graduation [1],
> > and would like to start an official VOTE thread now.
> >
> > Below are some facts and project highlights from the incubation phase
> > as well as the draft resolution:
> >
> > - Currently, our community consists of 19 committers (including
> > mentors) from more than 10 companies, with 13 serving as PPMC members.
> > - So far, we have boasted 81 contributors.
> > - Throughout the incubation period, we've made 6 releases in 16
> > months, at a stable pace.
> > - We've had 6 different release managers to date.
> > - Our software is used in production by 10+ well known entities.
> > - As yet, we have opened 1,302 issues with 1,191 successfully resolved.
> > - We have submitted a total of 1,840 PRs, out of which 1,830 have been
> > merged or closed.
> > - We have met all maturity criteria as outlined in [2].
> >
> > Please vote on the resolution pasted below to graduate Apache Celeborn
> > from the Incubator to the Top Level Project.
> >
> >  [ ] +1 Graduate Apache Celeborn from the Incubator.
> >  [ ] +0 No opinion.
> >  [ ] -1 Don't graduate Apache Celeborn from the Incubator because ...
> >
> > This vote will open for at least 72 hours.
> >
> > We would like to thank everyone who have participated in the Apache
> > Celeborn community. We would also like to thank the Apache Incubator
> > community as well as Apache Infrastructure team and general ASF
> > community for your support.
> >
> > [1] https://lists.apache.org/thread/9gyhhnhj5osjom38v9ws1b7o7fbf7fqh
> > [2]
> https://cwiki.apache.org/confluence/display/CELEBORN/Apache+Maturity+Model+Assessment+for+Celeborn
> >
> > ---
> >
> > Establish the Apache Celeborn 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 an intermediate data service for big data computing engines
> > to boost performance, stability, and flexibility.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Celeborn Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Celeborn Project be and hereby is responsible
> > for the creation and maintenance of software related to an intermediate
> > data service for big data computing engines to boost performance,
> > stability, and flexibility; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Celeborn" 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 Celeborn
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache Celeborn
> > 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 Celeborn
> > Project:
> >
> > * Becket Qin 
> > * Cheng Pan 
> > * Duo Zhang 
> > * Ethan Feng 
> > * Fu Chen 
> > * Jiashu Xiong 
> > * Kerwin Zhang 
> > * Keyong Zhou 
> > * Lidong Dai 
> > * Willem Ning Jiang 
> > * Wu Wei 
> > * Yi Zhu 
> > * Yu Li 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keyong Zhou be appointed to
> > the office of Vice President, Apache Celeborn, 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 Celeborn Project be and hereby is tasked with
> > the migration and rationalization of the Apache Incubator Celeborn
> > podling; and be it further
> >
> > RESOLVED, that all respons

Re: [VOTE] Have Amoro join the Incubator

[Xinyu Zhou]

+1 binding

Good Luck~

Regards,
Xinyu Zhou

On Mon, Mar 4, 2024 at 11:25 AM Shaoyun Chen  wrote:

> +1 (non-binding)
>
> Huajie Wang  于2024年3月4日周一 10:54写道：
> >
> > +1 (non-binding)
> >
> >
> > Best,
> > Huajie Wang
> >
> >
> >
> > ConradJam  于2024年3月4日周一 10:39写道：
> >
> > > +1 (non-binding)
> > >
> > > Best
> > >
> > > Bi Yan  于2024年3月4日周一 10:19写道：
> > >
> > > > +1 (non-binding)
> > > >
> > > > Best Wishes ~
> > > > Yann
> > > >
> > > > On 2024/03/03 01:44:24 Justin Mclean wrote:
> > > > > Hi,
> > > > >
> > > > > Following on from the discussion of the Amoro proposal [1][2],
> let's
> > > > vote on having it join the Incubator.
> > > > >
> > > > > Please cast your vote:
> > > > >
> > > > > [ ] +1, have it join the Incubator as an incubating project
> > > > > [ ] +0, I have no strong opinion either way
> > > > > [ ] -1, do not have it join the Incubator because...
> > > > >
> > > > > Kind Regards,
> > > > > Justin
> > > > >
> > > > > 1.
> https://cwiki.apache.org/confluence/display/INCUBATOR/AmoroProposal
> > > > > 2.
> https://lists.apache.org/thread/7t2bm6x19zq2d79cn8jj2wqd3f2t3k00
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> > > --
> > > Best
> > >
> > > ConradJam
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Apache Amoro proposal

[Xinyu Zhou]

+1, as one of the mentors, over the past few months, I have seen
significant progress within this community.

Regards,
Xinyu Zhou

On Mon, Feb 26, 2024 at 10:53 AM Xavier Bai  wrote:

> +1, I was also one of the early developers on the project, focusing on
> solving optimization and compaction issues with the company's Iceberg
> tables. I believe that many teams using datalake need a system like Amoro
> for effective data lake management and to reduce the complexity of data
> lake maintenance. Therefore, contributing it to ASF can enrich the usage
> scenarios and enhance datalake management capabilities.
>
> Thanks,
> Xu
>
> ConradJam  于2024年2月26日周一 10:12写道：
>
> > +1, I'm one of the developers. At present, I think the community is
> > developing well, and this project can help everyone better control the
> data
> > lake. I suggest joining the ASF incubator to let more people know about
> > this project and participate in it
> >
> > Justin Mclean  于2024年2月23日周五 16:44写道：
> >
> > > Hi,
> > >
> > > I would like to propose a new project to the ASF incubator - Apache
> > Amoro.
> > > I’m one of the mentors, but there are a lot of other people involved
> who
> > > have done all of the hard work.
> > >
> > > Amoro is a Lakehouse management system built on open data lake formats
> > > like Apache Iceberg and Apache Paimon (Incubating). Working with
> compute
> > > engines including Apache Flink, Apache Spark, and Trino, Amoro brings
> > > pluggable and self-managed features for Lakehouse to provide
> > out-of-the-box
> > > data warehouse experience, and helps data platforms or products easily
> > > build infra-decoupled, stream-and-batch-fused and lake-native
> > architecture.
> > > You can find the proposal here. [1]
> > >
> > > We are looking forward to anyone's feedback or questions.
> > >
> > > Thanks,
> > > Justin
> > >
> > > [1]
> https://cwiki.apache.org/confluence/display/INCUBATOR/AmoroProposal
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > --
> > Best
> >
> > ConradJam
> >
>

Re: [VOTE] Release Apache Paimon (Incubating) 0.7.0-RC1

[Xinyu Zhou]

Got it, +1 binding, thanks.

Regards,

On Mon, Feb 5, 2024 at 2:33 PM yu zelin  wrote:

> Hi Xinyu,
>
> Thanks for your reminder. This test is unstable. I re-run it and it passes
> this time.
> Please take a look, thanks.
>
> Best Regards,
> Zelin Yu
>
> > 2024年2月5日 13:12，Xinyu Zhou  写道：
> >
> > Hi Zelin,
> >
> > There is a test error
> >
> https://github.com/apache/incubator-paimon/actions/runs/7663292516/job/21054778493
> > for the 0.7.0-RC1 release. Is it an ignorable error?
> >
> > Regards,
> >
> > On Sun, Feb 4, 2024 at 12:40 PM Xuanwo  wrote:
> >
> >> Hi Yu,
> >>
> >> Got it. Thanks for sharing.
> >>
> >> On Sun, Feb 4, 2024, at 12:37, Yu Li wrote:
> >>> Hi Xuanwo,
> >>>
> >>> I just do manual checks without any magic scripts or tools, mainly
> >> focusing
> >>> on bundled-dependency-related commits. More specifically, any change on
> >> pom
> >>> files would draw my attention (whether there are any new bundled
> >>> dependencies introduced and correctly reflected in the NOTICE/LICENSE
> >>> files, etc.).
> >>>
> >>> Best Regards,
> >>> Yu
> >>>
> >>>
> >>> On Fri, 2 Feb 2024 at 14:53, Xuanwo  wrote:
> >>>
> >>>> Hi, Yu Li
> >>>>
> >>>> Could you please share how you check for differences in better
> versions?
> >>>> Since
> >>>> the changes could be significant, I assume there are specific points
> you
> >>>> focus
> >>>> on while checking. I would like to learn how to verify releases more
> >>>> effectively.
> >>>>
> >>>> Thank you in advance.
> >>>>
> >>>> On Fri, Feb 2, 2024, at 13:53, Yu Li wrote:
> >>>>> +1 (binding)
> >>>>>
> >>>>> - Checked the diff between 0.6.0 and 0.7.0-rc1: *OK* (
> >>>>>
> >>>>
> >>
> https://github.com/apache/incubator-paimon/compare/release-0.6.0-incubating...release-0.7.0-incubating-rc1
> >>>>> )
> >>>>> - Checked release file name and location: *OK*
> >>>>> - Checked sum and signatures: *OK*
> >>>>> - Checked DISCLAIMER file exists: *OK*
> >>>>> - Checked LICENSE and NOTICE files: *OK*
> >>>>> - Checked no binary files in source package: *OK*
> >>>>> - Checked compile from source: *OK* (JDK 11u21)
> >>>>>
> >>>>> Best Regards,
> >>>>> Yu
> >>>>>
> >>>>>
> >>>>> On Wed, 31 Jan 2024 at 22:25, Xuanwo  wrote:
> >>>>>
> >>>>>> +1 non-binding
> >>>>>>
> >>>>>> [x] Download links are valid
> >>>>>> [x] Checksums and signatures
> >>>>>>
> >>>>>> apache-paimon-0.7.0-incubating-src.tgz
> >>>>>> gpg: Signature made Fri 26 Jan 2024 02:34:51 PM CST
> >>>>>> gpg:using EDDSA key
> >>>>>> C81651102A8CE408792BA26FBD268155D61737A1
> >>>>>> gpg: Good signature from "Zelin Yu "
> >> [ultimate]
> >>>>>>
> >>>>>> [x] LICENSE/NOTICE files exist
> >>>>>> [x] NO unexpected binary files
> >>>>>> [x] Source files have ASF headers
> >>>>>> [x] Can compile from source
> >>>>>>
> >>>>>> Build passed on archlinux x86_64
> >>>>>>
> >>>>>> [INFO] Reactor Summary for Paimon : 0.7.0-incubating:
> >>>>>> [INFO]
> >>>>>> [INFO] Paimon : ... SUCCESS
> [
> >>>>>> 1.491 s]
> >>>>>> [INFO] Paimon : Test utils  SUCCESS
> [
> >>>>>> 8.218 s]
> >>>>>> [INFO] Paimon : Common  SUCCESS
> [
> >>>>>> 10.314 s]
> >>>>>> [INFO] Paimon : Benchmark . SUCCESS
> [
> >>>>>> 0.048 s]
> >>>>>> [INFO] Paimon : Benchmark : Cluster ... SUCCESS
> [
> >>>>>> 22.164 s]
> >>>>>> [INFO] Paimon : Code Gen ...

Re: [VOTE] Release Apache Paimon (Incubating) 0.6.1-RC3

[Xinyu Zhou]

+1 binding, I have checked:
[x] Checksums and PGP signatures are valid.
[x] Build the source release successfully
[x] DISCLAIMER,  LICENSE, and NOTICE files exist in the source release.
[x] Git commit hash is correct.

Regards,
Xinyu Zhou



On Sun, Feb 4, 2024 at 12:40 PM Yu Li  wrote:

> +1 (binding)
>
> - Checked the diff between 0.6.0 and 0.6.1-rc3: *OK* (
>
> https://github.com/apache/incubator-paimon/compare/release-0.6.0-incubating...release-0.6.1-incubating-rc3
> )
>* No bundled dependency change observed.
> - Checked release file name and location: *OK*
> - Checked sum and signatures: *OK*
> - Checked DISCLAIMER file exists: *OK*
> - Checked LICENSE and NOTICE files: *OK*
> - Checked no binary files in source package: *OK*
> - Checked compile from source: *OK* (JDK 11u21)
>
> Best Regards,
> Yu
>
>
> On Sun, 4 Feb 2024 at 12:19, Xiaoqiao He  wrote:
>
> > +1(binding)
> >
> > [x] Download links are valid.
> > [x] Checksums and PGP signatures are valid.
> > [x] LICENSE files exist.
> > [x] NOTICE is included.
> > [x] DISCLAIMER is included.
> > [x] Source code artifacts have correct names matching the current
> release.
> > [x] All source files have license headers if necessary.
> > [x] Build successfully with command `mvn clean install -DskipTests` on
> > JDK-1.8.0_202.
> >
> > One nit but not blocker issue about vote counter[1]. We should count with
> > RM's vote here.
> > Good Luck!
> >
> > [1] https://lists.apache.org/thread/looh8mvljpx2th444mkt6wlo5gy8yprn
> >
> > Best Regards,
> > - He Xiaoqiao
> >
> >
> > On Tue, Jan 30, 2024 at 8:25 PM Suyan  wrote:
> >
> > > +1 non-binding
> > >
> > > [x] Download links are valid
> > > [x] Checksums and signatures
> > > gpg: assuming signed data in './apache-paimon-0.6.1-incubating-src.tgz'
> > > gpg: Signature made 二  1/23 11:21:15 2024 CST
> > > gpg:using EDDSA key
> > > 5E4E56F56580BAD644ED84E68FEBA0ECFC7200B4
> > > gpg: Good signature from "biyan " [ultimate]
> > > [x] LICENSE/NOTICE files exist
> > > [x] NO unexpected binary files
> > > [x] Source files have ASF headers
> > > [x] Can compile from source on macOS with Apple Silicon M1(arm64)
> > >
> > > [INFO]
> > >
> 
> > > [INFO] Reactor Summary for Paimon : 0.6.1-incubating:
> > > [INFO]
> > > [INFO] Paimon : ... SUCCESS [
> > > 10.125 s]
> > > [INFO] Paimon : Test utils  SUCCESS [
> > > 10.242 s]
> > > [INFO] Paimon : Common  SUCCESS
> > [01:00
> > > min]
> > > [INFO] Paimon : Benchmark . SUCCESS [
> > > 0.415 s]
> > > [INFO] Paimon : Benchmark : Cluster ... SUCCESS [
> > > 14.914 s]
> > > [INFO] Paimon : Code Gen .. SUCCESS [
> > > 55.173 s]
> > > [INFO] Paimon : Code Gen Loader ... SUCCESS [
> > > 4.735 s]
> > > [INFO] Paimon : Format  SUCCESS [
> > > 14.681 s]
> > > [INFO] Paimon : Core .. SUCCESS [
> > > 25.327 s]
> > > [INFO] Paimon : FileSystems : . SUCCESS [
> > > 0.295 s]
> > > [INFO] Paimon : FileSystems : S3 : Impl ... SUCCESS [
> > > 7.168 s]
> > > [INFO] Paimon : FileSystems : S3 .. SUCCESS [
> > > 23.235 s]
> > > [INFO] Paimon : Hive .. SUCCESS [
> > > 0.170 s]
> > > [INFO] Paimon : Hive Common ... SUCCESS [
> > > 4.571 s]
> > > [INFO] Paimon : Hive Catalog .. SUCCESS [
> > > 7.079 s]
> > > [INFO] Paimon : Bundle  SUCCESS [
> > > 5.677 s]
> > > [INFO] Paimon : Benchmark : Micro . SUCCESS [
> > > 2.002 s]
> > > [INFO] Paimon : Flink . SUCCESS [
> > > 1.242 s]
> > > [INFO] Paimon : Flink : Common  SUCCESS [
> > > 20.629 s]
> > > [INFO] Paimon : Flink : CDC ... SUCCESS [
> > > 10.717 s]
> > > [INFO] Paimon : Flink : 1.14 .. SUCCESS [
&g

Re: [VOTE] Release Apache Paimon (Incubating) 0.7.0-RC1

[Xinyu Zhou]

Hi Zelin,

There is a test error
https://github.com/apache/incubator-paimon/actions/runs/7663292516/job/21054778493
for the 0.7.0-RC1 release. Is it an ignorable error?

Regards,

On Sun, Feb 4, 2024 at 12:40 PM Xuanwo  wrote:

> Hi Yu,
>
> Got it. Thanks for sharing.
>
> On Sun, Feb 4, 2024, at 12:37, Yu Li wrote:
> > Hi Xuanwo,
> >
> > I just do manual checks without any magic scripts or tools, mainly
> focusing
> > on bundled-dependency-related commits. More specifically, any change on
> pom
> > files would draw my attention (whether there are any new bundled
> > dependencies introduced and correctly reflected in the NOTICE/LICENSE
> > files, etc.).
> >
> > Best Regards,
> > Yu
> >
> >
> > On Fri, 2 Feb 2024 at 14:53, Xuanwo  wrote:
> >
> >> Hi, Yu Li
> >>
> >> Could you please share how you check for differences in better versions?
> >> Since
> >> the changes could be significant, I assume there are specific points you
> >> focus
> >> on while checking. I would like to learn how to verify releases more
> >> effectively.
> >>
> >> Thank you in advance.
> >>
> >> On Fri, Feb 2, 2024, at 13:53, Yu Li wrote:
> >> > +1 (binding)
> >> >
> >> > - Checked the diff between 0.6.0 and 0.7.0-rc1: *OK* (
> >> >
> >>
> https://github.com/apache/incubator-paimon/compare/release-0.6.0-incubating...release-0.7.0-incubating-rc1
> >> > )
> >> > - Checked release file name and location: *OK*
> >> > - Checked sum and signatures: *OK*
> >> > - Checked DISCLAIMER file exists: *OK*
> >> > - Checked LICENSE and NOTICE files: *OK*
> >> > - Checked no binary files in source package: *OK*
> >> > - Checked compile from source: *OK* (JDK 11u21)
> >> >
> >> > Best Regards,
> >> > Yu
> >> >
> >> >
> >> > On Wed, 31 Jan 2024 at 22:25, Xuanwo  wrote:
> >> >
> >> >> +1 non-binding
> >> >>
> >> >> [x] Download links are valid
> >> >> [x] Checksums and signatures
> >> >>
> >> >> apache-paimon-0.7.0-incubating-src.tgz
> >> >> gpg: Signature made Fri 26 Jan 2024 02:34:51 PM CST
> >> >> gpg:using EDDSA key
> >> >> C81651102A8CE408792BA26FBD268155D61737A1
> >> >> gpg: Good signature from "Zelin Yu "
> [ultimate]
> >> >>
> >> >> [x] LICENSE/NOTICE files exist
> >> >> [x] NO unexpected binary files
> >> >> [x] Source files have ASF headers
> >> >> [x] Can compile from source
> >> >>
> >> >> Build passed on archlinux x86_64
> >> >>
> >> >> [INFO] Reactor Summary for Paimon : 0.7.0-incubating:
> >> >> [INFO]
> >> >> [INFO] Paimon : ... SUCCESS [
> >> >> 1.491 s]
> >> >> [INFO] Paimon : Test utils  SUCCESS [
> >> >> 8.218 s]
> >> >> [INFO] Paimon : Common  SUCCESS [
> >> >> 10.314 s]
> >> >> [INFO] Paimon : Benchmark . SUCCESS [
> >> >> 0.048 s]
> >> >> [INFO] Paimon : Benchmark : Cluster ... SUCCESS [
> >> >> 22.164 s]
> >> >> [INFO] Paimon : Code Gen .. SUCCESS [
> >> >> 13.455 s]
> >> >> [INFO] Paimon : Code Gen Loader ... SUCCESS [
> >> >> 1.154 s]
> >> >> [INFO] Paimon : Format  SUCCESS [
> >> >> 4.134 s]
> >> >> [INFO] Paimon : Core .. SUCCESS [
> >> >> 5.679 s]
> >> >> [INFO] Paimon : FileSystems : . SUCCESS [
> >> >> 0.036 s]
> >> >> [INFO] Paimon : FileSystems : S3 : Impl ... SUCCESS [
> >> >> 2.481 s]
> >> >> [INFO] Paimon : FileSystems : S3 .. SUCCESS [
> >> >> 15.319 s]
> >> >> [INFO] Paimon : Hive .. SUCCESS [
> >> >> 0.038 s]
> >> >> [INFO] Paimon : Hive Common ... SUCCESS [
> >> >> 0.619 s]
> >> >> [INFO] Paimon : Hive Catalog .. SUCCESS [
> >> >> 0.965 s]
> >> >> [INFO] Paimon : Bundle  SUCCESS [
> >> >> 2.577 s]
> >> >> [INFO] Paimon : Benchmark : Micro . SUCCESS [
> >> >> 0.300 s]
> >> >> [INFO] Paimon : Service ... SUCCESS [
> >> >> 0.034 s]
> >> >> [INFO] Paimon : Service : Client .. SUCCESS [
> >> >> 0.258 s]
> >> >> [INFO] Paimon : Service : Runtime . SUCCESS [
> >> >> 0.328 s]
> >> >> [INFO] Paimon : Flink . SUCCESS [
> >> >> 0.982 s]
> >> >> [INFO] Paimon : Flink : Common  SUCCESS [
> >> >> 26.907 s]
> >> >> [INFO] Paimon : Flink : CDC ... SUCCESS [
> >> >> 19.482 s]
> >> >> [INFO] Paimon : Flink : 1.14 .. SUCCESS [
> >> >> 2.926 s]
> >> >> [INFO] Paimon : Flink : 1.15 .. SUCCESS [
> >> >> 2.948 s]
> >> >> [INFO] Paimon : Flink : 1.16 .. SUCCESS [
> >> >> 2.718 s]
> >> >> [INFO] Paimon : Flink : 1.17 .. SUCCESS [
> >> >> 2.507 s]

Re: [VOTE] Release Apache Celeborn(Incubating) 0.3.2-incubating-rc2

[Xinyu Zhou]

+1 binding, I have checked:
[x] Checksums and PGP signatures are valid.
[x] Build the source release successfully for one of the maven profiles.
[x] DISCLAIMER,  LICENSE, and NOTICE files exist in both the source and
binary releases.
[x] Git commit hash is correct.

Regards,
Xinyu Zhou

On Tue, Jan 2, 2024 at 3:48 PM Cheng Pan  wrote:

> This release process spans the 2024 New Year's Day, I have raised a PR[1]
> this morning to update the NOTICE year. It will be included in the next
> release if it’s not a blocking issue.
>
> [1] https://github.com/apache/incubator-celeborn/pull/2198
>
> Thanks,
> Cheng Pan
>
>
> > On Jan 2, 2024, at 15:37, Kent Yao  wrote:
> >
> > +1 (binding), I have checked:
> >
> > [✓] The checksums and signatures are validated
> > [ ] The LICENSE is fine, but NOTICE files[1-6] need to be updated to
> 2024(I'm not sure whether this is a blocker not but better to be fixed).
> > [✓] DISCLAIMER is present
> > [✓] No binary files found in the source release
> > [✓] Incubating in the name
> > [✓] Built from source
> >
> > Kent Yao
> >
> > [1] ./NOTICE
> > [2] ./client-spark/spark-3-shaded/src/main/resources/META-INF/NOTICE
> > [3] ./client-spark/spark-2-shaded/src/main/resources/META-INF/NOTICE
> > [4] ./client-flink/flink-1.14-shaded/src/main/resources/META-INF/NOTICE
> > [5] ./client-flink/flink-1.15-shaded/src/main/resources/META-INF/NOTICE
> > [6] ./client-flink/flink-1.17-shaded/src/main/resources/META-INF/NOTICE
> >
> >
> > On 2024/01/02 03:11:27 Nicholas Jiang wrote:
> >> Hi IPMC,
> >>
> >> This is a call for a vote to release Apache Celeborn (Incubating)
> >> 0.3.2-incubating-rc2
> >>
> >> The Apache Celeborn community has voted on and approved a proposal to
> >> release Apache Celeborn (Incubating) version 0.3.2-incubating-rc2.
> >> We now kindly request the Incubator PMC members review and vote on this
> >> incubator release.
> >>
> >> celeborn@dev vote thread:
> >>
> >> https://lists.apache.org/thread/zq5kb3ovr53xkocgh0jyx30nsrjqw9do
> >>
> >> celeborn@dev vote result thread:
> >>
> >> https://lists.apache.org/thread/d5djbkc4tdn1t06bpr9wbgryswvp2fm8
> >>
> >> The git tag to be voted upon:
> >>
> >>
> https://github.com/apache/incubator-celeborn/releases/tag/v0.3.2-incubating-rc2
> >>
> >> The git commit hash:
> >> 0dccad38e28554c36a5eef98de2540d996f946f7
> >>
> >> The source and binary artifacts can be found at:
> >>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.3.2-incubating-rc2
> >>
> >> The staging repo:
> >>
> >>
> https://repository.apache.org/content/repositories/orgapacheceleborn-1048
> >>
> >> Fingerprint of the PGP key release artifacts are signed with:
> >> D73CADC1DAB63BD3C770BB6D9476842D24B7C885
> >>
> >> My public key to verify signatures can be found in:
> >>
> >> https://dist.apache.org/repos/dist/release/incubator/celeborn/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 (and the reason)
> >>
> >> Checklist for release:
> >>
> >>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >>
> >> Steps to validate the release:
> >>
> >> https://www.apache.org/info/verification.html
> >>
> >> Instructions for making binary artifacts from source:
> >> build/make-distribution.sh --release
> >>
> >> Regards,
> >> Nicholas Jiang
> >
> > -
> > 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 Celeborn(Incubating) 0.3.2-incubating-rc1

[Xinyu Zhou]

+1 binding

I checked:
[x] Checksums and PGP signatures are valid.
[x] Build the source release successfully for one of the maven profiles.

Regards,
Xinyu Zhou

On Mon, Dec 25, 2023 at 11:24 AM Nicholas Jiang 
wrote:

> Hi IPMC,
>
>
>
> This is a call for a vote to release Apache Celeborn (Incubating)
>
> 0.3.2-incubating-rc1
>
>
> The Apache Celeborn community has voted on and approved a proposal to
> release Apache Celeborn (Incubating) version 0.3.2-incubating-rc1.
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> celeborn@dev vote thread:
>
> https://lists.apache.org/thread/w1jz9018p1cj9x0624oq86f9wo5wz1wd
>
> celeborn@dev vote result thread:
>
> https://lists.apache.org/thread/gqsg2o41tvfxd6vok809jcjg99m8wyv6
>
> The git tag to be voted upon:
>
>
> https://github.com/apache/incubator-celeborn/releases/tag/v0.3.2-incubating-rc1
>
> The git commit hash:
> bce190d8a0a53434ef57ef33e53720f5bf4d14d6
>
> The source and binary artifacts can be found at:
>
>
> https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.3.2-incubating-rc1
>
> The staging repo:
>
> https://repository.apache.org/content/repositories/orgapacheceleborn-1045
>
>
> Fingerprint of the PGP key release artifacts are signed with:
> D73CADC1DAB63BD3C770BB6D9476842D24B7C885
>
> My public key to verify signatures can be found in:
>
> https://dist.apache.org/repos/dist/release/incubator/celeborn/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 (and the reason)
>
> Checklist for release:
>
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Steps to validate the release:
>
> https://www.apache.org/info/verification.html
>
>
> Instructions for making binary artifacts from source:
> build/make-distribution.sh --release
>
> Regards,
> Nicholas Jiang

Re: [VOTE] Accept Seata Into the ASF Incubator

[Xinyu Zhou]

+1 binding

Regards,
Xinyu Zhou

On Wed, Oct 25, 2023 at 5:40 PM Willem Jiang  wrote:

> +1 binding.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sat, Oct 21, 2023 at 8:51 PM Sheng Wu 
> wrote:
> >
> > Hi Incubator
> >
> > Following the discussion from <[DISCUSS] Incubating Proposal of
> Seata>[1],
> > I am starting this official vote for the Seata project.
> >
> > Here is their proposal,
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal
> >
> > Please cast your vote:
> >
> > [ ] +1, bring into the Incubator
> > [ ] +0, I don't care either way
> > [ ] -1, do not bring Seata into the Incubator, because...
> >
> > The vote will open for one week from today, Oct. 21st, 2023
> >
> > [1] https://lists.apache.org/thread/jtg7tt725r9mf35gqxph65vz8gdbwq94
> >
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> > -
> > 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] Accept OpenDAL into the Apache Incubator

[Xinyu Zhou]

+1, Good luck.

Regards,

On Wed, Feb 22, 2023 at 10:12 AM Xiaoqiao He  wrote:

> +1(binding).
>
> Best Regards,
> - He Xiaoqiao
>
> On Wed, Feb 22, 2023 at 9:43 AM Xin Wang  wrote:
>
> > +1
> > Look forward to a growing and healthy community during the incubation
> > period.
> >
> > Willem Jiang  于2023年2月22日周三 09:04写道：
> >
> > > +1(binding).
> > > I'm looking forward to working with this project as a mentor.
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > >
> > > On Tue, Feb 21, 2023 at 9:24 PM tison  wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Following up on the [DISCUSS] thread on OpenDAL[1], I would like to
> > call
> > > a
> > > > VOTE to accept OpenDAL into the Apache Incubator, please check out
> the
> > > > OpenDAL Proposal from the incubator wiki[2].
> > > >
> > > > Please cast your vote:
> > > >
> > > > [ ] +1, bring OpenDAL into the Incubator
> > > > [ ] +0, I don't care either way
> > > > [ ] -1, do not bring OpenDAL into the Incubator, because...
> > > >
> > > > The vote will open at least for 72 hours, and only votes from the
> > > Incubator
> > > > PMC members are binding, but votes from everyone are welcome.
> > > >
> > > > [1] https://lists.apache.org/thread/px7wjcjy3rd4s59d4d3ll1x6y11d240r
> > > > [2]
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/OpenDAL+Proposal
> > > >
> > > > Best,
> > > > tison.
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > --
> > Thanks,
> > Xin
> >
>

Re: [DISCUSS] Incubating Proposal for OpenDAL

[Xinyu Zhou]

+1 Like the slogan of OpenDAL.

Storage software is increasingly adopting Rust, OpenDAL hides the
complexity of cloud storage and enables users to leverage the benefits of
cloud storage easily.

On Fri, Feb 17, 2023 at 7:21 AM tison  wrote:

> Hi IPMC,
>
> I would like to propose OpenDAL[1] as a new apache incubator project, you
> can find the proposal[2] of OpenDAL for more detail.
>
> [1] https://github.com/datafuselabs/opendal
> [2] https://cwiki.apache.org/confluence/display/INCUBATOR/OpenDAL+Proposal
>
> Best,
> tison.
>
> Full text of the proposal below:
>
> ## Abstract
>
> OpenDAL means “Open Data Access Layer”. It’s a Rust library that helps
> developers access data freely, painlessly, and efficiently over multiple
> services, including AWS S3, HDFS, POSIX-compatible file systems, and so on.
>
> ## Proposal
>
> OpenDAL provides the following features to support developers accessing
> data freely, painlessly, and efficiently:
>
> - Freely
> - Access different storage services in the same way
> - Behavior tests for all services
> - Cross-language/project bindings (working in progress)
> - Painlessly
> - **100%** of documents covered
> - Powerful [Layers](
> https://opendal.databend.rs/opendal/layers/index.html)
> - Automatic [retry](
> https://opendal.databend.rs/opendal/layers/struct.RetryLayer.html) support
> - Full observability support: [logging](
> https://opendal.databend.rs/opendal/layers/struct.LoggingLayer.html
> ), [tracing](
> https://opendal.databend.rs/opendal/layers/struct.TracingLayer.html), and
> [metrics](
> https://opendal.databend.rs/opendal/layers/struct.MetricsLayer.html).
> - Native chaos testing
> - Native service-side encryption support
> - Efficiently
> - Zero cost: mapping to underlying API calls directly
> - Best effort: auto-pick the best `read`/`seek`/`next` implementations
> based on services
> - [Auto metadata reuse](
> https://opendal.databend.rs/rfcs/0561-list-metadata-reuse.html): avoid
> extra `metadata` calls
>
> OpenDAL was originally designed to be used by the Databend project but is
> now being used by Mozilla's sccache, DeepETH's mars, and several database
> startups.
>
> We believe that the OpenDAL project will provide diversity value to the
> community if OpenDAL is brought into the Apache incubator.
>
> ## Background
>
> OpenDAL is being developed by an open-source community from day one and is
> owned by DatafuseLabs. The project has been launched in February 2022.
>
> ## Rationale
>
> OpenDAL provides a unified storage abstraction layer that simplifies the
> interfacing of different storage services. In addition, OpenDAL provides
> further advanced storage encapsulation, enabling enhancements such as
> automatic retry, request optimization, and observability. OpenDAL makes it
> possible to develop once and run on any storage service.
>
> ## Initial Goals
>
> By transferring ownership of the project to the ASF, OpenDAL expects to
> ensure its neutrality and further encourage and facilitate the adoption of
> OpenDAL by the community.
>
> Some of the areas we would like to focus on during the Apache incubation
> phase include:
>
> - A healthier community: more maintainers and contributors will be able to
> participate in OpenDAL and own different modules.
> - Wider adoption: OpenDAL can be adopted by more open source/commercial
> projects, which in turn drives its own functionality.
> - Richer integration: OpenDAL enables greater integration of storage
> services and offers a wider range of language bindings.
>
> ## Current Status
>
> ### Meritocracy
>
> We intend to radically expand the initial developer and user community by
> running the project the 'Apache way'. Users and new contributors will be
> respected and welcomed. They will earn credit by participating in the
> community and providing quality patches/support to move the project
> forward. They will also be encouraged to provide non-code contributions
> (documentation, events, community management, etc.) and will be rewarded
> accordingly. Those with a proven track record of support and quality will
> be encouraged to become committers.
>
> ### Community
>
> Contributors: 37
>
> Users:
>
> - Databend: A cloud data warehouse
> - GreptimeDB: A time-series database
> - Sccache: ccache with cloud storage
> - RisingWave: A Distributed SQL Database for Stream Processing
>
> ### Core Developers
>
> The core developers are all experienced open-source developers. They have
> been running the OpenDAL community for 1 year.
>
> ### Alignment
>
> ## Known Risks
>
> ### Project Name
>
> We have checked and believe that the name is appropriate and that the
> project has legal permission to continue using its current name. There are
> no other projects with this name found in a Google search.
>
> ### Orphan Products
>
> ### Inexperience with Open Source
>
> OpenDAL's core developers are all experienced open source contributors, and
> its main maintainer Xuanwo has 

Re: [VOTE] Graduate Apache DistributedLog as a subproject of Apache BookKeeper

[Xinyu Zhou]

+1

Regards,
yukon



On Fri, Jun 30, 2017 at 3:49am, Leigh Stewart < lstew...@twitter.com.invalid 
[lstew...@twitter.com.invalid] > wrote:
+1

On Jun 29, 2017 12:55 AM, "Von Gosling"  wrote:

> +1
>
> Best Regards,
> Von Gosling
>
>
> > 在 2017年6月29日，13:42，Sijie Guo  写道：
> >
> > +1
> >
> > On Wed, Jun 28, 2017 at 8:25 AM, John D. Ament 
> > wrote:
> >
> >> I have no idea why this is copying both public and private lists.
> >>
> >> I'm +1 to graduate.
> >>
> >> On Wed, Jun 28, 2017 at 8:06 AM Flavio Junqueira 
> wrote:
> >>
> >>> The Apache DistributedLog community has voted to graduate the project
> and
> >>> make it a subproject of Apache BookKeeper. The Apache BookKeeper PMC
> has
> >>> also voted to accept DistributedLog as a subproject. The links to the
> >> vote
> >>> threads are the following:
> >>>
> >>> DistributedLog PPMC vote:
> >>>
> >>> https://mail-search.apache.org/members/private-arch/
> >> distributedlog-private/201706.mbox/%3cCAO2yDyY3nzjtb934g-
> >> aryujswzjetktpupf_la0jkhf263f...@mail.gmail.com%3e
> >>> <
> >>> https://mail-search.apache.org/members/private-arch/
> >> distributedlog-private/201706.mbox/%3cCAO2yDyY3nzjtb934g-
> >> aryujswzjetktpupf_la0jkhf263f...@mail.gmail.com%3e
> 
> >>>
> >>> https://mail-search.apache.org/members/private-arch/
> >> distributedlog-private/201706.mbox/%3cCAO2yDybfqt72xGtrvR-
> 9eUYycHJvpCo5=
> >> ts87rzhpsm096r...@mail.gmail.com%3e
> >>> <
> >>> https://mail-search.apache.org/members/private-arch/
> >> distributedlog-private/201706.mbox/%3cCAO2yDybfqt72xGtrvR-
> 9eUYycHJvpCo5=
> >> ts87rzhpsm096r...@mail.gmail.com%3e
> 
> >>>
> >>> DistributedLog Community vote:
> >>>
> >>> http://mail-archives.apache.org/mod_mbox/incubator-
> >> distributedlog-dev/201706.mbox/%3cCAO2yDyZzinfGhjXqmVEHxDaULKw
> >> dt9v2nkqeyuzxe0i4tzg...@mail.gmail.com%3e
> >>> <
> >>> http://mail-archives.apache.org/mod_mbox/incubator-
> >> distributedlog-dev/201706.mbox/%3cCAO2yDyZzinfGhjXqmVEHxDaULKw
> >> dt9v2nkqeyuzxe0i4tzg...@mail.gmail.com%3e
> 
> >>>
> >>> http://mail-archives.apache.org/mod_mbox/incubator-
> >> distributedlog-dev/201706.mbox/%3cCAO2yDya-=
> 0cBfUM0SsL5kuf9HJ1G=pL7Z_=7Ps+
> >> TQgqwJs=c...@mail.gmail.com%3e
> >>> <
> >>> http://mail-archives.apache.org/mod_mbox/incubator-
> >> distributedlog-dev/201706.mbox/%3cCAO2yDya-=
> 0cBfUM0SsL5kuf9HJ1G=pL7Z_=7Ps+
> >> TQgqwJs=c...@mail.gmail.com%3e
> 
> >>>
> >>> BookKeeper PMC vote:
> >>>
> >>> https://mail-search.apache.org/members/private-arch/
> >> bookkeeper-private/201706.mbox/%3cCAO2yDyacdXuXh==iw1OqrRiuGoxHprP_
> >> htnofojot5rxmv6...@mail.gmail.com%3e
> >>> <
> >>> https://mail-search.apache.org/members/private-arch/
> >> bookkeeper-private/201706.mbox/%3cCAO2yDyacdXuXh==iw1OqrRiuGoxHprP_
> >> htnofojot5rxmv6...@mail.gmail.com%3e
> 
> >>>
> >>> https://mail-search.apache.org/members/private-arch/
> >> bookkeeper-private/201706.mbox/%3cCAO2yDyYzV_
> 7vVNg6Efyp3TPjddoYRyQx4rXvqP=
> >> W=c09qk2...@mail.gmail.com%3e
> >>> <
> >>> https://mail-search.apache.org/members/private-arch/
> >> bookkeeper-private/201706.mbox/%3cCAO2yDyYzV_
> 7vVNg6Efyp3TPjddoYRyQx4rXvqP=
> >> W=c09qk2...@mail.gmail.com%3e
> 
> >>>
> >>> This message is to start an IPMC vote. Please vote on the following:
> >>>
> >>> [ ] +1 Graduate Apache DistributedLog from the Incubator.
> >>> [ ] +0 No opinion
> >>> [ ] -1 Don't graduate Apache DistributedLog from the Incubator (please
> >>> provide
> >>> the reason)
> >>>
> >>> This VOTE will be opened for the next 72 hours.
> >>>
> >>> -Flavio
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Pulsar into the Apache Incubator

[Xinyu Zhou]

+1(non-binding)

Glad to see ASF will have another messaging solution~

On Fri, May 19, 2017 at 6:04pm, Luke Han < luke...@gmail.com 
[luke...@gmail.com] > wrote:
+1 (binding)


Best Regards!
-

Luke Han

On Thu, May 18, 2017 at 11:09 PM, Mohammad Noureldin <
nour.moham...@gmail.com> wrote:

> +1 (binding)
>
> On May 18, 2017 15:31, "Pierre Smits"  wrote:
>
> > +1, from the peanut gallery.
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > ORRTIZ.COM 
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Thu, May 18, 2017 at 1:03 AM, vintagewang 
> > wrote:
> >
> > > +1(non-binding)
> > >
> > > Pulsar is a powerful mq， I like it.
> > >
> > >
> > >
> > > On Wed, May 17, 2017 at 2:44 PM, Julian Hyde  wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > > On May 17, 2017, at 1:58 PM, Jia Zhai  wrote:
> > > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > On Thu, May 18, 2017 at 1:11 AM, P. Taylor Goetz <
> ptgo...@gmail.com>
> > > > wrote:
> > > > >
> > > > >> +1 (binding)
> > > > >>
> > > > >> -Taylor
> > > > >>
> > > > >>> On May 16, 2017, at 10:39 PM, Bryan Call 
> wrote:
> > > > >>>
> > > > >>> Hi All,
> > > > >>>
> > > > >>> As the champion for Pulsar, I would like to start a VOTE to bring
> > the
> > > > >>> project in as Apache incubator podling.
> > > > >>>
> > > > >>> The ASF voting rules are described:
> > > > >>>
> > > > >>> https://www.apache.org/foundation/voting.html
> > > > >>>
> > > > >>> A vote for accepting a new Apache Incubator podling is a majority
> > > vote
> > > > >> for which
> > > > >>> only Incubator PMC member votes are binding.
> > > > >>>
> > > > >>> This vote will run for at least 72 hours. Please VOTE as follows
> > > > >>> [] +1 Accept Pulsar into the Apache Incubator
> > > > >>> [] +0 Abstain.
> > > > >>> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> > > > >>>
> > > > >>> The proposal is listed below, but you can also access it on the
> > wiki:
> > > > >>>
> > > > >>> https://wiki.apache.org/incubator/PulsarProposal
> > > > >>>
> > > > >>> -Bryan
> > > > >>>
> > > > >>>
> > > > >>> = Pulsar Proposal =
> > > > >>>
> > > > >>> == Abstract ==
> > > > >>>
> > > > >>> Pulsar is a highly scalable, low latency messaging platform
> running
> > > on
> > > > >>> commodity hardware. It provides simple pub-sub semantics over
> > topics,
> > > > >>> guaranteed at-least-once delivery of messages, automatic cursor
> > > > >> management for
> > > > >>> subscribers, and cross-datacenter replication.
> > > > >>>
> > > > >>> == Proposal ==
> > > > >>>
> > > > >>> Pub-sub messaging is a very common design pattern that is
> > > increasingly
> > > > >> found
> > > > >>> in distributed systems powering Internet applications. These
> > > > applications
> > > > >>> provide real-time services, and need publish-latencies of 5ms on
> > > > average
> > > > >> and
> > > > >>> no more than 15ms at the 99th percentile. At Internet scale,
> these
> > > > >>> applications require a messaging system with ordering, strong
> > > > >> durability, and
> > > > >>> delivery guarantees. In order to handle the “five 9’s” durability
> > > > >> requirements
> > > > >>> of a production environment, the messages have to be committed on
> > > > >> multiple
> > > > >>> disks or nodes.
> > > > >>>
> > > > >>> Pulsar has been developed at Yahoo to address these specific
> > > > >> requirements by
> > > > >>> providing a hosted service supporting millions of topics for
> > multiple
> > > > >> tenants.
> > > > >>> The current incarnation of Pulsar has been open-sourced under
> > Apache
> > > > >> license
> > > > >>> in September 2016 and it is the direct evolution of systems that
> > were
> > > > >>> developed at Yahoo since 2011.
> > > > >>>
> > > > >>> We believe there is currently no other system that provides a
> > > > >> multi-tenant
> > > > >>> hosted messaging platform capable of supporting a huge number of
> > > topics
> > > > >> while
> > > > >>> maintaining strict guarantees for durability, ordering and low
> > > latency.
> > > > >>> Current solutions would require to run multiple individual
> clusters
> > > > with
> > > > >>> additional operational work and capacity overhead.
> > > > >>>
> > > > >>> Since the open sourcing of Pulsar, the development has been done
> > > > >> exclusively
> > > > >>> on the public Github repository and two major releases were
> shipped
> > > > >> (1.15 and
> > > > >>> 1.16), along with multiple minor ones. Several other companies
> have
> > > > >> expressed
> > > > >>> interest in the project and its future direction.
> > > > >>>
> > > > >>> == Rationale ==
> > > > >>>
> > > > >>> Pulsar is a platform that is built on top of several other Apache
> > > > >> projects. In
> > > > >>> particular, Apache BookKeeper is used to store the data and
> Apache
> > > > 

Re: [PROPOSAL] Pulsar - proposal for Apache Incubation

[Xinyu Zhou]

Hi Matteo,
Glad to see you and Pulsar are here.
John's idea is interesting and need to pay attention on it. There are so 
many messaging systems in ASF or other organizations, share client 
libraries between these products really make sense and will bring great 
benefit for our user.
But as Matteo said, this task is very complicated, due to different models 
and semantics. So we initiate a brand-new OpenMessaging specification, hope 
this spec can establish a interconnected bridge between diverse messaging 
solutions.

Regards, yukon Apache RocketMQ Committer
On Thu, Apr 27, 2017 at 4:41 PM, Jochen Theodorou  
wrote:



On 26.04.2017 23:19, Joe Francis wrote:
>
> Dear Apache Incubator Community,
>
>
> We would like to submit the Pulsar proposal to the incubator. Our draft 
is

> available at:
> https://wiki.apache.org/incubator/PulsarProposal
>
> A quick overview of Pulsar:
>
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub semantics over topics,
> guaranteed at-least-once delivery of messages, automatic cursor 
management for

> subscribers, and cross-datacenter replication.

Without really knowing the details of a messaging platform and even with
the danger of comparing apples and oranges... how would you compare for
example hazelcast based messaging to pulsar?

bye Jochen

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

Re: [VOTE] Weex to enter the Apache Incubator

[Xinyu Zhou]

+1
On 周五, 11月 25, 2016 at 5:05 下午, Feng Longda  wrote:
+1




2016-11-25 16:50 GMT+08:00 John D. Ament :
> +1
>
> On Thu, Nov 24, 2016 at 5:47 PM Edward J. Yoon 
> wrote:
>
>> Greetings!
>>
>> I would like to call a vote for accepting "Weex" for incubation in the
>> Apache Incubator. The full proposal is available below. We ask the
>> Incubator PMC to sponsor it, with myself (Edward J. Yoon) as Champion, and
>> Luke Han, Willem Jiang, Stephan Ewen, and Niclas Hedhman volunteering to be
>> Mentors.
>>
>> Please cast your vote:
>>
>> [ ] +1, bring Weex into Incubator
>> [ ] +0, I don't care either way,
>> [ ] -1, do not bring Weex into Incubator, because...
>>
>> This vote will be open at least for 72 hours and only votes from the
>> Incubator PMC are binding.
>>
>> --
>> https://wiki.apache.org/incubator/WeexProposal
>>
>> = Weex Proposal =
>>
>> == Abstract ==
>> Weex is a framework for building Mobile cross-platform high performance UI.
>> Weex enables developers to use Web-like syntax to build iOS, Android and
>> Web
>> UI with a single codebase.
>>
>> == Proposal ==
>> Weex provide an uniform Web-like syntax for develop native Mobile App UI.
>> By
>> leverage the Javascript engine that enable dynamic update, the process of
>> App interfce and content update can be simple and controllable just like
>> Web.Compared with WebView based UI framework which performance are limited,
>> Weex use build-in native components instead.
>>
>> Because of tag based syntax that maintain a consistent style with Web
>> standards Weex using. Developers write in this language just like writting
>> in HTML. After transforming to JSBundle by Weex tools, these tags will be
>> rendered by build-in platform-specific components. The logic part of Weex
>> syntax write in Javascript which don't need be compiled control these
>> components.
>>
>> The vision of Weex is to complement gap between platform-specific Native UI
>> and Web technical based UI in Mobile age. The team behind Weex believe that
>> dynamicly interface update and high performance should be achieved at the
>> same time when people develop a Mobile App. Meanwhile duplicate work
>> between
>> the different platforms should be avoided.
>>
>> == Background ==
>> Prior to Weex, in order to develop high performance mobile application we
>> need write at least three different codebase(iOS, Android, Mobile Web) or
>> adopt WebView based UI technique(Apache Cordova for example) which can't
>> satisfy the demand for performance.
>>
>> A special task force at Alibaba Inc try to provide a solution for this
>> problem has been setup since 2013. At first the team release a
>> cross-platform rendering engine which render a special format JSON to
>> native
>> components on different platform. To output this JSON file the team had
>> build a website which other developer can use to simply design final
>> interface.
>>
>> Although This solution had worked for a while, we found it not able to meet
>> our UI developer's habits. Most of our UI developer have Web background
>> which make them used to use tag based language to design App interface.
>> Meanwhile we found the JSON file lacks of enough flexibility. The following
>> discussion inspire we start to develop Weex.
>>
>> Nowaday, Mobile Taobao App which developed by Alibaba Inc, the largest user
>> volume eCommerce App in China has adapted Weex in a lot of UI. In the
>> latest
>> November 11th promotions(Alibaba's annual Singles' Day online shopping
>> event), UI developers from Alibaba Inc have build more then 1,500 pages
>> using Weex, 99.6% of all the promotional pages. The ratio of less than one
>> second page open time is more than 90%, the frame rate is 53.0~58.5(depend
>> on device) due to the high performance of Weex. In addition to user
>> experience improvement, the productivity of page development and the
>> efficiency of content delivery both have been improved.
>>
>> After open-source and have got a lot of followers in chinese mobile App
>> development community, several of popular Apps listed on chinese top charts
>> have adopted or planning for adopt Weex.(UCWeb, Tmall, YouKu, Suning
>> etc...)
>>
>> == Current Status ==
>> Weex has become an open source project since June 2016. It has been used
>> at
>> a lot of Alibaba producted mobile softwares which running on the mobile
>> phone of millions of users.
>>
>> Weex code repository located at GitHub. All development activities have
>> already happened on GitHub as open source manner.
>>
>> == Community ==
>> The community surrounding Weex is a variety of developer which have
>> different technique background.iOS, Android, Web developer must collaborate
>> closely to implement most Weex feature.
>>
>> Currently total 61 contributors involved in the GitHub development process.
>> Weex repository has received 791 pull requests until Nov 2016.
>>
>> Beyond committer from Alibaba Inc, Weex community 

Re: [VOTE] Accept RocketMQ into the Apache Incubator

[Xinyu Zhou]

k), Schneider Electric(
> > http://www.schneider-electric.com/), the China Railway Ministry official
> > ticketing website, China Union, Sina, Umei (http://sh.jumei.com),
> Chinese
> > Academy of Sciences and many more. We hope to grow the base of
> contributors
> > by inviting all those who offer significant contributions and excel
> through
> > the use of The Apache Way. Contributions from outside of Alibaba are now
> > being received by the RocketMQ project, including a dashboard, the
> > flume-rocketmq module, the storm-rocketmq and more.
> >
> > To further this goal, the project currently makes use of GitHub project
> > features as well as a public mailing list via Google Groups.
> >
> >
> > === Core Developers ===
> >
> > RocketMQ is currently being developed by engineers from Alibaba and
> > Yeahmobi: Xiaorui Wang, Von Gosling, Jiangwei Jiang, Xinyu Zhou, Zhanhui
> > Li. Xiaorui Wang, one of Alibaba MOM project owners is also the
> originator
> > of the RocketMQ project. He has rich experience with open source
> software,
> > as well as being active within the RocketMQ community. Von Gosling,
> another
> > MOM project owner at Alibaba and co-creator of the RocketMQ project, is
> an
> > active open source software committer and has been an active contributor
> to
> > several projects in Alibaba, Apache community and Google Code. Von also
> has
> > deep experience with performance tuning, distributed system design and
> > coding. Xinyu Zhou, Wei Zhou and Jinjixiang, They have rich experience in
> > distributed system design and performance tuning, especially in message
> > queue, big data, etc. Zhanhui Li, is a developer at Yeahmobi who has a
> > great passion for software engineering, especially in fields of
> distributed
> > system design and development. Longda, has been involved with several
> open
> > source projects released by Alibaba,especially jstorm project, which has
> > donated to apache.
> >
> > === Aligment ===
> >
> > The ASF is the natural choice to host the RocketMQ project as its goal of
> > encouraging community-driven open source projects fits with our vision
> for
> > RocketMQ. The ASF is also the home to many other projects with which we
> are
> > familiar with and hope to integrate with RocketMQ including Apache Storm,
> > Flume and Hadoop. We believe that there will be mutual benefit by close
> > proximity to these and other projects.
> >
> > == Known Risks ==
> >
> > === Orphaned products ===
> >
> > The core developers currently work full-time on the RocketMQ project for
> > Alibaba. RocketMQ provides a critical internal infrastructure and has
> been
> > in production use at Alibaba since 2011, so there is no concern that it
> > will become an orphaned project.
> >
> > === Inexperience with Open Source ===
> >
> > The core developers are all active contributors, users and followers of
> > open source. They are all already committers and contributors to the
> > RocketMQ Github project and several of them also have experience actively
> > contributing to open source projects. Though the core set of developers
> do
> > not have experience at the ASF, there are plans to onboard individuals to
> > the project who have ASF open source experience.
> >
> > === Homogenous Developers ===
> >
> > The current core developers are from Alibaba and Yeahmobi but the goal is
> > to establish a vibrant developer community and we will actively encourage
> > new contributors.
> >
> > === Reliance on Salaried Developers ===
> >
> > Currently, the developers are paid to work on RocketMQ for both Alibaba
> and
> > Yeahmobi. We look forward to building a strong community around the
> project
> > in order to encourage more contributors to join the project.
> >
> > === Relationships with Other Apache Products ===
> > RocketMQ is not currently integrated with any other ASF projects except
> for
> > several Apache Commons products, such as commons-lang, commons-cli, etc.
> As
> > a messaging server, it is mainly used to traditional publish/subscribe
> > scenario and demandingly high volume realtime transaction system that
> > tolerates no message loss. It uses java primitive file api and some jni
> > technology to custom-build storage desgin. More details about its
> storage,
> > please see the [[
> > https://github.com/alibaba/RocketMQ/wiki/how-to-support-
> > more-queues|RocketMQ
> > Storage Design]]) The table below providing some context for simple
> > compari