On Thu, Dec 2, 2010 at 7:36 AM, Vega <[email protected]> wrote:

> 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.


Honestly, the "limitations" that you mention aren't exactly earth
shattering. As has been mentioned before there are ways to use hg and git
with svn as the storage backend. The mailing list discussion point issue
really isn't one until our "dog food" instance has the following:

Delta persistance
Group support


> Also, there's no need for hurry. We have
> more important goals to concentrate on right now.


One of the goals we need to concentrate on right now is starting the wave
community on the right foot. Development wise we are making huge strides,
however we need to ensure that the community will survive past the first
rush of enthusiasm. Apache has a great deal of experience in this area and
we'd be silly not to take advantage of it.


> Why spend a lot of
> time on moving to Apache infrastructure right now?


If not now, later. We're going to have to do it at some point, and now is as
good time as any.


> Why go with the
> mailing list while we can use the WIAB dog food instance?


See above for why the dog food instance just isn't ready.

Once it is, I don't see why we can't turn around to apache and say "here's a
new way of collaborating that's better than mailing lists".


> Why move to
> svn instead of mercurial?


It's what apache uses, as mentioned previously there are ways to use hg and
other scm systems with svn as the storage backend.


> Why Apache? is it the only alternative?
>

The only other alternative is to create our own wave foundation. This would
require a hell of a lot more work to setup and would require legal and
financial commitments from community members.


> Maybe Wave doesn't need the "Apache" prefix?


If it's going to be an Apache project then naturally it's going to carry the
Apache prefix. This will not stop anyone else from building services on top
of it, forking the project and renaming it and so on.


> How about the Wiab
> potential users? What are the consequences for them?
>

Absolutely none.

James

-- 
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.

Reply via email to