Re: [MENTORS] Projects > 1000 days in Incubation

[Nathan Hartman]

On Wed, Oct 19, 2022 at 2:06 PM Justin Mclean 
wrote:

> Hi,
>
> We have several projects that seem to have been hanging about in the
> Incubator a little longer than they should. I took a look at all projects
> that have been incubating for more than a 1000 days, and this seems to be
> the state of play (corrections welcome):


(snip)

NuttX - discussing graduation


At NuttX I think the community feels ready to graduate to TLP. In about 24
hours I will open the [VOTE] thread at dev@nuttx.a.o so we will know for
sure shortly.

We would very much appreciate all the input and help we can get from our
mentors and IPMC to complete this process successfully!

NuttX Project Highlights Since Incubation:

* Incubating since 2019-12-09
* New website, nuttx.apache.org
* Shipped 9 releases under the ASF Incubator, including two non-WIP release
* Merged more than 7000 PRs across incubator-nuttx and incubator-nuttx-apps
* More than 1000 stars on GitHub
* More than 500 forks on GitHub
* More than 250 subscribers to d...@nuttx.apache.org
* Named the 9th most active Apache project of 2021 by number of commits [1]
* 5 mentors
* 18 PPMC members
* 25 committers
* 75 ICLAs
* 2 CCLAs
* 21 SGAs
* 2 release managers
* 3 NuttX online workshops
* And much, much more

[1]
https://thestack.technology/top-apache-projects-in-2021-from-superset-to-nuttx/

Cheers,
Nathan

Re: [MENTORS] Projects > 1000 days in Incubation

[Jerry Tan]

Hi， brpc has discussed graduation this year with our mentors，
and list some actions to do in the following days，
including more releases,  resolving branding issues, attract more committers.

Now we have resolved the branding issues 
(see it at https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-202)

We also have several apache releases including 1.0,1.1, 1.2, and 1.3 release is 
under voting.

And some new committers have been recognized and attracted.

So, we plan to graduate brpc by the end of this year and we do things 
accordingly.

Thanks.

On 2022/10/19 18:06:39 Justin Mclean wrote:
> Hi,
> 
> We have several projects that seem to have been hanging about in the 
> Incubator a little longer than they should. I took a look at all projects 
> that have been incubating for more than a 1000 days, and this seems to be the 
> state of play (corrections welcome):
> 
> Annotator - discussing graduation
> Brpc - unknown
> DataLab - should have graduated
> Flagon - should have graduated
> Heron - discussing graduation
> Livy - undergoing reboot
> Marvin-AI - role call
> Milagro - reboot / role call
> MXNet - has graduated
> Nemo - should have graduated
> NuttX - discussing graduation 
> PageSpeed - lack of community growth
> Pony Mail - have discussed but no actions
> SDAP - discussing steps to graduation (making a release)
> Spot - Roll call
> StreamPipes - Discussing graduation
> Teaclave - Role call
> Toree - Role call
> Training - lack of community growth
> Tuweni - discussing graduation
> 
> If you are a mentor of one of these projects, it would be great if you could 
> encourage the project to exist from the Incubator. If you are one of these 
> projects and your mentors are no longer engaged, please get in touch, and 
> we’ll see what we can do to help you.
> 
> 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: [DISCUSS] What to do with long incubating projects?

[Justin Mclean]

Hi,

> Is there a maximum time for incubation?  Target?  I have not read incubator
> docs closely.

Not really but we expect a projects to exit in 1-3 years, and at 4-5 years we 
tend to ask them to retire, but it does vary.

> I could also see a dashboard with milestones [ various requirements for
> graduation ] at various timelines, and whether projects are ahead/behind
> 'schedule’.

I like the idea but it might hard to gauge - the Incubator podling reports does 
have a general progress indicator.

Kind Regards,
Justin
-
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

[Greg Stein]

Sheng Wu is correct. I was a Mentor for the Apache Fineract project. Never
read the dev@ list, never checked out the code. They graduated, and I
didn't join the PMC. But I happen to still be subscribed to their mailing
list to offer historical perspective/advice.

There are many ways to contribute to a community and commit/coding doesn't
have to be the only path.

Cheers,
-g


