Re: [VOTE] Apache Tuweni 2.3.0-incubating

[Furkan KAMACI]

Hi,

+1 (binding, carrying over my vote as Antoine mentioned)

Kind Regards,
Furkan KAMACI

On 6 Oct 2022 Thu at 14:56 Antoine Toulme  wrote:

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

Re: [MENTORS] Late podling reports and missing signoffs

[Furkan KAMACI]

Hi,

Exactly! Most of the mentors (including me) at ApacheCon. I think they will
all take care of it before the deadline.

Kind Regards,
Furkan KAMACI

On 6 Oct 2022 Thu at 10:09 Calvin Kirs  wrote:

> On Thu, Oct 6, 2022 at 10:45 PM Daniel Gruno  wrote:
> >
> > On 2022-10-06 07:15, Calvin Kirs wrote:
> > > Hi,
> > >
> > > We are missing reports from:
> > > - EventMesh
> > > - HugeGraph
> > > - MarvinAI
> > > - Nuttx
> > > - Spot
> > > - Teaclave
> > > - PonyMail
> > >
> > > We are missing mentor sign-off on:(Mentor signoff due by end of days
> > > is Tue Oct 9)
> > > - DataLab
> > > - Flagon
> > > - Milagro
> > >
> >
> > I suspect ApacheCon is causing some reports to be delayed for a couple
> > of days...
> Yes, I know we have a lot of people who went to Apache Con, but it
> doesn't matter, we still have time to submit our reports.
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> --
> Best wishes！
> CalvinKirs
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache Tuweni 2.3.0-incubating

[Antoine Toulme]

Any member available to vote?

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


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

Re: [DISCUSS] Incubating Proposal for Pekko

[Chesnay Schepler]

>  Does the Flink team have any documentation on the alternatives to 
Akka that you're looking at?


We are / I am currently working a prototype based on gRPC.
Functionality-wise it looks promising and we're nearly there; but 
there's still a lot to be done w.r.t. testing & hardening the entire 
thing over the coming months of course.


Really anything that allows us to ship some binary blob from A to B with 
some ordering guarantees pretty much does the trick for us.
But this willy vary significantly between companies, depending on which 
of the many parts of Akka they're actually using; there's afaict no 
one-size-fits-all replacement.

(Which makes me wonder whether Akka just does too many different things?)

We used very little functionality of Akka; our only real dependencies 
are akka-actor and akka-remote.
In a way Akka was just providing a thread pool + 
one-active-thread-per-component-guarantees + shipping of messages.

That's not _that_ difficult to replace.

Our stack is also a bit out-dated; still stuck on Netty 3 for example 
instead of Artery.
That's another thing that makes switching attractive; the alternative 
isn't "stick with Akka" but "stick with Akka and fix these things 
_eventually_".


> Would the Flink team consider helping to get Pekko up and running?
> It may be that there is less effort involved in getting Pekko 
released than rewriting a large part of Flink.


That's of course a fair point, however releasing Pekko isn't the problem 
at hand though; it's maintaining it for several months/years.
That's a huge commitment over picking another library that /is/ already 
being maintained.


I can't speak for the entire project but I doubt that we have the 
capacity or knowledge to really help out in a significant way;
we're busy enough working on Flink as is, and those who introduced Akka 
into Flink are no longer active.


At least so far rewriting our Akka integration appears to require less 
effort.


On 06/10/2022 16:41, PJ Fanning wrote:

Thanks Chesnay for clarifying the Flink team's position on this.
Since many companies and OSS projects are in a similar position, does
the Flink team have any documentation on the alternatives to Akka that
you're looking at?

Feel free to ignore the suggestion but the volunteers for the Pekko
include a number of major Akka contributors but would the Flink team
consider helping to get Pekko up and running? It may be that there is
less effort involved in getting Pekko released than rewriting a large
part of Flink.

Regards,
PJ

On Wed, 5 Oct 2022 at 15:45, Chesnay Schepler  wrote:

Hello,

since Flink is mentioned several times in the proposal I feel the need to point 
out that we're actively looking into outright replacing Akka.

We need something that is guaranteed to work once the 2.6.x support provided by 
Lightbend ends next year, and with Akka being used in the very core of Flink 
this transition has to start early.
We can't really take a gamble on this fork still being active/useful in a year.

My current expectation is that we'd only use Pekko as an emergency replacement 
for older releases when the Lightbend support ends and a critical issue was 
found (which is quite unlikely to be honest).

