I was closely following the discussion regarding wave in a box product joining Apache. However, I couldn't see any real benefits to join besides having "Apache" before the "Wave". I guess the "pros and cons" discussions were held at the summit, but I couldn't access them. I am not against the move, it's just I am not sure I understand the consequences and the price. So 1. What are potential benefits? Are there things that Apache can provide that will make the work of wane in a box developers easier? 2. What are possible risks? I guess everything comes at price and joining Apache will impose certain restrictions. What are them? 3. Are there some alternatives? Maybe there are better ways to achieve the same goal.
Thanks -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
