I agree that spec and implementation should be "independent" eventually.
There are two more practical things worth considering IMHO: a) If specs are not part of the Apache project, we need to define our own governance rules or copy them which will cost time and effort b) There is a risk that specs and implementation differ too much because the communities are too disjoint. >From a practical perspective I would like to keep the specs together with WiaB for some time. Right now this will save us some additional overhead and it keeps the community together. WiaB could decide to check every 6 months whether time has come to spin off the specs in their own project. Finally, editing a spec in a Wiki is a no go. I would like to see a changes list to understand what happens to the protocol specs. Greetings Torben 2010/11/20 Chris Harvey <[email protected]> > Keeping two sites: Wave Protocol and RI development makes sense to me. > > Count me in to the protocol working group > > -- > Chris > iotawave.org > Singapore > > -- > 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]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > -- --------------------------- Prof. Torben Weis Universitaet Duisburg-Essen [email protected] -- 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.