On 2022/09/29 14:57:56 "Claude Warren, Jr" wrote:

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] Retire Livy podling

[larry mccay]

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
>

Re: [VOTE] Accept Baremaps into the Apache Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

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

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

[li gang]

+1 (non-binding)
I checked
- The release files have the word incubating in their name
- Checksums and signatures are valid
- DISCLAIMER,LICENSE and NOTICE files exist
- NOTICE year is correct
- All needed files have ASF headers.

Liang Zhang  于2022年10月4日周二 20:53写道：

> Hello all,
>
> This is a call for vote to release Apache DevLake (Incubating) v0.14.0-rc1
>
> The Apache DevLake community has voted on and approved a proposal to
> release
> Apache DevLake (Incubating) version v0.14.0-rc1
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Linkis community vote thread:
> https://lists.apache.org/thread/s6jj2tl5mlyb8jpdd88jmo5woydzhp54
>
> Vote result thread:
> https://lists.apache.org/thread/mb5sxdopprqksf1ppfggkvkwxs6110zk
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.14.0-incubating-rc1/
>
> Git tag for the release:
> https://github.com/apache/incubator-devlake/tree/v0.14.0-rc1
>
> Keys to verify the Release Candidate:
> https://downloads.apache.org/incubator/devlake/KEYS
>
> How to build:
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 


--
Best Regards

DolphinScheduler PMC
Gang Li 李岗

lgcar...@apache.org

Re: [VOTE] Accept Baremaps into the Apache Incubator

[Madhawa Gunasekara]

+1 (binding)
Madhawa


On Thu, Oct 6, 2022 at 4:19 PM Julian Hyde  wrote:

> +1 (binding)
>
> Julian
>
>
> On Thu, Oct 6, 2022 at 8:10 AM Josh Fischer  wrote:
> >
> > +1 (non-binding)
> >
> > On Thu, Oct 6, 2022 at 7:54 AM Bertrand Delacretaz <
> bdelacre...@apache.org>
> > wrote:
> >
> > > Bertrand Delacretaz  wrote:
> > > > ...I'm calling a vote to accept Baremap into the
> > > > Apache incubator.
> > > >...
> > >
> > > +1, bring Baremap into the Incubator!
> > >
> > > -Bertrand
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > > --
> > Sent from A Mobile Device
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [MENTORS] Late podling reports and missing signoffs

[Calvin Kirs]

On Thu, Oct 6, 2022 at 10:45 PM Daniel Gruno  wrote:
>
> On 2022-10-06 07:15, Calvin Kirs wrote:
> > Hi,
> >
> > We are missing reports from:
> > - EventMesh
> > - HugeGraph
> > - MarvinAI
> > - Nuttx
> > - Spot
> > - Teaclave
> > - PonyMail
> >
> > We are missing mentor sign-off on:(Mentor signoff due by end of days
> > is Tue Oct 9)
> > - DataLab
> > - Flagon
> > - Milagro
> >
>
> I suspect ApacheCon is causing some reports to be delayed for a couple
> of days...
Yes, I know we have a lot of people who went to Apache Con, but it
doesn't matter, we still have time to submit our reports.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>


-- 
Best wishes！
CalvinKirs

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

Re: [VOTE] Accept Baremaps into the Apache Incubator

[Calvin Kirs]

Hi,
+1 (binding)

On Thu, Oct 6, 2022 at 10:19 PM Julian Hyde  wrote:
>
> +1 (binding)
>
> Julian
>
>
> On Thu, Oct 6, 2022 at 8:10 AM Josh Fischer  wrote:
> >
> > +1 (non-binding)
> >
> > On Thu, Oct 6, 2022 at 7:54 AM Bertrand Delacretaz 
> > wrote:
> >
> > > Bertrand Delacretaz  wrote:
> > > > ...I'm calling a vote to accept Baremap into the
> > > > Apache incubator.
> > > >...
> > >
> > > +1, bring Baremap into the Incubator!
> > >
> > > -Bertrand
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > > --
> > Sent from A Mobile Device
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>


-- 
Best wishes！
CalvinKirs

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

Re: [MENTORS] Late podling reports and missing signoffs

[Daniel Gruno]

On 2022-10-06 07:15, Calvin Kirs wrote:

Hi,

We are missing reports from:
- EventMesh
- HugeGraph
- MarvinAI
- Nuttx
- Spot
- Teaclave
- PonyMail

We are missing mentor sign-off on:(Mentor signoff due by end of days
is Tue Oct 9)
- DataLab
- Flagon
- Milagro