On Fri, Sep 30, 2022 at 3:36 AM Sheng Wu  wrote:

> I think mentors don't have to be committers.
> Just some initial committers could be mentors. This is not required.
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
> Claude Warren, Jr  于2022年9月30日周五 16:20写道：
> >
> > 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 <
> claude.war...@aiven.io>
> > 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
> > >> > >
> > >> >
> > >>
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] What to do with long incubating projects?

[Austin Bennett]

Is there a maximum time for incubation?  Target?  I have not read incubator
docs closely.


I could also see a dashboard with milestones [ various requirements for
graduation ] at various timelines, and whether projects are ahead/behind
'schedule'.





On Wed, Oct 19, 2022 at 2:34 PM Justin Mclean 
wrote:

> Hi,
>
> > * Graduation Status
>
> This is included in the current report.
>
> > * Community issues for both users and maintainers
> >   - what are the barriers of entry for each - complexity in maintenance,
> > language use, continued relevance, etc
>
> This should also be in the reports but is perhaps not always included.
> Some projects just copy and paste the previous report and do not fill in
> the full details all the time, and some projects don’t like to publicise
> some issues. Some project set their committer bar too high, which can
> discourage contribution. In theory this is were the mentors can help.
>
> > Maybe this is a simple report to see how long they have been incubating
> > though?
>
> We have reports that do mention how old a podling is so that is visible.
>
> Kind Regards,
> Justin
>
>
> -
> 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

[Justin Mclean]

I made it read only for you

On Wed, 19 Oct 2022, 4:43 am Ryan Skraba, 
wrote:

> Hello!  It seems I don't have permissions to make
> https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal
> read-only
> 
> during the vote.  Can someone please take a look for us?
>
> Just to be clear, the proposal was on v10, last edited on October 18th when
> the vote was called.
>
> Thanks in advance!  Ryan
>
> On Wed, Oct 19, 2022 at 1:34 PM Ryan Skraba  wrote:
>
> > +1 (binding)
> >
> > All my best!  Ryan Skraba
> >
> > On Wed, Oct 19, 2022 at 12:46 PM Charles Zhang 
> > wrote:
> >
> >> + 1 （non-binding）
> >>
> >> Best wishes,
> >> Charles Zhang
> >> from Apache InLong
> >>
> >>
> >> tison  于2022年10月19日周三 18:23写道：
> >>
> >> > +1 (binding)
> >> >
> >> > Best,
> >> > tison.
> >> >
> >> >
> >> > Yu Xiao  于2022年10月19日周三 18:00写道：
> >> >
> >> > > + 1 （non-binding）
> >> > >
> >> > > Best wishes!
> >> > >
> >> > > Yu Xiao
> >> > > Apache ShenYu
> >> > >
> >> > > Calvin Kirs  于2022年10月19日周三 17:51写道：
> >> > > >
> >> > > > +1 binding
> >> > > > Good luck.
> >> > > >
> >> > > > On Wed, Oct 19, 2022 at 5:37 PM Sheng Wu <
> wu.sheng.841...@gmail.com
> >> >
> >> > > wrote:
> >> > > > >
> >> > > > > +1 binding
> >> > > > >
> >> > > > > Welcome
> >> > > > >
> >> > > > > Sheng Wu 吴晟
> >> > > > > Twitter, wusheng1108
> >> > > > >
> >> > > > > PJ Fanning  于2022年10月19日周三 17:32写道：
> >> > > > > >
> >> > > > > > Thanks Claude and Ryan for putting together the proposal.
> >> > > > > >
> >> > > > > > +1 binding
> >> > > > > >
> >> > > > > > On Wed, 19 Oct 2022 at 09:08, Claude Warren, Jr
> >> > > > > >  wrote:
> >> > > > > > >
> >> > > > > > > I'll even kick off the voting:
> >> > > > > > >
> >> > > > > > > +1 binding
> >> > > > > > >
> >> > > > > > > On Wed, Oct 19, 2022 at 9:04 AM Claude Warren, Jr <
> >> > > claude.war...@aiven.io>
> >> > > > > > > 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 

Re: [MENTORS] Projects > 1000 days in Incubation

[Julian Hyde]

> SDAP - discussing steps to graduation (making a release)

