Re: SwellRT tech overview

Following up Upayavira, I will be very glad to help anyone wanting to start with SwellRT's source code. In this regard I suggest... a) invite you all to *join our Gitter chat *( https://gitter.im/P2Pvalue/swellrt) to reach me out and other SwellRT contributors, and ask directly doubts, just chat

Re: SwellRT tech overview

If we are doing things for SwellRTs benefit, it seems like it should all be upto Pablo to me. As the main developer of SwellRT he has the most to risk, and any requirements or prerequisites he feels necessary to mitage that risk he should specify and we should accommodate. I certainly don't want

Re: SwellRT tech overview

Upayavira, +1 We have a lot of folks (myself included) who are very interested in wave, but aren’t actively developing. We need to show the SwellRT folks that we have something to offer from a contribution standpoint (e.g. coding, design, documentation, etc.). If we can bring them some extra

Re: SwellRT tech overview

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

Re: SwellRT tech overview

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

Re: SwellRT tech overview

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

Re: SwellRT tech overview

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

Re: SwellRT tech overview

Thanks Adam for clarifying the questions. Also I agree with Upayavira, the primary discussion it might be more about "ideas" and the community's "engagement" with them. After that, tech aspects would come. So, in this regard I would like to share some thoughts about SwellRT as a product... a)

Re: SwellRT tech overview

I want to see a proposal regarding importing SwellRT that gives me confidence that bringing SwellRT into Wave will actually lead to an active project. A way this could be achieved *before* bringing SwellRT would be if everyone who is interested in contributing headed over to SwellRT, and started

Re: SwellRT tech overview

Pablo, a lot of great information in this slide deck. I hope others have a chance to review as well. Outstanding work. Price, very thoughtful responses. I agree with the overall conclusion - SwellRT should be brought into Wave. I like the idea of moving the SwellRT fork in to replace the

Re: SwellRT tech overview

Thanks for your answer Price, I guess we should not delay this discussion... I'd happy to run another call if you think it can move things forward. 2016-10-01 18:40 GMT+02:00 Price Clark : > Pablo, thanks for the presentation. > > While my qualifications to answer this

Re: SwellRT tech overview

Pablo, thanks for the presentation. While my qualifications to answer this are 0 getting to listen to Upayavira talk this week (the last Apache mentor if I'm not mistaken) make me feel the answers to 1 and 2 are easy to answer. 1.) Upayavira communicated very fervently that there just isn't