Re: possible interest in forming a community fork of akka

[Ralph Goers]

+1 to everything Greg says, although I wouldn’t consider it to be a hostile 
fork 
just as I don’t consider the fork of Hudson to Jenkins to be a hostile fork. In 
my 
book it isn’t a hostile fork when the major contributors simply switch to the 
new 
repository and infrastructure. i.e - if the community largely is staying intact 
how 
can it possibly be a fork? You can certainly say the code forked (that happens 
all the time at GitHub and no one really cares) but what is more important to 
me is the community.

Ralph

> On Sep 27, 2022, at 4:23 PM, Greg Stein  wrote:
> 
> On Tue, Sep 27, 2022 at 4:55 AM PJ Fanning  wrote:
>> ...
> 
>> In some cases, the critical fix might be submitted to the fork first
>> and it may be easier for the Lightbend team to cherry pick those cases
>> than it is for the fork team to do the opposite.
>> 
> 
> Should an ALv2 fork arise *anywhere*[1], then I believe
> Lightbend's community will vaporize. That community will follow the OSS
> fork, and Lightbend will be relegated to picking up those ALv2-licensed
> patches into their proprietary version. There will simply be no reason for
> a community to hang around and contribute their work to the newly-licensed
> and proprietary version of Akka.
> 
> Cheers,
> -g
> 
> [1] whether at the ASF, or at an external hosting site. Note that,
> historically, the ASF has been mostly against forks where the owner(s)
> disagree with creating that fork (aka "a hostile fork").


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

Re: possible interest in forming a community fork of akka

[Greg Stein]

On Tue, Sep 27, 2022 at 4:55 AM PJ Fanning  wrote:
>...

> In some cases, the critical fix might be submitted to the fork first
> and it may be easier for the Lightbend team to cherry pick those cases
> than it is for the fork team to do the opposite.
>

Should an ALv2 fork arise *anywhere*[1], then I believe
Lightbend's community will vaporize. That community will follow the OSS
fork, and Lightbend will be relegated to picking up those ALv2-licensed
patches into their proprietary version. There will simply be no reason for
a community to hang around and contribute their work to the newly-licensed
and proprietary version of Akka.

Cheers,
-g

[1] whether at the ASF, or at an external hosting site. Note that,
historically, the ASF has been mostly against forks where the owner(s)
disagree with creating that fork (aka "a hostile fork").

Re: [Discuss] Baremaps Proposal

[Josh Fischer]

+1.  Count me in

On Tue, Sep 27, 2022 at 5:55 PM Julian Hyde  wrote:

> When I mentor a project (as I have volunteered to do for Baremaps) I
> usually host a Zoom meeting with the initial contributors explaining what
> really goes on during Incubation. I totally agree that learning the Apache
> Way and making releases are key activities. I usually invite other
> stakeholders (e.g. contributors’ managers) because people have a lot of
> questions, and it helps to set people’s expectations correctly early on.
>
> Julian
>
>
> > On Sep 27, 2022, at 3:44 PM, Josh Fischer  wrote:
> >
> > I think we should call out in the proposal of initial goals is learn the
> apache way how to make releases within the foundation.  There is much to
> learn in the incubating process.
> >
> >
> >
> > On Tue, Sep 27, 2022 at 12:22 PM Josh Fischer  > wrote:
> > +1.  Happy to talk anytime.
> >
> > On Tue, Sep 27, 2022 at 11:29 AM Bertil Chapuis  > wrote:
> > Hi Josh,
> >
> > Glad you are interested in the project, I added you to the list of
> committers in the proposal.
> >
> > I hope to learn more about your Web mapping use cases soon.
> >
> > Best,
> >
> > Bertil
> >
> >
> >
> >
> > > On 27 Sep 2022, at 04:03, Josh Fischer  j...@joshfischer.io>> wrote:
> > >
> > > Hi Bertil,
> > >
> > > I’d be happy to contribute if you’re interested.
> > >
> > > - Josh
> > >
> > > On Fri, Sep 16, 2022 at 8:25 AM Bertil Chapuis  > wrote:
> > >
> > >> Hello Everyone,
> > >>
> > >> Here is a proposal for Baremaps, a toolkit and a set of infrastructure
> > >> components for creating, publishing, and operating online maps. The
> > >> proposal is published on the wiki [1] and a demonstration of our base
> map
> > >> is available online [2].
> > >>
> > >> The key challenge for Baremaps will be to create a sustainable
> community.
> > >> We appreciate anyone who would be willing to support us with bug
> reports,
> > >> code, mentoring or feedback.
> > >>
> > >> [1] -
> > >>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Baremaps+Proposal <
> https://cwiki.apache.org/confluence/display/INCUBATOR/Baremaps+Proposal>
> > >> [2] - https://demo.baremaps.com/ 
> > >>
> > >> Best regards,
> > >>
> > >> Bertil Chapuis
> > >>
> > >> 
> > >>
> > >> 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 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 

