Hi Anthony,
Thanks for summarizing the thread. I am anxious to hear what Google
says to that.
Cheers,
Andrus
On Aug 6, 2010, at 6:42 PM, antwatkins wrote:
Great discussions. As expected the comments have ranged wide and far,
so I’m putting a summary below. I will update the wave (https://
wave.google.com/wave/waveref/googlewave.com/w+Q_-a_E3kB ) in a more
organized manner than a single forum thread can accomplish (with
attribution to the various authors), but I encourage people to
continue to post any idea here that contributes to how we move
forward. Think of the Wave as a summary of this thread for now or a
place you can carry on a threaded conversation around a specific
topic.
Of course a major element absent this discussion is the commitment
Google will provide, if they will donate the code, or the mode of
operation they see from this point. At the very least I think we have
shown we have a vibrant community capable and ready to ensure the
continuation of the principles and code forwarded by the Wave
technology. Hopefully this will influence the decisions Google makes
within the coming days/weeks and encourage them to continue to release
code and dedicate resources to this effort.
Summary of Thread so Far
How Community and Google can continue this effort
- Google donates code to a Foundation (like Apache or one we start)
who has responsibility for specs and protocols [James Purser, Douglas
Linder, David Butler, Andrus ?]
- Contact companies and organizations that have vested resources in
this tech like Novell, SAP, Pygowave, Ruby on Sails, Process One
[James Purser, Thomas Wrobel]
- Establish a forum or area for people currently work on WFP servers
to foster collaboration [Thomas Wrobel]
- Establish a consortium to pool resources and make recommendations
for protocols and way forward [Anthony Watkins]
How to garner more participation
- create sandbox environment for contributions that have yet or will
not make it through official review [Anthony Watkins]
- focus on federation (as soon as there are a few clients, servers,
and GUIs communicating on standard power of WFP will come across)
[Thomas Wrobel]
- reduce dependency on OT as a requirement to federate [Ian Roughley,
Christopher Harvey]
- promote a summer of code centered around wave with small (but not
insignificant) funding to students and research groups [Douglas
Linder]
- Use Apache since they have the advantage of good exposure and org
structure installs confidence. [David Butler]
- focus on developing domain specific application, even without
Federation in a first step [Andreas ?]
Suggestions for the Code
- combine/link wave data api and FedOne [Anthony Watkins]
- slick client like Splash [Anthony Watkins]
- need fully featured non-buggy editor that is available to all of
community off-the-self [Ian Roughley]
- slightly different protocol that allows for federation of existing
non-real-time content as well as real-time content and federating any
type of content (avoiding need for significant code changes of
existing infrastructure) [Ian Roughley]
- use Git or GoogleCode or Mecurial [Brett Morgan, James Purser,
Joseph Gentle, Brian May]
- Add abstraction layer over the OT stack allowing for OT on different
data types [Joseph Gentle
- look at TP2 or TTF[1] [Joseph Gentle]
--
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.