I suspect ApacheCon is causing some reports to be delayed for a couple 
of days...


-
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

[PJ Fanning]

Thanks Chesnay for clarifying the Flink team's position on this.
Since many companies and OSS projects are in a similar position, does
the Flink team have any documentation on the alternatives to Akka that
you're looking at?

Feel free to ignore the suggestion but the volunteers for the Pekko
include a number of major Akka contributors but would the Flink team
consider helping to get Pekko up and running? It may be that there is
less effort involved in getting Pekko released than rewriting a large
part of Flink.

Regards,
PJ

On Wed, 5 Oct 2022 at 15:45, Chesnay Schepler  wrote:
>
> Hello,
>
> since Flink is mentioned several times in the proposal I feel the need to 
> point out that we're actively looking into outright replacing Akka.
>
> We need something that is guaranteed to work once the 2.6.x support provided 
> by Lightbend ends next year, and with Akka being used in the very core of 
> Flink this transition has to start early.
> We can't really take a gamble on this fork still being active/useful in a 
> year.
>
> My current expectation is that we'd only use Pekko as an emergency 
> replacement for older releases when the Lightbend support ends and a critical 
> issue was found (which is quite unlikely to be honest).
>
> On 2022/09/29 14:57:56 "Claude Warren, Jr" wrote:
> > 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
>

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

Re: [VOTE] Accept Baremaps into the Apache Incubator

[Julian Hyde]

+1 (binding)

Julian


On Thu, Oct 6, 2022 at 8:10 AM Josh Fischer  wrote:
>
> +1 (non-binding)
>
> On Thu, Oct 6, 2022 at 7:54 AM Bertrand Delacretaz 
> wrote:
>
> > Bertrand Delacretaz  wrote:
> > > ...I'm calling a vote to accept Baremap into the
> > > Apache incubator.
> > >...
> >
> > +1, bring Baremap into the Incubator!
> >
> > -Bertrand
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> > --
> Sent from A Mobile Device

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

Re: [VOTE] Accept Baremaps into the Apache Incubator

[Josh Fischer]

+1 (non-binding)

On Thu, Oct 6, 2022 at 7:54 AM Bertrand Delacretaz 
wrote:

> Bertrand Delacretaz  wrote:
> > ...I'm calling a vote to accept Baremap into the
> > Apache incubator.
> >...
>
> +1, bring Baremap into the Incubator!
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
Sent from A Mobile Device

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

[Nathan Hartman]

