I can totally understand projects like Wave-VS or ARWave having little interest in WiaB, as what they want to achieve using the Wave protocol is totally diffrent from the "classical" Wave usages. I'm concerned of loosing contributors *if/when* the split doesn't occur or doesn't occur soon enough...
I think having so different Wave Protocol utilizations is a huge strength for the long-term expansion of the Protocol. As the recent discussion about ProcessOne illustrated, Protocol-only interested projects need a place to feel at home... If it suits Apache rules better, what about a wave-*protocol*@ incubator.apache.org mailing list ? Are the Apache mailing-list limited to dev / user / commits ? 2011/1/31 Alex North <[email protected]> > Yes, for sure. For now I do believe it's important to have everyone talking > in the one place, and our adoption by Apache requires that to be wave-dev, > but I agree the group may become a home for protocol-only discussion > if/when > we make such a split. > > On 30 January 2011 14:54, Michael MacFadden <[email protected] > >wrote: > > > We may indeed want to open the wav protocol google group again after we > get > > organized around protocol and WiaB separation. > > > > > > On Jan 19, 2011, at 2:42 PM, Alex North wrote: > > > > > Hi all, > > > > > > I've flipped the moderation bit on the > [email protected]. > > > It's now obsolete (or at least dormant). Please carry on wave > development > > > discussion on the [email protected] mailing list. > > > > > > The [email protected] list remains active, > and > > > will do so until we move our code to Apache's SVN and code review > tools. > > > > > > The archives will remain accessible online. In addition, it's possible > > we'll > > > resurrect this group at some point when protocol development is > separated > > > from WIAB application development. > > > > > > Alex > > > > >
