Re: [VOTE] Release Apache DevLake (Incubating) v0.21.0-rc1

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- LICENSE and NOTICE look good
- DISCLAIMER is present
- ASF header is there
- No binary file found in source distribution
- Build worked on my machine

Thanks
Regards
JB

On Thu, Apr 11, 2024 at 2:23 PM Zikuan An  wrote:
>
> Hello everyone,
>
> This is a call for the vote to release Apache DevLake (Incubating)
> v0.21.0-rc1.
> The Apache DevLake community has voted on and approved a proposal
> to release Apache DevLake (Incubating) version v0.21.0-rc1.
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
>
> https://lists.apache.org/thread/j8qowrhfdoqgyghg904bjs8ds639dl90
>
>
> Community vote result thread:
>
> https://lists.apache.org/thread/x32ln363j3rntglrbb1hsqj5bd8ns6y2
>
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.21.0-incubating-rc1
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-devlake/releases/tag/v0.21.0-rc1
>
>
> Keys to verify the Release Candidate:
>
> https://downloads.apache.org/incubator/devlake/KEYS
>
>
> How to build:
>
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
>
> Thanks
>
> Zikuan An

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

Re: [VOTE] Accept HertzBeat Into the ASF Incubator

[Jean-Baptiste Onofré]

+1 (binding)

It's an interesting podling. I see some "issues" to be fixed during
the incubation period (some dependencies use Cat-B/Cat-X licenses it
seems).
I think it's gonna be an interesting incubation period.

Regards
JB

On Fri, Mar 29, 2024 at 7:24 AM Zhang Yonglun  wrote:
>
> 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
>
> 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
>
> Best Regards,
> Zhang Yonglun
>
> -
> 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: [MENTORS] Missing podling reports

[Jean-Baptiste Onofré]

Hi Justin,

I already send message to the podling I'm mentoring (I didn't have
reply from all so far).
I will do a new pass within the podlings.

Thanks !
Regards
JB

On Fri, Apr 5, 2024 at 1:05 AM Justin Mclean  wrote:
>
> Hi,
>
> We are missing a large number of reports this month. Mentors, can you please 
> help your projects submit reports on time.
>
> We are still waiting on reports from:
> - Annotator
> - Gluten
> - HoraeDB
> - HugeGraph
> - Liminal
> - Pony Mail
> - ResilientDB
> - Teaclave
> - XTable
>
> 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: [VOTE] Accept StormCrawler Into the ASF Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Tue, Mar 12, 2024 at 9:33 PM PJ Fanning  wrote:
>
> Hi everyone,
>
> Following the discussion about the StormCrawler proposal [1], I am
> starting this official vote for the StormCrawler podling. Here is the
> proposal:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/StormCrawler+Proposal
>
> Please cast your vote:
> [ ] +1, bring into the Incubator
> [ ] +0, I don't care either way
> [ ] -1, do not bring StormCrawler into the Incubator, because...
>
> The vote will open for one week from today, 12 March, 2024.
>
> Thanks,
> PJ
>
> [1] https://lists.apache.org/thread/sjht4k1ojhcgfnzszxb809g1dh2t1dlw
>
> -
> 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 Celeborn (Incubating) as a Top Level Project

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Fri, Mar 8, 2024 at 11:44 AM 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 responsibilities pertaining to the Apache Incubator
> Celeborn podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> ---
>
> Best Regards,
> Yu (on behalf of the Apache Celeborn PPMC)
>
> -
> 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 StreamPark(Incubating) 2.1.3-rc1

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating in the name
- signature and checksum are good
- ASF header is present
- No unexpected binary files in the source distribution
- LICENSE, NOTICE, DISCLAIMER are there

NB: are we sure about SECURITY.md file ? Versions in this file look weird.

Regards
JB

On Tue, Mar 12, 2024 at 2:45 PM Qingrong wang  wrote:
>
> Hello Incubator Community:
>
> This is a call for a vote to release Apache StreamPark(Incubating)
> version 2.1.3-RC1.
> The Apache StreamPark community has voted on and approved a proposal
> to release Apache StreamPark(Incubating) version 2.1.3-RC1.
> We now kindly request the Incubator PMC members review and vote on
> this incubator release.
> Apache StreamPark, Make stream processing easier! Easy-to-use
> streaming application development framework and operation platform.
>
> StreamPark community vote thread:
> https://lists.apache.org/thread/l4dd4j70wp7rz40fm2nf2o3fwt5x0zr6
>
> Vote result thread:
> https://lists.apache.org/thread/8vd90kxwdvqtkqbtng7jg0mdzscc46xl
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/streampark/2.1.3-RC1/
>
> Git tag for the release:
> https://github.com/apache/incubator-streampark/releases/tag/v2.1.3-rc1
>
> The artifacts signed with PGP key [40EE71A2], corresponding
> to[monr...@apache.org], that can be found in keys file:
> https://downloads.apache.org/incubator/streampark/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
>
> More detailed checklist please refer:
> • 
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Steps to validate the release， Please refer to:
> • https://www.apache.org/info/verification.html
> • https://streampark.apache.org/community/release/how_to_verify_release
>
>
> How to Build:
>
> 1) clone source code:
> > git clone -b v2.1.3-rc1 g...@github.com:apache/incubator-streampark.git
>
> 2) build project:
> > cd incubator-streampark && sh ./build.sh
>
>
> Thanks,
>
> On behalf of Apache StreamPark(Incubating) community
>
>
> Best,
> Qingrong Wang
>
> -
> 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 Paimon (Incubating) as a Top Level Project

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Fri, Mar 8, 2024 at 11:50 AM 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 with
> the migration and rationalization of the Apache Incubator Paimon
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Paimon podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> ---
>
> Best Regards,
> Yu (on behalf of the Apache Paimon PPMC)
>
> -
> 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] Have Amoro join the Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Sun, Mar 3, 2024 at 2:44 AM 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

Re: Re: [DISCUSS] Apache Amoro proposal

[Jean-Baptiste Onofré]

Hi Nathan,

Thanks for the detailed information. Much appreciated.

I now have a better understanding of the goals. It looks interesting.

Happy to help as a mentor if you need.

Thanks !
Regards
JB

On Sat, Feb 24, 2024 at 6:24 AM nathan ma  wrote:
>
> hi, JB
>
> As co-creator of this project, I’d love to explain more about the
> positioning of lakehouse management system.
>
> When discussing databases or traditional data warehouses, we often used the
> term DBMS (Database Management System) to describe them. Traditional
> databases, including MPP databases, are typically considered “out-of-box”
> solutions. Unlike big data systems, they don’t require various components
> like compute engines, data lake formats, or metadata stores. When we need a
> database management tool, lightweight options like Navicat are commonly
> used.
>
> If we further abstract the capabilities of a DBMS and map them to the
> modern data stack, we find that the data read/write part of a DBMS is now
> shared among different compute engines such as Spark, Flink, Trino, and
> cloud-native services like Athena. Another part of a DBMS deals with data
> files, index files, and metadata (also known as the information schema)
> maintenance. Currently, there are successful open-source and commercial
> projects dedicated to managing metadata, such as HiveMetastore,
> UnityCatalog, and more recently, Gravitino. In practice, developers often
> combine these projects with compute engines to optimize data files. For
> example, many commercial compute engines include an optimize command.
>
> Amoro, as a lakehouse management system, aims to encapsulate the
> maintenance and management of data lake files, index files, and metadata in
> a way that is transparent and easy-to-use for users. The richness of
> diverse computing engines is a distinctive feature of the modern data
> stack, opening up a multitude of possibilities for various application
> scenarios. Additionally, concerning the part analogous to DBMS, we aspire
> to have a mature system in place—one that seamlessly accommodates data
> written to the lakehouse by any engine, in any manner, ensuring high data
> availability across all other engines. For instance, when Flink writes to
> Iceberg, Amoro’s self-optimizing mechanism ensures efficient data analysis
> performance by Trino or other engines while controlling compacting costs.
> Additionally, Amoro handles historical data, snapshots, and orphan file
> cleanup in the background.
>
> By positioning Amoro in this way, we aim to provide an ‘out-of-box’
> experience that feels as straightforward as traditional DBMS while keeping
> openness to various computing engines. At the same time, Amoro hopes to
> empower data product builders with a lightweight solution that integrates
> seamlessly into their modern data workflows.
>
>
>
> Thanks.
> Jin Ma
>
>
> On 2024/02/23 14:16:43 Jean-Baptiste Onofré wrote:
> > Hi Justin
> >
> > Even if it looks interesting, I'm not sure to understand exactly the
> > purpose of the proposal.
> >
> > What lakehouse management system means exactly ? Is it an abstraction
> > layer on top of Iceberg, Paimon + query engine powered by Flink,
> > Spark, Trino ?
> >
> > Please let me know if you want an additional mentor, I would be happy to
> help.
> >
> > Thanks !
> > Regards
> > JB
> >
> > On Fri, Feb 23, 2024 at 9:44 AM Justin Mclean 
> wrote:
> > >
> > > 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
> > >
> >
> > -
> > 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: [DISCUSS] Graduate Apache SDAP (Incubating) as a Top Level Project

[Jean-Baptiste Onofré]

+1 (binding)

I don't see any blocker for graduation.

Regards
JB

On Thu, Feb 22, 2024 at 7:01 PM Riley Kuttruff  wrote:
>
> Hi all,
>
> Apache SDAP joined Incubator in October 2017. In the time since, we've
> made significant progress towards maturing our community and our
> project and adopting the Apache Way.
>
> After community discussion [1][2][3], the community has voted [4] that we
> would like to proceed with graduation [5]. We now call upon the Incubator
> PMC to review and discuss our progress and would appreciate any and all
> feedback towards graduation.
>
> Below are some facts and project highlights from the incubation phase as
> well as the draft resolution:
>
> - Our community consists of 21 committers, with 2 being mentors and
> the remaining 19 serving as our PPMC
> - Several pending and planned invites to bring on new committers and/or
> PPMC members from additional organizations
> - Completed 2 releases with 2 release managers - with a 3rd release run by
> a 3rd release manager in progress
> - Our software is currently being utilized by organizations such as NASA
> Jet Propulsion Laboratory, NSF National Center for Atmospheric Research,
> Florida State University, and George Mason University in support of projects
> such as the NASA Sea Level Change Portal, Estimating the Circulation and
> Climate of the Ocean (ECCO) project, GRACE/GRACE-FO, Cloud-based
> Data Match-Up Service, Integrated Digital Earth Analysis System (IDEAS),
> and many others.
> - Opened 400+ PRs across 3 main code repositories, 350+ of which are
> merged or closed (some are pending our next release)
> - Maturity model self assessment [6]
>
> We have resolved all branding issues we are aware of: logo, GitHub,
> Website, etc
>
> We’d like to also extend a sincere thank you to our mentors, current and
> former for their invaluable insight and assistance with getting us to this
> point.
>
> Thank you, Julian, Jörn, Trevor, Lewis, Suneel, and Raphael!
>
> ---
>
> Establish the Apache SDAP 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 integrated data analytic center for Big Science problems.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache SDAP Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache SDAP Project be and hereby is responsible
> for the creation and maintenance of software related to an integrated data
> analytic center for Big Science problems; and be it further
>
> RESOLVED, that the office of "Vice President, Apache SDAP" 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 SDAP
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache SDAP
> 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 SDAP Project:
>
> - Edward M Armstrong 
> - Nga Thien Chung 
> - Thomas Cram 
> - Frank Greguska 
> - Thomas Huang 
> - Julian Hyde 
> - Joseph C. Jacob 
> - Jason Kang 
> - Riley Kuttruff 
> - Thomas G Loubrieu 
> - Kevin Marlis 
> - Stepheny Perez 
> - Wai Linn Phyo 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Nga Thien Chung
> be appointed to the office of Vice President, Apache SDAP, 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 SDAP Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator SDAP
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> SDAP podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> [1] https://lists.apache.org/thread/vjwjmp0h2f22dv423h262cvdg5x7jl03
> [2] https://lists.apache.org/thread/m9vqwv23jdsofwgmhgxg25f5l1v2j7nz
> [3] https://lists.apache.org/thread/4o1qjsk2cly2ppxcsmm2swzd6pcg3lxj
> [4] https://lists.apache.org/thread/qtxlxl4gj6n33wvm164vdxxnwdlppttl
> [5] https://lists.apache.org/thread/rr74c35fojc7ythmcgnoplyjllhbslj4
> [6] https://github.com/apache/incubator-sdap-website/blob/asf-site/maturity.md
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

[Jean-Baptiste Onofré]

+1 (binding)

nit: I still think there are some pre-existing code to improve
(existing at donation time), but it can be done once TLP

Regards
JB

On Mon, Feb 26, 2024 at 12:24 PM PJ Fanning  wrote:
>
> Hi everyone,
>
> We have positive feedback on the Pekko Vote thread [1] (result [2]).
>
> I'd like to start an official Incubator VOTE thread now.
>
> Below are some facts and project highlights from the incubation phase
> as well as the draft resolution:
>
> * All modules have at least a v1.0.0 release
> * 19 releases (across 12 modules) [3]
> * Evidence of good uptake of the Pekko releases and a large number of
> ecosystem libs now support Pekko - over 100 non Apache libraries use
> Pekko libs under the hood
> * well over 1000 PRs merged
> * 25+ code contributors
> * We've had 3 different release managers to date.
> * dozens more users who have been involved in discussions, code
> reviews, raising issues, etc.
> * We have met all maturity criteria as outlined in [4].
>
>
> Please vote on the resolution pasted below to graduate Apache Pekko
> from the Incubator to the Top Level Project.
>
>  [ ] +1 Graduate Apache Pekko from the Incubator.
>  [ ] +0 No opinion.
>  [ ] -1 Don't graduate Apache Pekko from the Incubator because ...
>
> This vote will open for at least 72 hours.
>
> I would like to thank everyone who have participated in the Apache
> Pekko community. I 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/q7jjmp7zpcxko607v5hvj514dyf6o8bx
> [2] https://lists.apache.org/thread/tsb7b8bkgfkts1nstmj413qocztj0s5o
> [3] https://incubator.apache.org/projects/pekko.html
> [4] 
> https://cwiki.apache.org/confluence/display/PEKKO/Apache+Maturity+Model+Assessment+for+Pekko
>
>
>
>  ---
>
> Establish the Apache Pekko 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 Pekko: a toolkit and an ecosystem for building
> highly concurrent, distributed, reactive and resilient applications
> for Java and Scala.
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Pekko Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
>
> RESOLVED, that the Apache Pekko Project be and hereby is responsible
> for the creation and maintenance of software related to Pekko: a
> toolkit and an ecosystem for building highly concurrent, distributed,
> reactive and resilient applications for Java and Scala.; and be it
> further
>
>
> RESOLVED, that the office of "Vice President, Apache Pekko" 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 Pekko
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Pekko
> 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 Pekko Project:
>
> Claude Warren (claude)
> Jean-Baptiste Onofré (jbonofre)
> Justin Mclean (jmclean)
> PJ Fanning (fanningpj)
> Roman Shaposhnik (rvs)
> Ryan Skraba (rskraba)
> Sheng Wu (wu-sheng)
> Alexandru Nedelcu (alexelcu)
> Arnout Engelen (engelen)
> Dani Schroeter (dsc)
> Greg Methvin (gregm)
> Guobin Li (liguobin)
> He Pin (hepin)
> Johannes Rudolph (jrudolph)
> Jonas Chapuis (jchapuis)
> Matthew de Detrich (mdedetrich)
> Nicolas Vollmar (nvollmar)
> Samuele Resca (samueler)
> Sean Glover (seanglover)
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that PJ Fanning be appointed
> to the office of Vice President, Apache Pekko, 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 Pekko Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Pekko
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pekko podling encumbered upon the Apache Incubator PMC are hereafter
> dischar

Re: [DISCUSS] Apache Amoro proposal

[Jean-Baptiste Onofré]

Hi Justin

Even if it looks interesting, I'm not sure to understand exactly the
purpose of the proposal.

What lakehouse management system means exactly ? Is it an abstraction
layer on top of Iceberg, Paimon + query engine powered by Flink,
Spark, Trino ?

Please let me know if you want an additional mentor, I would be happy to help.

Thanks !
Regards
JB

On Fri, Feb 23, 2024 at 9:44 AM Justin Mclean  wrote:
>
> 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
>

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

Re: [VOTE] Release Apache Answer(Incubating) v1.2.5-RC2

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- Checksums and signatures are OK
- incubating is in the name
- NOTICE, LICENSE and DISCLAIMER exist
- No binary found in the source distribution

Regards
JB

On Tue, Feb 6, 2024 at 4:11 AM LinkinStar  wrote:
>
> Hello,
>
> This is a call for vote to release Apache Answer(Incubating) version
> v1.2.5-RC2.
>
> The vote thread:
> https://lists.apache.org/thread/qjsmh7y4fb946pso5nwrbfjntfydhslh
>
> Vote Result:
> https://lists.apache.org/thread/89jgwznxn69296nxl5fn5jtd9ywcndog
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.5-incubating-RC2/
>
> Release notes:
> https://github.com/apache/incubator-answer/releases/tag/v1.2.5-RC2
>
> Git tag for the release:
> https://github.com/apache/incubator-answer/releases/tag/v1.2.5-RC2
>
> Git commit id for the release:
>
> https://github.com/apache/incubator-answer/commit/5132cb391238cf26d3d206403b5b737451fd189a
>
> Keys to verify the Release Candidate:
> The artifacts signed with PGP key [C34934CC], corresponding to [
> linkins...@apache.org], that can be found in keys file:
> https://dist.apache.org/repos/dist/release/incubator/answer/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
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and PGP signatures are valid.
> [ ] Source code distributions have correct names matching the current
> release.
> [ ] LICENSE and NOTICE files are correct for each Answer repo.
> [ ] All files have license headers if necessary.
> [ ] No unlicensed compiled archives bundled in source archive.
>
> To compile from the source, please refer to:
>
> https://github.com/apache/incubator-answer#building-from-source
>
> Thanks,
> LinkinStar

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

Re: [VOTE] Release Apache DevLake (Incubating) v0.19.0-rc4

[Jean-Baptiste Onofré]

As it's distributed (part of the source distribution), we should add
the ASF header wherever it's possible.
If it's an issue for third party (I understand for json, but I think
it's ok for md), then it's ok but should be noticed imho.

Regards
JB

On Wed, Jan 17, 2024 at 7:27 AM Willem Jiang  wrote:
>
> From my understanding, we don't need to add the ASF headers on the
> markdown or JSON files, as the license header comment could cause some
> trouble for other software to consume.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Jan 16, 2024 at 6:32 PM Jean-Baptiste Onofré  
> wrote:
> >
> > +0.8 (binding)
> >
> > I checked:
> > - hash and signature are OK
> > - incubating is in name
> > NB: some files doesn't contain ASF headers whereas they can (for
> > instance few md files like README.md or DevelopmentManual.md).
> > NB: I found some binaries (png, svg, ... from the grafana dashboard)
> > in the source distribution. That's OK imho but just wanted to mention
> > it.
> > It would be great to fix that for the next release at least.
> >
> > Regards
> > JB
> >
> > On Fri, Jan 5, 2024 at 11:30 AM Zikuan An  wrote:
> > >
> > > Hello everyone,
> > >
> > > This is a call for the vote to release Apache DevLake (Incubating)
> > > v0.19.0-rc4.
> > > The Apache DevLake community has voted on and approved a proposal
> > > to release Apache DevLake (Incubating) version v0.19.0-rc4.
> > >
> > >
> > > We particularly checked the updates on the license of yarn-3.4.1.cjs (see
> > > PR: https://github.com/apache/incubator-devlake/pull/6711) based on the
> > > relatively specific and clear parts of the feedback we received and the
> > > practices of other ASF projects sharing the similar problems such as 
> > > Apache
> > > BRPC, Apache Dubbo, etc.
> > >
> > >
> > > We now kindly request the Incubator PMC members review and vote on this
> > > incubator release.
> > >
> > > Community vote thread:
> > >
> > > https://lists.apache.org/thread/pk7w87rdqos6j949dtktzwcosokmw5ql
> > >
> > >
> > > Community vote result thread:
> > >
> > > https://lists.apache.org/thread/5wb75wyrqylr7gkl4b1jbqjqpvjm6tpm
> > >
> > >
> > > The release candidates:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/devlake/0.19.0-incubating-rc4
> > >
> > >
> > > Git tag for the release:
> > >
> > > https://github.com/apache/incubator-devlake/releases/tag/v0.19.0-rc4
> > >
> > >
> > > Keys to verify the Release Candidate:
> > >
> > > https://downloads.apache.org/incubator/devlake/KEYS
> > >
> > >
> > > How to build:
> > >
> > > https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
> > >
> > >
> > > The vote will be open for at least 72 hours or until the necessary number
> > > of votes is reached.
> > >
> > > Please vote accordingly:
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > >
> > > Thanks
> > >
> > > Zikuan An
> >
> > -
> > 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 DevLake (Incubating) v0.19.0-rc4

[Jean-Baptiste Onofré]

That's right, the reason is because I'm puzzled :)
I was hesitating between +1 (binding) and +0.8 (non binding).

So, let me put +1 (binding) here and target to fix these small issues
in the next release.

Regards
JB

On Tue, Jan 16, 2024 at 3:41 PM Xuanwo  wrote:
>
> Hi, JB
>
> Based on the "APACHE VOTING PROCESS" [1]:
>
> > Votes from PMC Members on releases must use +1, 0, -1 to be considered 
> > binding.
>
> Please correct me if I'm wrong, but I believe a +0.8 vote might not be 
> sufficient
> to be considered binding.
>
> [1] https://www.apache.org/foundation/voting.html
>
> On Tue, Jan 16, 2024, at 18:31, Jean-Baptiste Onofré wrote:
> > +0.8 (binding)
> >
> > I checked:
> > - hash and signature are OK
> > - incubating is in name
> > NB: some files doesn't contain ASF headers whereas they can (for
> > instance few md files like README.md or DevelopmentManual.md).
> > NB: I found some binaries (png, svg, ... from the grafana dashboard)
> > in the source distribution. That's OK imho but just wanted to mention
> > it.
> > It would be great to fix that for the next release at least.
> >
> > Regards
> > JB
> >
> > On Fri, Jan 5, 2024 at 11:30 AM Zikuan An  wrote:
> >>
> >> Hello everyone,
> >>
> >> This is a call for the vote to release Apache DevLake (Incubating)
> >> v0.19.0-rc4.
> >> The Apache DevLake community has voted on and approved a proposal
> >> to release Apache DevLake (Incubating) version v0.19.0-rc4.
> >>
> >>
> >> We particularly checked the updates on the license of yarn-3.4.1.cjs (see
> >> PR: https://github.com/apache/incubator-devlake/pull/6711) based on the
> >> relatively specific and clear parts of the feedback we received and the
> >> practices of other ASF projects sharing the similar problems such as Apache
> >> BRPC, Apache Dubbo, etc.
> >>
> >>
> >> We now kindly request the Incubator PMC members review and vote on this
> >> incubator release.
> >>
> >> Community vote thread:
> >>
> >> https://lists.apache.org/thread/pk7w87rdqos6j949dtktzwcosokmw5ql
> >>
> >>
> >> Community vote result thread:
> >>
> >> https://lists.apache.org/thread/5wb75wyrqylr7gkl4b1jbqjqpvjm6tpm
> >>
> >>
> >> The release candidates:
> >>
> >> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.19.0-incubating-rc4
> >>
> >>
> >> Git tag for the release:
> >>
> >> https://github.com/apache/incubator-devlake/releases/tag/v0.19.0-rc4
> >>
> >>
> >> Keys to verify the Release Candidate:
> >>
> >> https://downloads.apache.org/incubator/devlake/KEYS
> >>
> >>
> >> How to build:
> >>
> >> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
> >>
> >>
> >> The vote will be open for at least 72 hours or until the necessary number
> >> of votes is reached.
> >>
> >> Please vote accordingly:
> >> [ ] +1 approve
> >> [ ] +0 no opinion
> >> [ ] -1 disapprove with the reason
> >>
> >>
> >> Thanks
> >>
> >> Zikuan An
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
> Xuanwo
>
> -
> 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 DevLake (Incubating) v0.19.0-rc4

[Jean-Baptiste Onofré]

+0.8 (binding)

I checked:
- hash and signature are OK
- incubating is in name
NB: some files doesn't contain ASF headers whereas they can (for
instance few md files like README.md or DevelopmentManual.md).
NB: I found some binaries (png, svg, ... from the grafana dashboard)
in the source distribution. That's OK imho but just wanted to mention
it.
It would be great to fix that for the next release at least.