Last week I joined SDAP as a mentor. I am encouraging them to reassess
what's left before graduation. As Justin says, the main thing is to
make a release. There's a lot of stuff that they *think* they need to
do (e.g. setting up CI) that they don't strictly need to do.

Sometimes the key step to graduate is the community waking up and
saying 'Yes, we're ready to graduate!'

Julian


Julian

On Wed, Oct 19, 2022 at 11:07 AM Justin Mclean  wrote:
>
> Hi,
>
> We have several projects that seem to have been hanging about in the 
> Incubator a little longer than they should. I took a look at all projects 
> that have been incubating for more than a 1000 days, and this seems to be the 
> state of play (corrections welcome):
>
> Annotator - discussing graduation
> Brpc - unknown
> DataLab - should have graduated
> Flagon - should have graduated
> Heron - discussing graduation
> Livy - undergoing   reboot
> Marvin-AI - role call
> Milagro - reboot / role call
> MXNet - has graduated
> Nemo - should have graduated
> NuttX - discussing graduation
> PageSpeed - lack of community growth
> Pony Mail - have discussed but no actions
> SDAP - discussing steps to graduation (making a release)
> Spot - Roll call
> StreamPipes - Discussing graduation
> Teaclave - Role call
> Toree - Role call
> Training - lack of community growth
> Tuweni - discussing graduation
>
> If you are a mentor of one of these projects, it would be great if you could 
> encourage the project to exist from the Incubator. If you are one of these 
> projects and your mentors are no longer engaged, please get in touch, and 
> we’ll see what we can do to help you.
>
> 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: [DISCUSS] What to do with long incubating projects?

[Justin Mclean]

Hi,

> * Graduation Status

This is included in the current report.

> * Community issues for both users and maintainers
>   - what are the barriers of entry for each - complexity in maintenance,
> language use, continued relevance, etc

This should also be in the reports but is perhaps not always included. Some 
projects just copy and paste the previous report and do not fill in the full 
details all the time, and some projects don’t like to publicise some issues. 
Some project set their committer bar too high, which can discourage 
contribution. In theory this is were the mentors can help.

> Maybe this is a simple report to see how long they have been incubating
> though?

We have reports that do mention how old a podling is so that is visible.

Kind Regards,
Justin


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

[MENTORS] Projects > 1000 days in Incubation

[Justin Mclean]

Hi,

We have several projects that seem to have been hanging about in the Incubator 
a little longer than they should. I took a look at all projects that have been 
incubating for more than a 1000 days, and this seems to be the state of play 
(corrections welcome):

Annotator - discussing graduation
Brpc - unknown
DataLab - should have graduated
Flagon - should have graduated
Heron - discussing graduation
Livy - undergoing   reboot
Marvin-AI - role call
Milagro - reboot / role call
MXNet - has graduated
Nemo - should have graduated
NuttX - discussing graduation   
PageSpeed - lack of community growth
Pony Mail - have discussed but no actions
SDAP - discussing steps to graduation (making a release)
Spot - Roll call
StreamPipes - Discussing graduation
Teaclave - Role call
Toree - Role call
Training - lack of community growth
Tuweni - discussing graduation

If you are a mentor of one of these projects, it would be great if you could 
encourage the project to exist from the Incubator. If you are one of these 
projects and your mentors are no longer engaged, please get in touch, and we’ll 
see what we can do to help you.

Kind Regards,
Justin


-
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

[Ryan Skraba]

Hello!  It seems I don't have permissions to make
https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal
read-only during the vote.  Can someone please take a look for us?

Just to be clear, the proposal was on v10, last edited on October 18th when
the vote was called.

Thanks in advance!  Ryan

On Wed, Oct 19, 2022 at 1:34 PM Ryan Skraba  wrote:

