Let me see if I can figure this out.

On Sun, Jan 13, 2013 at 10:42 AM, Zachary “Gamer_Z.” Yaro
<[email protected]>wrote:

> Bumping this now that we are past the holidays.  Are any Gwave team members
> here who would be able to answer my question?
>
>
> —Zachary “Gamer_Z.” Yaro
>
>
> On 26 December 2012 06:08, Thomas Wrobel <[email protected]> wrote:
>
> > I can only say this is a fantastic idea.
> > Wave, at its heart, is a protocol - and to be successful it not only
> needs
> > a flagships implementation, but also the resources and information in a
> > convenient form to help it spread.
> >
> > I'd suggest the site by structured with the easiest possible paths to
> > getting a wave server running as the forefront, with supplementary
> > information about various other options and extensions later.
> > Possibly also a list of current running wave servers (even if its just a
> > embedded google doc manually updated). It would be useful to have that
> info
> > up for people to test federation against eventually, or when its finally
> > possible to make standalone clients people can test them against existing
> > servers to ensure compatibility.
> >
> > And yes, Id hope google can be kind enough to give up that domain.
> >
> > On 26 December 2012 09:18, Zachary “Gamer_Z.” Yaro <[email protected]>
> > wrote:
> >
> > > I was thinking it would be nice to have a central user-focused site
> about
> > > wave that could introduce new users to wave and educate them about
> > > different wave services, extensions, federation, etc.
> > >
> > > Question though: I noticed wave.org is currently owned by Google.  To
> > the
> > > former Gwave team members here, since Google is no longer pursuing
> Wave,
> > > would it be possible to give other wave developers control of the
> domain?
> > >
> > > Any comments?  I also posted about this on the +Wavers
> > > community<
> > https://plus.google.com/114745581771396366390/posts/NDqSSeideJy>
> > > if
> > > you would prefer to respond there.
> > >
> > > —Zachary “Gamer_Z.” Yaro
> > >
> >
>

Reply via email to