Regards
JB

On Fri, Jan 5, 2024 at 11:30 AM Zikuan An  wrote:
>
> Hello everyone,
>
> This is a call for the vote to release Apache DevLake (Incubating)
> v0.19.0-rc4.
> The Apache DevLake community has voted on and approved a proposal
> to release Apache DevLake (Incubating) version v0.19.0-rc4.
>
>
> We particularly checked the updates on the license of yarn-3.4.1.cjs (see
> PR: https://github.com/apache/incubator-devlake/pull/6711) based on the
> relatively specific and clear parts of the feedback we received and the
> practices of other ASF projects sharing the similar problems such as Apache
> BRPC, Apache Dubbo, etc.
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
>
> https://lists.apache.org/thread/pk7w87rdqos6j949dtktzwcosokmw5ql
>
>
> Community vote result thread:
>
> https://lists.apache.org/thread/5wb75wyrqylr7gkl4b1jbqjqpvjm6tpm
>
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.19.0-incubating-rc4
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-devlake/releases/tag/v0.19.0-rc4
>
>
> Keys to verify the Release Candidate:
>
> https://downloads.apache.org/incubator/devlake/KEYS
>
>
> How to build:
>
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
>
> Thanks
>
> Zikuan An

-
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-rc2

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- Hash and signatures are good
- incubating is in the version/name
- LICENSE and NOTICE look good
- DISCLAIMER exists
- ASF headers are present
- no binary file found in the source distribution

Regards
JB

On Tue, Jan 2, 2024 at 4:11 AM 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

Re: [VOTE] Release Apache OpenDAL(incubating) 0.44.1 - Incubator Vote Round 1

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- Hashes and signatures are good
- incubating is in the version
- LICENSE and NOTICE look good
- DISCLAIMER is present
- ASF headers are present
- No binary found in the source distribution

Regards
JB

On Wed, Jan 3, 2024 at 8:33 AM Xuanwo  wrote:
>
> Hello Incubator PMC,
>
> The Apache OpenDAL community has voted and approved the release of Apache
> OpenDAL(incubating) 0.44.1. We now kindly request the IPMC members
> review and vote for this release.
>
> OpenDAL is a data access layer that allows users to easily and efficiently
> retrieve data from various storage services in a unified way.
>
> OpenDAL community vote thread:
>
> https://lists.apache.org/thread/r76vnpfm2g1rhf1q33x7bmtmw137dlb4
>
> Vote result thread:
>
> https://lists.apache.org/thread/rbh65l5sbrd1bd45d2nm2h20lqhzy7x1
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/opendal/0.44.1-rc.1/
>
> This release has been signed with a PGP available here:
>
> https://downloads.apache.org/incubator/opendal/KEYS
>
> Git tag for the release:
>
> https://github.com/apache/incubator-opendal/releases/tag/v0.44.1-rc.1
>
> Maven staging repo:
>
> https://repository.apache.org/content/repositories/orgapacheopendal-1023/
>
> Please download, verify, and test.
>
> The VOTE will be open for at least 72 hours and until the necessary
> number of votes are reached.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache opendal, please see https://opendal.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
>
> More detailed checklist please refer to:
> https://github.com/apache/incubator-opendal/tree/main/scripts
>
> To compile from source, please refer to:
> https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
>
> Here is python script in release to help you verify the release candidate:
>
> ./scripts/verify.py
>
> Thanks
>
> Xuanwo
>
> -
> 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 Gluten Into the ASF Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Thu, Jan 4, 2024 at 3:47 AM ShaoFeng Shi  wrote:
>
> Hi Incubator,
>
> Following the discussion [DISCUSS] Gluten proposal[1],
> I am starting this official vote for the Gluten project.
>
> Here is their proposal:
> https://cwiki.apache.org/confluence/display/INCUBATOR/GlutenProposal
>
> Please cast your vote:
>
> [ ] +1, bring into the Incubator
> [ ] +0, I don't care either way
> [ ] -1, do not bring Gluten into the Incubator, because...
>
> The vote will open for one week from today.
>
> [1] https://lists.apache.org/thread/xgsm75t721vgnlthgy84909ggqok77j4
>
> Best regards,
>
> Shaofeng Shi 史少锋
> Apache Kylin PMC member,
> Apache Incubator PMC member,
> Email: shaofeng...@apache.org

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

Re: [DISCUSS] Procedure for graduating an existing sub project to new top level project

[Jean-Baptiste Onofré]

Hi Andrew

We did a similar move while ago for Apache Karaf (from Apache
ServiceMix, then Felix, then TLP :)).

AFAIR, you propose a resolution to the board with approval from PMC,
proposing a new PMC/committer set.

Regards
JB

On Fri, Dec 15, 2023 at 4:06 PM Andrew Lamb  wrote:
>
> I apologize if this is not the right list on which to ask this question.
>
> Can someone point to information about the procedure to propose
> “graduating” an *existing* sub project to a new top level project?
>
> Specifically, we are working on a proposal to graduate the “Apache Arrow
> DataFusion”[1]  sub project to its own Top Level Project. The DataFusion
> project has sort of been “incubating” within the Arrow top level project
> for several years and has grown to the point where it can both stand on its
> own as well as benefit from more focused community[2].
>
> I searched the archives of this list [3] and did not find anything that
> seemed relevant.
>
> I did find, farther back in history, that the Mahout, Avro and HBase
> projects appear to have previously “graduated” from sub projects of Hadoop
> to their own top level projects but could not determine how they did so.
>
> Thank you for any guidance you may be able to provide,
>
> Andrew
>
> [1] https://arrow.apache.org/datafusion/
>
> [2] https://github.com/apache/arrow-datafusion/discussions/6475
>
> [3] https://lists.apache.org/list.html?general@incubator.apache.org
> [4]
> https://news.apache.org/foundation/entry/the_apache_software_foundation_announces4

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

Re: [VOTE] Accept XTable into the ASF Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Sat, Dec 16, 2023 at 5:17 AM Jesus Camacho Rodriguez
 wrote:
>
> Hi All,
>
> Following the discussion in the incubator mailing list [1], I am starting
> this official vote for the XTable project.
>
> Here is the proposal -
> https://cwiki.apache.org/confluence/display/INCUBATOR/XTable+Proposal
>
> Please cast your vote:
>
> [ ] +1, bring XTable into the Incubator
> [ ] +0, I don't care either way
> [ ] -1, do not bring XTable into the Incubator, because...
>
> This majority vote is open for at least 96 hours (due to the weekend).
>
> Only votes from Incubator PMC members are binding, but other votes are
> welcome!
>
> Thanks,
> Jesús
>
> [1] https://lists.apache.org/thread/rx9z8ffrf37qjhpkf1vp5rqg5lhht7jm

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

Re: [DISCUSS] OneTable proposal

[Jean-Baptiste Onofré]

> > > in this thread.
> > >
> > > Regarding the name-changing process and your concerns about it, we're
> > > looking for advice based on past experiences. Specifically, we're
> > > considering whether it's better to change the project's name before
> > pushing
> > > the code to the ASF, or if it's more practical to push the code to the
> > ASF
> > > repository first and then proceed with the name change. Any insights or
> > > guidance on whether one option is better than the other based on previous
> > > instances would be appreciated.
> > >
> > > Thanks,
> > > Jesús
> > >
> > >
> > >
> > > On Mon, Dec 11, 2023 at 5:43 AM Jean-Baptiste Onofré <
> > jbono...@apache.org>
> > > wrote:
> > >
> > > > Of course, it's a big +1 one for me.
> > > >
> > > > The purpose is interesting, creating "connection" with other Apache
> > > > projects.
> > > > Happy to be a mentor on this proposal and contribute to the project :)
> > > >
> > > > Thanks !
> > > > Regards
> > > > JB
> > > >
> > > > On Mon, Dec 4, 2023 at 10:23 PM Jesus Camacho Rodriguez
> > > >  wrote:
> > > > >
> > > > > Hi All,
> > > > >
> > > > > I would like to propose a new project to the ASF incubator -
> > OneTable.
> > > > >
> > > > > OneTable[1] is an omni-directional converter for table formats that
> > > > facilitates interoperability across data processing systems and query
> > > > engines. Currently, OneTable supports widely adopted open-source table
> > > > formats such as Apache Hudi, Apache Iceberg, and Delta Lake.
> > > > >
> > > > > Here is the proposal -
> > > > >
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal
> > > > >
> > > > > I would be the Champion of the project. I will mentor and help the
> > > > project through the incubator with Hitesh Shah [hit...@apache.org],
> > > > Stamatis Zampetakis [zabe...@apache.org], and Jean-Baptiste Onofré [
> > > > jbono...@apache.org].
> > > > >
> > > > > We are looking forward to your feedback!
> > > > >
> > > > > Thanks,
> > > > > Jesús
> > > > >
> > > > > [1] https://github.com/onetable-io/onetable
> > > >
> > >
> >

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

Re: [VOTE] Accept Fury Into the ASF Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Fri, Dec 8, 2023 at 12:57 PM Shawn Yang  wrote:
>
> +1 (non-binding)
>
> Best regards,
> Chaokun Yang
>
> -
> 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: [DISCUSS] OneTable proposal

[Jean-Baptiste Onofré]

Hi Jesus

Yes, we first have to trigger the vote to accept XTable into the
incubator. As soon as the vote pass (hopefully), we have to trigger
the name search.

Regards
JB

On Wed, Dec 13, 2023 at 4:06 PM Jesus Camacho Rodriguez
 wrote:
>
> Thanks JB. Based on the guidelines described here [1], I was going to run
> the name search process for XTable after the project is accepted for
> incubation, but before we start to request resources.
>
> -Jesús
>
> [1] https://www.apache.org/foundation/marks/naming.html#startsearch
>
> On Wed, Dec 13, 2023 at 2:02 AM Jean-Baptiste Onofré 
> wrote:
>
> > Thanks Jesus
> >
> > XTable sounds good but we need a name search anyway to be sure it's
> > suitable.
> >
> > Regards
> > JB
> >
> > On Wed, Dec 13, 2023 at 4:30 AM Jesus Camacho Rodriguez
> >  wrote:
> > >
> > > I've updated the proposal with the new name: XTable. You can review it
> > > here:
> > https://cwiki.apache.org/confluence/display/INCUBATOR/XTable+Proposal
> > > (please also see _Project Name_ subsection)
> > >
> > > We hope this change addresses the concern that was raised during this
> > > discussion, helping to convey a message of neutrality to anyone
> > interested
> > > in contributing to the project.
> > >
> > > We look forward to hearing from you soon. If there are no further
> > concerns,
> > > we would love to move forward with the VOTE as soon as possible.
> > >
> > > -Jesús
> > >
> > >
> > >
> > > On Mon, Dec 11, 2023 at 10:09 PM Jesus Camacho Rodriguez <
> > > jcama...@apache.org> wrote:
> > >
> > > > Thanks Julian. I was mainly considering the code, but, as you
> > mentioned,
> > > > it's probably not the primary concern. The current proposal aligns with
> > > > your feedback: The project will go through the vote (and hopefully be
> > > > accepted into the incubator) using the new name, so all the infra and
> > > > project setup can be done (hopefully) only once.
> > > >
> > > > -Jesús
> > > >
> > > > On Mon, Dec 11, 2023 at 5:29 PM Julian Hyde 
> > > > wrote:
> > > >
> > > >> Much easier to change the name before incubation. It’s not so much
> > code
> > > >> as all the infrastructure (mailing lists, git repos, web servers, svn
> > > >> files, …) that goes along with a podling. It’s a lot of work for
> > INFRA and
> > > >> for the PPMC/champion.
> > > >>
> > > >> Also, branding. Calcite entered incubation as ‘Optiq’ and then
> > renamed,
> > > >> but not before it had appeared in a few conference talks; people are
> > still
> > > >> asking me ‘What happened to Optiq?'
> > > >>
> > > >> Julian
> > > >>
> > > >>
> > > >> > On Dec 11, 2023, at 5:08 PM, Jesus Camacho Rodriguez <
> > > >> jcama...@apache.org> wrote:
> > > >> >
> > > >> > Thanks to everyone who expressed support and offered help. It's
> > great to
> > > >> > see that the project's mission resonates with so many different
> > people.
> > > >> >
> > > >> > Jacques, we acknowledge your concern about the project name. We are
> > > >> working
> > > >> > on selecting a new name for ASF incubation that avoids confusion
> > with
> > > >> any
> > > >> > specific corporation or product in the space. Currently we are doing
> > > >> some
> > > >> > due diligence to minimize the risk of having to change it again
> > during
> > > >> > incubation; we'll update the proposal with the new name soon and
> > share
> > > >> it
> > > >> > in this thread.
> > > >> >
> > > >> > Regarding the name-changing process and your concerns about it,
> > we're
> > > >> > looking for advice based on past experiences. Specifically, we're
> > > >> > considering whether it's better to change the project's name before
> > > >> pushing
> > > >> > the code to the ASF, or if it's more practical to push the code to
> > the
> > > >> ASF
> > > >> > repository first and then proceed with the name change. Any
> > insights or
> > > >> > guidance on whether one option is bett

Re: [DISCUSS] OneTable proposal

[Jean-Baptiste Onofré]

Thanks Jesus

XTable sounds good but we need a name search anyway to be sure it's suitable.

Regards
JB

On Wed, Dec 13, 2023 at 4:30 AM Jesus Camacho Rodriguez
 wrote:
>
> I've updated the proposal with the new name: XTable. You can review it
> here: https://cwiki.apache.org/confluence/display/INCUBATOR/XTable+Proposal
> (please also see _Project Name_ subsection)
>
> We hope this change addresses the concern that was raised during this
> discussion, helping to convey a message of neutrality to anyone interested
> in contributing to the project.
>
> We look forward to hearing from you soon. If there are no further concerns,
> we would love to move forward with the VOTE as soon as possible.
>
> -Jesús
>
>
>
> On Mon, Dec 11, 2023 at 10:09 PM Jesus Camacho Rodriguez <
> jcama...@apache.org> wrote:
>
> > Thanks Julian. I was mainly considering the code, but, as you mentioned,
> > it's probably not the primary concern. The current proposal aligns with
> > your feedback: The project will go through the vote (and hopefully be
> > accepted into the incubator) using the new name, so all the infra and
> > project setup can be done (hopefully) only once.
> >
> > -Jesús
> >
> > On Mon, Dec 11, 2023 at 5:29 PM Julian Hyde 
> > wrote:
> >
> >> Much easier to change the name before incubation. It’s not so much code
> >> as all the infrastructure (mailing lists, git repos, web servers, svn
> >> files, …) that goes along with a podling. It’s a lot of work for INFRA and
> >> for the PPMC/champion.
> >>
> >> Also, branding. Calcite entered incubation as ‘Optiq’ and then renamed,
> >> but not before it had appeared in a few conference talks; people are still
> >> asking me ‘What happened to Optiq?'
> >>
> >> Julian
> >>
> >>
> >> > On Dec 11, 2023, at 5:08 PM, Jesus Camacho Rodriguez <
> >> jcama...@apache.org> wrote:
> >> >
> >> > Thanks to everyone who expressed support and offered help. It's great to
> >> > see that the project's mission resonates with so many different people.
> >> >
> >> > Jacques, we acknowledge your concern about the project name. We are
> >> working
> >> > on selecting a new name for ASF incubation that avoids confusion with
> >> any
> >> > specific corporation or product in the space. Currently we are doing
> >> some
> >> > due diligence to minimize the risk of having to change it again during
> >> > incubation; we'll update the proposal with the new name soon and share
> >> it
> >> > in this thread.
> >> >
> >> > Regarding the name-changing process and your concerns about it, we're
> >> > looking for advice based on past experiences. Specifically, we're
> >> > considering whether it's better to change the project's name before
> >> pushing
> >> > the code to the ASF, or if it's more practical to push the code to the
> >> ASF
> >> > repository first and then proceed with the name change. Any insights or
> >> > guidance on whether one option is better than the other based on
> >> previous
> >> > instances would be appreciated.
> >> >
> >> > Thanks,
> >> > Jesús
> >> >
> >> >
> >> >
> >> > On Mon, Dec 11, 2023 at 5:43 AM Jean-Baptiste Onofré <
> >> jbono...@apache.org>
> >> > wrote:
> >> >
> >> >> Of course, it's a big +1 one for me.
> >> >>
> >> >> The purpose is interesting, creating "connection" with other Apache
> >> >> projects.
> >> >> Happy to be a mentor on this proposal and contribute to the project :)
> >> >>
> >> >> Thanks !
> >> >> Regards
> >> >> JB
> >> >>
> >> >> On Mon, Dec 4, 2023 at 10:23 PM Jesus Camacho Rodriguez
> >> >>  wrote:
> >> >>>
> >> >>> Hi All,
> >> >>>
> >> >>> I would like to propose a new project to the ASF incubator - OneTable.
> >> >>>
> >> >>> OneTable[1] is an omni-directional converter for table formats that
> >> >> facilitates interoperability across data processing systems and query
> >> >> engines. Currently, OneTable supports widely adopted open-source table
> >> >> formats such as Apache Hudi, Apache Iceberg, and Delta Lake.
> >> >>>
> >> >>> Here is the proposal -
> >> >>>
> >> https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal
> >> >>>
> >> >>> I would be the Champion of the project. I will mentor and help the
> >> >> project through the incubator with Hitesh Shah [hit...@apache.org],
> >> >> Stamatis Zampetakis [zabe...@apache.org], and Jean-Baptiste Onofré [
> >> >> jbono...@apache.org].
> >> >>>
> >> >>> We are looking forward to your feedback!
> >> >>>
> >> >>> Thanks,
> >> >>> Jesús
> >> >>>
> >> >>> [1] https://github.com/onetable-io/onetable
> >> >>
> >>
> >>
> >> -
> >> 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: [DISCUSS] OneTable proposal

[Jean-Baptiste Onofré]

Hi,

I think it makes sense to start a name search process asap.

I don't know if OneTable is an acceptable name (I doubt that :)), but
it's worth checking.

I did some name search already (for instance
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-205), so let
me know if you want me to help with that.

Regards
JB

On Tue, Dec 12, 2023 at 2:08 AM Jesus Camacho Rodriguez
 wrote:
>
> Thanks to everyone who expressed support and offered help. It's great to see 
> that the project's mission resonates with so many different people.
>
> Jacques, we acknowledge your concern about the project name. We are working 
> on selecting a new name for ASF incubation that avoids confusion with any 
> specific corporation or product in the space. Currently we are doing some due 
> diligence to minimize the risk of having to change it again during 
> incubation; we'll update the proposal with the new name soon and share it in 
> this thread.
>
> Regarding the name-changing process and your concerns about it, we're looking 
> for advice based on past experiences. Specifically, we're considering whether 
> it's better to change the project's name before pushing the code to the ASF, 
> or if it's more practical to push the code to the ASF repository first and 
> then proceed with the name change. Any insights or guidance on whether one 
> option is better than the other based on previous instances would be 
> appreciated.
>
> Thanks,
> Jesús
>
>
>
> On Mon, Dec 11, 2023 at 5:43 AM Jean-Baptiste Onofré  
> wrote:
>>
>> Of course, it's a big +1 one for me.
>>
>> The purpose is interesting, creating "connection" with other Apache projects.
>> Happy to be a mentor on this proposal and contribute to the project :)
>>
>> Thanks !
>> Regards
>> JB
>>
>> On Mon, Dec 4, 2023 at 10:23 PM Jesus Camacho Rodriguez
>>  wrote:
>> >
>> > Hi All,
>> >
>> > I would like to propose a new project to the ASF incubator - OneTable.
>> >
>> > OneTable[1] is an omni-directional converter for table formats that 
>> > facilitates interoperability across data processing systems and query 
>> > engines. Currently, OneTable supports widely adopted open-source table 
>> > formats such as Apache Hudi, Apache Iceberg, and Delta Lake.
>> >
>> > Here is the proposal -
>> > https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal
>> >
>> > I would be the Champion of the project. I will mentor and help the project 
>> > through the incubator with Hitesh Shah [hit...@apache.org], Stamatis 
>> > Zampetakis [zabe...@apache.org], and Jean-Baptiste Onofré 
>> > [jbono...@apache.org].
>> >
>> > We are looking forward to your feedback!
>> >
>> > Thanks,
>> > Jesús
>> >
>> > [1] https://github.com/onetable-io/onetable

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

Re: [DISCUSS] OneTable proposal

[Jean-Baptiste Onofré]

Of course, it's a big +1 one for me.

The purpose is interesting, creating "connection" with other Apache projects.
Happy to be a mentor on this proposal and contribute to the project :)

Thanks !
Regards
JB

On Mon, Dec 4, 2023 at 10:23 PM Jesus Camacho Rodriguez
 wrote:
>
> Hi All,
>
> I would like to propose a new project to the ASF incubator - OneTable.
>
> OneTable[1] is an omni-directional converter for table formats that 
> facilitates interoperability across data processing systems and query 
> engines. Currently, OneTable supports widely adopted open-source table 
> formats such as Apache Hudi, Apache Iceberg, and Delta Lake.
>
> Here is the proposal -
> https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal
>
> I would be the Champion of the project. I will mentor and help the project 
> through the incubator with Hitesh Shah [hit...@apache.org], Stamatis 
> Zampetakis [zabe...@apache.org], and Jean-Baptiste Onofré 
> [jbono...@apache.org].
>
> We are looking forward to your feedback!
>
> Thanks,
> Jesús
>
> [1] https://github.com/onetable-io/onetable

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

Re: [VOTE] Accept Seata Into the ASF Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Sat, Oct 21, 2023 at 2:50 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: [DISCUSS] Incubating Proposal of Seata

[Jean-Baptiste Onofré]

Hi

It's a very interesting project and proposal.

As Seata is already an Open Source project for a while, why going to
an ASF project now ?
The idea is to grow the community and/or to have an open governance ?

Just curious :)

Thanks,
Regards
JB

On Wed, Oct 11, 2023 at 8:36 AM Sheng Wu  wrote:
>
> Hi Incubator
>
> I would like to propose a new project to the ASF incubator - Seata.
>
> Seata[1] is an open-source distributed transaction solution that
> delivers high-performance and easy-to-use distributed transaction
> services under a microservices architecture.
> This project is owned by Alibaba and Ant Group. They have agreed to
> sign the SGAs and CCLAs for the donation.
>
> Here is their proposal,
> https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal
>
> I would be the Champion of the project. I am going to mentor and help
> the project go through the incubator with Justin Mclean(justin at
> classsoftware dot com), Huxing Zhang(huxing at apache dot org), and
> Heng Du(duhengforever at apache dot org).
>
> So far, the project has a large user group and diverse dev team, it is
> healthy and moving forward.
> Within the ASF requirements, the MySQL dependency is the major issue
> we need to resolve after being accepted due to GPL limitations. The
> project community has supported to use other databases such as
> PostgreSQL, they just need to remove the MySQL driver from the binary
> and keep it optional.
>
> We are open to hearing the feedback from the incubator.
>
> [1] https://seata.io/en/
>
> 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] Release Apache Pekko(incubating) Persistence Cassandra 1.0.0-RC1

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- signatures and hashes
- license, notice and disclaimer
- asf header

Regards
JB

Le mer. 27 sept. 2023 à 12:48, PJ Fanning  a écrit :