Re: [Discuss] Baremaps Proposal

[Julian Hyde]

When I mentor a project (as I have volunteered to do for Baremaps) I usually 
host a Zoom meeting with the initial contributors explaining what really goes 
on during Incubation. I totally agree that learning the Apache Way and making 
releases are key activities. I usually invite other stakeholders (e.g. 
contributors’ managers) because people have a lot of questions, and it helps to 
set people’s expectations correctly early on.

Julian


> On Sep 27, 2022, at 3:44 PM, Josh Fischer  wrote:
> 
> I think we should call out in the proposal of initial goals is learn the 
> apache way how to make releases within the foundation.  There is much to 
> learn in the incubating process. 
> 
> 
> 
> On Tue, Sep 27, 2022 at 12:22 PM Josh Fischer  > wrote:
> +1.  Happy to talk anytime. 
> 
> On Tue, Sep 27, 2022 at 11:29 AM Bertil Chapuis  > wrote:
> Hi Josh,
> 
> Glad you are interested in the project, I added you to the list of committers 
> in the proposal.
> 
> I hope to learn more about your Web mapping use cases soon.
> 
> Best,
> 
> Bertil
> 
> 
> 
> 
> > On 27 Sep 2022, at 04:03, Josh Fischer  > > wrote:
> > 
> > Hi Bertil,
> > 
> > I’d be happy to contribute if you’re interested.
> > 
> > - Josh
> > 
> > On Fri, Sep 16, 2022 at 8:25 AM Bertil Chapuis  > > wrote:
> > 
> >> Hello Everyone,
> >> 
> >> Here is a proposal for Baremaps, a toolkit and a set of infrastructure
> >> components for creating, publishing, and operating online maps. The
> >> proposal is published on the wiki [1] and a demonstration of our base map
> >> is available online [2].
> >> 
> >> The key challenge for Baremaps will be to create a sustainable community.
> >> We appreciate anyone who would be willing to support us with bug reports,
> >> code, mentoring or feedback.
> >> 
> >> [1] -
> >> https://cwiki.apache.org/confluence/display/INCUBATOR/Baremaps+Proposal 
> >> 
> >> [2] - https://demo.baremaps.com/ 
> >> 
> >> Best regards,
> >> 
> >> Bertil Chapuis
> >> 
> >> 
> >> 
> >> 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 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 

Re: [Discuss] Baremaps Proposal

[Josh Fischer]

I think we should call out in the proposal of initial goals is learn the
apache way how to make releases within the foundation.  There is much to
learn in the incubating process.



On Tue, Sep 27, 2022 at 12:22 PM Josh Fischer  wrote:

> +1.  Happy to talk anytime.
>
> On Tue, Sep 27, 2022 at 11:29 AM Bertil Chapuis 
> wrote:
>
>> Hi Josh,
>>
>> Glad you are interested in the project, I added you to the list of
>> committers in the proposal.
>>
>> I hope to learn more about your Web mapping use cases soon.
>>
>> Best,
>>
>> Bertil
>>
>>
>>
>>
>> > On 27 Sep 2022, at 04:03, Josh Fischer  wrote:
>> >
>> > Hi Bertil,
>> >
>> > I’d be happy to contribute if you’re interested.
>> >
>> > - Josh
>> >
>> > On Fri, Sep 16, 2022 at 8:25 AM Bertil Chapuis 
>> wrote:
>> >
>> >> Hello Everyone,
>> >>
>> >> Here is a proposal for Baremaps, a toolkit and a set of infrastructure
>> >> components for creating, publishing, and operating online maps. The
>> >> proposal is published on the wiki [1] and a demonstration of our base
>> map
>> >> is available online [2].
>> >>
>> >> The key challenge for Baremaps will be to create a sustainable
>> community.
>> >> We appreciate anyone who would be willing to support us with bug
>> reports,
>> >> code, mentoring or feedback.
>> >>
>> >> [1] -
>> >>
>> https://cwiki.apache.org/confluence/display/INCUBATOR/Baremaps+Proposal
>> >> [2] - https://demo.baremaps.com/
>> >>
>> >> Best regards,
>> >>
>> >> Bertil Chapuis
>> >>
>> >> 
>> >>
>> >> 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 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 

