I am also a cheerleader of the project and given some more time I'm sure I could become a contributor to the codebase. I have experience with Android, GWT, frontend and backend JavaScript, Python, etc.
I also have ops and test automation experience so I am able to help with some of the less-loved aspects of the project lifecycle. On Tue, Aug 30, 2016, 7:56 AM Thomas Wrobel <darkfl...@gmail.com> wrote: > Once again, a small reminder; gwt+android developer willing to work > client side and dedicate time to it whenever/if there ever is > separation of client and server. > I dont hold out much hope though. Many times separation has come up > over the last 4(?) years, and despite consensus of it being a good > idea it seems to much work for the precious few that know the code > in/out to take on. Chicken and egg....sort of. > > I still massively cheerleading wave as its still a unique project. > There is no "myriad competitors" - useful bits and pieces here and > there,sure, but no one else even aspires to federation one day. Closed > bespoke systems tied to single servers are still dominating. In terms > of successful federation the web has email/smtp, it has irc > and...umm...not much else. > > -- > http://lostagain.nl <-- our company site. > http://fanficmaker.com <-- our, really,really, bad story generator. > > > On 30 August 2016 at 16:25, Upayavira <u...@odoko.co.uk> wrote: > > > > > > On Wed, 24 Aug 2016, at 06:16 AM, Bradley D. Thornton wrote: > >> > >> > >> On 8/23/2016 7:05 PM, Evan Hughes wrote: > >> > Hello all, > >> > > >> > Its that time of year again. Its nearing a year since retirement of > the > >> > project was brought up and it may be a good time to review the current > >> > situation. > >> > >> Well, not withstanding all the myriad competitors to this technology, > >> there are still operational sites linked to and functional from the > >> pages of this forum, and it appears that some development continues to > >> take place as well. > >> > >> Not to mention the fact that support for Wave is still needed, this list > >> providing that service (to some degree). > >> > >> So I think that although it may in fact be a stalled project, with very > >> little forward momentum or development, it is actually still quite > >> viable, and relevant, some commercial interests have also really done a > >> very nice, if not fully with a complete UI, job of deploying a unique > >> and good looking implementation. > > > > Bradley, > > > > The Apache Incubator is not necessarily going to be concerned with how > > useful or how used a technology is. The real question is whether the > > project is moving towards graduation from the incubator. The most > > noticeable aspect of this is the fact that we are *very* low on > > developers. The absolute minimum required by Apache would be three > > -people who know the code and would be willing to review a release and > > confirm that it both works, and meets the licensing rules specified by > > Apache. > > > > Unfortunately, the Wave project, despite all of its promise, does not > > appear to have managed to achieve that level of activity - despite > > numerous attempts to do so. > > > > If we do not hear anything convincing on this thread, I will, soon, > > start a vote of retirement. If there is insufficient response, that may, > > by itself, be sufficient for the Incubator PMC (project management > > committee) to retire the project. > > > > Note on retirement: This means that the community disolves as an > > *Apache* community. Whilst Apache retains rights to the name "Apache > > Wave", I cannot imagine anyone objecting to a "Wave" project being set > > up, e.g. on Github. So long as the terms of the Apache License V2 are > > honoured, it is quite acceptable for the project to continue elsewhere, > > where there is no particular expectation of activity level. > > > > Upayavira >