> Hi everyone,
>
> This vote thread has been open for over a week and we are still short of
> votes. If any of the Pekko mentors or Incubator PMC members generally have
> time to review the release that would be greatly appreciated.
>
> Regards,
> PJ
>
> On 2023/09/20 06:14:32 Matthew de Detrich wrote:
> > Carrying over my +1 vote from
> > https://lists.apache.org/thread/om585kyt94loncslvf2cfckdzvbo80ow
> >
> > On Wed, Sep 20, 2023 at 12:51 AM PJ Fanning 
> wrote:
> >
> > > Hello Incubator Community,
> > >
> > > This is a call for a vote to release Apache Pekko(incubating)
> > > Persistence Cassandra version 1.0.0-RC1.
> > >
> > > The discussion thread:
> > >
> > > https://lists.apache.org/thread/bqhqr1qjps71y5fdjxcyn6c65fdz633z
> > >
> > > The Pekko PPMC vote thread
> > >
> > > https://lists.apache.org/thread/tf2tp86lhfqzqqkr218k7b8o43ym6rkk
> > >
> > > The Pekko PPMC result
> > >
> > > https://lists.apache.org/thread/ts9tg6rh8gkmlztk42lhl5b0w9jmkwvk
> > >
> > > The release candidate:
> > >
> > >
> > >
> https://dist.apache.org/repos/dist/dev/incubator/pekko/PERSISTENCE_CASSANDRA-1.0.0-RC1/
> > >
> > > This release has been signed with a PGP key available here:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS
> > >
> > > Release Notes:
> > >
> > >
> > >
> https://pekko.apache.org/docs/pekko-persistence-cassandra/1.0.0/release-notes.html
> > >
> > > Git branch for the release:
> > >
> > >
> > >
> https://github.com/apache/incubator-pekko-persistence-cassandra/tree/v1.0.0-RC1
> > > Git commit ID: 7741ba0ab3be3ab0c132dcfc866d14c25e2c08de
> > >
> > > Please download, verify, and test.
> > >
> > > We have also staged jars in the Apache Nexus Repository. These were
> > > built with the same code
> > > as appears in this Source Release Candidate. We would appreciate if
> > > users could test with these too.
> > > If anyone finds any serious problems with these jars, please also
> > > notify us on this thread.
> > >
> > > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> > >
> > > In sbt, you can add this resolver.
> > >
> > > resolvers += "Apache Pekko Staging" at
> > > "https://repository.apache.org/content/groups/staging;
> > >
> > >
> > > The vote will be left open for at least 72hrs.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > To learn more about Apache Pekko, please see https://pekko.apache.org/
> > >
> > > Checklist for reference:
> > >
> > > [ ] Download links are valid.
> > > [ ] Checksums and signatures.
> > > [ ] LICENSE/NOTICE files exist
> > > [ ] No unexpected binary files
> > > [ ] Source files have ASF headers
> > > [ ] Can compile from source
> > >
> > > To compile from the source, please refer to:
> > >
> > >
> > >
> https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
> > >
> > > This module is best built with Java 8.
> > >
> > > Some notes about verifying downloads can be found at:
> > >
> > > https://pekko.apache.org/download.html#verifying-downloads
> > >
> > >
> > > Here is my +1 (binding). Matthew de Detrich also cast a +1 (binding)
> > > vote on the Pekko vote thread.
> > >
> > > Thanks,
> > >
> > > PJ Fanning (Apache Incubator PMC member)
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > --
> >
> > Matthew de Detrich
> >
> > *Aiven Deutschland GmbH*
> >
> > Immanuelkirchstraße 26, 10405 Berlin
> >
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >
> > *m:* +491603708037
> >
> > *w:* aiven.io *e:* matthew.dedetr...@aiven.io
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Baremaps 0.7.2-rc3 (incubating)

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- signatures and hashes ok
- asf headers
- license, notice and disclaimer are there
- no binary found in source distribution

Thanks
Regards
JB

Le mar. 3 oct. 2023 à 00:10, Bertil Chapuis  a écrit :

> Hello Everyone,
>
> This is a call for a vote to release Apache Baremaps 0.7.2 (incubating),
> release candidate 3. Apache Baremaps is a toolkit and a set of
> infrastructure components for creating, publishing, and operating online
> maps.
>
> We would like to thanks everyone who has vetted the previous release
> candidates and who has contributed to the project. This release candidate
> fixes the issues identified in the previous vote thread:
> https://lists.apache.org/thread/vzvl8rl5h5k9vj3j2xhbkn92zvn4db2f
>
> We now would like to request the Incubator PMC members to review and vote
> on this new release candidate.
>
> You can read the release notes here:
> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.2-rc3
>
> The commit to be voted upon:
> https://github.com/apache/incubator-baremaps/tree/v0.7.2-rc3
>
> Its hash is 823b55507eec425776d996b64b489c8235f6bb37.
>
> Its tag is v0.7.2-rc3.
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/baremaps/0.7.2-rc3/
>
> The hashes of the artifacts are as follows:
> 658ed9f9d7836c774095bd6079a39c92b366da38d733a04f2334ca39e55d41001ea997c826f9024bae51034ee6861d153ef1948defff8ebf02ce18b79d52319b
> ./apache-baremaps-0.7.2-incubating-src.tar.gz
> 778a4c2e657b5f632f9abe547d68978da40f162bdddc6dc342586b40952b0c72a0c4f6976cc47f720134c7e547af58f1efa39ddb2441e7f57c7a35fee68a1915
> ./apache-baremaps-0.7.2-incubating-bin.tar.gz
>
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/bchapuis.asc
> https://downloads.apache.org/incubator/baremaps/KEYS
>
> The README file for the src distribution contains instructions for
> building and testing the release.
>
> Please vote on releasing this package as Apache Baremaps 0.7.2.
>
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Baremaps 0.7.2
> [ ] 0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Best,
>
> Bertil
>

Re: [VOTE] Release Apache Livy 0.8.0-incubating (RC2)

[Jean-Baptiste Onofré]

+1 (binding)

Casting my vote here.

Regards
JB

Le mer. 4 oct. 2023 à 19:25, Damon Cortesi  a écrit :

> Hello Incubator Community,
>
> The Apache Livy has recently been working on reviving the Livy project and
> would like to call for a vote to release Apache Livy(Incubating) version
> 0.8.0-incubating-rc2.
>
> Notable changes from RC1 include removing Category X licenses where
> possible and opting for the more permissive license for dual-licensed
> dependencies.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
> • https://lists.apache.org/thread/hzvbwtx4khdyll21owsnwr45v5l4d6wj
>
> Vote result thread:
> • https://lists.apache.org/thread/20ghfpgdvos6mvrzrkk287pp4gb1zzdf
>
> The release candidate:
> •
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.8.0-incubating-rc2
>
> Git tag for the release:
> •
> https://github.com/apache/incubator-livy/releases/tag/v0.8.0-incubating-rc2
>
>
> Public keys file:
> • https://dist.apache.org/repos/dist/dev/incubator/livy/KEYS
>
> The change log is available in:
> •
>
> https://github.com/apache/incubator-livy/compare/v0.7.1-incubating-rc1...v0.8.0-incubating-rc2
>
> Dev instructions:
> • https://github.com/apache/incubator-livy/tree/master/dev/docker
>
> 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,
> Damon Cortesi
>

Re: [DISCUSS] Incubating Proposal of ResilientDB

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

Le mar. 3 oct. 2023 à 13:23, Atri Sharma  a écrit :

> We want to propose ResilientDB as a new Apache Incubator project.
>
> ResilientDB[1] is a distributed blockchain framework that is written
> in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash
> Fault-Tolerant (CFT) consensus protocols. Code is present at [2].
>
> Key features:
>
> Provides a scalable client-server architecture. Each developer can use
> the ResilientDB framework to deploy a replicated service acting as a
> service. The developer can choose the desired number of replicas and
> the number of clients its system should tolerate.
>
> Provides native integration with PBFT consensus protocol – arguably
> the most popular BFT consensus protocol. PBFT helps replicas reach an
> agreement for ordering the client's requests.
>
> Provides a mechanism to simulate the failure of different replicas
> (including the leader).
>
> Provides a correct implementation of the view-change protocol that
> replaces a faulty (or malicious) leader and moves all replicas to the
> new view.
>
> Provides checkpoint and recovery protocols to facilitate garbage
> collection, recovery of failed replicas, and durably logging of the
> blockchain state.
>
> Eases development and testing of newer and optimized BFT and CFT
> consensus protocols.
> Provides clients with support for three different application interfaces:
>
> Key-Value Stores - where client transactions include key-value pairs.
>
> Smart Contracts - where clients issue smart contracts in Solidity for
> processing.
>
> UTXO - where clients issue unspent transactions similar to ones in Bitcoin.
>
> Facilitates benchmarking system/protocol performance with the help of
> existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23].
>
> Stores non-volatile ledger (blockchain) in memory and for further
> durability, provides APIs to store both client data and blockchain in
> LevelDB and RocksDB.
>
>
> The serving mentors would be:
>
> Junping Du 
>
> Calvin Kirs 
>
> Kevin Ratnasekera 
>
> Roman Shaposhnik 
>
> Christian Grobmeier 
>
> and I shall be serving as the Champion.
>
> We have not done a trademark check yet for the name but that can be
> pursued independently.
>
> [1]
> https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal
> [2] https://github.com/resilientdb/resilientdb
>
> Atri
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Answer into the Apache Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Good luck !

Regards
JB