Re: [Discuss] Baremaps Proposal

[Josh Fischer]

+1.  Happy to talk anytime.

On Tue, Sep 27, 2022 at 11:29 AM Bertil Chapuis  wrote:

> Hi Josh,
>
> Glad you are interested in the project, I added you to the list of
> committers in the proposal.
>
> I hope to learn more about your Web mapping use cases soon.
>
> Best,
>
> Bertil
>
>
>
>
> > On 27 Sep 2022, at 04:03, Josh Fischer  wrote:
> >
> > Hi Bertil,
> >
> > I’d be happy to contribute if you’re interested.
> >
> > - Josh
> >
> > On Fri, Sep 16, 2022 at 8:25 AM Bertil Chapuis 
> wrote:
> >
> >> Hello Everyone,
> >>
> >> Here is a proposal for Baremaps, a toolkit and a set of infrastructure
> >> components for creating, publishing, and operating online maps. The
> >> proposal is published on the wiki [1] and a demonstration of our base
> map
> >> is available online [2].
> >>
> >> The key challenge for Baremaps will be to create a sustainable
> community.
> >> We appreciate anyone who would be willing to support us with bug
> reports,
> >> code, mentoring or feedback.
> >>
> >> [1] -
> >> https://cwiki.apache.org/confluence/display/INCUBATOR/Baremaps+Proposal
> >> [2] - https://demo.baremaps.com/
> >>
> >> Best regards,
> >>
> >> Bertil Chapuis
> >>
> >> 
> >>
> >> 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 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 

Re: possible interest in forming a community fork of akka

[Austin Bennett]

This seems needed given the state of Lightbend/licensing.  Agreed with
Roman's sentiment, though getting Lightbend to change at this point seems
unlikely [ also, I don't have direct contacts there so am not well
positioned to try to negotiate any changes ].  Glad to see people coming
together around this.  Notably, I imagine the Flink community will have an
interest in collaborating [ 1 ].  Happy to help the effort, however I can
be useful!

Cheers,
Austin


[1] https://flink.apache.org/news/2022/09/08/akka-license-change.html

On Tue, Sep 27, 2022 at 3:32 AM Claude Warren, Jr
 wrote:

> PJ,
>
> Several of us working on the mdedetrich github projects  [1] are preparing
> to submit a proposal to the incubator, hopefully by the end of the week.
> We have had contact from several individual devlopers, organizations,
> projects, and companies about such a project.  We identified a champion and
> several mentors, we would be happy to add you to our list of mentors.
>
> Claude
>
> [1] https://github.com/mdedetrich/akka-apache-project
>
> On Mon, Sep 26, 2022 at 7:11 PM PJ Fanning  wrote:
>
> > Hi everyone,
> >
> > Apologies if this is not the right mailing list. If it is not, please
> > let me know and I'll switch the thread to the right list.
> >
> > Lighbend [1], the company that maintains the popular open source
> > framework, Akka [2], recently announced they are moving Akka to a
> > non-OSS commercial license [3].
> >
> > There is interest in the OSS community in forking Akka under a new
> > name and maintaining it as an ASF project [4].
> >
> > It is early days yet but there is some discussion online [5].
> >
> > Reading the incubator cookbook, a new podling would need to have
> > champions and mentors from within the Incubator PMC [6].
> >
> > I would like to put my name forward for such a role, as an existing
> > ASF member [7].
> >
> > If anyone else in the Incubator PMC would like to get involved, that
> > would be great.
> >
> > Regards,
> > PJ
> >
> > [1] https://www.lightbend.com/
> > [2] https://akka.io/
> > [3] https://www.lightbend.com/akka/license-faq
> > [4] https://github.com/mdedetrich/akka-apache-project
> > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9
> > [6]
> >
> https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator
> > [7] https://whimsy.apache.org/roster/committer/fanningpj
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [Discuss] Baremaps Proposal

[Bertil Chapuis]

Hi Josh,

Glad you are interested in the project, I added you to the list of committers 
in the proposal.

I hope to learn more about your Web mapping use cases soon.

Best,

Bertil




> On 27 Sep 2022, at 04:03, Josh Fischer  wrote:
> 
> Hi Bertil,
> 
> I’d be happy to contribute if you’re interested.
> 
> - Josh
> 
> On Fri, Sep 16, 2022 at 8:25 AM Bertil Chapuis  wrote:
> 
>> Hello Everyone,
>> 
>> Here is a proposal for Baremaps, a toolkit and a set of infrastructure
>> components for creating, publishing, and operating online maps. The
>> proposal is published on the wiki [1] and a demonstration of our base map
>> is available online [2].
>> 
>> The key challenge for Baremaps will be to create a sustainable community.
>> We appreciate anyone who would be willing to support us with bug reports,
>> code, mentoring or feedback.
>> 
>> [1] -
>> https://cwiki.apache.org/confluence/display/INCUBATOR/Baremaps+Proposal
>> [2] - https://demo.baremaps.com/
>> 
>> Best regards,
>> 
>> Bertil Chapuis
>> 
>> 
>> 
>> 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 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 

