Re: [VOTE] Release Apache Pegasus (Incubating) 2.4.0-RC3

[Liang Chen]

Carry my +1(binding) from dev

Regards
Liang

Jia Shuo  于 2022年10月22日周六 05:37写道：

> ​Hi, all
>
> This is a call for a vote to release Apache Pegasus (Incubating) version
> 2.4.0-RC3.
>
> Pegasus is a distributed key-value storage system that is designed to be
> simple, horizontally scalable, strongly consistent, and high-performance.
>
> The Apache Pegasus community has voted on and approved a proposal to
> release Apache Pegasus 2.4.0-RC3.
>
> Apache Pegasus community vote thread:
> [VOTE] Release Apache Pegasus (incubating) 2.4.0-RC3-Apache Mail Archives<
> https://lists.apache.org/thread/s07qtnlc2l8z35hm0zz6ps7yzp3gzwww>
>
> Result thread:
> [RESULT][VOTE] Release Apache Pegasus (incubating) 2.4.0-RC3-Apache Mail
> Archives
>
> The source tarball, including signatures, digests, etc. can be found at:
> dist - Revision 57509: /dev/incubator/pegasus/2.4.0-RC3 (apache.org)<
> https://dist.apache.org/repos/dist/dev/incubator/pegasus/2.4.0-RC3/>
>
> It is tagged in Git as v2.4.0-RC3 and the corresponding hash is the
> following:
> ASF Git Repos - incubator-pegasus.git/commit (apache.org)<
> https://gitbox.apache.org/repos/asf?p=incubator-pegasus.git;a=commit;h=8bdca79a7f871e91283bd0270e5bd7913d8c295e
> >
>
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/pegasus/KEYS
>
>
> For information about the contents of this release, see:
> Apache Pegasus 2.4.0 Release Note - Google<
> https://docs.google.com/document/d/1zzHT-AmDfp6fXZN4-80Mv5_8eNi4wjpLZd4v_K02wFY/edit#heading=h.2ozarc20gnha
> >
>
> The vote will be open for 72 hours.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Expecting your votes.
> Thanks,
> Shuo Jia
>

[VOTE] Release Apache Pegasus (Incubating) 2.4.0-RC3

[Jia Shuo]

​Hi, all

This is a call for a vote to release Apache Pegasus (Incubating) version
2.4.0-RC3.

Pegasus is a distributed key-value storage system that is designed to be
simple, horizontally scalable, strongly consistent, and high-performance.

The Apache Pegasus community has voted on and approved a proposal to
release Apache Pegasus 2.4.0-RC3.

Apache Pegasus community vote thread:
[VOTE] Release Apache Pegasus (incubating) 2.4.0-RC3-Apache Mail 
Archives

Result thread:
[RESULT][VOTE] Release Apache Pegasus (incubating) 2.4.0-RC3-Apache Mail 
Archives

The source tarball, including signatures, digests, etc. can be found at:
dist - Revision 57509: /dev/incubator/pegasus/2.4.0-RC3 
(apache.org)

It is tagged in Git as v2.4.0-RC3 and the corresponding hash is the
following:
ASF Git Repos - incubator-pegasus.git/commit 
(apache.org)


KEYS file available:
https://dist.apache.org/repos/dist/dev/incubator/pegasus/KEYS


For information about the contents of this release, see:
Apache Pegasus 2.4.0 Release Note - 
Google

The vote will be open for 72 hours.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Expecting your votes.
Thanks,
Shuo Jia

[ANNOUNCE] Apache Uniffle (incubating) 0.6.0 available

[roryqi]

Hi all,

Apache Uniffle (incubating) Team is glad to announce the new release of
Apache Uniffle (incubating) 0.6.0.

Apache Uniffle (incubating)  is a high performance, general purpose Remote
Shuffle
Service for distributed compute engines like Apache Spark <
https://spark.apache.org/>,
Apache Hadoop MapReduce , Apache Flink <
https://flink.apache.org/>
and so on.So We are aiming to make Uniffle a universal shuffle service for
distributed compute engines.


Download Links: https://uniffle.apache.org/download/


Release Notes: https://uniffle.apache.org/download/release-notes-0.6.0


Website: https://uniffle.apache.org


Uniffle Resources:

- Issue: https://github.com/apache/incubator-uniffle/issues

- Mailing list: d...@uniffle.apache.org


- Apache Uniffle (incubating) Team

NuttX community graduation vote started

[Nathan Hartman]

Dear Apache Incubator Community,

A community graduation VOTE at Apache NuttX (Incubating) is now taking
place [1] regarding graduation to Top-Level Project (TLP).

I'd like to take this opportunity to express a big THANK YOU to the
ASF, Incubator, our mentors, PPMC, committers, and all community
members, for helping us get this far. THANK YOU!

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

Cheers,
Nathan Hartman

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

Re: Available to help with projects

[Nathan Hartman]

On Thu, Oct 20, 2022 at 11:35 PM Justin Mclean 
wrote:

> HI,
>
> I don’t mean to dampen anyone's enthusiasm, but NuttX probably doesn’t
> need a lot of help to graduate, but there are other podlings that do need
> more help.
>
> Kind Regards,
> Justin



On the contrary, I think that should improve everyone's enthusiasm!

Cheers
Nathan

Re: [VOTE] Accept Pekko into the Apache Incubator

[healchow]

+1 (non-binding)

Best wishes to the project!

Heal Chow, Apache InLong PMC

On Fri, Oct 21, 2022 at 11:51 AM Michael Marshall 
wrote:

> +1 (non-binding)
>
> - Michael
>
> On 2022/10/19 08:04:30 "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 c