On Tue, Oct 3, 2023 at 2:17 AM Willem Jiang  wrote:
>
> Following up the [DISCUSS] thread on Answer [1] I would like to call a
> VOTE to accept into the Apache Incubator.
>
> Answer is a question-and-answer (Q) platform software for teams at
> any scale to build a help center, knowledge base, community forum,
> etc.
>
> Please cast your vote:
>
>   [ ] +1, bring into the Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring Answer 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.
>
> Please check out the Answer Proposal from the incubator wiki[2].
>
> [1]https://lists.apache.org/thread/42tvz3rqfy4w5poqgslh71sm1o1td7zn
> [2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal
>
> Best Regards,
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> -
> 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: [DISCUSS] Incubating Proposal of Answer

[Jean-Baptiste Onofré]

Hi,

It looks interesting at first glance. I will do a new pass on the
proposal (in more details).

Regards
JB

On Thu, Sep 21, 2023 at 2:00 PM Willem Jiang  wrote:
>
> We want to propose  Answer as a new Apache Incubator project.
>
> Answer[1] is a question-and-answer (Q) platform software for teams
> at any scale to build a help center, knowledge base, community forum,
> etc.
> The key features of Answer:
> 1. Questions and Answers - Ask questions and get answers from your
> users and team.
> 2. Content Organization and Management - Organize your content with
> flag, moderation, and permission.
> 3. Content Management - Manage topics and discussions in the community
> with tags.
> 4. Reputation - Reward users for their contribution: answer, verify,
> and upvote correct info. Always keep the information up-to-date.
>
> I'd be happy to be the Champion of this project, and may Thanks to
> Zili Chen ， Justin Mclean  apache.org>, and Christofer Dutz   for mentoring
> the answer project and helping us polish the incubating proposal[2].
>
> The word answer is a generic name, and trademarking it is impossible.
> But if we add the prefix of Apache, it could be more reasonable to
> use.  I look forward to your feedback and thank you for your help.
>
> [1]https://github.com/answer.dev/
> [2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal
>
> Best regards,
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> -
> 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] Retirement of the Apache DataLab

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Wed, Aug 9, 2023 at 11:27 AM Ruslan Kulynych  wrote:
>
> Hi all,
>
> Based on discussion[1], I would like to call for a vote to retire the Apache 
> DataLab.
>
> The voting will last for at least one week to ensure that everyone has time 
> to express their opinions.
>
> Please vote accordingly:
>
> [] +1 Approve
> [] +0 No opinion
> [] -1 Disapprove with a reason
>
> [1]: https://lists.apache.org/thread/k3zsksrkd5k0147pxzqndrhgsg2o6x6j
>
> Thank you all for your participation.
>
> Best regards,
> Ruslan Kulynych
>
> -
> 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 DevLake (Incubating) v0.18.0-rc1

[Jean-Baptiste Onofré]

+1(binding)

I checked:
- checksums and signatures are good.
- incubating is on the name
- LICENSE, NOTICE, DISCLAIMER files look good.
- ASF headers are present in source files
- No binary files found in source distribution

Regards
JB

On Wed, Sep 6, 2023 at 6:17 AM Junren Yu  wrote:
>
> Hello everyone,
>
> This is a call for a vote to release Apache DevLake (Incubating)
> v0.18.0-rc1.
> The Apache DevLake community has voted on and approved a proposal to
> release Apache DevLake (Incubating) version v0.18.0-rc1.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
>
> https://lists.apache.org/thread/p187lnld8qr5gn7z21kv1fsb0m420of9
>
> Community vote result thread:
>
> https://lists.apache.org/thread/6g79vnn3c15lz8z0x82p48zr0p8xyj5s
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.18.0-incubating-rc1
>
> Git tag for the release:
>
> https://github.com/apache/incubator-devlake/releases/tag/v0.18.0-rc1
>
> Keys to verify the Release Candidate:
>
> https://downloads.apache.org/incubator/devlake/KEYS
>
> How to build:
>
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
> 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
>
>
> Regards,
> Junren Yu

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

Re: [VOTE] Release Apache Wayang (Incubating) v0.7.1 RC3

[Jean-Baptiste Onofré]

+1 (binding)

Casting my vote from the podling.

Regards
JB

On Sat, Sep 9, 2023 at 7:18 PM Gláucia Esppenchutz
 wrote:
>
> Hello everyone,
>
> This calls for a vote to release Release Apache Wayang (Incubating) v0.7.1
> RC3.
> The Apache Wayang voted on and approved a proposal to release Apache Wayang
> (Incubating) version v0.7.1 RC3.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
>
> https://lists.apache.org/thread/c6d59nfmjq4gs2sfhh1n5gf4c6hxy5vb
>
> Community vote result thread:
>
> https://lists.apache.org/thread/hlc0dh2mwbpwmd9oc1s1oh7l7lj7od36
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/wayang/0.7.1/rc3/
>
> Git tag for the release:
>
> https://github.com/apache/incubator-wayang/tree/wayang-0.7.1
>
> Keys to verify the Release Candidate:
>
> https://downloads.apache.org/incubator/wayang/KEYS
>
> How to build:
>
> https://github.com/apache/incubator-wayang/tree/wayang-0.7.1#building
>
> 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
>
> --
> Gláucia Esppenchutz

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

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

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Fri, May 12, 2023 at 5:55 AM hulk  wrote:
>
> Hello all,
>
> We've got positive feedback on the DISCUSS thread[1], I'd like to start an
> official VOTE thread now.
>
> Please vote on the resolution pasted below to graduate Apache Kvrocks from
> the incubator to the Top Level Project.
>
> [ ] +1 Graduate Apache Kvrocks from the Incubator.
> [ ] +0 No opinion.
> [ ] -1 Don't graduate Apache Kvrocks from the Incubator because ...
>
> This vote will open for at least 72 hours.
>
> Many thanks to our mentors and everyone else for their support.
>
> [1] https://lists.apache.org/thread/ld8x1wvh1n745j96ksy0pmy92gwn2t06
>
> ---
>
> Establish the Apache Kvrocks 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 distributed key-value NoSQL database, supporting the rich
> data structure.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Kvrocks Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Kvrocks Project be and hereby is responsible
> for the creation and maintenance of software related to a distributed
> key-value NoSQL database, supporting the rich data structure; and be it
> further
>
> RESOLVED, that the office of "Vice President, Apache Kvrocks" 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 Kvrocks
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Kvrocks
> 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 Kvrocks Project:
>
>  * Alfejik Liu  
>  * Hulk Lin 
>  * Jean-Baptiste Onofré 
>  * Liang Chen   
>  * Mingyang Liu 
>  * Von Gosling  
>  * Xiaoqiao He  
>  * Yaroslav Stepanchuk  
>  * Yuan Wang
>  * Zili Chen
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hulk Lin be appointed to
> the office of Vice President, Apache Kvrocks, 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 Kvrocks Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Kvrocks
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Kvrocks podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.

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

Re: [VOTE] Release Apache SDAP (incubating) 1.1.0-rc0

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- the signatures/hash look OK
- incubating is in the name
- NOTICE, DISCLAIMER, LICENSE are there and look good
- ASF headers are in present in source files
- No binary found in the source distributions

Regards
JB

On Wed, May 10, 2023 at 8:00 PM Riley Kuttruff  wrote:
>
> Hello,
>
> This vote has been open for about 9 days and has so far received one binding 
> vote from our project mentor. We will need an additional 2 binding votes to 
> be able to close this thread.
>
> Thank you,
> Riley
>
> On 2023/05/01 17:20:32 Nga Chung wrote:
> > Hello Incubator PMC,
> >
> > This is a call for a vote to release Apache SDAP (incubating) version
> > 1.1.0-rc0.
> >
> > The Apache SDAP community has voted to approve the release of Apache SDAP
> > (incubating) version 1.1.0-rc0.
> >
> > We now request the Incubator PMC review and vote on this release.
> >
> > SDAP community thread:
> > https://lists.apache.org/thread/z5llljrb10zrq39368xvpm7h0bto65kh
> >
> > CHANGELOG for version 1.1.0 are available here:
> > https://github.com/apache/incubator-sdap-ingester/blob/1.1.0-rc0/CHANGELOG.md#110---2023-04-26
> > https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/CHANGELOG.md#110---2023-04-26
> >
> > Instructions for building docker images from source can be found here:
> > https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/docs/build.rst
> > Instructions for deploying locally to test can be found here:
> > https://github.com/apache/incubator-sdap-nexus/blob/1.1.0-rc0/docs/quickstart.rst
> >
> > The release files, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.1.0-rc0/
> >
> > For convenience, the tags we built the release artifacts to be voted on
> > from are 1.1.0-rc0:
> >
> > - ingester:
> >  - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.1.0-rc0
> >  - Commit: 8632b262eef9a33c816ec9b733c1ddc0156fa4c5
> >
> > - nexus:
> >  - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.1.0-rc0
> >  - Commit: 370190db8c4db86ce7837bc9fb3889c6658fac7f
> >
> > For verification, the hashes (SHA-512) of the .tar.gz artifacts we are
> > voting on are as follows:
> >
> > apache-sdap-ingester-1.1.0-incubating-src.tar.gz:
> > ab243d84d0ab7dd33bc61ab84129080b1de0dc22f15d519950dda55ade41bf65cc8b02fe0b131c6640e0782613978c8ba9e9e573156a8657cb7ce14c599fbe7c
> >
> > apache-sdap-nexus-1.1.0-incubating-src.tar.gz:
> > c51340b040ffb4e82cdd9c8ba02ba3e8b54a9194826486bac781e966218491b700685b92effc200fd8a97ee10cffb301b618e6e9c73a3a21cd42d1b75a54670e
> >
> > Release artifacts are signed with the following key:
> > https://keyserver.ubuntu.com/pks/lookup?op=get=0x1392A8A11801359247A803D8D2449E0EB5EF1E73
> >
> > Please vote on releasing this package as Apache SDAP (incubating) 1.1.0.
> >
> > The vote is open for 72 hours and passes if at least 3 +1 PMC votes are
> > cast.
> >
> > [ ] +1 Release this package as Apache SDAP (incubating) {version}
> > [ ] +0 No opinion
> > [ ] -1 Do not release this package because ...
> >
> > Thank you,
> > Nga
> >
>
> -
> 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: [DISCUSS] Graduate Apache Kvrocks (incubating) as a TLP

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Tue, May 9, 2023 at 5:46 AM hulk  wrote:
>
> Hi all,
>
> Apache Kvrocks has been incubating since 2022 April. Within this time, the
> Kvrocks community has made great progress, has adopted the Apache way, and
> has grown with the help of our mentors.
>
> After discussion with the community [1] and voted [2] for graduation with
> the result at [3]. So, we'd like to start the discussion and would
> appreciate any feedback toward graduation!
>
> Below are some facts and project highlights from the incubation phase as
> well as the draft resolution:
>
> - Released 4 Apache releases, through 4 different release managers
> - Invited 4 new committers (all accepted), bringing the total number of
> PPMC members to 19
> - Invited 2 new PPMC members (all accepted), bringing the total number of
> PPMC members to 10
> - There are 74 contributors for now
> - 442 Issues created and 383 Issues resolved
> - 911 PRs created and 819 PRs merged
> - Apache Kvrocks name search has been approved [4]
> - Finished the Podling Maturity Assessment for Kvrocks [5], all items are
> passed
>
> We've resolved all branding issues which include Logo, GitHub repo,
> document, website, and others.
>
> This is also an excellent opportunity to say a big thank you to our
> mentors. I really appreciated the prompt help at any time during incubation
> for the many questions we had. Thanks a lot, Liang Chen, tison, Xiaoqiao
> He, JB, and Von!
>
> ---
>
> Establish the Apache Kvrocks 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 distributed key-value NoSQL database, supporting the rich
> data structure.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Kvrocks Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Kvrocks Project be and hereby is responsible
> for the creation and maintenance of software related to a distributed
> key-value NoSQL database, supporting the rich data structure; and be it
> further
>
> RESOLVED, that the office of "Vice President, Apache Kvrocks" 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 Kvrocks
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Kvrocks
> 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 Kvrocks Project:
>
>  * Alfejik Liu  
>  * Hulk Lin 
>  * Jean-Baptiste Onofré 
>  * Liang Chen   
>  * Mingyang Liu 
>  * Von Gosling  
>  * Xiaoqiao He  
>  * Yaroslav Stepanchuk  
>  * Yuan Wang
>  * Zili Chen
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hulk Lin be appointed to
> the office of Vice President, Apache Kvrocks, 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 Kvrocks Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Kvrocks
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Kvrocks podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
>  [1] https://lists.apache.org/thread/5jmd8z8wsdkf9mdc0ygqc8ofxnlwz4dj
>  [2] https://lists.apache.org/thread/sn7cdvlth3xb1jmt33451snwdy47zt4w
>  [3] https://lists.apache.org/thread/hpswn4jc343dv7dos07bqjlrtwhhok99
>  [4] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-204
>  [5]
> https://github.com/apache/incubator-kvrocks-website/blob/main/maturity.md

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

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Fri, Feb 10, 2023 at 3:31 AM Eason Chen  wrote:
>
> Dear Apache Incubator Community and IPMC members,
>
> After having the graduation discussion in the EventMesh community [1],
> we passed the vote within the EventMesh community [2] and the vote
> result was published[3].
> We then discussed the graduation for EventMesh in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
>
> I would like to start this voting thread to request graduating Apache
> EventMesh(incubating) from Apache Incubator as a Top Level Project.
>
> Please provide your vote accordingly:
> [ ] +1 Yes, I support the EventMesh project to graduate from the
> Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the EventMesh project is not ready to graduate, because...
>
> Thank you for participating in the vote. This vote will stay open for
> at least 72 hours.
>
> Here is an overview of the Apache EventMesh(incubating) to help with the vote.
>
> *Community*
>
> ● 5 new PPMC members were added, bringing the total number of PPMC
> members to 14 from at least 9 different organizations.
> ● 20 new Committers were added, bringing the total number of
> committers to 42 from at least 30 different organizations.
> ● 220+ new contributors participate in the community. The number of
> contributors is now 250+ and growing.
> ● 20 Bi-weekly online meetings were held among the committers,
> contributors, and users. The meeting minutes are recorded on the
> mailing list[5] and cwiki [6].
> ● The dev@eventmesh mailing list currently has 117 subscribers.
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@eventmesh [7]. Eason
> Chen(chenguangsh...@apache.org) was recommended as Vice President.
>
> *Project*
>
> ● Apache EventMesh(incubating) builds a fully serverless platform for
> distributed event-driven applications.
> ● Project maturity model is detailed in [8].
> ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> ● EventMesh community released a total of 7 Apache releases [10] by 6
> different release managers from 5 different organizations.
> ● 1300+ issues created, and 1100+ issues closed [11].
> ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> 2500+ commits added.
> ● The release cadence is about 3 months, with an average of 180+
> issues and 230+ pull requests per release.
> ● Please refer to the EventMesh project incubation status [13][14] for
> more information.
>
> *Brands, License, and Copyright*
>
> ● We applied the brand [15], which has been reviewed and approved.
> ● EventMesh community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● EventMesh official website [17] is compliant with Apache Foundation
> requirements[18].
>
> -
> BEGINNING OF DRAFT RESOLUTION
> -
>
> Establish the Apache EventMesh 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 fully serverless platform used to build distributed
> event-driven applications.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> for the creation and maintenance of software related to a fully
> serverless platform used to build distributed event-driven applications;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache EventMesh" 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 EventMesh
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache EventMesh
> 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 EventMesh
> Project:
>
>  * Alex Luo 
>  * Du Heng  
>  * Eason Chen   
>

Re: [QUESTION] do pom files need to have a license header

[Jean-Baptiste Onofré]

Hi,

It's a better to have ASF header in all files where it's possible.
However, it's sometime difficult (test static files, web content, ..).
So if you can, it's better Pekko community fixes it.

Thanks,
Regards
JB

On Sun, Jan 29, 2023 at 6:31 PM PJ Fanning  wrote:
>
> Hi everyone,
>
> The Apache Pekko builds use the sbt tool for building and this generates pom 
> files for us. They do not include any headers (example [1]).
> It seems the norm to add an XML comment with Apache License info (example 
> from log4j [2]).
> Does the Pekko team need to fix this or is it just a nicety to have the 
> license header in the pom files? If the answer is that we do need to fix 
> this, does this also apply to other published files? sbt generates and 
> publishes a 'buildinfo' file as part of the maven publish (example [2]).
>
> Regards,
> PJ
>
>
> [1] 
> https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-actor_2.13/0.0.0+26546-767209a8-SNAPSHOT/pekko-actor_2.13-0.0.0+26546-767209a8-SNAPSHOT.pom
> [2] 
> https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-api/2.19.0/log4j-api-2.19.0.pom
> [3] 
> https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-actor_2.13/0.0.0+26546-767209a8-SNAPSHOT/pekko-actor_2.13-0.0.0+26546-767209a8-SNAPSHOT.buildinfo
>
> -
> 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 Liminal (incubating) 0.0.5rc2-INCUBATING

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- name contains incubating
- signatures and hashes are ok
- LICENSE, NOTICE, DISCLAIMER are fine
- No binary files in source distribution
- ASF headers are there

Regards
JB

On Mon, Jan 23, 2023 at 11:16 AM Lidor Ettinger  wrote:
>
> Hi All,
>
> We would like to vote on RC1 of version 0.0.5. The main purpose of V
> 0.0.5 is to provide a clear extensibility API for developers to add
> their own implementations of liminal abstractions - executor, task,
> image builder. In addition this version supports Apache Airflow 2.0.
>
> Liminal community vote and result threads:
> Vote:
> https://lists.apache.org//thread/yftpyhfzszmhbtfr6xjdyhfkpyocfy11
>
> Result:
> https://lists.apache.org//thread/9hsm5z4hygv4f0l059crp5bmp3hgg3m4
>
> Installation and testing instructions can be found in the README included.
>
> The release files, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/liminal/0.0.5rc2-INCUBATING/
>
>
> The tag to be voted on:
>
> https://github.com/apache/incubator-liminal/releases/tag/0.0.5rc2-INCUBATING
>
>
> The SHA512 Checksum for these artifacts is:
>
> apache-liminal-0.0.5rc1-incubating-source.tar.gz:
>
> 1937572ef1296d6f182ee855513b9884a290134d033afecaccb31c2208578d46395579192c37721d01e1807e3838915c96e55a8156e24871bf8aaf340e533500
>
>
> Release artifacts are signed with the following key:
>
> https://dist.apache.org/repos/dist/dev/incubator/liminal/KEYS
>
>
> For more information about the contents of this release,
> see:https://issues.apache.org/jira/projects/LIMINAL/versions/12352738
>
>
> Please vote on releasing this package as Apache Liminal
> 0.0.5-INCUBATING. A majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Liminal 0.0.5
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
>
> Regards,
> Lidor Ettinger

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

Re: [VOTE]Release Apache Liminal (incubating) 0.0.5rc1-incubating

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Wed, Jan 11, 2023 at 11:40 PM Lidor Ettinger  wrote:
>
>
> Hi All,
>
> We would like to vote on RC1 of version 0.0.5. The main purpose of V
> 0.0.5 is to provide a clear extensibility API for developers to add
> their own implementations of liminal abstractions - executor, task,
> image builder. In addition this version supports Apache Airflow 2.0.
>
> Liminal community vote and result threads:
> Vote:
> https://lists.apache.org//thread/rko6z3c2vxk4hrg201n72lxjhycjwkh4
>
> Result:
> https://lists.apache.org//thread/zqtj82nh3mm33k2ddfby7442d901h0qo
>
> Installation and testing instructions can be found in the README included.
>
> The release files, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/liminal/0.0.5rc1-incubating/
>
> The tag to be voted on:
>
> https://github.com/apache/incubator-liminal/releases/tag/0.0.5rc1-incubating
>
>
> The SHA512 Checksum for these artifacts is:
>
> apache-liminal-0.0.5rc1-incubating-source.tar.gz:
>
> bebd119326ffe455f6b8f4227e36af5452648e7ffefc6d864ee9ec0a050b71e7701dbe1b90354b5d164191a505a3f50191be41be8e474379755d1a36934e4516
>
>
> Release artifacts are signed with the following key:
>
> https://dist.apache.org/repos/dist/dev/incubator/liminal/KEYS
>
> For more information about the contents of this release,
> see:https://issues.apache.org/jira/projects/LIMINAL/versions/12352738
>
> Please vote on releasing this package as Apache Liminal
> 0.0.5-INCUBATING. A majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Liminal 0.0.5
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
>
> Regards,
> Lidor Ettinger

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

Re: [VOTE] Release Apache DataLab (incubating) 2.6.0

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- Signature and hash are good
- LICENSE, NOTICE and DISCLAIMER are there and look good
- ASF headers are present
- No binary file found in source distribution

Regards
JB

On Tue, Nov 22, 2022 at 11:39 AM  wrote:
>
> Hello Incubator Community,
>
>
>
> The Apache DataLab community has voted on and approved a proposal to release
> Apache DataLab (incubating) version 2.6.0. We now kindly request the
> Incubator PMC members review and vote in this release.
>
> DataLab is a platform for creating self-service, exploratory data science
> environments in the cloud using best-of-breed data science tools. DataLab
> includes a self-service web console, used to create and manage exploratory
> environments. It allows teams to spin up analytical environments with just a
> single click of a mouse. Once established, the environment can be managed by
> an analytical team itself, leveraging simple and easy-to-use web-based
> interface.
>
>
>
> DataLab community vote thread:
>
>   https://lists.apache.org/thread/dyz4b5dwr995o632yr630c3d4v0tco3q
>
>
>
> Vote result thread:
>
>   https://lists.apache.org/thread/7yz825y1ys2sqfsdbk2v0tkcg56rl8oh
>
>
>
> The release candidate:
>
>   https://dist.apache.org/repos/dist/dev/incubator/datalab/2.6.0/
>
>
>
> Git tag for the release:
>
>   https://github.com/apache/incubator-datalab/tree/2.6.0
>
>
>
> Release notes:
>
>   https://github.com/apache/incubator-datalab/blob/v2.6.0/RELEASE_NOTES.md
>
>
>
> The artifacts signed with PGP key CDEDB0F011390548, corresponding to
> frolovl...@gmail.com  .
>
> KEYS file is available here:
> https://downloads.apache.org/incubator/datalab/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,
>
> The Apache DataLab (Incubating) Team
>
>
>

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

Re: [VOTE] Release Apache Sedona 1.3.0-incubating-rc2

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- LICENSE, NOTICE and DISCLAIMER are present and look good
- Signature and hash look good
- ASF headers present in most of source files
- No binary file found in source distribution
- Build is OK

Regards
JB

On Mon, Nov 28, 2022 at 4:45 PM li gang  wrote:
>
> +1 (non-binding)
> I checked
> - Files have the word incubating in their name.
> - Good signature from .
> - Checksum is correct.
> - DISCLAIMER,LICENSE and NOTICE files exist.
> - LICENSE looks good.
>
> Jia Yu  于2022年11月22日周二 12:36写道：
>
> > Hi all,
> >
> > This is a call for vote on Apache Sedona 1.3.0-incubating-rc2. Please refer
> > to the changes listed at the bottom of this email.
> >
> > Sedona Community vote thread (Permalink from
> > https://lists.apache.org/list.html):
> > https://lists.apache.org/thread/f7vnm6pchltjco686dsqfc8ntrhbwto2
> >
> > Sedona community vote result thread (Permalink from
> > https://lists.apache.org/list.html):
> > https://lists.apache.org/thread/4098nf7rl8byl8pkcyyj8z62qt3l9rkh
> >
> > Release notes:
> >
> > https://github.com/apache/incubator-sedona/blob/sedona-1.3.0-incubating-rc2/docs/setup/release-notes.md
> >
> > Build instructions:
> >
> > https://github.com/apache/incubator-sedona/blob/sedona-1.3.0-incubating-rc2/docs/setup/compile.md
> >
> > GitHub tag:
> >
> > https://github.com/apache/incubator-sedona/releases/tag/sedona-1.3.0-incubating-rc2
> >
> > GPG public key to verify the Release:
> > https://downloads.apache.org/incubator/sedona/KEYS
> >
> > Source code and binaries:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/sedona/1.3.0-incubating-rc2/
> >
> > The vote will be open for at least 72 hours or until at least 3 "+1" PMC
> > votes are cast
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove with the reason
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> >
> > [ ] Checksums and PGP signatures are valid.
> >
> > [ ] DISCLAIMER is included.
> >
> > [ ] Source code artifacts have correct names matching the current release.
> >
> > For a detailed checklist  please refer to:
> >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > Thanks,
> > Jia
> >
>
>
> --
>
>
> --
> Best Regards
>
> DolphinScheduler PMC
> Gang Li 李岗
>
> lgcar...@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 EventMesh (incubating) 1.7.0-rc1

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- LICENSE, NOTICE and DISCLAIMER files are there and look good
- Signatures and hashes are good
- ASF headers are present in source files
- No binaries found in the source distribution

Regards
JB

On Fri, Nov 25, 2022 at 6:01 AM Alex Luo  wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache EventMesh(Incubating)
> version 1.7.0-rc1
>
> The Apache EventMesh community has voted on and approved a proposal to
> release
> Apache EventMesh(Incubating) version 1.7.0-rc1
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> EventMesh community vote thread:
> • https://lists.apache.org/thread/0t8lz5d3ypbnd1094tkrc57ql12w6ckl
>
> Vote result thread:
> • https://lists.apache.org/thread/p4zm61p636gjj7msmj8smyx8nsthn9kx
>
> The release candidate:
> •https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.7.0-rc1
>
> Git tag for the release:
> • https://github.com/apache/incubator-eventmesh/tree/v1.7.0-rc1
> Release notes:
> • https://eventmesh.apache.org/events/release-notes/v1.7.0
>
> The artifacts signed with PGP key
> 235DBB05A82D0D8C1492D50079CD973EA1DBF237, corresponding to
> alex...@apache.org, that can be found in keys file:
> • https://downloads.apache.org/incubator/eventmesh/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 Apache EventMesh(Incubating) community

-
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

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Sun, Nov 27, 2022 at 11:17 AM Shuai Di  wrote:
>
> Dear Apache Incubator Community and IPMC members,
>
> After having the graduation discussion in the Linkis community [1], we
> have passed the vote within Linkis community [2] and the vote result
> was published[3].
> We then discussed the graduation for Linkis in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
>
> I would like to start this voting thread to request graduating Apache
> Linkis(incubating) from Apache Incubator as a Top Level Project.
>
> Please provide your vote accordingly:
> [ ] +1 Yes, I support Linkis project to graduate from the Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the Linkis project is not ready to graduate, because...
>
> Thank you for participating in the vote. This vote will stay open for at
> least 72 hours.
>
> Here is an overview of the Apache Linkis(incubating) to help with the
> vote.
>
> *Community*
>
> ● 4 new PPMC members were added, bringing the total number of PPMC
> members to 24 from 15 different organizations.
> ● 13 new committers were added(including the new PPMC members),
> bringing the total number of committers to 33 from 21 different
> organizations.
> ● 79 new contributors. The number of contributors is now 128 and growing.
> ● 21 biweekly online meetings were held in the community among PPMC
> members, committers, contributors, and users. The meeting minutes are
> recorded on the cwiki and mailing list [5].
> ● The dev@linkis mailing list currently has 113 subscribers [6].
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@linkis [7]. Shuai Di(shua...@apache.org) was
> voted as Vice President.
>
> *Project*
>
> ● Apache Linkis(incubating) builds a computation middleware layer to
> facilitate connection, governance and orchestration between the upper
> applications and the underlying data engines.
> ● Project maturity model is detailed in [8]
> ● Linkis has been incubating [9] since 2021-08-02 for over 15
> months.
> ● Linkis community released a total of 7 Apache releases [10] by 7
> different release managers from 6 different organizations.
> ● 1935 pull requests created, and 1894 pull requests closed [11].
> ● 1488 issues created, and 1271 issues closed [12].
> ● The release cadence is about 2 months, with an average of 200+
> issues and 270+ pull requests per release.
> ● Please refer to the Linkis project incubation status [13][14] for more
> information.
>
> *Brand, License, and Copyright*
>
> ● We submitted an application for the brand [15] and it has been
> reviewed and approved.
> ● Linkis community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● Linkis official website [17] is compliant with Apache Foundation
> requirements [18].
>
> -
> BEGINNING OF DRAFT RESOLUTION
> -
>
> Establish the Apache Linkis 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 distributed and computation middleware to
> facilitate connection, governance, and orchestration between the upper
> 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 

Re: [VOTE] Graduate Apache bRPC to a TLP

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Fri, Nov 11, 2022 at 3:47 PM Jerry Tan  wrote:
>
> Hello, dear IPMC members,
>
> following the [DISCUSS] thread at [1],
>
> I'd like to call a vote to graduate bRPC to a TLP.
>
>
> Please vote accordingly:
>
> [ ] +1 Apache bRPC (incubating) is ready to graduate to a TLP
>
> [ ] +0 No opinion.
>
> [ ] -1 Apache bRPC (Incubating) is not ready to graduate (please state
> reasons)
>
>
> Thank you for participating in the vote!
>
>
> Best regards
>
> Jerry Tan
>
>
> ---
>
> Project Updates since 2018-11-13:
>
> ---
>
>
> 1. We release 1.0.0,1.1.0, 1.2.0, 1.3.0, 4 apache releases, and
> 0.9.6,0.9.7, 2 disclaim releases; by different release managers (including
> Jerry Tan, Jiashun Zhu, Lorin Lee, Wang Weibing, Shuai Liu, Xiguo Hu) (see
> it at [2])
>
>
> 2. We add 5 new PPMC members including Jiashun Zhu, Wang Weibing, Cai
> Daojin, He Lei, and Lorin Lee. see it at [2]. Now we have 10 PPMC members
> altogether, they are from different companies, including ByteDance (James Ge,
> He Lei), Baidu (Yao Wang, Wang Weibing), Google (Jiashun Zhu), 4Paradigm 
> (Jerry
> Tan), Shopee (Cai Daojin), Momenta.AI (Zhangyi Chen), Ant Group (Bear Jiang
> ), Freelancer (Lorin Lee).
>
>
> 3. We add 9 new committers, including Cai Daojin, He Lei, Mou Gaidong, Lorin
> Lee, Wang Wei, Shuai Liu, Wang Xiaofeng, Xiguo Hu, and Guangming Chen. see
> it at [2].
>
>
> 4. There are 17 members subscribed to the private email list and 60
> engineers subscribed to the dev mail list. The discussion on the dev mail
> list is active, including release, roadmap, committer related topics. see
> it at [3]
>
>
> 5. Branding issues have been solved and name searching has been completed.
> See it at [4]
>
>
> 6. Assessment of the maturity model is available at [5]. All answers to
> these check items are 'Yes'.
>
>
> 7. The bRPC website has passed the Apache Podling Website Checks [6].
>
>
> 8. 1000+ issues resolved[7], and 600+ pull requests merged and closed[8].
>
>
> 9. bRPC has been widely adopted outside Baidu since incubating, including
> iQiyi， Bytedance， Bilibili， Bigo， Didi， Weibo， Vivo，4padradigm， X
> iaohongshu， Ishumei， Doris， Amap， etc.
>
>
> And we plan to move on with new features and new scenarios, such as RDMA
> support has been integrated into the trunk and will be included in the next
> release, and extend bRPC with service mesh features.
>
> ---
>
> Draft resolution
>
> ---
>
> Establish the Apache bRPC 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 industrial-grade RPC framework for building reliable and
>
> high-performance services.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>
> (PMC), to be known as the "Apache bRPC Project", be and hereby is
>
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache bRPC Project be and hereby is responsible for
>
> the creation and maintenance of software related to an industrial-grade
>
> RPC framework for building reliable and high-performance services; and
>
> be it further
>
> RESOLVED, that the office of "Vice President, Apache bRPC" 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 bRPC Project, and to
>
> have primary responsibility for management of the projects within the
>
> scope of responsibility of the Apache bRPC 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 bRPC Project:
>
> * Bear Jiang 
>
> * Cai Daojin 
>
> * He Lei 
>
> * James Ge 
>
> * Jean-Baptiste Onofré 
>
> * Jerry Tan 
>
> * Jiashun Zhu 
>
> * Juan Pan 
>
> * Lorin Lee 
>
> * Von Gosling 
>
> * Wang Weibing 
>
> * Yao Wang 
>
> * Zhangyi Chen 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that James Ge be appointed to
>
> the office of Vice President, Apache bRPC, 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 fur

Re: [VOTE] Release Apache Kvrocks (incubating) 2.2.0

[Jean-Baptiste Onofré]

+1 (binding)

Casting my vote from dev to incubator mailing list.

Regards
JB

On Mon, Nov 14, 2022 at 2:20 PM Twice  wrote:
>
> Hello IPMC,
>
> The Apache Kvrocks (incubating) community has voted and approved the
> release of Apache
> Kvrocks(incubating) 2.2.0. We now kindly request the IPMC members
> review and vote for this release.
>
> Kvrocks is a distributed key value NoSQL database that uses RocksDB as the
> storage engine
> and is compatible with Redis protocol. The current release provides many
> new features,
> improvements to existing features and bug fixes.
>
> Kvrocks community vote thread:
>
> https://lists.apache.org/thread/10bxhgdd4nlk6dt039b4zxh2k4c3xncb
>
> Vote result thread:
>
> https://lists.apache.org/thread/djtoc1lgy56wtchtsl0r4jy6r8lhbv3l
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.2.0
>
> This release has been signed with a PGP available here:
>
> https://dist.apache.org/repos/dist/dev/incubator/kvrocks/KEYS
>
> Git tag for the release:
>
> https://github.com/apache/incubator-kvrocks/tree/v2.2.0
>
> Build guide can be found at:
>
> https://github.com/apache/incubator-kvrocks#build
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
>
> Please vote accordingly:
> [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.2.0
> [ ] +0
> [ ] -1 Do not approve (please specify the reason)
>
> Thanks!
>
> Best wishes,
> Twice

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

Re: [VOTE] Graduate Kyuubi from Apache Incubator as a Top Level Project

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Tue, Nov 15, 2022 at 4:57 AM Kent Yao  wrote:
>
> Hello, Incubator community and IMPC-ers,
>
> Following the discussion[0], I'd like to call a vote to graduate Kyuubi from
> Apache Incubator as a Top-Level Project.
>
> Please vote accordingly:
> [ ] +1 it is ready to graduate from the Apache Incubator to a TLP.
> [ ] +0 No opinion.
> [ ] -1 it is not ready to graduate (please state reasons)
>
> Thank you for participating in the vote. This vote will stay open for at
> least 72 hours.
>
> Best Regards,
> Kent Yao
>
>
> Kyuubi has been an incubating project since 2021-06-21 after the
> proposal[1] was accepted. During the incubation, the Kyuubi project
> and community developed stably and continuously following the Apache
> Way. By sorting out and self-checking the Kyuubi maturity model[2],
> we believe that the Kyuubi project is ready for graduating as a Top
> Level Project. Meanwhile, corresponding threads for both discussions[3]
> and vote[4][5] have been finished in the kyuubi@dev mailing list with
> positive results. Please refer to the Kyuubi project incubation status[15]
> for more information.
>
> Here is a brief overview of the progress of the Apache Kyuubi(incubating)
> project and community since entering the incubator:
>
> ** Community **
>
> - 3 new PPMC members were added, bringing the total number to 12.
> The community strives to be meritocratic and diverse, the current
> PPMC(mentors excluded) consists of individuals from different 
> organizations[16],
> China Mobile(1), Ctrip(1), eBay(1), NetEase(4), and T3(1).
> - 8 new committers were added, bringing the total number to 17. The newly
> added committers(PPMC excluded) are also from different organizations,
> AsiaInfo(1), Bilibili(1), Dingxiangyuan(1), iQiYi(1), and NetEase(1).
> - 60+ new contributors participate in the community. The number of
> contributors are now 99 and still growing.
> - The dev@kyuubi mailing list currently has 89 subscribers, and all major
> project discussions happen there. The GitHub discussions page is also being
> actively used for user questions, feature requests, story sharing, etc.
> - Held 3 meetups by our community, and participated in 20+ events, such as
> ApacheCon, to promote the Kyuubi project.
> - All PPMC members are willing to join the Kyuubi PMC membership after
> graduation[6][7].
> - Kent Yao(y...@apache.org) was voted as Vice President[8].
>
> ** Project **
>
> - 8 releases[9] by 8 different release managers.
> - 1400+ pull requests merged[10], and 900+ issues resolved[11].
> - Kyuubi website[12] is now compliant with the Apache Project Website
> requirements[13].
> - Project maturity model is detailed in[2].
>
> ** Licensing and Branding Issues **
>
> - We have applied the podling name search[14] and it has been reviewed
> and approved.
> - IP Clearance: 2021-06-21
> - Software Grant Received on: 2021-07-04
> - Confirmation of ASF Copyright Headers on Source Code on: 2021-06-21
> - Confirmation of Binary Distribution Licensing: 2021-09-14
>
>
> --
> BEGINNING OF DRAFT RESOLUTION
> --
>
> Establish the Apache Kyuubi 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 distributed and multi-tenant gateway to provide serverless
> SQL on data warehouses and lakehouses.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Kyuubi Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Kyuubi Project be and hereby is responsible
> for the creation and maintenance of software related to a distributed
> and multi-tenant gateway to provide serverless SQL on data warehouses
> and lakehouses.; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Kyuubi" 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 Kyuubi
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Kyuubi
> 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 Kyuubi Project:
>
> * Akira Ajisaka 
> * Cheng Pan 
> * Dongdong Hong 
> * Duo Zhang 
> * Fei Wang 
> * Hongxiang Jiang 
> * Jeff Zhang 
> * Kent Yao 
> * Shaoyun Chen 
> * Vino Yang 
> * Willem Ning Jiang 
> * XiDuo You 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kent Yao be appointed to
> the office of Vice President, Apache Kyuubi, to serve in accordance with
> and subject to the direction of the 

Re: [VOTE] Graduate Apache StreamPieps to a TLP

[Jean-Baptiste Onofré]

+1

Regards
JB

On Sun, Nov 6, 2022 at 10:32 PM Dominik Riemer  wrote:
>
> Hi everyone,
>
> following the [DISCUSS] thread at [0], I'd like to call a vote to graduate 
> StreamPipes to a TLP.
>
> Please vote accordingly:
>
> [ ] +1 Apache StreamPipes (incubating) is ready to graduate from the
> Apache Incubator to a TLP.
>
> [ ] +0 No opinion.
>
> [ ] -1 Apache StreamPipes (Incubating) is not ready to graduate (please state 
> reasons)
>
> Thank you for participating in the vote!
>
> Cheers
> Dominik
>
>
> ---
> Project highlights
> ---
>
> * Incubating since 2019-11-11
> * 5 releases (0.66.0, 0.67.0, 0.68.0, 0.69.0, 0.70.0)
> * 3 different release managers
> * 13 PPMC members (almost all from different organizations), including 5 
> mentors
> * 8 additional committers
> * active community with all discussions happening on the mailing list and 
> dedicated user mailing list as support channel
> * community building & talks at ACNA19, 20, 21, 22 + Asia, SF Big Data 
> Analytics and many other webinars
> * over 9.000 commits
> * 52 subscribers on the dev list, 57 subscribers on the users list
> * Articles about StreamPipes in the US Linux Magazine [4], and StreamPipes 
> was named one of the
> top 5 open source tools for IoT Analytics by OpenSourceForU [5]
> * Number of Github stars has increased to currently 350
> * Website [6], extensive documentation [7] and a developer wiki [8]
> * Strong connection and integration with other projects in the Apache IoT 
> space (e.g., PLC4X)
> * Completed maturity self-assessment [9]
>
>
> ---
> Draft resolution
> ---
>
> Establish the Apache StreamPipes 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 self-service Industrial IoT toolbox which enables
> non-technical users to connect, analyze and explore IoT
> data streams.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache StreamPipes Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache StreamPipes Project be and hereby is
> responsible for the creation and maintenance of software related to a
> self-service Industrial IoT toolbox which enables non-technical users to
> connect, analyze and explore IoT data streams; and be it
> further
>
> RESOLVED, that the office of "Vice President, Apache StreamPipes" 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
> StreamPipes Project, and to have primary responsibility for management
> of the projects within the scope of responsibility of the Apache
> StreamPipes 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 StreamPipes
> Project:
>
> * Christofer Dutz 
> * Dominik Riemer 
> * Grainier Perera 
> * Jean-Baptiste Onofré 
> * Johannes Tex 
> * Julian Feinauer 
> * Justin Mclean 
> * Kenneth Knowles 
> * Marco Heyden 
> * Patrick Wiener 
> * Philipp Zehnder 
> * Stefan Obermeier 
> * Tim Bossenmaier 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Philipp Zehnder be
> appointed to the office of Vice President, Apache StreamPipes, 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 StreamPipes Project be and hereby is tasked
> with the migration and rationalization of the Apache Incubator
> StreamPipes podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> StreamPipes podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
>
> ---
>
> [0] https://lists.apache.org/thread/dg3z175h2szcg3wgz9tmq770krvscvp8
>
> [1] https://lists.apache.org/thread/18vgpw0jq93rwh9mj9bb27nj7gjhmldg
>
> [2] https://lists.apache.org/thread/q6n11kfmmj1vgo6vq19nq1km5p1vow28
>
> [3] https://lists.apache.org/thread/5ybqmx8z768ksdymz2h2gjsx91p1drpp
>
> [4] https://www.linux-magazine.com/Issues/2021/244/Apache-StreamPipes
>
> [5] 
> https://www.o

Re: Voting Counting Procedure - need counted votes be on vote thread?

[Jean-Baptiste Onofré]

Hi Austin,

Only the vote on the [VOTE] thread should count, as a best practice.

Regards
JB

On Sun, Nov 6, 2022 at 11:42 PM Austin Bennett  wrote:
>
> Hi Incubator,
>
> Looking for guidance on Voting - and I do mean more general than just for
> incubating projects.  I do see:
> https://www.apache.org/foundation/voting.html
>
> I wonder about how to count votes.  Specifically, must they occur on the
> Vote thread?  Can someone cast their vote on another mailing list or
> another [ ? related ? ] thread?
>
> My inclination is that a Vote needs to occur on the common Vote thread, for
> cleanliness and ease of people tracking throughout the vote.  But I don't
> see definitive guidelines from the documentation which I have looked at. I
> imagine there are at least conventions if not more spelled out
> documentation/guidelines?
>
> Please advise,
> Thanks,
> Austin

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

Re: [VOTE] Release Apache Milagro (incubating) MPC v0.1

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- LICENSE, NOTICE, DISCLAIMER are there and look good
- Signature and hash are OK
- ASF header is there (rat complains about some missing header in sh scripts)
- No binary file in source distribution
- Build passed on my machine

Regards
JB

On Wed, Oct 26, 2022 at 7:32 PM John McCane-Whitney
 wrote:
>
> Hi,
>
> This is a call to vote on the release of the Apache Milagro (incubating) MPC 
> v0.1
>
> The Apache Milagro (incubating) community has voted to approve this release 
> with 5 +1 votes. The vote result thread can be found here:
> https://lists.apache.org/thread/y95lold2mt751w6z2g5cycr9dr1rjsjr
>
> Release tag for Incubator-milagro-MPC:
> https://github.com/apache/incubator-milagro-MPC/releases/tag/0.1
>
> OVERVIEW
> libmpc is a modern cryptographic C library that implements Multi-Party 
> Computation, or MPC.
> This library implements the primitives necessary to instantiate the 
> multi-party ECDSA signature scheme provided in Gennaro and Goldfeder’s “Fast 
> Multiparty Threshold ECDSA with Fast Trustless Setup” (GG18) 
> (https://eprint.iacr.org/2019/114.pdf).
> GG18 consists of a multiparty threshold signature scheme which enables 
> distributed signing among n players such that any subgroup of size t + 1 can 
> sign, whereas any group with t or fewer players cannot. This scheme is proven 
> secure for any t <= n and provides significant reduction of computation and 
> communication complexity comparing to other existing schemes.
> NCC Group has conducted a security assessment of libmpc 
> (https://research.nccgroup.com/wp-content/uploads/2020/07/NCC_Group_Qredo_Apache_Milagro_MPC_Cryptographic_Review_2020-07-16_v1.3.pdf).
>
> RELEASE RATIONALE
> libmpc has been under development for several years now, and we consider it 
> to be stable enough to have a first official release.
> With this release, we also introduce a modernised docker-first build-system 
> that we would like to extend to other Apache Milagro releases. We have taken 
> this step to better support the most diverse development and deployment 
> environments currently used by the community. Please provide feedback if 
> there is anything you would like to see happening next.
> As always, please see the README for build/test instructions, a list of 
> contributors and guidelines on how to contribute yourself.
>
> The repo has the required DISCLAIMER, NOTICE and LICENSE file in its root 
> directory. All source files have the appropriate license header. No binaries 
> are included in this release.
>
> I have successfully built and ran the tests as per the instructions in the 
> readme file.
>
> The compressed archives from this release along with a SHA512 checksum, PGP 
> signature and PGP key file are being staged here:
> https://dist.apache.org/repos/dist/dev/incubator/milagro/apache-milagro-mpc-0.1-incubating/
>
> Specifically:
> Source code archive: 
> https://dist.apache.org/repos/dist/dev/incubator/milagro/apache-milagro-mpc-0.1-incubating/apache-milagro-mpc-0.1-incubating-src.tar.gz
> SHA512 checksum: 
> https://dist.apache.org/repos/dist/dev/incubator/milagro/apache-milagro-mpc-0.1-incubating/apache-milagro-mpc-0.1-incubating-src.tar.gz.sha512
> PGP Signature: 
> https://dist.apache.org/repos/dist/dev/incubator/milagro/apache-milagro-mpc-0.1-incubating/apache-milagro-mpc-0.1-incubating-src.tar.gz.asc
> Keys: https://dist.apache.org/repos/dist/dev/incubator/milagro/KEYS
>
> Documentation can be found here: https://milagro.apache.org/docs/mpc-api-0.1/ 
> (including a link at the bottom of the page to the Doxygen output from the 
> MPC library).
>
> Please note that the project’s website (https://milagro.apache.org/) will be 
> updated with download links as soon as the release’s approval has been 
> completed and the archives are available for public download.
>
> We now kindly request that the Incubator PMC members review and vote on this 
> incubator release as follows:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Checklist for reference:
>
> [ ] Download links are valid
> [ ] Checksums and PGP signatures are valid
> [ ] DISCLAIMER, LICENCE & NOTICE files are included
> [ ] Source code archives have correct names matching the current release.
> [ ] All source code files have licence headers
> [ ] No compiled binaries are included
> [ ] Libraries build correctly and all tests pass (as per the instructions in 
> the readme file)
>
> The vote will be open for a minimum of 72 hours. 3 x +1 votes are required to 
> approve this release.
>
> Many thanks,
> John
>
> John McCane-Whitney
> DIRECTOR OF PRODUCT
> +44 (0) 7966 490687
> qredo.com 
>     
>  
> Qredo Ltd is a limited company registered in England and Wales (registered 
> number 7834052).  This e-mail and any attachments are confidential, and are 
> intended only for the 

Re: [VOTE] Release Apache SeaTunnel(Incubating) 2.3.0-beta

[Jean-Baptiste Onofré]

+0 (binding)

I checked:
- incubating is in the name
- LICENSE, NOTICE, DISCLAIMER are there and look good
- ASF header in source files but missing in some pom.xml, adding rat
and fixing that would be good
- No binary file found in source distribution
- Hash and signature are OK
- Simple build failed on machine (I didn't have time to check why)

Regards
JB

On Thu, Oct 27, 2022 at 5:44 PM JUN GAO  wrote:
>
> Hello IPMC, This is an official vote for the Apache SeaTunnel(Incubating)
> 2.3.0-beta that we have been working toward. To learn more about Apache
> SeaTunnel(Incubating), please see [https://seatunnel.apache.org](
> https://seatunnel.apache.org/) Apache SeaTunnel (incubating) community has
> voted and approved the release. Vote thread:
> https://lists.apache.org/thread/bjco85g5j6q8b22h5w8t5h4g0o7nv6ch
>
> Result thread:
>
>  https://lists.apache.org/thread/4117768lxy9t8x7c6o8d94kf2wywqyzc
>
> Release changes:
>
>   https://github.com/apache/incubator-seatunnel/blob/2.3.0-beta/release-note
> 
> .md The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/seatunnel/2.3.0-bet
> a
> Maven 2 staging repository:
> https://repository.apache.org/content/repositories/orgapacheseatunnel-1014/org/apache/seatunnel/
> Git tag for the release:
> https://github.com/apache/incubator-seatunnel/tree/2.3.0-beta Release
> Commit ID:
>
> https://github.com/apache/incubator-seatunnel/commit/f57b897079e51e63a708e4ad475f073358495029
>
> Keys to verify the Release
> Candidate: https://downloads.apache.org/incubator/seatunnel/KEYS
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no
> opinion [ ] -1 disapprove with the reason Checklist for reference: [ ]
> Download links are valid. [ ] Checksums and PGP signatures are valid. [ ]
> DISCLAIMER is included. [ ] Source code artifacts have correct names
> matching the current release. [ ] LICENSE and NOTICE files are correct for
> each SeaTunnel repo. [ ] All files have license headers if necessary. [ ]
> No compiled archives bundled in source archive. More detail checklist
> please refer:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> The following votes are carried over from the SeaTunnel dev mailing list:
> +1(binding) David,
> William Kwok，
> Calvin Kirs
>
> --
>
> Best Regards
>
> 
>
> EricJoy2048
> gaojun2...@gmail.com

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

Re: [VOTE] Accept Pekko into the Apache Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Wed, Oct 19, 2022 at 10:04 AM Claude Warren, Jr
 wrote:
>
> After reviewing the [DISCUSS] threads concerning bringing Pekko into the
> incubator [1][2], and finding that there is no further comment, I am
> calling for a VOTE to accept Pekko into the Apache Incubator.  The text of
> the proposal is included below for convenience, final and definitive text
> is in the Pekko Proposal from the Incubator wiki.[3] .
>
> Thank you for your time and consideration,
> Claude
>
> [1] https://lists.apache.org/thread/1t0x6d815td9dgjxhck51b5txcjm28rr
> [2] https://lists.apache.org/thread/cjo86gdwvqlqslq68gd0c8hxq6ds6yrz
> [3] https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal
>
> *Pekko Proposal*
>
> *Abstract*
>
> Pekko is a toolkit and an ecosystem for building highly concurrent,
> distributed, reactive and resilient applications for Java and Scala.
>
> *Proposal*
>
> Pekko is a toolkit that brings the actor model (popularised by Erlang) to
> the JVM, providing the basis for building both locally and distributed
> concurrency. On top of this Pekko provides a rich set of libraries built on
> top of Actors to solve modern problems, including:
>
>- Streams: Fully bi-directional backpressured streams following the
>Reactive manifesto
>- HTTP: A fully streamed HTTP client/server built on top of streams that
>also provides expected tools (such as connection pooling) necessary for
>highly available web services
>- connectors: A rich set of connectors for various databases, messaging,
>persistent services built on top of streams
>- grpc: A gRPC server/client
>- projection: Provides abstractions necessary for CQRS pattern such as
>envelope, necessary for systems such as Kafka.
>
> *Background*
>
> Pekko is a fork of the Akka project just before its licence changed from
> Apache 2 to Business Source License 1.1. The project provides a set of
> tools and frameworks that covers the complex problem space of distributed
> concurrent systems. It is designed to support the design principles of the
> Reactive Manifesto by providing components to efficiently scale up systems
> within a server or scale out across multiple servers, are high performance,
> resilient to failure, distributed systems without a single point of failure.
>
> *Rationale*
>
> There is a large cohort of applications and libraries that were dependent
> upon the original open source version of this project. Numerous developers
> contributed their time in the belief that the project would stay open
> source. When the licence was changed the work of those developers was
> locked up and a vital resource for the cohort of applications and libraries
> disappeared. Apache Flink is an example of a library that used the original
> library upon which this project is based. This project is to continue the
> open source development that was promised under the original Apache 2
> licence. We ask that the Apache Foundation accept this project so as to
> prevent any future incompatible licence switch in the future.
>
> Apache has a long standing tradition of not accepting hostile forks. There
> has been some discussion of whether this project violates that tradition.
> We believe that it does not.
>
> For many years, Lightbend has been a steward for this open source project,
> attracting contributions from many developers and building a community
> under the Apache License. It's within their rights to offer their future
> work under a different licence. The Pekko project will provide the
> continuity of an Apache-licensed home for long-term support, maintenance
> and new features for the developers that wish to continue using and
> building on their previous work. The major historical reason why Apache
> would be a good home for Pekko is that it will protect the project from
> licence changes similar to what is instigating the initial incubation
> proposal. If Pekko becomes part of Apache then it gives confidence to the
> community/users of Pekko that such an incident won’t happen in the future
> again. There are also currently existing Apache projects such as Flink that
> use Akka to varying degrees and hence having Pekko to be part of Apache
> gives confidence to these other Apache projects. We believe that this fork
> is a maintenance of the pre-existing Apache 2 licence and ask that the
> Apache community view it as such.
>
> In general, Akka had a very large penetration in both Scala and Java
> codebases, particularly in large scale enterprise projects/systems. Since
> it is a JVM based library it fits well into the Apache ecosystem. We feel
> that we can contribute to the stability of existing Apache projects as
> Apache can contribute to the stability of Pekko.
>
> *Initial Goals*
>
> Due to the sheer size of Akka, initial goals will be largely be adjusting
> and modifying the codebase so its fit for community orientated
> contributions, this includes:
>
>
>- Removing the Akka 

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

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- signature and hash are OK
- ASF headers are present in the sources (.h/.c files)
- LICENSE, NOTICE, DISCLAIMER look good
- No binary file in the source distribution (only the png files in docs/images)

Regards
JB

On Sat, Oct 15, 2022 at 3:59 PM Xiguo Hu  wrote:
>
> Hi Incubator Community,
>
> This is a call for a vote to release Apache brpc(Incubating) version
> 1.3.0.
>
> The Apache brpc community has voted and approved the release of Apache
> brpc (Incubating) 1.3.0.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> brpc is an industrial-grade RPC framework with extremely high performance,
> and it supports multiple protocols, full rpc features, and has many
> convenient tools.
>
> brpc community vote thread:
> https://lists.apache.org/thread/hrymv716j1q5cw382h1t0zq7gjpp2tbd
>
> Vote result thread:
> https://lists.apache.org/thread/xzkp3zlqkf7khnctfoqxdqxs8fkj6lt7
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/brpc/1.3.0/
>
> This release has been signed with a PGP available here:
> https://downloads.apache.org/incubator/brpc/KEYS
>
> Git tag for the release:
> https://github.com/apache/incubator-brpc/releases/tag/1.3.0
>
> Build guide and get started instructions can be found at:
> https://brpc.apache.org/docs/getting_started
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Regards,
> Huixxi
> Apache brpc (Incubating) community
>
> -
> 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

[Jean-Baptiste Onofré]

+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

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

Re: Proposal to Revive Apache Livy Community

[Jean-Baptiste Onofré]

Hi Larry,

thanks for this !

I'm still interested to work on Livy. Can you please add me as mentor ?

Thanks !
Regards
JB

On Fri, Oct 14, 2022 at 8:38 PM larry mccay  wrote:
>
> Abstract
>
> Livy is a 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 [1].
>
> While this project has been well regarded and used in many contexts as the
> defacto standard API to Spark environments, it has been incubating for over
> 5 years without graduation to a TLP and it has become difficult to
> impossible for fixes and improvements to be contributed as the current
> community seems to have moved on.
>
> There has been discussion regarding retirement of this podling where there
> seems to be some increasing interest in joining and reviving the community
> [2].
>
> The intent of this proposal is to avoid retiring a well regarded, actively
> used and rather mature project by reviving the PPMC and community with new
> folks that have a vested interest in the project and health of the
> community.
> Proposal
>
> We propose to revive the PPMC with a set of contributors and maintainers as
> mentors, PPMC members and committers.
>
> The retirement DISCUSS thread [2] has shown a growing interest in providing
> new committers and bringing improvements and fixes from organization’s
> internally maintained forks back to a revived community.
>
> General Approach to Revival:
>
>-
>
>Add new Mentors
>-
>
>   Larry McCay, lmc...@apache.org , Cloudera
>   -
>
>   Sunil Govindan, sun...@apache.org, Cloudera
>   -
>
>   Imran Rashid - iras...@apache.org, Cloudera
>
>
>
>-
>
>Add new Committers/PPMC
>-
>
>   Larry McCay, lmc...@apache.org, Cloudera
>   -
>
>   Vinod Kumar Vavilapalli, vino...@cloudera.com, Cloudera
>   -
>
>   Gyorgy Gal, ggal ,gal.gyo...@gmail.com, Cloudera
>   -
>
>   Wing Yew Poon, wyp...@cloudera.com, Cloudera
>   -
>
>   Xilang Yan, xilang@gmail.com, Shopee
>   -
>
>   Jianzhen Wu, myjianz...@gmail.com, Shopee
>   -
>
>   Nagella Jagadeewara Rao, jnage...@visa.com, Visa
>   -
>
>   Pralab Kumar, pralk...@visa.com, Visa
>   -
>
>   Prasad Shrikant, shrikant@gmail.com, Visa
>   -
>
>   Brahma Reddy Battula, bra...@apache.org, Visa
>
>
>
>-
>
>Invite existing PPMC members to opt-in or otherwise go emeritus
>-
>
>   Jean-Baptiste Onofré, jbono...@apache.org, Talend (opted-in via
>   Retirement DISCUSS thread [2])
>
>
>
>-
>
>Invite existing Committers/PPMC members to opt-in or otherwise go
>emeritus
>
>
>
>-
>
>Establish Roadmap via follow up DISCUSS thread
>-
>
>   Known Improvements from Forks which will need proposals and
>   discussion:
>   -
>
>  Adding HA for Livy
>  -
>
>  Updating security capabilities (eg. kerberos for jdbc, fixing bugs
>  in encryption)
>  -
>
>  Expanding the support for kubernetes
>  -
>
>  Responding to CVEs in dependencies (eg. log4j, thrift)
>  -
>
>  Livy rest cluster - IS THIS SAME AS HA for Livy ABOVE?
>  -
>
>  Support multi Spark versions
>  -
>
>  Implemented a metrics system for Livy
>  -
>
>  Support customize batch/interactive session lifecycle event
>  handler, default log event with log4j, very helpful for
> trouble shooting
>  -
>
>  Optimize log to track which session id the log message came from,
>  also very helpful for trouble shooting
>  -
>
>  Support customize Spark config optimization rules, can be used to
>  optimize config for users’ job
>  -
>
>  A set of command line tool which can be used to replace Spark’s
>  spark-submit, pyspark, spark-sql but actually submit
> application in Livy
>  -
>
>  We are planning to implement a JDBC state store, and allow multi
>  Livy Thrift sessions to share one backend Spark application
> in the next few
>  months.
>  -
>
>   These items and others that are brought to community may need
>   consolidation or multiple configurable options and will need to
> be part of
>   the discussion
>   -
>
>  One-pager Livy Improv

Re: [DISCUSS] Remove 72 hour waiting time to add PPMC members.

[Jean-Baptiste Onofré]

+1

It sounds good to me.

Regards
JB

On Fri, Oct 14, 2022 at 8:24 AM Willem Jiang  wrote:
>
> +1 for removing the 72-hour wait time to add a PPMC member.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Oct 14, 2022 at 6:45 AM Justin Mclean  
> wrote:
> >
> > Hi,
> >
> > The board recently changed the 72-hour waiting time to add a PMC member to 
> > a top level project. We have the same 72-hour waiting time to add PPMC 
> > members to a podling.
> >
> > Do we want to consider removing this 72-hour waiting time and just require 
> > a PMC to notify the IPMC that they want to add someone?
> >
> > 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
>

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

Re: [DISCUSS] Retire Livy podling

[Jean-Baptiste Onofré]

There's no need to reestablished the podling as it's still running ;)

I think we can just update the original proposal, reshape the PPMC and
move forward.

Thoughts ?

Regards
JB

On Fri, Oct 14, 2022 at 9:55 AM Brahma Reddy Battula  wrote:
>
> Hi Justin,
>
> Any chance to re-establish podding or add some members to existing
> community so that it can be active ,as we can see so many people are
> interested to contribute to Livy podling?
>
>
>
> On Thu, 13 Oct 2022 at 10:02 PM, Justin Mclean 
> wrote:
>
> > Hi,
> >
> > Just a note, poddlings do not go to the attic, only top level projects do.
> > Most often a podling in this state will continue to live on GitHub as long
> > as there is a community to support it.
> >
> > 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: [MENTORS] Podlings that have missing reports

[Jean-Baptiste Onofré]

Hi,

about Livy, I added a note few days ago regarding the current
discussion on the mailing list.

I can sign the report, but it's an empty one for now. I will write a
report with action plan next month.

Regards
JB

On Fri, Oct 14, 2022 at 12:52 AM Justin Mclean  wrote:
>
> Hi,
>
> Several projects have not submitted a report. The incubator report has been 
> submitted to the board, and there is still a short window where you may be 
> able to submit your report via Whimsey [1]
>
> Podlings that failed to report and are currently expected next month are:
> • Livy
> • Marvin-AI
> • Milagro
> • Spot
> • Teaclave
> • Toree
>
> Kind Regards,
> Justin
>
> 1. https://whimsy.apache.org/board/agenda/2022-10-19/
> -
> 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 Celeborn into the Apache Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Wed, Oct 12, 2022 at 5:49 AM Yu Li  wrote:
>
> Hi all,
>
> Following up on the [DISCUSS] thread on Celeborn [1] [2], I would like to
> call a VOTE to accept Celeborn into the Apache Incubator, please check out
> the Celeborn Proposal from the incubator wiki [3].
>
> Please cast your vote:
>
> [ ] +1, bring Celeborn into the Incubator
> [ ] +0, I don't care either way
> [ ] -1, do not bring Celeborn 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.
>
> Best Regards,
> Yu
>
> [1] https://lists.apache.org/thread/rlkzg8m5923vngyon0bwcv97x3m68x4c
> [2] https://lists.apache.org/thread/hjy3gpvocjtls5vp9h1llcvmwkgz3lcy
> [3] https://cwiki.apache.org/confluence/display/INCUBATOR/CelebornProposal

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

Re: [DISCUSS] Retire Livy podling

[Jean-Baptiste Onofré]

Hi,

If you plan to contribute on Livy, you are welcome to be part of the
proposal imho.

Regards
JB

On Mon, Oct 10, 2022 at 7:19 AM Brahma Reddy Battula  wrote:
>
> Hi Larry,
>
> Nice to hear from you that you are planning propose new features and make
> active.
>
> We do use Livy in our prod clusters, any chance to include us in your
> proposal so that we can also contribute.
>
>
>
> On Mon, 10 Oct 2022 at 3:54 AM, larry mccay  wrote:
>
> > Sure.
> > Thanks, Craig.
> >
> > --larry
> >
> > On Sun, Oct 9, 2022, 5:38 PM Craig Russell  wrote:
> >
> > > Hi Larry,
> > >
> > > > On Oct 8, 2022, at 10:30, larry mccay  wrote:
> > > >
> > > > Good to hear, Jean-Baptiste!
> > > > We will send the proposal both here and to the Livy private list, I
> > > guess.
> > > > Once we come to an agreement and direction we can share with the dev@
> > > and
> > > > user@ lists.
> > >
> > > I support the effort to revive the Livy podling, but I'd advise against
> > > using the private list to discuss it. The incubator general list is
> > public
> > > and the livy dev list is public, so these are the lists I'd suggest you
> > use
> > > for further discussion.
> > >
> > > Again, good luck with the effort,
> > > Craig
> > > >
> > > > Thanks again!
> > > >
> > > > --larry
> > > >
> > > > On Sat, Oct 8, 2022 at 12:49 AM Jean-Baptiste Onofré 
> > > > wrote:
> > > >
> > > >> Hi Larry,
> > > >>
> > > >> Agree with Claude: if we can have concrete proposal (in terms of
> > > >> community and roadmap), it's OK. We are not in a rush, if we can have
> > > >> this in the commit weeks, it's fine.
> > > >> I would sent this on the Livy mailing list.
> > > >>
> > > >> Again, I would be more than happy to help and contribute on Livy.
> > > >>
> > > >> Regards
> > > >> JB
> > > >>
> > > >> On Fri, Oct 7, 2022 at 6:08 PM larry mccay  wrote:
> > > >>>
> > > >>> I was hoping that we could bring a set of contributors as:
> > > >>>
> > > >>> * mentors - 1 or 2 plus whoever wants to remain
> > > >>> * PPMC/Committers - 2 or 3 plus whoever wants to remain
> > > >>> * election of a PPMC chair if needed
> > > >>>
> > > >>> Also open it up for folks to ask to join (as well as go emeritus) as
> > I
> > > >> know
> > > >>> there are others that have tried to contribute and have gotten know
> > > where
> > > >>> or have long since decided it wasn't worth trying anymore.
> > > >>>
> > > >>> So, my thought was almost a new Proposal and solicitation for
> > community
> > > >>> bootstrap with a few seeds planted to help it grow.
> > > >>> I was also considering a goal of getting it back off the ground with
> > > some
> > > >>> number of releases and proof of health as a project to fast track to
> > a
> > > >>> graduation discussion.
> > > >>> A bit early to talk about that now but that was a detail that I
> > thought
> > > >>> would possibly go into such a reboot proposal.
> > > >>>
> > > >>> @Jean-Baptiste - we have compiled a list of features/improvements
> > that
> > > we
> > > >>> would be able to bring to the table with the reboot as well.
> > > >>> These are improvements that have been made internally due the sense
> > of
> > > >> not
> > > >>> being able to get them in. I lack the details around the attempts at
> > > this
> > > >>> time but we would be bringing source as well.
> > > >>> We could list these as part of the proposal/concrete plans.
> > > >>>
> > > >>> If you think this proposal can be done more casually, that's fine
> > too.
> > > I
> > > >>> just would like to make it clear that we would open it up to new
> > folks
> > > as
> > > >>> well.
> > > >>>
> > > >>> However you'd like to see it done, we can have concrete commitments
> > to
> > > >> you
> > > >>>

Re: [VOTE] Release Apache NuttX (Incubating) 11.0.0

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- ASF headers are present
- Signature and hash are OK
- LICENSE, NOTICE and DISCLAIMER look good
- No binary in the source distribution

Regards
JB

On Fri, Oct 7, 2022 at 7:00 PM TimH  wrote:
>
> +1 (non-binding)
>
> Built for out-of-tree custom board and successfully got a working nuttx
> shell.
>
>
> > From: Alin Jerpelea 
> > Sent: 22 September 2022 13:26
> > To: general@incubator.apache.org
> > Subject: [VOTE] Release Apache NuttX (Incubating) 11.0.0
> >
> > This is a call for a vote to release Apache NuttX (Incubating) version
> > 11.0.0.
>
>
> -
> 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: [DISCUSS] Retire Livy podling

[Jean-Baptiste Onofré]

Hi Larry,

Agree with Claude: if we can have concrete proposal (in terms of
community and roadmap), it's OK. We are not in a rush, if we can have
this in the commit weeks, it's fine.
I would sent this on the Livy mailing list.

Again, I would be more than happy to help and contribute on Livy.

Regards
JB

On Fri, Oct 7, 2022 at 6:08 PM larry mccay  wrote:
>
> I was hoping that we could bring a set of contributors as:
>
> * mentors - 1 or 2 plus whoever wants to remain
> * PPMC/Committers - 2 or 3 plus whoever wants to remain
> * election of a PPMC chair if needed
>
> Also open it up for folks to ask to join (as well as go emeritus) as I know
> there are others that have tried to contribute and have gotten know where
> or have long since decided it wasn't worth trying anymore.
>
> So, my thought was almost a new Proposal and solicitation for community
> bootstrap with a few seeds planted to help it grow.
> I was also considering a goal of getting it back off the ground with some
> number of releases and proof of health as a project to fast track to a
> graduation discussion.
> A bit early to talk about that now but that was a detail that I thought
> would possibly go into such a reboot proposal.
>
> @Jean-Baptiste - we have compiled a list of features/improvements that we
> would be able to bring to the table with the reboot as well.
> These are improvements that have been made internally due the sense of not
> being able to get them in. I lack the details around the attempts at this
> time but we would be bringing source as well.
> We could list these as part of the proposal/concrete plans.
>
> If you think this proposal can be done more casually, that's fine too. I
> just would like to make it clear that we would open it up to new folks as
> well.
>
> However you'd like to see it done, we can have concrete commitments to you
> within a week or so more than likely.
>
> BTW, I did note that Ambari was sent to the attic and then pulled back out
> [1] back in June into July of this year.
> I would hope that we could avoid the administrative headache that seems to
> have been involved in that reinstatement.
>
> 1. https://issues.apache.org/jira/browse/ATTIC-205
>
> On Fri, Oct 7, 2022 at 11:04 AM Claude Warren, Jr
>  wrote:
>
> > Larry et.al.
> >
> > I think we need concrete steps. So if Larry produced a list of new
> > committers could we get them added to the list and see if development
> > starts again?
> >
> > Mentors / Champion does that work for you?
> >
> > Larry, can you produce such a list?
> >
> > Is there an objection to proceeding along these lines?
> >
> > Claude
> >
> > On Fri 7 Oct 2022, 03:07 Jean-Baptiste Onofré,  wrote:
> >
> > > Hi Larry,
> > >
> > > I tried maybe 3 times to get Livy back to active, without success.
> > > I was a volunteer to contribute, but not alone, we need a community
> > around
> > > Livy.
> > >
> > > I don't remember having seen new active contributions on the mailing
> > > list, and very limited on source code.
> > >
> > > If you really think we can have a team, that would be great, and I
> > > still agree to support. But it has to be concrete.
> > >
> > > Let's see what the other IPMC members are thinking, but IMHO, I doubt
> > > we will have Livy back to life in the short term.
> > >
> > > Regards
> > > JB
> > >
> > > On Thu, Oct 6, 2022 at 5:29 PM larry mccay  wrote:
> > > >
> > > > Folks,
> > > >
> > > > As I mentioned in a previous thread [1], I would like to help avoid
> > > sending
> > > > a well regarded, actively consumed and mature product to the attic.
> > There
> > > > have been discussions internally at my employer and we have also
> > > struggled
> > > > getting our contributions committed. The original group of committers
> > > seem
> > > > to have all moved on, and this is the core challenge for those that are
> > > > trying to contribute, but are not committers.  This doesn’t represent a
> > > > lack of interest in doing so and I think there are others in this
> > > position.
> > > >
> > > > We are interested in trying to reboot with additional PPMC leadership
> > and
> > > > investing in contributors that we would like to install as new
> > > committers.
> > > >
> > > > I’d like to hear what the incubator would think about a Reproposal for
> > > the
> > > > Livy project that would be open to existing P

Re: [VOTE] Apache Tuweni 2.3.0-incubating

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- LICENSE, NOTICE, DISCLAIMER files look good
- Signature and hash are good
- ASF header is present in source files
- No binary files in the source distribution

I didn't have time to try a full build.

Regards
JB

On Thu, Oct 6, 2022 at 9:55 PM Antoine Toulme  wrote:
>
> Any member available to vote?
>
> > On Oct 1, 2022, at 18:30, Antoine Toulme  wrote:
> >
> > Please allow me to report 2 votes of IPMC members in favor of the release 
> > from the initial vote thread:
> > Furkan Kamaci, +1 
> > https://lists.apache.org/thread/342l7ofon5omdw4bvh8tvqqnrgx96lxo
> > Antoine Toulme, +1 
> > https://lists.apache.org/thread/jyp26prn001tfp46jq02s5z15mbx6r5m
> >
> > Thanks,
> >
> > Antoine
> >
> >> On Oct 1, 2022, at 6:27 PM, Antoine Toulme  wrote:
> >>
> >> Hello all,
> >> This is a call for a vote to release Apache Tuweni (incubating) version 
> >> 2.3.0. Apache Tuweni is a set of libraries and other tools to aid 
> >> development of blockchain and other decentralized software in Java and 
> >> other JVM languages. It includes a low-level bytes library, serialization 
> >> and deserialization codecs (e.g. RLP), various cryptography functions and 
> >> primitives, and lots of other helpful utilities.
> >>
> >> The Apache Tuweni community has voted on and approved a proposal to 
> >> release Apache Tuweni (Incubating) version 2.3.0. We would like to request 
> >> the Incubator PMC members review and vote on this incubator release.
> >>
> >> Release information:
> >> Vote result thread:
> >> https://lists.apache.org/thread/ol831yssngqj3rcjybbmjq66h9cp9wpb
> >>
> >>
> >> We're voting on the source distributions available here:
> >> https://dist.apache.org/repos/dist/dev/incubator/tuweni/2.3.0-incubating
> >> The release tag is present here:
> >> https://github.com/apache/incubator-tuweni/releases/tag/v2.3.0-incubating-rc
> >>
> >> Please review and vote as appropriate.
> >>
> >> The following changes were made since 2.2.0:
> >> * Improvements to EVM lib, and a EVM DSL
> >> * Performance improvements to Bytes
> >> * Fixing sync logic of ethereum client
> >> * New genesis file library, allowing to build your own genesis file with a 
> >> DSL
> >> * Small improvements to transaction handling, encrypting/decrypting with 
> >> secp256k1 keys.
> >>
> >> The vote is open until Wednesday October 5th, 7pm PST.
> >> Cheers,
> >>
> >> Antoine
> >
> >
> > -
> > 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: [DISCUSS] Retire Livy podling

[Jean-Baptiste Onofré]

Hi Larry,

I tried maybe 3 times to get Livy back to active, without success.
I was a volunteer to contribute, but not alone, we need a community around Livy.

I don't remember having seen new active contributions on the mailing
list, and very limited on source code.

If you really think we can have a team, that would be great, and I
still agree to support. But it has to be concrete.

Let's see what the other IPMC members are thinking, but IMHO, I doubt
we will have Livy back to life in the short term.

Regards
JB

On Thu, Oct 6, 2022 at 5:29 PM larry mccay  wrote:
>
> Folks,
>
> As I mentioned in a previous thread [1], I would like to help avoid sending
> a well regarded, actively consumed and mature product to the attic. There
> have been discussions internally at my employer and we have also struggled
> getting our contributions committed. The original group of committers seem
> to have all moved on, and this is the core challenge for those that are
> trying to contribute, but are not committers.  This doesn’t represent a
> lack of interest in doing so and I think there are others in this position.
>
> We are interested in trying to reboot with additional PPMC leadership and
> investing in contributors that we would like to install as new committers.
>
> I’d like to hear what the incubator would think about a Reproposal for the
> Livy project that would be open to existing PMC members and committers as
> well as new contributors with a vested interest in this project and the
> health of its community.
>
> How would we best propose such a thing here?
>
> Thanks,
>
> –larry
>
>
>1.
>
>https://lists.apache.org/list?general@incubator.apache.org:2022-7
>
>
> On Thu, Oct 6, 2022 at 5:21 AM Luciano Resende  wrote:
>
> > Based on the failed attempts to resurrect a community, +1 for retirement.
> >
> > On Wed, Oct 5, 2022 at 07:26 Jean-Baptiste Onofré  wrote:
> >
> > > Hi guys,
> > >
> > > After several attempts, we are struggling to execute Livy podling: the
> > > activity is pretty low, and even after a couple of calls for action,
> > > we don't have a clear sign of community around Livy.
> > >
> > > I would like to discuss/propose to retire the Livy podling.
> > >
> > > Thoughts ?
> > >
> > > Regards
> > > JB
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > > --
> > Sent from my Mobile device
> >

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

Re: [VOTE] Accept Baremaps into the Apache Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Thu, Oct 6, 2022 at 2:52 PM Bertrand Delacretaz
 wrote:
>
> Hi,
>
> The [DISCUSS] thread on Baremaps [1] has slowed down, with no
> objections AFAICS, so I'm calling a vote to accept Baremap into the
> Apache incubator.
>
> The proposal is copied below and available at
> https://cwiki.apache.org/confluence/display/INCUBATOR/Baremaps+Proposal
>
> Please cast your vote:
>
>   [ ] +1, bring Baremap into the Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring Baremap into the Incubator, because...
>
> This majority vote is open for at least 72 hours.
>
> Only votes from Incubator PMC members are binding, but other votes are 
> welcome!
>
> -Bertrand
>
> [1] https://lists.apache.org/thread/wlqvf709oljv20qd3f44pstn4l8vt4n3
>
> -- Baremaps Proposal --
>
> Abstract
>
> Apache Baremaps is a toolkit and a set of infrastructure components
> for creating, publishing, and operating online maps.
>
> Proposal
>
> Apache Baremaps is a toolkit and a set of infrastructure components
> for creating, publishing, and operating online maps. It provides a
> data pipeline enabling developers to build maps with different data
> sources. It offers live reload capabilities that allow cartographers
> to customize the content and the style of a map. It includes an
> attribution-free map schema and style that stimulates derived work.
> Finally, it provides services commonly used in online maps, such as
> location search and IP to location.
>
> Background
>
> The infrastructure components required to publish and operate
> large-scale online maps are often closed-source, heterogeneous,
> complex, and expensive. For instance: the visualization of maps in Web
> browsers or on mobile devices requires processing and tiling large
> spatial datasets, such as OpenStreetMap; the location of users based
> on their IP addresses requires aggregating and merging data from
> network information centers; the ability to search in a map requires
> indexing features based on text and spatial attributes in different
> languages.
>
> Rationale
>
> Web mapping infrastructure is often managed by large teams of
> developers (e.g., Google Maps, Apple Maps, Mapbox, etc.), which makes
> it hard to customize and evolve. Apache Baremaps is a Web mapping
> infrastructure for the rest of us: it enables individuals and small
> teams of developers to regain control over spatial data and to develop
> custom mapping experiences. As a result, Apache Baremaps facilitates
> innovation in niche areas where resources are limited and
> customization is needed (e.g., sustainable mobility, civil
> engineering, urban planning, environment monitoring, startups, etc.).
>
> Initial Goals
>
> The primary goals are:
>
> to learn the Apache Way;
> to release a customizable attribution-free map schema and style;
> to publish a tiled world map in different formats (mvt, png, 3D Tiles
> Next, etc.);
> to grow the community and attract new contributors;
> to release additional services and components (IP to location,
> location search, etc.).
>
> Current Status
>
> Meritocracy
>
> Baremaps is a project initially developed by Bertil Chapuis. It has
> already attracted outside contributors. Therefore, the process of
> electing new committers and project management committee members
> should be natural.
>
> Community
>
> The need for Web mapping infrastructure is great, hence a good
> potential for a diverse community mixing developers and cartographers.
>
> Core Developers
>
> The contributors to Baremaps include developers from academia and
> industry, mainly located in Europe. The contributions include
> documentation, bug fixes, and new features. Most of the development
> and communication currently takes place on GitHub.
>
> Alignment
>
> Many critical components used in the geospatial community are released
> under LGPL (e.g., Geotools, Geotoolkit). We are strongly aligned with
> the terms of the Apache license. Joining the geospatial community at
> Apache will enable us to be less reliant on components with
> contaminating licenses. For instance, Apache SIS seeks to become an
> alternative to Geotools and Geotoolkit.
>
> Known Risks
>
> Project Name
>
> No trademark is associated with the Baremaps name, and the project is
> already well referenced by search engines. The .com, .org, and .net
> domains are the property of Bertil Chapuis, who agrees to transfer
> them to the Apache Software Foundation unconditionally upon request.
>
> Orphaned Products
>
> There is a risk of being orphaned due to the small number of
> committers. Even if the main contributor has no plan to leave the
> project, this is a problem we need to address in the future.
>
> Inexperience with open source
>
> The initial committers contributed to open source projects in the past
> but have only a few experiences with the governance of open source
> projects in a Foundation such as Apache.
>
> Length of incubation
>
> We expect to achieve most of the initial goals 

[DISCUSS] Retire Livy podling

[Jean-Baptiste Onofré]

Hi guys,

After several attempts, we are struggling to execute Livy podling: the
activity is pretty low, and even after a couple of calls for action,
we don't have a clear sign of community around Livy.

I would like to discuss/propose to retire the Livy podling.

Thoughts ?

Regards
JB

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

Re: [VOTE] Release Apache DevLake (Incubating) v0.14.0-rc1

[Jean-Baptiste Onofré]

+1 (binding)

I checked:

- incubating is in the version
- DISCLAIMER, NOTICE, LICENSE look good
- Signature and hash are valid
- ASF headers present in source files
- No binary files in source distribution

Regards
JB

On Tue, Oct 4, 2022 at 2:53 PM Liang Zhang
 wrote:
>
> Hello all,
>
> This is a call for vote to release Apache DevLake (Incubating) v0.14.0-rc1
>
> The Apache DevLake community has voted on and approved a proposal to release
> Apache DevLake (Incubating) version v0.14.0-rc1
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Linkis community vote thread:
> https://lists.apache.org/thread/s6jj2tl5mlyb8jpdd88jmo5woydzhp54
>
> Vote result thread:
> https://lists.apache.org/thread/mb5sxdopprqksf1ppfggkvkwxs6110zk
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.14.0-incubating-rc1/
>
> Git tag for the release:
> https://github.com/apache/incubator-devlake/tree/v0.14.0-rc1
>
> Keys to verify the Release Candidate:
> https://downloads.apache.org/incubator/devlake/KEYS
>
> How to build:
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
>
> -
> 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: [DISCUSS] Incubating Proposal for Pekko

[Jean-Baptiste Onofré]

Hi Claude

Very interesting. I would be more than happy to mentor this podling (if
accepted of course).

I will take a deeper look on the proposal wiki page.

Thanks !

Regards
JB

Le jeu. 29 sept. 2022 à 16:57, Claude Warren, Jr
 a écrit :

> Greetings,
>
> I would like to propose Pekko [1]  as a new Apache Incubator project.
>
> Pekko is a toolkit that brings the actor model (popularised by Erlang) to
> the JVM, providing the basis for building both locally and distributed
> concurrency. On top of this Pekko provides a rich set of libraries built on
> top of Actors to solve modern problems, including:
>
>
>- Streams: Fully bi-directional backpressured streams following the
>Reactive manifesto
>- HTTP: A fully streamed HTTP client/server built on top of streams that
>also provides expected tools (such as connection pooling) necessary for
>highly available web services
>- connectors: A rich set of connectors for various databases, messaging,
>persistent services built on top of streams
>- grpc: A gRPC server/client
>- projection: Provides abstractions necessary for CQRS pattern such as
>envelope, necessary for systems such as Kafka.
>
>
>
> Controversially Pekko is a fork of the Akka project just prior to its
> licence changed from Apache 2 to Business Source License 1.1.
>
> I look forward to your feedback and discussions,
>
> Thank you,
> Claude Warren
> [1] https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal
>

Re: [VOTE] Graduate Apache MXNet to a TLP

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Wed, Aug 17, 2022 at 4:40 PM Joe Evans  wrote:
>
> Hi Apache Incubator community,
>
> The Apache MXNet (incubating) community has discussed[1] graduating to a
> top level project and passed a community vote[2][3]. We have also
> discussed[4] graduating in the Incubator community.
>
> In the incubator discussion, some branding issues[5] were brought up. We
> have fixed the issues[6] we were able to and discussed the others with
> trademarks@. This work is ongoing. In addition, a few website issues[7]
> were brought up which were subsequently resolved[8].
>
> Based on the positive feedback from the incubator discussion, we would like
> to start a vote on graduating Apache MXNet (incubating) to a top level
> project.
>
> Please cast your vote as one of the following options:
>
> [ ] +1 Yes, I support Apache MXNet (incubating) graduating from the Apache
> Incubator to a top level project.
>
> [ ] +0 No opinion.
>
> [ ] -1 No, the Apache MXNet (incubating) project is not ready to graduate,
> because ...
>
> This vote will remain open for at least 72 hours.
>
> Here is a brief overview of the progress of the Apache MXNet (incubating)
> project and community since entering the incubator:
>
> Community
>
>-
>
>38 new PPMC members were added, bringing the total number of PPMC
>members to 51
>-
>
>56 new committers were added (which include new PPMC members), bringing
>the total number of committers to 87
>-
>
>The total number of contributors is now 870 and growing.
>
> Project
>
>-
>
>18 releases by 13 different release managers. All compliance issues have
>been resolved with the 1.9.0 and 2.0.beta releases.
>-
>
>MXNet website is now compliant with Apache Project Website requirements
>-
>
>MXNet has completed the project maturity self assessment[9]
>
>
> References:
>
> [1] https://lists.apache.org/thread/l9h2qgb2vqs2y0cm46wh83sgomr9w190
>
> [2] https://lists.apache.org/thread/py1nw6whov78sch5kkm1gcg7cv3zb2sv
>
> [3] https://lists.apache.org/thread/b8bngc6qcb33n0jo6m1rw0ylwlqzkmgx
>
> [4] https://lists.apache.org/thread/3rxzjcmo2y457y6r8ohz1j4qv49joyo6
>
> [5] https://lists.apache.org/thread/6brq4jg1x3hnt0sr3phboh2vwoo33db1
>
> [6] https://github.com/apache/incubator-mxnet/issues/21036
>
> [7] https://lists.apache.org/thread/j29jcv0zdkvx7vyy701qnfhnj09fzv8o
>
> [8] https://github.com/apache/incubator-mxnet/issues/21054
>
> [9]
> https://cwiki.apache.org/confluence/display/MXNET/Apache+Maturity+Model+Assessment+for+MXNet
>
>
> Here is the proposed resolution:
>
> —--
>
> Establish the Apache MXNet 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 flexible and efficient library for Deep Learning.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>
> (PMC), to be known as the "Apache MXNet Project", be and hereby is
>
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache MXNet Project be and hereby is responsible for
>
> the creation and maintenance of software related to a flexible and
>
> efficient library for Deep Learning; and be it further
>
> RESOLVED, that the office of "Vice President, Apache MXNet" 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 MXNet
>
> Project, and to have primary responsibility for management of the
>
> projects within the scope of responsibility of the Apache MXNet 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 MXNet Project:
>
> * Anirudh Subramanian 
>
> * Bing Xu 
>
> * Bob Paulin 
>
> * Carin Meier 
>
> * Chiyuan Zhang 
>
> * Chris Olivier 
>
> * Dick Carter 
>
> * Eric Xie 
>
> * Furkan Kamaci 
>
> * Haibin Lin 
>
> * Henri Yandell 
>
> * Hongliang Liu 
>
> * Indhu Bharathi 
>
> * Jackie Wu 
>
> * Jason Dai 
>
> * Jian Zhang 
>
> * Joe Evans 
>
> * Joe Spisak 
>
> * Jun Wu 
>
> * Leonard Lausen 
>
> * Liang Depeng 
>
> * Ly Nguyen 
>
> * Madan Jampani 
>
> * Marco de Abreu 
>
> * Markus Weimer 
>
> * Mu Li 
>
> * Nan Zhu 
>
> * Naveen Swamy 
>
> * Przemysław Trędak 
>
> * Qiang Kou 
>
> * Qing Lan 
>
> * Sandeep Krishnamurthy 
>
> * Sergey Kolychev 
>
> * Sheng Zha 
>
> * Shiwen Hu 
>
> * Tao Lv 
>
> * Terry Chen 
>
> * Thomas Delteil 
>
> * Tianqi Chen 
>
> * Tong He 
>
> * Tsuyoshi Ozawa 
>
> * Xingjian Shi 
>
> * YiZhi Liu 
>
> * Yifeng Geng 
>
> * Yu Zhang 
>
> * Yuan Tang 
>
> * Yutian Li 
>
> * Zhi Zhang 
>
> * Zihao Zheng 
>
> * Ziheng Jiang 
>
> * Ziyue Huang 
>
> NOW, THEREFORE, BE 

Re: [DISCUSS] Incubating Proposal for StreamPark

[Jean-Baptiste Onofré]

Hi,

Interesting proposal. How do you compare StreamPark with Apache Beam,
Wayang, NiFI ?

Thanks

Regards
JB

On Wed, Aug 17, 2022 at 3:13 AM tison  wrote:
>
> Hi all,
>
> I would like to propose StreamPark[1] as a new apache incubator project,
> you can find the proposal[2] of StreamPark for more detail.
>
> StreamPark is a streaming application development platform. Aimed at ease
> building and managing streaming applications, StreamPark provides
> scaffolding for writing streaming process logic with Apache Flink and
> Apache Spark. Also, StreamPark provides a dashboard for controlling and
> monitoring streaming tasks. It was initially known as StreamX and renamed
> to StreamPark in August 2022.
>
> StreamPark abstracts the environment and program parameters of task
> development and deployment in a convention over configuration manner for
> low code development. It initializes a runtime environment and context and
> combines it with a series of connectors to simplify development. From the
> aspect of a task management platform, StreamPark is a streaming data
> management platform based on the JVM platform.
>
> So far, StreamPark has accumulated a few users, and the accrued download
> time is over 5,000. The representative users are Baidu, China Unicom,
> Ziroom, Yonghui Supermarket, InMobi, YTO Express, and so on. StreamPark has
> built an open-source community with 52 developers and released over ten
> versions in the past year.
>
> The proposed initial committers are interested in joining ASF to increase
> the connections in the open-source world. Based on extensive collaboration,
> it is possible to build a community of developers and committers that live
> longer than the founder. Also, the Apache Brand can help encourage more
> organizations to use StreamPark more confidently.
>
> We believe that the StreamPark project will provide diversity value for the
> community if StreamPark is introduced into the Apache incubator.
>
> I (@tison) will help this project as the champion and many thanks to four
> other mentors:
>
> * Willem Ning Jiang [ningji...@apache.org]
> * Stephan Ewen [se...@apache.org]
> * Thomas Weise [t...@apache.org]
> * Duo Zhang [zhang...@apache.org]
>
> Best,
> tison.
>
> [1] https://github.com/streamxhub/streamx
> [2]
> https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal

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

Re: [VOTE] Release Apache Sedona 1.2.1-incubating-rc1

[Jean-Baptiste Onofré]

Hi,

Can you please include the link to dist source package ? That's the
most important thing to check.

Thanks,
Regards
JB

On Wed, Aug 10, 2022 at 4:55 AM Kanchan Chowdhury  wrote:
>
> Hi all,
>
> This is a call for vote on Apache Sedona 1.2.1-incubating-rc1. Please refer
> to the changes listed at the bottom of this email.
>
> Sedona Community vote thread:
> https://lists.apache.org/thread/511gjndxmdxh4g2rzwyxppjc00orz3s3
>
> Sedona community vote result thread:
> https://lists.apache.org/thread/jyb3yp2wpnhp8kx7t8dnls8xljwqflxr
>
> Release notes:
> https://github.com/apache/incubator-sedona/blob/bcb1803c24dc9decfb113a31db8fc14433be025b/docs/setup/release-notes.md
>
> Build instructions:
> https://github.com/apache/incubator-sedona/blob/sedona-1.2.1-incubating-rc1/docs/setup/compile.md
>
> GitHub tag:
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.2.1-incubating-rc1
>
> GPG public key to verify the Release:
> https://downloads.apache.org/incubator/sedona/KEYS
>
> Source code and binaries:
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.2.1-incubating-rc1/
>
> The vote will be open for at least 72 hours or until at least 3 "+1" PMC
> votes are cast
>
> Please vote accordingly:
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
> Checklist for reference (because of DISCLAIMER-WIP, other checklist items
> are not blockers):
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] Source code artifacts have correct names matching the current release.
>
> For a detailed checklist  please refer to:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist

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

Re: [VOTE] Release Apache DevLake (Incubating) v0.12.0-rc2

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- hash and checksum
- LICENSE, NOTICE, DISCLAIMER-WIP are there and look good
- ASF headers are there in source file
- no binary file in the source distribution

Regards
JB

On Mon, Aug 1, 2022 at 4:15 PM Liang Zhang
 wrote:
>
> Hello all,
>
> This is a call for vote to release Apache DevLake (Incubating) v0.12.0-rc2
>
> The Apache DevLake community has voted on and approved a proposal to release
> Apache DevLake (Incubating) version v0.12.0-rc2
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Linkis community vote thread:
> https://lists.apache.org/thread/yxy3kokhhhxlkxcr4op0pwslts7d8tcy
>
> Vote result thread:
> https://lists.apache.org/thread/qr3fj42tmryztt919jsy5q8hbpmcztky
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.12.0-incubating-rc2/
>
> Git tag for the release:
> https://github.com/apache/incubator-devlake/tree/v0.12.0-rc2
>
> Keys to verify the Release Candidate:
> https://downloads.apache.org/incubator/devlake/KEYS
>
> some issues raised from the last voting[1].
> - Several files don't have have ASF headers -- Fixed in this release
>
> - NOTICE is there but need to be extended (it's almost empty) -- No new 
> entries for now, we will append them at the first time when needed
>
> - Use CI to help check license header -- We followed this advice and have set 
> up a GitHub Action workflow to do the job
>
> - Use https://downloads.apache.org/incubator/devlake/KEYS as the link of KEYS 
> -- As shown above, we are using the correct link
>
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> [1]https://lists.apache.org/thread/hbwf24xmfl5xkn3mocvn55hpzodcf010
> Thanks,
> Apache DevLake(Incubating) community
> -
> 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 Kvrocks(incubating) 2.1.0

[Jean-Baptiste Onofré]

+1 (binding)

Casting my vote here (already checked the release at podling)

Regards
JB

On Sat, Jul 30, 2022 at 12:12 PM hulk  wrote:
>
> Hello IPMC,
>
> The Apache Kvrocks community has voted and approved the release of Apache
> Kvrocks(incubating) 2.1.0. We now kindly request the IPMC members
> review and vote for this release.
>
> Kvrocks is a distributed key value NoSQL database that uses RocksDB as the
> storage engine
> and is compatible with Redis protocol. The current release provides the
> first official
> package, resolves all of the license issues, many improvements and fixes
> many bugs.
>
> Kvrocks community vote thread:
>
> https://lists.apache.org/thread/b6hdnsq7fw2tnqlfo1h1yzqhbrxjkyg4
>
> Vote result thread:
>
> https://lists.apache.org/thread/rw0s8m72f5kp0pohs2xc75xsvk6wyw44
>
> **Vote Results**:
> No 0 or -1 votes.
>
> 7 (+1) Binding Vote:
>
> - Yuan Wang
> - tison
> - hulk
> - Liang Chen
> - Jean-Baptiste Onofré
> - Xiaoqiao He
> - donghui liu
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/kvrocks/2.1.0
>
> This release has been signed with a PGP available here:
>
> https://downloads.apache.org/incubator/kvrocks/KEYS
>
> Git tag for the release:
>
> https://github.com/apache/incubator-kvrocks/releases/tag/v2.1.0
>
> Build guide can be found at:
>
> https://github.com/apache/incubator-kvrocks#build
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
>
> Please vote accordingly:
> [ ] +1 Approve the release of Apache Kvrocks(incubating) 2.1.0
> [ ] +0
> [ ] -1 Do not approve (please specify the reason)
>
> Best Regards,
> hulk
> Apache Kvrocks (incubating)
>
> --
> Best Regards,
> - *Hulk Lin*

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

Re: Is Livy podling still active?

[Jean-Baptiste Onofré]

Hi Larry,

Already sent several messages about Livy to try to revive the podling
and eventually move forward to the graduation.

Unfortunately, I didn't have feedback. So, imho, it will be hard to
build a community (especially contributors) around Livy. That's why,
IPMC are discussing about retiring the podling.

Regards
JB

On Sat, Jul 23, 2022 at 5:27 PM larry mccay  wrote:
>
> Haven't seen any additional movement on this thread.
> Just curious whether anyone has considered a graduation into an existing
> TLP like Spark which would be very appropriate.
>
> Interesting and well stated post on the need for Livy here:
> https://www.linkedin.com/posts/activity-6953087197935763456-yoDW/?utm_source=linkedin_share_medium=member_desktop_web
>
>
> On Mon, Jul 4, 2022 at 9:55 AM larry mccay  wrote:
>
> > I would be willing to join livy as a committer and mentor in a reboot if
> > there is interest.
> >
> >
> > On Mon, Jul 4, 2022, 3:05 AM Calvin Kirs  wrote:
> >
> >> We had discussions last year, graduate or retire[1], but the project
> >> still keep has remained downturn.
> >>
> >> Therefore, I agree to retire.
> >>
> >> [1]https://lists.apache.org/thread/3w2bbotwqr8sr59ojhqkcwt3p9wbq793
> >>
> >> Jean-Baptiste Onofré  于2022年7月4日周一 13:30写道：
> >> >
> >> > Agree to move forward with a formal retirement vote.
> >> >
> >> > Regards
> >> > JB
> >> >
> >> > On Mon, May 9, 2022 at 12:13 AM John D. Ament 
> >> wrote:
> >> > >
> >> > > Hi all
> >> > >
> >> > > Based on the discussions, it seems like we should start a formal
> >> retirement
> >> > > vote.  I will plan to start it within the next couple of days unless
> >> > > someone else does.
> >> > >
> >> > > John
> >> > >
> >> > > On Tue, Apr 5, 2022 at 9:38 AM sebb  wrote:
> >> > >
> >> > > > On Tue, 5 Apr 2022 at 13:27, Jean-Baptiste Onofré 
> >> wrote:
> >> > > > >
> >> > > > > Hi,
> >> > > > >
> >> > > > > AFAIR, a report has been submitted since. Report on cwiki doesn't
> >> mean
> >> > > > > it's the last send, we should check in the incubator board report.
> >> > > > >
> >> > > > > It's true that Livy is a "stable" project and kind of "mature"
> >> > > > > podling. IMHO, it should have graduated to TLP.
> >> > > >
> >> > > > Huh?
> >> > > > That would require an active PMC, for which there is little
> >> evidence.
> >> > > >
> >> > > > > As said, I tried to restart podling activity, but I didn't get a
> >> lot
> >> > > > > of updates: most people are Livy users but they don't seem to
> >> want to
> >> > > > > become contributors.
> >> > > >
> >> > > > Nor does anyone seem to want to deal with issues.
> >> > > >
> >> > > > > Regards
> >> > > > > JB
> >> > > > >
> >> > > > > On Tue, Apr 5, 2022 at 8:56 AM Javi Roman 
> >> wrote:
> >> > > > > >
> >> > > > > > Hi community!
> >> > > > > >
> >> > > > > > I see that the project is losing interest from the community,
> >> however
> >> > > > it is
> >> > > > > > a project widely used by companies (I know personally). It is a
> >> pity
> >> > > > that
> >> > > > > > the project may die.
> >> > > > > >
> >> > > > > > In my opinion one of the first actions to take is to recreate
> >> the
> >> > > > reports
> >> > > > > > correctly (Podling reports). I have seen that the last one sent
> >> was in
> >> > > > > > August last year [1].
> >> > > > > >
> >> > > > > > Personally I would like to get involved in this project and
> >> help in
> >> > > > > > restarting it. If you like, I could be in charge of the next
> >> report, if
> >> > > > > > there is no inconvenience.
> >> > > &g

Re: [VOTE] Release Apache DevLake (Incubating) v0.11.0-rc2

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- DISCLAIMER-WIP is there (need to be worked)
- NOTICE is there but need to be extended (it's almost empty), can you
please check that for next release ?
- LICENSE is there
- Several files don't have have ASF headers (the scss, yaml, yml, ...
files), can you please fix that for next release ?
- No binary files in the src archive (if we exclude the png file of course ;))

I hesitated to vote -1 for this release, but as it's RC2, let's give
chance to fix the pending issues for next release.

Regards
JB

On Mon, Jul 4, 2022 at 6:27 PM Liang Zhang
 wrote:
>
> Hello all,
>
> This is a call for vote to release Apache DevLake (Incubating) v0.11.0-rc2
>
> The Apache DevLake community has voted on and approved a proposal to release
> Apache DevLake (Incubating) version v0.11.0-rc1
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Linkis community vote thread:
> https://lists.apache.org/thread/8bnm8v1zvc97rxtd5yfsx53p27wjwtyh
>
> Vote result thread:
> https://lists.apache.org/thread/0n0t1mdcs2qkx6w2qlydojj4ptwp0h35
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.11.0-incubating-rc2/
>
> Git tag for the release:
> https://github.com/apache/incubator-devlake/tree/v0.11.0-rc2
>
> Keys to verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/devlake/KEYS
>
>
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> Apache DevLake(Incubating) community
>
>
> -
> 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: Is Livy podling still active?

[Jean-Baptiste Onofré]

Agree to move forward with a formal retirement vote.

Regards
JB

On Mon, May 9, 2022 at 12:13 AM John D. Ament  wrote:
>
> Hi all
>
> Based on the discussions, it seems like we should start a formal retirement
> vote.  I will plan to start it within the next couple of days unless
> someone else does.
>
> John
>
> On Tue, Apr 5, 2022 at 9:38 AM sebb  wrote:
>
> > On Tue, 5 Apr 2022 at 13:27, Jean-Baptiste Onofré  wrote:
> > >
> > > Hi,
> > >
> > > AFAIR, a report has been submitted since. Report on cwiki doesn't mean
> > > it's the last send, we should check in the incubator board report.
> > >
> > > It's true that Livy is a "stable" project and kind of "mature"
> > > podling. IMHO, it should have graduated to TLP.
> >
> > Huh?
> > That would require an active PMC, for which there is little evidence.
> >
> > > As said, I tried to restart podling activity, but I didn't get a lot
> > > of updates: most people are Livy users but they don't seem to want to
> > > become contributors.
> >
> > Nor does anyone seem to want to deal with issues.
> >
> > > Regards
> > > JB
> > >
> > > On Tue, Apr 5, 2022 at 8:56 AM Javi Roman  wrote:
> > > >
> > > > Hi community!
> > > >
> > > > I see that the project is losing interest from the community, however
> > it is
> > > > a project widely used by companies (I know personally). It is a pity
> > that
> > > > the project may die.
> > > >
> > > > In my opinion one of the first actions to take is to recreate the
> > reports
> > > > correctly (Podling reports). I have seen that the last one sent was in
> > > > August last year [1].
> > > >
> > > > Personally I would like to get involved in this project and help in
> > > > restarting it. If you like, I could be in charge of the next report, if
> > > > there is no inconvenience.
> > > >
> > > > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/August2021
> > > >
> > > >
> > > > On Mon, Apr 4, 2022 at 9:44 AM Jean-Baptiste Onofré 
> > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > You are right, I tried to bring Livy podling back to active. We had
> > > > > few PRs/contributions and I also worked on reload4j switch and so on.
> > > > >
> > > > > If the activity around the code is low, there are few. Unfortunately,
> > > > > the mailing list is pretty quiet.
> > > > >
> > > > > Regards
> > > > > JB
> > > > >
> > > > > On Sun, Apr 3, 2022 at 11:46 PM Luciano Resende <
> > luckbr1...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > There seem to have been a couple of initiatives to reboot the
> > podling and
> > > > > > make it healthy again but without much success.
> > > > > >
> > > > > > What are other mentors' thoughts?
> > > > > >
> > > > > > On Sun, Apr 3, 2022 at 12:59 PM sebb  wrote:
> > > > > >
> > > > > > > There doesn't seem to be any recent activity on the mailing
> > lists, and
> > > > > > > no recent commits.
> > > > > > >
> > > > > > > Sebb
> > > > > > >
> > > > > > >
> > -
> > > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > > > For additional commands, e-mail:
> > general-h...@incubator.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > Luciano Resende
> > > > > > http://twitter.com/lresende1975
> > > > > > http://lresende.blogspot.com/
> > > > >
> > > > > -
> > > > > 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
> >
> >

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

Re: [VOTE] Release Apache EventMesh(Incubating) 1.5.0-rc0

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- LICENSE, NOTICE, DISCLAIMER (even if it's WIP) are there and look good
- hash and signature are OK
- ASF header are there
- No binary file found in the source package

Regards
JB

On Tue, Jun 28, 2022 at 2:37 PM wenjun  wrote:
>
> Hi IPMC,
>
> This is an official vote for the Apache EventMesh(Incubating) 1.5.0-rc0
> that we have been working toward.
>
> To learn more about Apache EventMesh(Incubating), please see
> https://eventmesh.apache.org/
>
> Apache EventMesh (incubating) community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread/gr029kpf3f7qdsnptj5drs47lx9rj3j3
> Result thread:
> https://lists.apache.org/thread/vwh603cfftw5t335r7y6omzno42cmsj9
>
> Release changes:
> https://github.com/apache/incubator-eventmesh/blob/v1.5.0-rc0/release-note.md
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/eventmesh/1.5.0-incubating
>
> Maven 2 staging repository:
> https://repository.apache.org/content/repositories/orgapacheeventmesh-1025/org/apache/eventmesh
>
> Git tag for the release:
> https://github.com/apache/incubator-eventmesh/tree/v1.5.0-rc0
>
> Release Commit ID:
> https://github.com/apache/incubator-eventmesh/commit/f6df71fddae0ed3b24bac425a47d83ba3d65acb7
>
> Keys to verify the Release Candidate:
> https://downloads.apache.org/incubator/eventmesh/KEYS
>
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
> Checklist for reference:
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] Source code artifacts have correct names matching the current release.
>
> [ ] LICENSE and NOTICE files are correct for each EventMesh repo.
>
> [ ] All files have license headers if necessary.
>
> [ ] No compiled archives bundled in source archive.
>
> More detail checklist please refer:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
>
>
> Best,
> Wenjun Ruan
>
> -
> 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 Linkis(Incubating) 1.1.2-RC2

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- ASF headers are there
- hash and signature look good
- LICENSE, NOTICE, DISCLAIMER files are there and look good
- incubating is in the name
- No binary file found in the source package

Regards
JB

On Wed, Jun 29, 2022 at 5:16 PM seayi  wrote:
>
> Hello Incubator Community,
>
> The Apache Linkis community has voted and approved the release of Apache
> Linkis(incubating) 1.1.2-RC2. We now kindly request IPMC members and the
> incubator community to help review and vote for this release.
>
>  Apache Linkis builds a computation middleware layer to decouple the upper
> applications and the underlying data engines, provides standardized
> interfaces (REST, JDBC, WebSocket etc.) to easily connect to various
> underlying engines (Spark, Presto, Flink, etc.), while enables cross engine
> context sharing, unified job& engine governance and orchestration.
>
> Linkis community vote thread:
> • https://lists.apache.org/thread/llcy6fbbh2z2yjt21gmo0bz5htjkwobt
>
> Vote result thread:
> • https://lists.apache.org/thread/t9y1o82x47905l84jzg26l8rzrvm9bwo
>
> The release candidate:
> • https://dist.apache.org/repos/dist/dev/incubator/linkis/1.1.2-RC2/
>
> Git tag for the release:
> •
> https://github.com/apache/incubator-linkis/releases/tag/release-1.1.2-rc2
>
> Release notes:
> • https://linkis.apache.org/docs/1.1.2/release-notes-1.1.2
>
> The artifacts signed with PGP key [seayi], corresponding to [
> se...@apache.org], that can be found in keys file:
> • https://downloads.apache.org/incubator/linkis/KEYS
>
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> More detail checklist  please refer:
> •
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Steps to validate the release，Please refer to:
> • https://linkis.apache.org/community/how-to-verify
>
> Thanks,
> On behalf of Apache Linkis(Incubating) community

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

Re: [VOTE] Release Apache Linkis(Incubating) 1.1.2-RC1

[Jean-Baptiste Onofré]

-1 (binding)

IMHO, LICENSE file looks incomplete for me and some ASF headers don't look good.

Can you please fix that and submit a new release ?

Regards
JB

On Mon, Jun 20, 2022 at 5:17 PM seayi  wrote:
>
> Hello Incubator Community,
>
> The Apache Linkis community has voted and approved the release of Apache
> Linkis(incubating) 1.1.2-RC1. We now kindly request IPMC members and the
> incubator community to help review and vote for this release.
>
>  Apache Linkis builds a computation middleware layer to decouple the upper
> applications and the underlying data engines, provides standardized
> interfaces (REST, JDBC, WebSocket etc.) to easily connect to various
> underlying engines (Spark, Presto, Flink, etc.), while enables cross engine
> context sharing, unified job& engine governance and orchestration.
>
> Linkis community vote thread:
> • https://lists.apache.org/thread/h2v71m9pr2z8286386r59c1jhv5f32z7
>
> Vote result thread:
> • https://lists.apache.org/thread/4wovq49zroqpd9ttt9f17d8mvdsf2p3p
>
> The release candidate:
> • https://dist.apache.org/repos/dist/dev/incubator/linkis/1.1.2-RC1/
>
> Git tag for the release:
> •
> https://github.com/apache/incubator-linkis/releases/tag/release-1.1.2-rc1
>
> Release notes:
> • https://linkis.apache.org/docs/1.1.2/release-notes-1.1.2/
>
> The artifacts signed with PGP key [seayi], corresponding to [
> se...@apache.org], that can be found in keys file:
> • https://downloads.apache.org/incubator/linkis/KEYS
>
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> More detail checklist  please refer:
> •
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Steps to validate the release，Please refer to:
> • https://linkis.apache.org/community/how-to-verify
>
> Thanks,
> On behalf of Apache Linkis(Incubating) community

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

Re: [VOTE] Graduate Apache ShenYu(Incubating) as a TLP [ROUND 2]

[Jean-Baptiste Onofré]

+1 (binding)

Good luck,
Regards
JB

On Wed, Jun 22, 2022 at 8:42 AM XiaoYu  wrote:
>
> Dear Apache Incubator Community,
>
> In the previous vote[1] thread,
>
> I only described the functionality of the project and not the scope of
> the project in the resolution template.It doesn't fit the standard
> template. so I initiate cancel the vote thread[2].
>
> Under the guidance of our mentors, I refactor the project description
> in this resolution template.
>
> The Apache ShenYu community has a discussion thread [3],
> passed the community vote[4], and the vote result is published [5].
> We have discussed the graduation for ShenYu in the Incubator Community [6],
> where no issues were raised and lots of positive responses were received.
>
> I would like to start this voting thread to request graduating Apache
> ShenYu (incubating) from the incubator as a TLP. Please provide your vote
> as one of the following options:
>
> [ ] +1 Yes, I support ShenYu to graduate from the Apache incubator.
>
> [ ] +0 No opinion.
>
> [ ] -1 No, the ShenYu project is not ready to graduate, because ...
>
> The VOTE will remain open for at least 72 hours.
>
>
> ** Community **
>
> - 6 new PPMC members were added, bringing the total number of PPMC
> members to 30 from at least 15+ different organizations.
>
> - 7 new Committers were added, bringing the total number of Committers 37.
>
> - 110+ new contributors participate in the community. The number
> of contributors is now 270+ and growing.
>
> - The dev@shenyu.a.o mailing list currently has 350+ subscribers,
> and all major project discussions are happening in the dev@shenyu.a.o.
>
> - 26 Bi-weekly online meetings were held between committers,
> contributors and users. The meeting minutes are recorded on the
> mailing list [7].
>
> - 1100+ pull requests merged [8], and 700+ issues closed [9] after
> into the apache incubator.
>
> ** Project **
>
> - 4 releases by 4 release managers.
>
> - ShenYu official website [10] is compliant with Apache Foundation
> requirements [11].
>
> - Project maturity model is detailed in [12].
>
> - See ShenYu Project Incubation Status [13] for more info.
>
> ** Brands ,License, and Copyright **
>
> - We submitted an application for the brand[14] and it has been
> reviewed and approved.
> - Apache ShenYu community maintains project code on GitHub, and all 
> modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [15]. All
> the status files, license headers, and copyright are up to date.
>
> ** PMC members **
>
>- Please see the proposed board resolution below and let us know what you
> think. The initial PMC members were passed by the discussion and invitation
> [16].
>
> [1] https://lists.apache.org/thread/yk6kjx3j2mh9c5xzfojcln5dtrzt87yf
> [2] https://lists.apache.org/thread/53rj96r63sf2vxcdbfqbqbl27r4v9j0c
> [3] https://lists.apache.org/thread/lc1xr9gjf1t2lbk8070thf1bgt3sq1v3
> [4] https://lists.apache.org/thread/0fo3f3whl7bb5r7bhoh85czlgjdn7rog
> [5] https://lists.apache.org/thread/jdh2dcs4qd97t1mjjl8hp62sso470wc7
> [6] https://lists.apache.org/thread/cc2myvso0pbyl39yv26bdmzml8jjvpt2
> [7] https://lists.apache.org/list.html?d...@shenyu.apache.org
> [8] 
> https://github.com/apache/incubator-shenyu/pulls?q=is%3Apr+merged%3A%3E%3D2021-05-03+
> [9] 
> https://github.com/apache/incubator-shenyu/issues?q=is%3Aissue+is%3Aclosed+closed%3A%3E2021-05-03
> [10] https://shenyu.incubator.apache.org/
> [11] https://whimsy.apache.org/pods/project/shenyu
> [12] https://github.com/apache/incubator-shenyu/blob/master/MATURITY.md
> [13] https://incubator.apache.org/projects/shenyu.html
> [14] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-197
> [15] https://github.com/apache/incubator-shenyu/blob/master/LICENSE
> [16] https://lists.apache.org/thread/gp1bnjflz7ysgopxk515l9clswgrvnko
>
> --
>
> Establish the Apache ShenYu Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to Apache ShenYu is a Java native API Gateway for service
> proxy, protocol conversion and API governance.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache ShenYu Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache ShenYu Project be and hereby is responsible
> for the creation and maintenance of software related to
> Apache ShenYu is a Java native API Gateway for service
> proxy, protocol conversion and API governance; and be it further
>
> RESOLVED, that the 

Re: [VOTE] Release Apache DevLake (Incubating) v0.11.0-rc1

[Jean-Baptiste Onofré]

Hi,

I would recommend to cancel this vote and prepare a new release including:
- cleanup on the icon and png file about license
- flag DISCLAIMER on WIP
- improve NOTICE file

Regards
JB

On Fri, Jun 24, 2022 at 9:27 PM Hezheng Yin  wrote:
>
> Hi Felix, thanks for the suggestion. If we were able to resolve the
> licensing issues Justin raised, would you still recommend us switching to
> WIP DISCLAIMER?
>
> Hi Justin, thanks for the clarification. We have gone through all the
> image files in the release:
>
> 1. All flaticon icons [1] are replaced with blueprintjs icons [2] that have
> Apache 2.0 license.
> 2. For images created by ourselves, do we need to formally license them? If
> so, is there a guideline that we can follow?
> 3. In DevLake UI, we also make use of GitHub/GitLab/Jenkins/Jira logos on
> the integration page. We found their logo usage guidelines [3][4][5][6]
> online but couldn't find a formal license for these logos. For example, the
> GitHub Logos and Usage page [3] states it's ok to "Use the Octocat or
> GitHub logo to advertise that your product has built-in GitHub
> integration". Is it compliant with Apache policy to include such logos in
> the release?
>
> We'll restart the voting process on the DevLake mailing list once we
> address the issues above.
>
> [1] https://www.flaticon.com/pricing
> [2] https://blueprintjs.com/
> [3] https://github.com/logos
> [4]
> https://about.gitlab.com/handbook/marketing/corporate-marketing/brand-activation/trademark-guidelines/
> [5] https://www.jenkins.io/press/
> [6] https://www.atlassian.com/company/news/press-kit
>
> Best,
> Hezheng
>
>
>
> On Wed, Jun 22, 2022 at 8:52 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > And to be sure, we should go through the community vote step again before
> > > making another voting thread in general@incubator.apache.org. Is this
> > > correct? Thanks in advance!
> >
> > Yes your PPMC will ned to vote on the new release candidate before
> > bringing it for a vote by the incubator PMC.
> >
> > 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: [VOTE] Retire Crail

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Mon, Jun 6, 2022 at 9:48 PM Julian Hyde  wrote:
>
> After years of declining activity[1][2], and following discussions on
> dev@ [3][4] the Crail podling has voted to retire from incubation
> [5][6]. Per policy [7] I am proposing an IPMC vote to retire Crail.
>
> The vote is by lazy consensus and runs for 72 hours.
>
> +1 [ ] Retire Crail from the Incubator
> -1 [ ] Do not retire Crail from the Incubator
>
> Here is my vote:
> +1 [x] Retire Crail from the Incubator
>
> Julian Hyde
> (Member IPMC, Crail mentor)
>
> [1] https://incubator.apache.org/projects/crail.html
> [2] https://lists.apache.org/list?d...@crail.apache.org
> [3] https://lists.apache.org/thread/6hxkph98gobb5y7lrvx62rgr6ob9o91h
> [4] https://lists.apache.org/thread/9n08m29xgpshs4f2wxgspm4tlt44r98g
> [5] https://lists.apache.org/thread/xzss2o1oj2k85bbhvx883ojlrlozg3zm
> [6] https://lists.apache.org/thread/7165g55mrchzrlmhczfgybgzlnl2hxpj
> [7] https://incubator.apache.org/guides/retirement.html#deciding_to_retire
>
> -
> 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: [HELP WANTED] Creating the next board report

[Jean-Baptiste Onofré]

Good idea, let me take a look at the wiki page.

Regards
JB

On Thu, May 26, 2022 at 10:44 AM Justin Mclean  wrote:
>
> Hi,
>
> Thanks for offering to help. To help manage who does what I’ve created a page 
> here [1] just put your name next to something if you want to do it. If you 
> need help with anything just ask.
>
> Kind Regards,
> Justin
>
>
> 1. 
> https://cwiki.apache.org/confluence/display/INCUBATOR/June+2022+Incubator+Report++Tasks
> -
> 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: [HELP WANTED] Creating the next board report

[Jean-Baptiste Onofré]

Hi Justin,

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

Thanks,
Regards
JB

On Thu, May 12, 2022 at 9:15 AM Justin Mclean  wrote:
>
> Hi,
>
> As noted here [2] the board report should not be the sole responsibility of 
> the chair to put together.
>
> Here's what is roughly needed for each board report.
>
> After the board meeting:
> - Update podlings.xml to mark podling that did not report, ones whose report 
> was missing but reported and podlings at the end of their monthly reporting 
> period
> - assign podling shepherds using assign_shepherds.py
> - run clutch script (./clutch2.sh) and generate report 
> template(clutch2report.py)
> - Update wiki report page to have correct podling listed (may need to remove 
> graduated and retired podlings and add new podlings)
> - Add any new PPMCs to the wiki so they can edit their report
> - Send out email containing list of podlings to report and dates
>
> During the month:
> - Send out 2 or 3 reminders using report_reminders.py
>
> Before the report is due:
> - Write a summary of what has happened on the mailing list with anything of 
> interest
> - List all releases made during the month /  check if incubator votes match 
> with what’s in the release area
> - List who been added/removed to IPMC during the month
> - Check that PPMC members have been added correctly
> - Remove the non-reporting podlings sections from the report and note them as 
> not reporting
> - Note any podlings that didn’t get mentor sign off
> - Reflow the report and fix the report formatting including remove text 
> prompts for mentor activity and branding questions
> - Lock the wiki page so it can’t be edited
> - Send email to this list for review
> - Submit the report to the board
>
> If anyone would like to do any of these tasks just ask. If you need more 
> detail on how to do them just ask. The report run book report_reminders.py 
> and these pages [1][2] can also help. If no one volunteers then I’ll do them. 
> I’ll also check the report’s format and details if we do get volunteers.
>
> One thing it might be useful to look into is to see if we can automate 
> sending out the reminders each month rather than having it as a manual task.
>
> Kind Regards,
> Justin
>
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR
> 2. https://incubator.apache.org/guides/chair.html#board_report
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

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

[Jean-Baptiste Onofré]

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

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

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

[Jean-Baptiste Onofré]

eal-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

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

Re: [VOTE] Release Apache MXNet (incubating) version 1.9.1.rc0

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- LICENSE, NOTICE, DISCLAIMER are there and look good
- Hash and signature files look good
- No binary found in the source distribution

Regards
JB

On Wed, May 4, 2022 at 1:17 AM Wei Chu  wrote:
>
> Dear community,
>
> This is a call for releasing Apache MXNet (incubating) 1.9.1, release
> candidate 0.
>
> The Apache MXNet (incubating) community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread/2pj38r31fpk5g6jz87bnspt8lk0hvq73
>
> Result thread:
> https://lists.apache.org/thread/fbw6w8obogrvkg8gs0ng2lqwrlo2gs6k
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.9.1.rc0
>
> The tag to be voted upon is 1.9.1.rc0:
> https://github.com/apache/incubator-mxnet/releases/tag/1.9.1.rc0
>
> The release hash is 3f8f3be9987e259491ddc5a78aa9c6903e0b21e3:
> https://github.com/apache/incubator-mxnet/commit/3f8f3be9987e259491ddc5a78aa9c6903e0b21e3
>
> KEYS file available:
> https://downloads.apache.org/incubator/mxnet/KEYS
>
>
> The vote will be open for 72 hours.
>
> [ ] +1 release this package as 1.9.1.rc0
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
>
>
> Best regards,
> Wei Chu

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

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

[Jean-Baptiste Onofré]

+1 (binding)

Good luck as TLP.

Regards
JB

On Mon, May 9, 2022 at 1:34 AM Eya Badal  wrote:
>
> Dear Apache Incubator Community,
>
> Having passed the Community Graduation Vote [1] by the AGE community with a
> vote result to graduate the incubation [2], we have discussed Apache AGE's
> graduation in the general@incubator [DISCUSS] thread [3], where no issues
> were raised and lots of positive responses were received.
>
> I would like to start this voting thread to request graduating Apache AGE
> (incubating) from the incubator as a TLP.
>
> Please provide your vote as one of the following options:
>
> [ ] +1 - Recommend graduation of Apache AGE as a Top Level
>
> [ ] 0   - I don't feel strongly about it, but don't object
>
> [ ] -1  - Do not recommend the graduation of Apache AGE because …
>
> The VOTE will remain open for at least 72 hours.
>
>
>
> In addition to building and releasing the AGE software the Apache Way, the
> Apache AGE (Incubating) project community has grown in the following areas:
>
>
>-
>
>Close to 1000 commits
>-
>
>Added 9 new committers (from 7 different companies/institutions in 7
>different countries) and elevated 4 committers to PPMC
>-
>
>7 Apache releases (AGE 0.3, 0.4, 0.5, 0.6, 0.7 and 1.0 and sub-project
>AGE Viewer 1.0) from different release managers [4]
>-
>
>4 mentors, 13 PPMC members / committers (mentors excluded)
>-
>
>50+ unique contributors - Contributions span more than 20 countries
>across the globe
>
>
>-
>
>Developed and maintained the Apache AGE website [5]
>-
>
>Created an online user guide updated automatically to support new
>version of AGE. [6]
>-
>
>Assessed ourselves against the Apache Project maturity matrix [7] and
>didn't find any issues
>
>
>
>
> [1] https://lists.apache.org/thread/q2cgbnhvpzk2k0m8yfh89lzc75qym9k9
>
> [2] https://lists.apache.org/thread/lr3x9bm8jyv6o5kvyh7cf3tyxrpp2kwm
>
> [3] https://lists.apache.org/thread/fhdc27bp8lp7nsklq0ttc3cvyx7543ky
>
> [4] Apache AGE website release page 
>
> [5] https://age.apache.org/
>
> [6] Online user guide at Apache AGE website 
> under the Documentation menu
>
> [7] Apache AGE maturity assessment 
>
>
>
> 
>
> Establish the Apache AGE 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 multi-model database that enables graph and relational
>
> models built on PostgreSQL.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>
> (PMC), to be known as the "Apache AGE Project", be and hereby is
>
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache AGE Project be and hereby is responsible for
>
> the creation and maintenance of software related to a multi-model
>
> database that enables graph and relational models built on PostgreSQL;
>
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache AGE" 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 AGE Project, and to
>
> have primary responsibility for management of the projects within the
>
> scope of responsibility of the Apache AGE 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 AGE Project:
>
>  * Alex Kwak   
>
>  * Dehowe Feng 
>
>  * Eya Badal   
>
>  * Felix Cheung
>
>  * Jasper Blues
>
>  * John Gemignani  
>
>  * Josh Innis  
>
>  * Juan Pan
>
>  * Kevin Ratnasekera   
>
>  * Nick Sorrell
>
>  * Pieterjan De Potter 
>
>  * Von Gosling 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eya Badal be appointed to
>
> the office of Vice President, Apache AGE, 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 AGE Project be and hereby is tasked with the
>
> migration and rationalization of the Apache Incubator AGE podling; and
>
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
>
> AGE podling encumbered upon the Apache Incubator PMC are hereafter
>
> discharged.
>
> 

Re: [VOTE]Release Apache SeaTunnel(Incubating) 2.1.1

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- hash and signature are good
- DISCLAIMER is there
- LICENSE is there
- NOTICE is there but it seems incomplete, I would suggest to mention
dependencies license (Apache projects are mentioned in the NOTICE file
but not third parties like scala, fastjson, eclipse jetty, etc)
- ASF headers are present
- No binaries in the source distribution
- build ok using mvn

Thanks,
Regards
JB

On Fri, Apr 22, 2022 at 9:25 AM wenjun  wrote:
>
> Hi IPMC,
>
> This is an official vote for the Apache SeaTunnel(Incubating) 2.1.1
> that we have been working toward.
>
> To learn more about Apache SeaTunnel(Incubating), please see
> https://seatunnel.apache.org/
>
> Apache SeaTunnel (incubating) community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread/xkrr8po0frm6176x6wkvzngy1t44qlfo
> Result thread:
> https://lists.apache.org/thread/twtvx0zgh2t0xopf1nf30s64cm8wozq8
>
> Release changes:
> https://github.com/apache/incubator-seatunnel/blob/2.1.1/release-note.md
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/seatunnel/2.1.1
>
> Maven 2 staging repository:
> https://repository.apache.org/content/repositories/orgapacheseatunnel-1006/org/apache/seatunnel/
>
> Git tag for the release:
> https://github.com/apache/incubator-seatunnel/tree/2.1.1
>
> Release Commit ID:
> https://github.com/apache/incubator-seatunnel/commit/81c523b1d04864db3d936e3186fe43771adde224
>
> Keys to verify the Release Candidate:
> https://downloads.apache.org/incubator/seatunnel/KEYS
>
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
> Checklist for reference:
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] Source code artifacts have correct names matching the current release.
>
> [ ] LICENSE and NOTICE files are correct for each SeaTunnel repo.
>
> [ ] All files have license headers if necessary.
>
> [ ] No compiled archives bundled in source archive.
>
> More detail checklist please refer:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
>
> The following votes are carried over from the SeaTunnel dev mailing list:
> +1(binding)
> Calvin Kirs,
> Zhenxu Ke
>
> Best,
> Wenjun Ruan
>
> -
> 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 into the Apache Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Good luck ;)

Regards
JB

On Fri, Apr 22, 2022 at 3:38 PM Willem Jiang  wrote:
>
> Hi all,
>
> Following up the [DISCUSS] thread on DevLake [1], I would like to call a
> VOTE to accept DevLake into the Apache Incubator.
>
> Please cast your vote:
>
>   [ ] +1, bring DevLake into the Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring DevLake 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.
>
> Please check out the DevLake Proposal from the incubator wiki[2].
>
> [1]https://lists.apache.org/thread/b4jj51v7o9db193skfhzkn0nz2w8361l
> [2]https://cwiki.apache.org/confluence/display/INCUBATOR/DevLakeProposal
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> -
> 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: [DISCUSS] Incubating Proposal of DevLake

[Jean-Baptiste Onofré]

Hi Hezheng

Thanks for the details. It helps as well.

If you need help/additional mentor, please let me know. I don't know
go very well but happy to learn and help. However, I think you already
have enough and good mentors on the proposal.

Regards
JB

On Thu, Apr 21, 2022 at 8:18 AM Hezheng Yin  wrote:
>
> Hi JB,
>
> Thanks for your interests in DevLake. One key difference between DevLake and 
> Gobblin/NiFi is that Gobblin/NiFi are domain agnostic general frameworks 
> while DevLake specializes in the domain of software development data. This 
> focus allows DevLake to better “understand” the data that it ingests, 
> cleanses, transforms, analyzes, and visualizes for developers. At the 
> foundation of this understanding is DevLake’s data 
> model<https://github.com/merico-dev/lake/wiki/DataModel.Domain-layer-schema> 
> built on top of the software development process. We’ll keep expanding this 
> model as DevLake supports new DevOps tools (data sources) requested by the 
> community. If you have any other question or suggestion, please let us know. 
> Any feedback is greatly appreciated!
>
> Best,
> Hezheng
> Maintainer of DevLake
>
> From: Jean-Baptiste Onofré 
> Date: Monday, April 18, 2022 at 7:23 AM
> To: general@incubator.apache.org 
> Subject: Re: [DISCUSS] Incubating Proposal of DevLake
> Thanks, it helps !
>
> Regards
> JB
>
> On Mon, Apr 18, 2022 at 4:14 PM Willem Jiang  wrote:
> >
> > Hi JB
> >
> > You may find the information about the DevOps data collection here[1]
> > There are some domain related entities schema[2] which are built on
> > top of the development process.
> >
> > [1]https://github.com/merico-dev/lake/blob/main/ARCHITECTURE.md
> > [2]https://github.com/merico-dev/lake/wiki/DataModel.Domain-layer-schema
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sun, Apr 17, 2022 at 12:14 AM Jean-Baptiste Onofré  
> > wrote:
> > >
> > > Hi Willem,
> > >
> > > It looks interesting. I took a look on github repo. I don't see the
> > > relation between DevOps and data collection/ETL part mentioned on the
> > > README.
> > >
> > > For the data collection/ETL framework, it sounds similar to
> > > Gobblin/NiFi, etc. The DevOps part is more interesting IMHO. I have to
> > > dig into this.
> > >
> > > Regards
> > > JB
> > >
> > > On Thu, Apr 7, 2022 at 10:20 AM Willem Jiang  
> > > wrote:
> > > >
> > > > We want to propose  DevLake[1]  as a new Apache Incubator project.
> > > >
> > > > DevLake helps developer teams integrate and analyze software
> > > > development data throughout the software development life cycle
> > > > (SDLC).
> > > > Specifically, DevLake provides:
> > > >
> > > > * High-quality connectors that integrate data from various DevOps tools;
> > > > * A comprehensive and unified data model and metrics that enable
> > > > developers to easily query data and answer questions regarding their
> > > > development process;
> > > > * A plugin system that allows customizable data connectors and 
> > > > enrichers;
> > > > * An unified ETL management module that orchestrates data collection
> > > > and analysis.
> > > >
> > > > I'd be happy to be the Champion of this project and many thanks to
> > > > Liang Zhang (zhangliang at apache dot org)，Lidong Dai (lidongdai at 
> > > > apache
> > > > dot org)，Sijie Guo (sijie at apache dot org） for being the mentor of  
> > > > DevLake
> > > > project and helping us to polish the incubating proposal[2].
> > > >
> > > > Looking forward to your feedback and thank you very much.
> > > >
> > > > [1]https://github.com/merico-dev/lake
> > > > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/DevLakeProposal
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > -
> > > > 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
> >
>
> -
> 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 InLong(Incubating) 1.1.0-incubating RC0

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- Hash and signature are OK
- LICENSE and NOTICE are there and OK (NOTICE could be simplified by
just mentioning Apache projects in general, not listing all Apache
projects like HBase, etc, but that's OK)
- DISCLAIMER-WIP is there (I guess it could be renamed to just DISCLAIMER)
- No binary found in source artifact
- ASF headers are present in all source files

Regards
JB

On Wed, Apr 20, 2022 at 5:23 AM dockerzhang  wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache InLong(Incubating) version
> 1.1.0-incubating RC0
>
> The Apache InLong community has voted on and approved a proposal to
> release
> Apache InLong(Incubating) version 1.1.0-incubating RC0
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> InLong community vote thread:
> • https://lists.apache.org/thread/mtwxgcf2sh4lgohpdo6vk1gkpnwn5qo5
>
> Vote result thread:
> • https://lists.apache.org/thread/hc9bkb37n0sdwmon6pqnvnntszt0vb0n
>
> The release candidate:
> •
> https://dist.apache.org/repos/dist/dev/incubator/inlong/1.1.0-incubating-RC0/
>
> Git tag for the release:
> •
> https://github.com/apache/incubator-inlong/releases/tag/1.1.0-incubating-RC0
>
> Release notes:
> •
> https://github.com/apache/incubator-inlong/blob/1.1.0-incubating-RC0/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

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

Re: [VOTE] Release Apache Kyuubi(Incubating) v1.5.1-incubating rc0

[Jean-Baptiste Onofré]

+1 (binding)

I checked:
- incubating is in the name
- LICENSE, NOTICE and DISCLAIMER files are present and look good
- Signature and hash are OK
- ASF headers are present in source files
- No binary files found in the source artifact

Regards
JB

On Tue, Apr 19, 2022 at 5:47 AM Kent Yao  wrote:
>
> +1, carried from dev
>
> Fu Chen  于2022年4月18日周一 10:46写道：
> >
> > Hello Incubator Community,
> >
> > The Apache Kyuubi community has voted on and approved a proposal to release
> > Apache Kyuubi(Incubating) version v1.5.1-incubating rc0.
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Kyuubi community vote thread:
> > https://www.mail-archive.com/dev@kyuubi.apache.org/msg02421.html
> >
> > Vote result thread:
> > https://www.mail-archive.com/dev@kyuubi.apache.org/msg02434.html
> >
> > [ ] +1 Release this package as Apache Kyuubi v1.5.1-incubating
> > [ ] +0
> > [ ] -1 Do not release this package because ...
> >
> > To learn more about Apache Kyuubi (Incubating), please see
> > https://kyuubi.apache.org/
> >
> > The tag to be voted on is v1.5.1-incubating-rc0 (commit
> > 84fb1c084a030a31e4766187818a0f2cb73b24cc):
> > https://github.com/apache/incubator-kyuubi/tree/v1.5.1-incubating-rc0
> >
> > The release files, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/kyuubi/v1.5.1-incubating-rc0/
> >
> > Signatures used for Kyuubi RCs can be found in this file:
> > https://downloads.apache.org/incubator/kyuubi/KEYS
> >
> > The staging repository for this release can be found at:
> > https://repository.apache.org/content/repositories/orgapachekyuubi-1018/
> >
> > The release note is available in:
> > https://github.com/apache/incubator-kyuubi/releases/tag/v1.5.1-incubating-rc0
> >
> >
> > Thanks,
> > On behalf of Apache Kyuubi(Incubating) community
>
> -
> 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 Kvrocks into the Apache Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On Wed, Apr 20, 2022 at 1:18 AM Liang Chen  wrote:
>
> Hi all,
>
> Following up the [DISCUSS] thread on Kvrocks[1], I would like to
> call a VOTE to accept Kvrocks into the Apache Incubator, please check out
> the Kvrocks Proposal from the incubator wiki[2].
>
> Please cast your vote:
>
> [ ] +1, bring Kvrocks into the Incubator
> [ ] +0, I don't care either way
> [ ] -1, do not bring Kvrocks 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/bdtmvbmvzrgjd1kj7mdrp9tkqrhg3d31
> [2] https://cwiki.apache.org/confluence/display/INCUBATOR/KvrocksProposal
>
> Regards
> Liang

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

Re: [DISCUSS] Incubating Proposal of DevLake

[Jean-Baptiste Onofré]

Thanks, it helps !

Regards
JB

On Mon, Apr 18, 2022 at 4:14 PM Willem Jiang  wrote:
>
> Hi JB
>
> You may find the information about the DevOps data collection here[1]
> There are some domain related entities schema[2] which are built on
> top of the development process.
>
> [1]https://github.com/merico-dev/lake/blob/main/ARCHITECTURE.md
> [2]https://github.com/merico-dev/lake/wiki/DataModel.Domain-layer-schema
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sun, Apr 17, 2022 at 12:14 AM Jean-Baptiste Onofré  
> wrote:
> >
> > Hi Willem,
> >
> > It looks interesting. I took a look on github repo. I don't see the
> > relation between DevOps and data collection/ETL part mentioned on the
> > README.
> >
> > For the data collection/ETL framework, it sounds similar to
> > Gobblin/NiFi, etc. The DevOps part is more interesting IMHO. I have to
> > dig into this.
> >
> > Regards
> > JB
> >
> > On Thu, Apr 7, 2022 at 10:20 AM Willem Jiang  wrote:
> > >
> > > We want to propose  DevLake[1]  as a new Apache Incubator project.
> > >
> > > DevLake helps developer teams integrate and analyze software
> > > development data throughout the software development life cycle
> > > (SDLC).
> > > Specifically, DevLake provides:
> > >
> > > * High-quality connectors that integrate data from various DevOps tools;
> > > * A comprehensive and unified data model and metrics that enable
> > > developers to easily query data and answer questions regarding their
> > > development process;
> > > * A plugin system that allows customizable data connectors and enrichers;
> > > * An unified ETL management module that orchestrates data collection
> > > and analysis.
> > >
> > > I'd be happy to be the Champion of this project and many thanks to
> > > Liang Zhang (zhangliang at apache dot org)，Lidong Dai (lidongdai at apache
> > > dot org)，Sijie Guo (sijie at apache dot org） for being the mentor of  
> > > DevLake
> > > project and helping us to polish the incubating proposal[2].
> > >
> > > Looking forward to your feedback and thank you very much.
> > >
> > > [1]https://github.com/merico-dev/lake
> > > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/DevLakeProposal
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > -
> > > 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
>

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