Re: possible interest in forming a community fork of akka

[Claude Warren, Jr]

PJ,

Several of us working on the mdedetrich github projects  [1] are preparing
to submit a proposal to the incubator, hopefully by the end of the week.
We have had contact from several individual devlopers, organizations,
projects, and companies about such a project.  We identified a champion and
several mentors, we would be happy to add you to our list of mentors.

Claude

[1] https://github.com/mdedetrich/akka-apache-project

On Mon, Sep 26, 2022 at 7:11 PM PJ Fanning  wrote:

> Hi everyone,
>
> Apologies if this is not the right mailing list. If it is not, please
> let me know and I'll switch the thread to the right list.
>
> Lighbend [1], the company that maintains the popular open source
> framework, Akka [2], recently announced they are moving Akka to a
> non-OSS commercial license [3].
>
> There is interest in the OSS community in forking Akka under a new
> name and maintaining it as an ASF project [4].
>
> It is early days yet but there is some discussion online [5].
>
> Reading the incubator cookbook, a new podling would need to have
> champions and mentors from within the Incubator PMC [6].
>
> I would like to put my name forward for such a role, as an existing
> ASF member [7].
>
> If anyone else in the Incubator PMC would like to get involved, that
> would be great.
>
> Regards,
> PJ
>
> [1] https://www.lightbend.com/
> [2] https://akka.io/
> [3] https://www.lightbend.com/akka/license-faq
> [4] https://github.com/mdedetrich/akka-apache-project
> [5] https://github.com/mdedetrich/akka-apache-project/discussions/9
> [6]
> https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator
> [7] https://whimsy.apache.org/roster/committer/fanningpj
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: possible interest in forming a community fork of akka

[PJ Fanning]

Thanks Willem for taking the time to look into this.

The license change means the fork project will not be able to cherry
pick future fixes from Lightbend - at least not readily.

On a case by case basis, we could request that the PR submitter also
contribute them to the fork project.

In some cases, the critical fix might be submitted to the fork first
and it may be easier for the Lightbend team to cherry pick those cases
than it is for the fork team to do the opposite.

The real hope would be that the fork can attract a strong enough
community that any security issues can be fixed in house.

The core of Akka is quite stable at this point so hopefully critical
bugs should be rare. It's possible that some of the less used non-core
code might be more susceptible to having issues.

Links for recent security issues in Akka:
* https://doc.akka.io/docs/akka/current/security/index.html
* https://doc.akka.io/docs/akka-http/current/security.html


On Tue, 27 Sept 2022 at 02:30, Willem Jiang  wrote:
>
> After going through the FAQ of the Akka license,   it looks like we
> cannot backport the BSL codes to the Apache License branch.
>
> > If there is a newer version of the software under BSL, can I backport any 
> > of the code to an older, Open Source, version of Akka?
>
> > No. In this circumstance, you would either violate Lightbend’s copyright by 
> > re-releasing the code under Open Source, or you would violate the earlier 
> > Akka version’s Apache license by introducing incompatible BSL code (i.e., 
> > code subject to a use limitation not allowed by the Open Source Apache 2.0 
> > license).
>
> It will cause us a lot of effort to maintain the code, even if we just
> want to backport some critical bug fixes.
>
> [1]https://www.lightbend.com/akka/license-faq
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Sep 27, 2022 at 6:25 AM Ralph Goers  
> wrote:
> >
> > Before going too far with this I would be interested to know:
> > 1. Who the initial committers/PMC members would be.
> > 2. How much familiarity the proposed people already have with the code base.
> > 3. How diverse the community is from an employment point of view.
> >
> > In other words, I would be concerned if this is pushed by just 3 or 4 
> > people,
> > none of which have ever spent much time in the code, and who all work for
> > the same employer.
> >
> > Ralph
> >
> > > On Sep 26, 2022, at 11:11 AM, PJ Fanning  wrote:
> > >
> > > Hi everyone,
> > >
> > > Apologies if this is not the right mailing list. If it is not, please
> > > let me know and I'll switch the thread to the right list.
> > >
> > > Lighbend [1], the company that maintains the popular open source
> > > framework, Akka [2], recently announced they are moving Akka to a
> > > non-OSS commercial license [3].
> > >
> > > There is interest in the OSS community in forking Akka under a new
> > > name and maintaining it as an ASF project [4].
> > >
> > > It is early days yet but there is some discussion online [5].
> > >
> > > Reading the incubator cookbook, a new podling would need to have
> > > champions and mentors from within the Incubator PMC [6].
> > >
> > > I would like to put my name forward for such a role, as an existing
> > > ASF member [7].
> > >
> > > If anyone else in the Incubator PMC would like to get involved, that
> > > would be great.
> > >
> > > Regards,
> > > PJ
> > >
> > > [1] https://www.lightbend.com/
> > > [2] https://akka.io/
> > > [3] https://www.lightbend.com/akka/license-faq
> > > [4] https://github.com/mdedetrich/akka-apache-project
> > > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9
> > > [6] 
> > > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator
> > > [7] https://whimsy.apache.org/roster/committer/fanningpj
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: possible interest in forming a community fork of akka