> +1 (binding)
>
> All my best!  Ryan Skraba
>
> On Wed, Oct 19, 2022 at 12:46 PM Charles Zhang 
> wrote:
>
>> + 1 （non-binding）
>>
>> Best wishes,
>> Charles Zhang
>> from Apache InLong
>>
>>
>> tison  于2022年10月19日周三 18:23写道：
>>
>> > +1 (binding)
>> >
>> > Best,
>> > tison.
>> >
>> >
>> > Yu Xiao  于2022年10月19日周三 18:00写道：
>> >
>> > > + 1 （non-binding）
>> > >
>> > > Best wishes!
>> > >
>> > > Yu Xiao
>> > > Apache ShenYu
>> > >
>> > > Calvin Kirs  于2022年10月19日周三 17:51写道：
>> > > >
>> > > > +1 binding
>> > > > Good luck.
>> > > >
>> > > > On Wed, Oct 19, 2022 at 5:37 PM Sheng Wu > >
>> > > wrote:
>> > > > >
>> > > > > +1 binding
>> > > > >
>> > > > > Welcome
>> > > > >
>> > > > > Sheng Wu 吴晟
>> > > > > Twitter, wusheng1108
>> > > > >
>> > > > > PJ Fanning  于2022年10月19日周三 17:32写道：
>> > > > > >
>> > > > > > Thanks Claude and Ryan for putting together the proposal.
>> > > > > >
>> > > > > > +1 binding
>> > > > > >
>> > > > > > On Wed, 19 Oct 2022 at 09:08, Claude Warren, Jr
>> > > > > >  wrote:
>> > > > > > >
>> > > > > > > I'll even kick off the voting:
>> > > > > > >
>> > > > > > > +1 binding
>> > > > > > >
>> > > > > > > On Wed, Oct 19, 2022 at 9:04 AM Claude Warren, Jr <
>> > > claude.war...@aiven.io>
>> > > > > > > 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.

Re: [VOTE] Accept Pekko into the Apache Incubator

[Ryan Skraba]

+1 (binding)

All my best!  Ryan Skraba

On Wed, Oct 19, 2022 at 12:46 PM Charles Zhang 
wrote:

> + 1 （non-binding）
>
> Best wishes,
> Charles Zhang
> from Apache InLong
>
>
> tison  于2022年10月19日周三 18:23写道：
>
> > +1 (binding)
> >
> > Best,
> > tison.
> >
> >
> > Yu Xiao  于2022年10月19日周三 18:00写道：
> >
> > > + 1 （non-binding）
> > >
> > > Best wishes!
> > >
> > > Yu Xiao
> > > Apache ShenYu
> > >
> > > Calvin Kirs  于2022年10月19日周三 17:51写道：
> > > >
> > > > +1 binding
> > > > Good luck.
> > > >
> > > > On Wed, Oct 19, 2022 at 5:37 PM Sheng Wu 
> > > wrote:
> > > > >
> > > > > +1 binding
> > > > >
> > > > > Welcome
> > > > >
> > > > > Sheng Wu 吴晟
> > > > > Twitter, wusheng1108
> > > > >
> > > > > PJ Fanning  于2022年10月19日周三 17:32写道：
> > > > > >
> > > > > > Thanks Claude and Ryan for putting together the proposal.
> > > > > >
> > > > > > +1 binding
> > > > > >
> > > > > > On Wed, 19 Oct 2022 at 09:08, Claude Warren, Jr
> > > > > >  wrote:
> > > > > > >
> > > > > > > I'll even kick off the voting:
> > > > > > >
> > > > > > > +1 binding
> > > > > > >
> > > > > > > On Wed, Oct 19, 2022 at 9:04 AM Claude Warren, Jr <
> > > claude.war...@aiven.io>
> > > > > > > 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
> > > > > > > > 

Re: [VOTE] Accept Pekko into the Apache Incubator

[Charles Zhang]

+ 1 （non-binding）

Best wishes,
Charles Zhang
from Apache InLong


tison  于2022年10月19日周三 18:23写道：

> +1 (binding)
>
> Best,
> tison.
>
>
> Yu Xiao  于2022年10月19日周三 18:00写道：
>
> > + 1 （non-binding）
> >
> > Best wishes!
> >
> > Yu Xiao
> > Apache ShenYu
> >
> > Calvin Kirs  于2022年10月19日周三 17:51写道：
> > >
> > > +1 binding
> > > Good luck.
> > >
> > > On Wed, Oct 19, 2022 at 5:37 PM Sheng Wu 
> > wrote:
> > > >
> > > > +1 binding
> > > >
> > > > Welcome
> > > >
> > > > Sheng Wu 吴晟
> > > > Twitter, wusheng1108
> > > >
> > > > PJ Fanning  于2022年10月19日周三 17:32写道：
> > > > >
> > > > > Thanks Claude and Ryan for putting together the proposal.
> > > > >
> > > > > +1 binding
> > > > >
> > > > > On Wed, 19 Oct 2022 at 09:08, Claude Warren, Jr
> > > > >  wrote:
> > > > > >
> > > > > > I'll even kick off the voting:
> > > > > >
> > > > > > +1 binding
> > > > > >
> > > > > > On Wed, Oct 19, 2022 at 9:04 AM Claude Warren, Jr <
> > claude.war...@aiven.io>
> > > > > > 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 