On Thu, Sep 22, 2022 at 10:57 PM Alin Jerpelea  wrote:
>
> Hello all,
>
> This is a call for a vote to release Apache NuttX (Incubating) version
> 11.0.0.
>
> The Apache NuttX community has voted on and approved a proposal to
> release Apache NuttX (Incubating) version 11.0.0.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> NuttX is a real-time operating system (RTOS) with an emphasis on
> standards compliance and small footprint. Scalable from 8-bit to 64-bit
> microcontroller environments, the primary governing standards in NuttX
> are Posix and ANSI standards. Additional standard APIs from Unix and
> other common RTOS’s (such as VxWorks) are adopted for functionality not
> available under these standards, or for functionality that is not
> appropriate for deeply- embedded environments (such as fork()).
>
> Because this project targets embedded systems there is more complexity
> involved in the build process.
>
> Apache NuttX community vote and result thread:
> Result:https://lists.apache.org/thread/c0lv34jvwbdh6wfnl7xsprxmggllpmcw
> Vote:https://lists.apache.org/thread/rv9pf8gtbcq4zjnydv2h2lsymszzb33f
>
> SCM Information:
>   Release tag: nuttx-11.0.0-RC2
>   Hash for the release incubating-nuttx
> tag:d32555f3e0492b8f4caeb407db55de23322724ef
>   Hash for the release incubating-nuttx-apps
> tag:8b43f9f9ca30f44c1cccae9a9078d5d45b776d35
>
>
> [1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/11.0.0-RC2/
> [2]https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-11.0.0-RC2/ReleaseNotes
> [3] https://www.apache.org/dev/release.html#approving-a-release
> [4]https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Alin Jerpelea
> Apache NuttX

Just pinging this thread... we need just one more IPMC vote to make
the NuttX-11.0.0 release!

Nathan

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

Re: [VOTE] Accept Baremaps into the Apache Incubator

[Bertrand Delacretaz]

Bertrand Delacretaz  wrote:
> ...I'm calling a vote to accept Baremap into the
> Apache incubator.
>...

+1, bring Baremap into the Incubator!

-Bertrand

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

[VOTE] Accept Baremaps into the Apache Incubator

[Bertrand Delacretaz]

Hi,

The [DISCUSS] thread on Baremaps [1] has slowed down, with no
objections AFAICS, so I'm calling a vote to accept Baremap into the
Apache incubator.

The proposal is copied below and available at
https://cwiki.apache.org/confluence/display/INCUBATOR/Baremaps+Proposal

Please cast your vote:

  [ ] +1, bring Baremap into the Incubator
  [ ] +0, I don't care either way
  [ ] -1, do not bring Baremap into the Incubator, because...

This majority vote is open for at least 72 hours.

Only votes from Incubator PMC members are binding, but other votes are welcome!

-Bertrand

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

-- Baremaps Proposal --

Abstract

Apache Baremaps is a toolkit and a set of infrastructure components
for creating, publishing, and operating online maps.

Proposal

Apache Baremaps is a toolkit and a set of infrastructure components
for creating, publishing, and operating online maps. It provides a
data pipeline enabling developers to build maps with different data
sources. It offers live reload capabilities that allow cartographers
to customize the content and the style of a map. It includes an
attribution-free map schema and style that stimulates derived work.
Finally, it provides services commonly used in online maps, such as
location search and IP to location.

Background

The infrastructure components required to publish and operate
large-scale online maps are often closed-source, heterogeneous,
complex, and expensive. For instance: the visualization of maps in Web
browsers or on mobile devices requires processing and tiling large
spatial datasets, such as OpenStreetMap; the location of users based
on their IP addresses requires aggregating and merging data from
network information centers; the ability to search in a map requires
indexing features based on text and spatial attributes in different
languages.

Rationale

Web mapping infrastructure is often managed by large teams of
developers (e.g., Google Maps, Apple Maps, Mapbox, etc.), which makes
it hard to customize and evolve. Apache Baremaps is a Web mapping
infrastructure for the rest of us: it enables individuals and small
teams of developers to regain control over spatial data and to develop
custom mapping experiences. As a result, Apache Baremaps facilitates
innovation in niche areas where resources are limited and
customization is needed (e.g., sustainable mobility, civil
engineering, urban planning, environment monitoring, startups, etc.).

Initial Goals

The primary goals are:

to learn the Apache Way;
to release a customizable attribution-free map schema and style;
to publish a tiled world map in different formats (mvt, png, 3D Tiles
Next, etc.);
to grow the community and attract new contributors;
to release additional services and components (IP to location,
location search, etc.).

Current Status

Meritocracy

Baremaps is a project initially developed by Bertil Chapuis. It has
already attracted outside contributors. Therefore, the process of
electing new committers and project management committee members
should be natural.

Community

The need for Web mapping infrastructure is great, hence a good
potential for a diverse community mixing developers and cartographers.

Core Developers

The contributors to Baremaps include developers from academia and
industry, mainly located in Europe. The contributions include
documentation, bug fixes, and new features. Most of the development
and communication currently takes place on GitHub.

Alignment

Many critical components used in the geospatial community are released
under LGPL (e.g., Geotools, Geotoolkit). We are strongly aligned with
the terms of the Apache license. Joining the geospatial community at
Apache will enable us to be less reliant on components with
contaminating licenses. For instance, Apache SIS seeks to become an
alternative to Geotools and Geotoolkit.

Known Risks

Project Name

No trademark is associated with the Baremaps name, and the project is
already well referenced by search engines. The .com, .org, and .net
domains are the property of Bertil Chapuis, who agrees to transfer
them to the Apache Software Foundation unconditionally upon request.

Orphaned Products

There is a risk of being orphaned due to the small number of
committers. Even if the main contributor has no plan to leave the
project, this is a problem we need to address in the future.

Inexperience with open source

The initial committers contributed to open source projects in the past
but have only a few experiences with the governance of open source
projects in a Foundation such as Apache.

Length of incubation

We expect to achieve most of the initial goals within one year.
However, some other goals (e.g., growing a community sufficiently
diverse and healthy to leave the incubator) are harder to estimate and
may span over a more extended time.

Homogenous Developers

Most current developers work for the same institution (University of
Applied Sciences and Arts of 

Re: [MENTORS] Late podling reports and missing signoffs

[Nathan Hartman]

On Thu, Oct 6, 2022 at 8:15 AM Calvin Kirs  wrote:
> We are missing reports from:
> - EventMesh
> - HugeGraph
> - MarvinAI
> - Nuttx
> - Spot
> - Teaclave
> - PonyMail

The NuttX report is posted.

Cheers,
Nathan

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

[MENTORS] Late podling reports and missing signoffs

[Calvin Kirs]

Hi,

We are missing reports from:
- EventMesh
- HugeGraph
- MarvinAI
- Nuttx
- Spot
- Teaclave
- PonyMail

We are missing mentor sign-off on:(Mentor signoff due by end of days
is Tue Oct 9)
- DataLab
- Flagon
- Milagro

-- 
Best wishes！
CalvinKirs

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

Re: [DISCUSS] Retire Livy podling

[Luciano Resende]

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

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

[david zollo]

+1 binding

I checked,
- incubating in name
- DISCLAIMER is fine
- No unexpected binary files
- ASF headers exists


Best Regards

---
Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
David
Linkedin: https://www.linkedin.com/in/davidzollo
Twitter: @WorkflowEasy 
---


On Wed, Oct 5, 2022 at 4:27 PM Jean-Baptiste Onofré  wrote:

> +1 (binding)
>
> I checked:
>
> - incubating is in the version
> - DISCLAIMER, NOTICE, LICENSE look good
> - Signature and hash are valid
> - ASF headers present in source files
> - No binary files in source distribution
>
> Regards
> JB
>
> On Tue, Oct 4, 2022 at 2:53 PM Liang Zhang
>  wrote:
> >
> > Hello all,
> >
> > This is a call for vote to release Apache DevLake (Incubating)
> v0.14.0-rc1
> >
> > The Apache DevLake community has voted on and approved a proposal to
> release
> > Apache DevLake (Incubating) version v0.14.0-rc1
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Linkis community vote thread:
> > https://lists.apache.org/thread/s6jj2tl5mlyb8jpdd88jmo5woydzhp54
> >
> > Vote result thread:
> > https://lists.apache.org/thread/mb5sxdopprqksf1ppfggkvkwxs6110zk
> >
> > The release candidates:
> >
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.14.0-incubating-rc1/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-devlake/tree/v0.14.0-rc1
> >
> > Keys to verify the Release Candidate:
> > https://downloads.apache.org/incubator/devlake/KEYS
> >
> > How to build:
> > https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
> >
> > The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

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

[Madhawa Gunasekara]

+1 (binding)
checked
 -Include the word incubating in the release file name
 -Include an ASF LICENSE and NOTICE file
 -Have valid signatures

Thanks & Regards,

Madhawa


[image: Mailtrack]

Sender
notified by
Mailtrack

10/06/22,
10:15:01 AM
Remove

On Wed, Oct 5, 2022 at 10:27 AM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> I checked:
>
> - incubating is in the version
> - DISCLAIMER, NOTICE, LICENSE look good
> - Signature and hash are valid
> - ASF headers present in source files
> - No binary files in source distribution
>
> Regards
> JB
>
> On Tue, Oct 4, 2022 at 2:53 PM Liang Zhang
>  wrote:
> >
> > Hello all,
> >
> > This is a call for vote to release Apache DevLake (Incubating)
> v0.14.0-rc1
> >
> > The Apache DevLake community has voted on and approved a proposal to
> release
> > Apache DevLake (Incubating) version v0.14.0-rc1
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Linkis community vote thread:
> > https://lists.apache.org/thread/s6jj2tl5mlyb8jpdd88jmo5woydzhp54
> >
> > Vote result thread:
> > https://lists.apache.org/thread/mb5sxdopprqksf1ppfggkvkwxs6110zk
> >
> > The release candidates:
> >
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.14.0-incubating-rc1/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-devlake/tree/v0.14.0-rc1
> >
> > Keys to verify the Release Candidate:
> > https://downloads.apache.org/incubator/devlake/KEYS
> >
> > How to build:
> > https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
> >
> > The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Retire Livy podling

[david zollo]

hi,
 There are no activities for the Livy community.
 +1 for the retire



Best Regards

---
Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
David
Linkedin: https://www.linkedin.com/in/davidzollo
Twitter: @WorkflowEasy 
---


On Wed, Oct 5, 2022 at 8:40 PM Calvin Kirs  wrote:

> Hi.
>
> The project has been depressed since 2021,
> with basically no commits since, no activity on the mailing list,
> and a lot of missed reports, despite JB's attempts to revive the
> community, but to no avail.
>
> So I think it's time for Livy to retire.
>
> On Wed, Oct 5, 2022 at 8:26 PM 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
> >
>
>
> --
> Best wishes！
> CalvinKirs
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>