[tison]

Hi PJ,

Thanks for driving this discussion!

As mentioned above, Lightbend switched the license from upstream and we
simply _cannot_ backport code from there any longer.

However, it's reasonable to me that we start a new project based on the
latest APL-2.0 licensed version (forked) to save users depending on Akka
open-source ecosystem to get further bugfixes and new features. Given that
there're a number of volunteers for this initiative, I believe it is worth
a try to revive the open-source project:

1. We need a new name here. IIUC "akka" will cause legal issues.
2. The aim of this project should be declared in the first place,
especially about new features and breaking changes. TrinoDB forked from
PrestoDB can be a good pioneer to learn from.

> "hostile forks"

The answer of the second question listed above should answer this question
also. My perspective is that the initial purpose of this project is to save
users depending on Akka open-source ecosystem and it's community driven.

> If anyone else in the Incubator PMC would like to get involved, that
> would be great.

The same as Roman :) Count me in. I'd like to be involved all the way in
this effort.

Best,
tison.


PJ Fanning  于2022年9月27日周二 17:39写道：

> Thanks Ralph for looking at this.
>
> It is early days but a number of people have expressed an interest in
> joining the new community.
>
> https://github.com/mdedetrich/akka-apache-project/discussions/3
>
> There are some former Lightbend employees and some very active
> contributors. Most of the people appear to have contributed to akka or
> to related projects.
>
> So far, it looks like quite a diverse group with no company or
> interest group having too great a say.
>
> There are other discussions, including ones about goals and release
> plans at https://github.com/mdedetrich/akka-apache-project/discussions
>
> On Mon, 26 Sept 2022 at 23:25, Ralph Goers 
> wrote:
> >
> > Before going too far with this I would be interested to know:
> > 1. Who the initial committers/PMC members would be.
> > 2. How much familiarity the proposed people already have with the code
> base.
> > 3. How diverse the community is from an employment point of view.
> >
> > In other words, I would be concerned if this is pushed by just 3 or 4
> people,
> > none of which have ever spent much time in the code, and who all work for
> > the same employer.
> >
> > Ralph
> >
> > > On Sep 26, 2022, at 11:11 AM, PJ Fanning  wrote:
> > >
> > > Hi everyone,
> > >
> > > Apologies if this is not the right mailing list. If it is not, please
> > > let me know and I'll switch the thread to the right list.
> > >
> > > Lighbend [1], the company that maintains the popular open source
> > > framework, Akka [2], recently announced they are moving Akka to a
> > > non-OSS commercial license [3].
> > >
> > > There is interest in the OSS community in forking Akka under a new
> > > name and maintaining it as an ASF project [4].
> > >
> > > It is early days yet but there is some discussion online [5].
> > >
> > > Reading the incubator cookbook, a new podling would need to have
> > > champions and mentors from within the Incubator PMC [6].
> > >
> > > I would like to put my name forward for such a role, as an existing
> > > ASF member [7].
> > >
> > > If anyone else in the Incubator PMC would like to get involved, that
> > > would be great.
> > >
> > > Regards,
> > > PJ
> > >
> > > [1] https://www.lightbend.com/
> > > [2] https://akka.io/
> > > [3] https://www.lightbend.com/akka/license-faq
> > > [4] https://github.com/mdedetrich/akka-apache-project
> > > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9
> > > [6]
> https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator
> > > [7] https://whimsy.apache.org/roster/committer/fanningpj
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> >
> > -
> > 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: possible interest in forming a community fork of akka

[PJ Fanning]

