[DISCUSS] Retire Wave

["John D. Ament" <jo...@apache.org>]

All,

Based on the on going discussions, I wanted to call a formal discussion to
retire the Wave podling.

Wave has been incubating for 7 years now.  In that period, you have
executed a couple of releases, but ultimately have not been able to sustain
a community around the project.  As I've mentioned in other emails,
retirement isn't a failure of a project.

I plan to leave this discussion open for a few days to resolve any open
items, followed by a vote here, then a vote on the incubator list.

John

Translate Wave to Kotlin or Go?

[Ali Nabavi <al...@alijnabavi.info>]

Are there any efforts to implement Wave in different programming languages,
specifically the more modern languages Kotlin or Go?  In my case, at least,
that would make me much more interested in investing in the project and I
think it might make the project a little shinier to people would be more
inclined to participate in its development.  I believe strongly in the
concept of Wave but for various reasons the Java generation of languages is
a deal-breaker at this point.

-Ali

On Mon, Dec 11, 2017 at 9:15 AM Michael MacFadden <
michael.macfadden@gmail.com> wrote:

> John,
>
> As a long-time lurker and initial contributor, I agree. The project has
> just not ever hit critical mass. There have been several dedicated
> induvial, there have been spurts of activity, and there is still much
> potential. However, the project just hasn’t been able to move toward
> graduation within the Apache eco-system. I would very much like to see
> development of wave continue in one form or another, but there is not much
> benefit to wave or the apache community by having it remain in incubation
> at this point. Hopefully Wave will can continue to evolve elsewhere.
>
> Of course, all of this is my own opinion.
>
> ~Michael
>
> On 12/9/17, 10:14 AM, "John D. Ament" <jo...@apache.org> wrote:
>
>     All,
>
>     Based on the on going discussions, I wanted to call a formal
> discussion to
>     retire the Wave podling.
>
>     Wave has been incubating for 7 years now.  In that period, you have
>     executed a couple of releases, but ultimately have not been able to
> sustain
>     a community around the project.  As I've mentioned in other emails,
>     retirement isn't a failure of a project.
>
>     I plan to leave this discussion open for a few days to resolve any open
>     items, followed by a vote here, then a vote on the incubator list.
>
>     John
>
>
>
>

Re: [DISCUSS] Retire Wave

[Michael MacFadden <mi...@gmail.com>]

John,

As a long-time lurker and initial contributor, I agree. The project has just not ever hit critical mass. There have been several dedicated induvial, there have been spurts of activity, and there is still much potential. However, the project just hasn’t been able to move toward graduation within the Apache eco-system. I would very much like to see development of wave continue in one form or another, but there is not much benefit to wave or the apache community by having it remain in incubation at this point. Hopefully Wave will can continue to evolve elsewhere.

Of course, all of this is my own opinion.

~Michael

On 12/9/17, 10:14 AM, "John D. Ament" <jo...@apache.org> wrote:

    All,
    
    Based on the on going discussions, I wanted to call a formal discussion to
    retire the Wave podling.
    
    Wave has been incubating for 7 years now.  In that period, you have
    executed a couple of releases, but ultimately have not been able to sustain
    a community around the project.  As I've mentioned in other emails,
    retirement isn't a failure of a project.
    
    I plan to leave this discussion open for a few days to resolve any open
    items, followed by a vote here, then a vote on the incubator list.
    
    John