I am sorry I didn't make the meeting, glade to see it was productive.
However, I am curious though why there is questions still as to if
SwellRT should be merged with wave.
Wave development at apache is nearly dead.
Doing nothing and it will have to retire. No one has proposed a 3rd
option that I
My concern is not for Wave, it is for SwellRT. The last thing I'd want
is them (I don't know how many of them there are) to move over to
Apache, only to find out that the match with Apache isn't sufficient,
and Wave closes down anyway. I want to be sure we can avoid that
eventuality, and the best w
Sorry to have missed you, Thomas.
"Cant a date be set, a vote be taken, then either import SwellRT or not?"
According to Upayavira there should be a proposal.
This is what I've found: http://incubator.apache.org/guides/proposal.html
Although this seems more targeted to new projects.
So the proce
I'm suggesting that before we go to the proposal phase, people just
start participating in SwellRT. Just do it. Let's see what you can all
accomplish over there - let SwellRT see what they have to gain, and let
Apache see how more vibrant and active SwellRT is as a community. Then
it will be a no-b