Thanks Ralph for looking at this.

It is early days but a number of people have expressed an interest in
joining the new community.

https://github.com/mdedetrich/akka-apache-project/discussions/3

There are some former Lightbend employees and some very active
contributors. Most of the people appear to have contributed to akka or
to related projects.

So far, it looks like quite a diverse group with no company or
interest group having too great a say.

There are other discussions, including ones about goals and release
plans at https://github.com/mdedetrich/akka-apache-project/discussions

On Mon, 26 Sept 2022 at 23:25, Ralph Goers  wrote:
>
> Before going too far with this I would be interested to know:
> 1. Who the initial committers/PMC members would be.
> 2. How much familiarity the proposed people already have with the code base.
> 3. How diverse the community is from an employment point of view.
>
> In other words, I would be concerned if this is pushed by just 3 or 4 people,
> none of which have ever spent much time in the code, and who all work for
> the same employer.
>
> Ralph
>
> > On Sep 26, 2022, at 11:11 AM, PJ Fanning  wrote:
> >
> > Hi everyone,
> >
> > Apologies if this is not the right mailing list. If it is not, please
> > let me know and I'll switch the thread to the right list.
> >
> > Lighbend [1], the company that maintains the popular open source
> > framework, Akka [2], recently announced they are moving Akka to a
> > non-OSS commercial license [3].
> >
> > There is interest in the OSS community in forking Akka under a new
> > name and maintaining it as an ASF project [4].
> >
> > It is early days yet but there is some discussion online [5].
> >
> > Reading the incubator cookbook, a new podling would need to have
> > champions and mentors from within the Incubator PMC [6].
> >
> > I would like to put my name forward for such a role, as an existing
> > ASF member [7].
> >
> > If anyone else in the Incubator PMC would like to get involved, that
> > would be great.
> >
> > Regards,
> > PJ
> >
> > [1] https://www.lightbend.com/
> > [2] https://akka.io/
> > [3] https://www.lightbend.com/akka/license-faq
> > [4] https://github.com/mdedetrich/akka-apache-project
> > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9
> > [6] 
> > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator
> > [7] https://whimsy.apache.org/roster/committer/fanningpj
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> 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: possible interest in forming a community fork of akka

[Roman Shaposhnik]

Hi PJ! Thanks for moving the discussion to this list! For
completeness' sake -- let me repeat the comments I made on the legal
one:

On Mon, Sep 26, 2022 at 9:12 PM PJ Fanning  wrote:
>
> Hi everyone,
>
> Apologies if this is not the right mailing list. If it is not, please
> let me know and I'll switch the thread to the right list.
>
> Lighbend [1], the company that maintains the popular open source
> framework, Akka [2], recently announced they are moving Akka to a
> non-OSS commercial license [3].
>
> There is interest in the OSS community in forking Akka under a new
> name and maintaining it as an ASF project [4].
>
> It is early days yet but there is some discussion online [5].

I would absolutely agree that there's clearly a need for a community
supported, neutrally governed version of Akka under the Apache License.
The real question is how can we make sure we've exhausted all the options
to work with the original maintainers to achieve that goal.

As you probably know, ASF doesn't look kindly on "hostile forks", but the
key word in that phrase is *hostile*. So let's try to avoid that (if we can).

So my question to you and everyone else on this list is: do you think we
can somehow steer the disussion (on the GitHub) to gauge the level of
interest of Lightbend (or individuals employed by it) to actually work *with*
ASF to try and see whether a win-win here is possible?

> Reading the incubator cookbook, a new podling would need to have
> champions and mentors from within the Incubator PMC [6].
>
> I would like to put my name forward for such a role, as an existing
> ASF member [7].

Same here! (*)

> If anyone else in the Incubator PMC would like to get involved, that
> would be great.

Count me in. I'd like to be involved all the way in this effort (regardless
of whether we build some win-win combo with existing Lightbend folks
or decide to do it with a new community).

Thanks,
Roman.

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

Re: [DISCUSS] Incubating Proposal for Datark

[Kaijie Chen]

Hi Yu,

Thanks for your explanation. Yes it makes sense.
It's nice we can see the migration process in the community.
And it will probably help create better docs for the project.

Best,
Kaijie

