I am not against joining. But it seems to me that the decision is enthusiastic, however, all benefits are somewhat potential, while limitations are immediate. Also, there's no need for hurry. We have more important goals to concentrate on right now. Why spend a lot of time on moving to Apache infrastructure right now? Why go with the mailing list while we can use the WIAB dog food instance? Why move to svn instead of mercurial? Why Apache? is it the only alternative? Maybe Wave doesn't need the "Apache" prefix? How about the Wiab potential users? What are the consequences for them? I am sorry I sound negative, but it seems to me that everybody are happy to find a new home, while no one wants to evaluate the risks.
On Dec 1, 9:13 pm, Ian Roughley <[email protected]> wrote: > On 12/01/2010 01:50 PM, Vega wrote: > > > The wave team has a very demanding goal - to have a functional version > > working out out the box - as soon as possible, and it seems to me that > > working on joining Apache now, only distracts us from working toward > > reaching the main goal. > > What do you mean by wave team? As I understand it, officially there is none, > or after Dec/Jan will > be no official time for Googlers to be spend on WiAB. > > And even if they did finish getting a stand alone version, this is a RI that > needs a lot of work. > > By joining Apache, we have a community and process for others to join the > team and help out and to > progress the project. Building up the contributors to the project is a very > important goal, as is > having a name that people trust when they go to use open source. > > /Ian -- 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.
