Ali,
I don't know off any concrete event. But I know for sure it is possible.
Basically, the project would need to find another set of
mentors/champion is it
needed to do with this incubation. I can imagine people may ask what is
the difference from the previous incubation trial.
A project can a
Christian,
This seems to be the age-old Wave problem.
Regarding your last comment, is there any precedent for a project
leaving Apache and returning at future point - it does seem like a
strange set of circumstances would be needed to trigger it?
Ali
On 23 March 2015 at 14:06, Christian Grobmei
Hi,
if Wave moves out this list, Jira etc will be read only, but available.
Same for the current source code.
I agree with 1: in the end Apache is a strong brand and also shows that
you can rely on a few things.
However at this point we know the benefits of Apache, but can this
project also fulf
> Also, is there a general repository for all the contributions that have
> been done so far from the Community?
More than git:
http://incubator.apache.org/wave/source-code.html
maybe the reviews:
https://reviews.apache.org/groups/wave/
El 17/03/15 a las 18:41, Yuri Z escribió:
> I agree that from the point of view of adding to the source/experimenting -
> there's no advantage to staying with Apache. However, there are other
> reasons.
> 1. Doing a release will signify that the code base is free of legal issues
> and thus encourag
Yuri,
Please know that there’d be no reason (as far as I am aware) that
current data would be removed from JIRA/Wiki/etc. It would simply be
marked read-only. I don’t know whether it’d be possible to add a
forwarding message to the top of such pages.
Upayavira
On Tue, Mar 17, 2015, at 05:41 PM,
I concur with Yuri.
One thing I would add is that a lot of knowledge is actually dispersed
in this mailing list.
It would not be bad to have a forum on which to engage at least a
mainstream part of the community.
Information would be searchable and more accessible.
Also, is there a general rep
I agree that from the point of view of adding to the source/experimenting -
there's no advantage to staying with Apache. However, there are other
reasons.
1. Doing a release will signify that the code base is free of legal issues
and thus encourage adoption of it by other parties, like wiab.pro,
co
Hi,
I guess this is my first post to this list, even though I am subscribed
for a year or so know and "following" the discussions here.
The technology in Wave seems quite amazing to me (in particular the
federation part, which hardly any commercial entity would add to their
product out of a busin
How can you retire something that is already dead? (*not kidding*)
How many years more will the "Apache Wave" community keep lurking around
instead of accepting the inevitable. Remove the elephant of the room, so
new things can arise, elsewhere.
Let Apache Wave burn once it for all... Let Wave mo
+1 to build a community is to help new developers start using the code, so
better documentation is needed. Also to make clear the options and benefits
for using Wave protocol.
Answering Thomas, the client-server communication of my forked Wave is
exactly the original, no changes in the protocol ar
Again as a new member of this list I surely act on a limited knowledge
of prior situations.
Still, I personally would not opt out of Apache.
Several reasons:
* building a community around Wave it's something you can take on both
on Apache or on Github, and nothing would actually forbid us to
To have demonstrated the community’s knowledge of how to make Apache
compatible releases, and to have shown a stable and sustainable
community.
These are the most important, regarding Wave.
As a community, we’ve sat back and waited - we’ve not really put any
effort into attracting new talent. Whe
What are the technical requirements for graduation?
On Mon, Mar 16, 2015 at 11:39 AM Vicente J. Ruiz Jurado
wrote:
> El 16/03/15 a las 08:35, Christian Grobmeier escribió:
> > I would like to highlight that retirement does not mean end of life.
> > There is a chance thing will get easier once o
El 16/03/15 a las 08:35, Christian Grobmeier escribió:
> I would like to highlight that retirement does not mean end of life.
> There is a chance thing will get easier once on GitHub. Don't
> forget, Apache is not only a great community, it's also a set of
> rules, frameworks, restrictions and so
Noob question: what does it take to get it to graduate?
On 3/16/2015 12:35 AM, Christian Grobmeier wrote:
I would like to highlight that retirement does not mean end of life.
There is a chance thing will get easier once on GitHub. Don't forget,
Apache is not only a great community, it's also a s
I would like to highlight that retirement does not mean end of life.
There is a chance thing will get easier once on GitHub. Don't forget,
Apache is not only a great community, it's also a set of rules,
frameworks, restrictions and so on. It's do-able for a bigger community.
But the Wave community
I think it is helpful that the wave standard be maintained by an
established organization like the Apache. Yes, other tools with wave-y
features, such as Google Docs, Rizzoma, and Slack, exist, but one of the
most exciting promises of Wave was the open protocol for real-time
communication and coll
Thanks for that I'll look into both your Javascript API and your Android
one.
Is your communication between client and server just between your forked
one or the "standard" wave server as well?
If your approach is functional and everyone could agree to use it I feel a
lot of progress could be made
I’d like to clarify a bit more my work during the last year and a half, as
I think it can respond to the needs that are being raised in this thread:
- Wave storage based on Database
- Server-Client separation
- Reduce code complexity or cover it up
- No dependency to GWT / Ability to b
"Splash is an old client but looked like it was quite split from the server
architecture.
What am I missing?"
That its almost certainly not compatible with the current Wave sever code.
Back when it was Google wave there was 4-5 clients, including prototype
mobile ones.
All died pretty soon after
All,
Just because Wave would be potentially retired as an apache incubator project,
does not mean that it is any more or less viable as an open source project. It
just means that the project is not right for the apache software foundation.
The code could be, will be, moved to a github reposit
I've been interested on Wave since almost one year, first as Kune
contributor and lately in a separated project trying to reuse Wave
technology in general way. I agree, the issue is the lack of separation
between server and client and other components, the handicap to develop on
top of Wave unless
Yuri suggested me in PVT some interesting open alternatives although I
think they would still lack the options that Wave has.
Just to name 2 of them:
share.js
rizzoma
of course they have different functions, but at least they would share
some Wave dna.
the point is that coding on top of those s
The problem is technology keeps marching on while the wave project has
remained mostly stagnant. I wanted to setup an internal wave server at
our company and try to get it adopted as the company standard for our
communications. I hate trying to manage email threads that get so long
and disjoi
Guys,
I'm a newbie too and we are thinking of building an entire app over wave.
It sounds really bat that the community is willing to give up.
On 3/15/2015 3:14 AM, ujadatron wrote:
It sounds bad.
I'm a "few days newbee" in this mailing list. (I'm looking for a
flexible open source collaborat
It sounds bad.
I'm a "few days newbee" in this mailing list. (I'm looking for a
flexible open source collaboration framework).
Do you suggest any of them? (if the Wave will retire)
thanks in advance
adatron
2015.03.14. 22:28 keltezéssel, James Keener írta:
I was going to write almost exactly
I was going to write almost exactly the same email and decided not to.
I found wave and wanted to use it, but it's dependence on the GWT and
how intertwined the Client and Server were made it very difficult for me
to understand and I moved to share.js because I could more easily
comprehend it's inn
I'll just sadly from my little lurker corner repeat what I have been saying
for 3 years or so now;
I wanted to work on a client, despite trying, I lacked the ability to
understand the server side code.
There was never a clear separation of client and sever that I feel would
have allowed less skill
he's dead jim ..
On Mar 14, 2015 9:56 PM, "Upayavira" wrote:
> Wave has been incubating for some years now, and, unfortunately, has not
> shown a level of growth that, in my opinion, would suggest that it is
> likely to reach graduation from the Incubator.
>
> Unfortunately, I think it is time w
30 matches
Mail list logo