On 2022/09/27 06:05:10 Yu Li wrote:
> Hi BLAST and Kaijie,
> 
> Yes, we've done quite some work on merging the two rss projects (or more
> accurately, try to extract the high-level architecture and interfaces to
> form a more general framework) but still not fully completed. However, on
> second thought, we feel incubating the project first and involving more
> community forces to discuss and complete the work together might be a
> better idea. I believe more information on this topic will be shared in the
> community, and further discussion and the incubation process won't block
> each other. Wdyt?
> 
> @Gon
> Apache Nemo is an interesting project and we will further investigate and
> search for the cooperation between the two projects (smile).
> 
> Best Regards,
> Yu
> 
> 
> On Tue, 27 Sept 2022 at 10:45, Kaijie Chen  wrote:
> 
> > Hi Yu,
> >
> > You mentioned you will merge RemoteShuffleService and flink-remote-shuffle
> > previously in this thread:
> >
> > https://lists.apache.org/thread/1w74z5f0pb7bhslhzcl5x7rdj9s9objz
> >
> > > Our proposal is still not fully prepared because the merge of the two
> > projects
> > > is still in progress
> >
> > Have you done the merge? Or is there a plan to merge them later?
> > I just checked the github repositories, seems there is no mention of the
> > merge
> > and both project are still being actively developed.
> >
> > Best,
> > Kaijie
> >
> > -
> > 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 Datark

[tison]

Hi Gabriel,

Thanks for your explanation!

Best,
tison.


Gabriel Lee  于2022年9月27日周二 16:25写道：

> Hi Tison,
>
> Thanks for your curiosity.
>
> To be clear, as I know, RSS[1] was born in 2019 and has grown rapidly from
> then. RSS was open-sourced in Dec, 2021 [2]. But before this, RSS has
> already become a commercialized product on Alibaba Cloud EMR and attracts
> lots of attention from cloud customers. You can refer to [3] for more
> details if you want.
>
> Best,
> Gabriel
>
> [1] https://www.alibabacloud.com/help/en/e-mapreduce/latest/rss-new
> [2] https://github.com/alibaba/RemoteShuffleService
> [3] https://www.51cto.com/article/699346.html
>
> On Tue, 27 Sept 2022 at 15:45, tison  wrote:
>
> > Hi Gabriel,
> >
> > > Datark became a popular remote shuffle service in the past few years
> and
> > > I'm very glad to see it will be one of us soon.
> >
> > Out of curiosity, I can see the history of this project starts from Dec.
> > 2021. How can it be a popular solution for years?
> >
> > Best,
> > tison.
> >
> >
> > Yu Li  于2022年9月27日周二 14:05写道：
> >
> > > Hi BLAST and Kaijie,
> > >
> > > Yes, we've done quite some work on merging the two rss projects (or
> more
> > > accurately, try to extract the high-level architecture and interfaces
> to
> > > form a more general framework) but still not fully completed. However,
> on
> > > second thought, we feel incubating the project first and involving more
> > > community forces to discuss and complete the work together might be a
> > > better idea. I believe more information on this topic will be shared in
> > the
> > > community, and further discussion and the incubation process won't
> block
> > > each other. Wdyt?
> > >
> > > @Gon
> > > Apache Nemo is an interesting project and we will further investigate
> and
> > > search for the cooperation between the two projects (smile).
> > >
> > > Best Regards,
> > > Yu
> > >
> > >
> > > On Tue, 27 Sept 2022 at 10:45, Kaijie Chen  wrote:
> > >
> > > > Hi Yu,
> > > >
> > > > You mentioned you will merge RemoteShuffleService and
> > > flink-remote-shuffle
> > > > previously in this thread:
> > > >
> > > > https://lists.apache.org/thread/1w74z5f0pb7bhslhzcl5x7rdj9s9objz
> > > >
> > > > > Our proposal is still not fully prepared because the merge of the
> two
> > > > projects
> > > > > is still in progress
> > > >
> > > > Have you done the merge? Or is there a plan to merge them later?
> > > > I just checked the github repositories, seems there is no mention of
> > the
> > > > merge
> > > > and both project are still being actively developed.
> > > >
> > > > Best,
> > > > Kaijie
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Incubating Proposal for Datark

[Gabriel Lee]

Hi Tison,

Thanks for your curiosity.

To be clear, as I know, RSS[1] was born in 2019 and has grown rapidly from
then. RSS was open-sourced in Dec, 2021 [2]. But before this, RSS has
already become a commercialized product on Alibaba Cloud EMR and attracts
lots of attention from cloud customers. You can refer to [3] for more
details if you want.

Best,
Gabriel

[1] https://www.alibabacloud.com/help/en/e-mapreduce/latest/rss-new
[2] https://github.com/alibaba/RemoteShuffleService
[3] https://www.51cto.com/article/699346.html

On Tue, 27 Sept 2022 at 15:45, tison  wrote:

