incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pratik Paranjape <>
Subject Re: Mailing Lists vs Wave
Date Thu, 30 May 2013 19:45:27 GMT

Then perhaps we should take it as our first use case both to showcase Wave
to others and to test how well we are doing. It will drive us towards most
of the functional goals we want to have in the end. Most engineers will
feel better if they know what the purpose of the building is and where it
is supposed to be placed.

On Fri, May 31, 2013 at 1:02 AM, Upayavira <> wrote:

> On Thu, May 30, 2013, at 08:28 PM, Pratik Paranjape wrote:
> > There can be a workaround at some point though.
> >
> > We can have discussions going on a Wave server for Wave project and make
> > sure that all messages are forwarded to this
> > mailing list as well. If someone responds here, we can have wave pull it
> > out and merge into wave discussion. Interesting
> > use case and fits with what we are trying accomplish.
> >
> > Realistically, its not going to be easy for a whole organization to
> > replace
> > its primary communication platform unless something
> > equally proven comes along.
> >
> > Another point will be: who reliably pays for the server once it has
> > traffic? In such places, like John mentioned, funding comes handy.
> The sorts of intermediates you mention would be the right kind of
> approach - maintaining the accessibility people currently appreciate
> with mailing lists, while providing another approach also.
> As to funding, while Apache doesn't pay people to develop software, it
> does have funds to cover server hardware, if a good case can be put
> forwards.
> If folks wanted a place to run a test wave server, for 'collective
> play', it wouldn't be too hard to arrange a VM for the purpose.
> Upayavira

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message