[RESULT][VOTE] Accept Pekko into the Apache Incubator
After 120 hours of voting the vote passes with more than 3 binding +1's and a few non-binding +1s and no other votes. The final tally was 12 binding +1s and 7 non-binding +1s. Thanks to all who voted. I'll ask for the podling to be set up and mailing lists to be created as per https://incubator.apache.org/cookbook/#podling_infrastructure_setup and will report here when the dev@ list is ready. -- Claude
Re: [VOTE] Accept Pekko into the Apache Incubator
I'll even kick off the voting: +1 binding On Wed, Oct 19, 2022 at 9: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 > Ap
[VOTE] Accept Pekko into the Apache Incubator
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 trademark from all sections in the code. - Setting up the build system using github actions to make sure we have a CI system setup whenever pull requests are made (some Akka projects use github actions already, in which case we need to make sure it still
Re: [DISCUSS] Retire Livy podling
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 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: [DISCUSS] Incubating Proposal for Pekko
Tison, I send the email yesterday before submitting the proposal. Thanks for the heads up though. As to the other part, I think I will remove myself from the committer list at this time. On Thu, Sep 29, 2022 at 6:23 PM tison wrote: > Hi Claude, > > Thanks for starting this discussion! +1 to this proposal. > > It answers my previous questions on > https://lists.apache.org/thread/hdknoyvr9c0d4j70xqw6t2t7gnbzc7nq a new > name + a clear goal. > > I'm interested to act as a mentor to help with this podling's growth. > > w.r.t the membership, I notice that Claude Warren and PJ Fanning are listed > on both initial committers and mentors, while other mentors don't. Perhaps > you should check what's the intention here. > > Also, Claude Warren (you) and PJ Fanning are Apache members who can become > IPMC members with a notice, but it still needs to go through the > process[1][2]. > > Best, > tison. > > [1] > > https://incubator.apache.org/guides/roles_and_responsibilities.html#incubator_project_management_committee_ipmc > [2] https://lists.apache.org/thread/t6k3mg97pyshzoxzjg4c62n166l3crcw > > > > Jean-Baptiste Onofré 于2022年9月29日周四 23:36写道： > > > 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: [DISCUSS] Incubating Proposal for Pekko
Is is standard for mentors to be committers on the project? And should they be listed in both sections. Claude On Fri, Sep 30, 2022 at 9:15 AM Claude Warren, Jr wrote: > Tison, > > I send the email yesterday before submitting the proposal. Thanks for the > heads up though. > > As to the other part, I think I will remove myself from the committer list > at this time. > > On Thu, Sep 29, 2022 at 6:23 PM tison wrote: > >> Hi Claude, >> >> Thanks for starting this discussion! +1 to this proposal. >> >> It answers my previous questions on >> https://lists.apache.org/thread/hdknoyvr9c0d4j70xqw6t2t7gnbzc7nq a new >> name + a clear goal. >> >> I'm interested to act as a mentor to help with this podling's growth. >> >> w.r.t the membership, I notice that Claude Warren and PJ Fanning are >> listed >> on both initial committers and mentors, while other mentors don't. Perhaps >> you should check what's the intention here. >> >> Also, Claude Warren (you) and PJ Fanning are Apache members who can become >> IPMC members with a notice, but it still needs to go through the >> process[1][2]. >> >> Best, >> tison. >> >> [1] >> >> https://incubator.apache.org/guides/roles_and_responsibilities.html#incubator_project_management_committee_ipmc >> [2] https://lists.apache.org/thread/t6k3mg97pyshzoxzjg4c62n166l3crcw >> >> >> >> Jean-Baptiste Onofré 于2022年9月29日周四 23:36写道： >> >> > 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 >> > > >> > >> >
[DISCUSS] Incubating Proposal for Pekko
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: possible interest in forming a community fork of akka
PJ, Several of us working on the mdedetrich github projects [1] are preparing to submit a proposal to the incubator, hopefully by the end of the week. We have had contact from several individual devlopers, organizations, projects, and companies about such a project. We identified a champion and several mentors, we would be happy to add you to our list of mentors. Claude [1] https://github.com/mdedetrich/akka-apache-project On Mon, Sep 26, 2022 at 7:11 PM PJ Fanning wrote: > Hi everyone, > > Apologies if this is not the right mailing list. If it is not, please > let me know and I'll switch the thread to the right list. > > Lighbend [1], the company that maintains the popular open source > framework, Akka [2], recently announced they are moving Akka to a > non-OSS commercial license [3]. > > There is interest in the OSS community in forking Akka under a new > name and maintaining it as an ASF project [4]. > > It is early days yet but there is some discussion online [5]. > > Reading the incubator cookbook, a new podling would need to have > champions and mentors from within the Incubator PMC [6]. > > I would like to put my name forward for such a role, as an existing > ASF member [7]. > > If anyone else in the Incubator PMC would like to get involved, that > would be great. > > Regards, > PJ > > [1] https://www.lightbend.com/ > [2] https://akka.io/ > [3] https://www.lightbend.com/akka/license-faq > [4] https://github.com/mdedetrich/akka-apache-project > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9 > [6] > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator > [7] https://whimsy.apache.org/roster/committer/fanningpj > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