> Hi Gabriel,
>
> > Datark became a popular remote shuffle service in the past few years and
> > I'm very glad to see it will be one of us soon.
>
> Out of curiosity, I can see the history of this project starts from Dec.
> 2021. How can it be a popular solution for years?
>
> Best,
> tison.
>
>
> Yu Li  于2022年9月27日周二 14:05写道：
>
> > Hi BLAST and Kaijie,
> >
> > Yes, we've done quite some work on merging the two rss projects (or more
> > accurately, try to extract the high-level architecture and interfaces to
> > form a more general framework) but still not fully completed. However, on
> > second thought, we feel incubating the project first and involving more
> > community forces to discuss and complete the work together might be a
> > better idea. I believe more information on this topic will be shared in
> the
> > community, and further discussion and the incubation process won't block
> > each other. Wdyt?
> >
> > @Gon
> > Apache Nemo is an interesting project and we will further investigate and
> > search for the cooperation between the two projects (smile).
> >
> > Best Regards,
> > Yu
> >
> >
> > On Tue, 27 Sept 2022 at 10:45, Kaijie Chen  wrote:
> >
> > > Hi Yu,
> > >
> > > You mentioned you will merge RemoteShuffleService and
> > flink-remote-shuffle
> > > previously in this thread:
> > >
> > > https://lists.apache.org/thread/1w74z5f0pb7bhslhzcl5x7rdj9s9objz
> > >
> > > > Our proposal is still not fully prepared because the merge of the two
> > > projects
> > > > is still in progress
> > >
> > > Have you done the merge? Or is there a plan to merge them later?
> > > I just checked the github repositories, seems there is no mention of
> the
> > > merge
> > > and both project are still being actively developed.
> > >
> > > Best,
> > > Kaijie
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [DISCUSS] Incubating Proposal for Datark

[tison]

Hi Gabriel,

> Datark became a popular remote shuffle service in the past few years and
> I'm very glad to see it will be one of us soon.

Out of curiosity, I can see the history of this project starts from Dec.
2021. How can it be a popular solution for years?

Best,
tison.


Yu Li  于2022年9月27日周二 14:05写道：

> Hi BLAST and Kaijie,
>
> Yes, we've done quite some work on merging the two rss projects (or more
> accurately, try to extract the high-level architecture and interfaces to
> form a more general framework) but still not fully completed. However, on
> second thought, we feel incubating the project first and involving more
> community forces to discuss and complete the work together might be a
> better idea. I believe more information on this topic will be shared in the
> community, and further discussion and the incubation process won't block
> each other. Wdyt?
>
> @Gon
> Apache Nemo is an interesting project and we will further investigate and
> search for the cooperation between the two projects (smile).
>
> Best Regards,
> Yu
>
>
> On Tue, 27 Sept 2022 at 10:45, Kaijie Chen  wrote:
>
> > Hi Yu,
> >
> > You mentioned you will merge RemoteShuffleService and
> flink-remote-shuffle
> > previously in this thread:
> >
> > https://lists.apache.org/thread/1w74z5f0pb7bhslhzcl5x7rdj9s9objz
> >
> > > Our proposal is still not fully prepared because the merge of the two
> > projects
> > > is still in progress
> >
> > Have you done the merge? Or is there a plan to merge them later?
> > I just checked the github repositories, seems there is no mention of the
> > merge
> > and both project are still being actively developed.
> >
> > Best,
> > Kaijie
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] Incubating Proposal for Datark

[Yu Li]

Hi BLAST and Kaijie,

Yes, we've done quite some work on merging the two rss projects (or more
accurately, try to extract the high-level architecture and interfaces to
form a more general framework) but still not fully completed. However, on
second thought, we feel incubating the project first and involving more
community forces to discuss and complete the work together might be a
better idea. I believe more information on this topic will be shared in the
community, and further discussion and the incubation process won't block
each other. Wdyt?

@Gon
Apache Nemo is an interesting project and we will further investigate and
search for the cooperation between the two projects (smile).

Best Regards,
Yu


On Tue, 27 Sept 2022 at 10:45, Kaijie Chen  wrote:

> Hi Yu,
>
> You mentioned you will merge RemoteShuffleService and flink-remote-shuffle
> previously in this thread:
>
> https://lists.apache.org/thread/1w74z5f0pb7bhslhzcl5x7rdj9s9objz
>
> > Our proposal is still not fully prepared because the merge of the two
> projects
> > is still in progress
>
> Have you done the merge? Or is there a plan to merge them later?
> I just checked the github repositories, seems there is no mention of the
> merge
> and both project are still being actively developed.
>
> Best,
> Kaijie
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>