Re: [VOTE] Accept Pekko into the Apache Incubator

[tison]

+1 (binding)

Best,
tison.


Yu Xiao  于2022年10月19日周三 18:00写道：

> + 1 （non-binding）
>
> Best wishes!
>
> Yu Xiao
> Apache ShenYu
>
> Calvin Kirs  于2022年10月19日周三 17:51写道：
> >
> > +1 binding
> > Good luck.
> >
> > On Wed, Oct 19, 2022 at 5:37 PM Sheng Wu 
> wrote:
> > >
> > > +1 binding
> > >
> > > Welcome
> > >
> > > Sheng Wu 吴晟
> > > Twitter, wusheng1108
> > >
> > > PJ Fanning  于2022年10月19日周三 17:32写道：
> > > >
> > > > Thanks Claude and Ryan for putting together the proposal.
> > > >
> > > > +1 binding
> > > >
> > > > On Wed, 19 Oct 2022 at 09:08, Claude Warren, Jr
> > > >  wrote:
> > > > >
> > > > > I'll even kick off the voting:
> > > > >
> > > > > +1 binding
> > > > >
> > > > > On Wed, Oct 19, 2022 at 9:04 AM Claude Warren, Jr <
> claude.war...@aiven.io>
> > > > > 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. 

Re: [VOTE] Accept Pekko into the Apache Incubator

[Yu Xiao]

+ 1 （non-binding）

Best wishes!

Yu Xiao
Apache ShenYu

Calvin Kirs  于2022年10月19日周三 17:51写道：
>
> +1 binding
> Good luck.
>
> On Wed, Oct 19, 2022 at 5:37 PM Sheng Wu  wrote:
> >
> > +1 binding
> >
> > Welcome
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> > PJ Fanning  于2022年10月19日周三 17:32写道：
> > >
> > > Thanks Claude and Ryan for putting together the proposal.
> > >
> > > +1 binding
> > >
> > > On Wed, 19 Oct 2022 at 09:08, Claude Warren, Jr
> > >  wrote:
> > > >
> > > > 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 

Re: [VOTE] Accept Pekko into the Apache Incubator

[Calvin Kirs]

+1 binding
Good luck.

On Wed, Oct 19, 2022 at 5:37 PM Sheng Wu  wrote:
>
> +1 binding
>
> Welcome
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
> PJ Fanning  于2022年10月19日周三 17:32写道：
> >
> > Thanks Claude and Ryan for putting together the proposal.
> >
> > +1 binding
> >
> > On Wed, 19 Oct 2022 at 09:08, Claude Warren, Jr
> >  wrote:
> > >
> > > 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 

Re: [VOTE] Accept Pekko into the Apache Incubator

[Sheng Wu]

+1 binding

Welcome

Sheng Wu 吴晟
Twitter, wusheng1108

PJ Fanning  于2022年10月19日周三 17:32写道：
>
> Thanks Claude and Ryan for putting together the proposal.
>
> +1 binding
>
> On Wed, 19 Oct 2022 at 09:08, Claude Warren, Jr
>  wrote:
> >
> > 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 

Re: [VOTE] Accept Pekko into the Apache Incubator

[PJ Fanning]

Thanks Claude and Ryan for putting together the proposal.

+1 binding

On Wed, 19 Oct 2022 at 09:08, Claude Warren, Jr
 wrote:
>
> 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 

Re: [VOTE] Accept Pekko into the Apache Incubator

[Claude Warren, Jr]

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

[VOTE] Accept Pekko into the Apache Incubator

[Claude Warren, Jr]

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