*Upayavira* * * Thanks for your explanation, the reasons you stated are extremely valid and important.
--- About *Upayavira *and *Pratik Paranjape *idea/suggestion of setting up a test project for this * * I can't help much in terms of servers and hard-code, but I can assist on UI design and, if needed?, promoting and helping discussions (the What is Wave? link that I shared before is an example of what we're doing) Would a Wiab like this http://waveinabox.net/<http://waveinabox.net/auth/signin?r=/> be enough or we would need to develop a different kind of client? http://alfredo.abambres.com *"Moving, always moving, and living inside movement". Rainer Maria Rilke* On Thu, May 30, 2013 at 8:45 PM, Pratik Paranjape <pratikparanj...@gmail.com > wrote: > Awesome! > > 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 <u...@odoko.co.uk> 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 > > >
