On Thu, Aug 1, 2013 at 1:48 AM, John Blossom wrote:
> Christian,
>
> Having borrowed most of this copy from the Cloud Stack
> guidelines,apparently they have a list specifically devoted to marketing.
> Seems like this might be a good move for Apache Wave so that developers can
> focus more on what
Christian,
Having borrowed most of this copy from the Cloud Stack
guidelines,apparently they have a list specifically devoted to marketing.
Seems like this might be a good move for Apache Wave so that developers can
focus more on what they want to without being annoyed. I've lived in both
worlds f
Joseph,
I agree that the fundamental issues that you raise are the key of how to
get development moving. "Mobile strategy" is there at this point simply to
say that whatever solutions that we have, they need to be able to work well
in a mobile environment. My own opinion is that Apache Wave needs
Maybe. We can expose a similar client<->server API despite changes to
the OT. If we're also changing the data type, that *will* effect the
client. (And those two changes can happen in parallel)
-J
On Wed, Jul 31, 2013 at 1:32 PM, Thomas Wrobel wrote:
> Question; Will changes in the OT (and thus
Question; Will changes in the OT (and thus server to server) effect
how clients communicate with the servers?
Is the intention for client<>server communication be similar to server<>server?
If not, I am just wondering if they are not tied together, then if
development can happen in parallel?
Bec
On Wed, Jul 31, 2013 at 10:04 PM, John Blossom wrote:
> Social Media guidelines are up, I made a few minor tweaks to bring the
> Cloud Stack template up to date.
>
> https://cwiki.apache.org/confluence/display/WAVE/Apache+Wave+Social+Media+Guidelines
This is very good!
I would add that PMC membe
I still want a technical deep-dive on OT at some point.
Issues:
- Are we building a platform or a product? (In my opinion our platform
isn't good enough, and thats where I want to focus our efforts for
now)
- What OT algorithms should we use?
- If we use Torben's OT system, how expensive is it act
On Wed, Jul 31, 2013 at 9:49 PM, John Blossom wrote:
> Yuri,
>
> I am fine with WaveWatchers being who we are, but WaveWatchers carries its
> own branding - if we're going to do things specific to Apache Wave as a
> community, then we should use that brand specifically, is my thinking. Most
> espe
Social Media guidelines are up, I made a few minor tweaks to bring the
Cloud Stack template up to date.
https://cwiki.apache.org/confluence/display/WAVE/Apache+Wave+Social+Media+Guidelines
On Wed, Jul 31, 2013 at 3:51 PM, John Blossom wrote:
> Ali,
>
> Great suggestion on guidelines, will post
Ali,
Great suggestion on guidelines, will post similar for us for review.
John
On Wed, Jul 31, 2013 at 2:32 PM, Ali Lown wrote:
> This seems like a good idea to me.
> As long as we keep multiple comitters as admins, I don't think there should
> be a problem.
>
> Could you first put together a
Yuri,
I am fine with WaveWatchers being who we are, but WaveWatchers carries its
own branding - if we're going to do things specific to Apache Wave as a
community, then we should use that brand specifically, is my thinking. Most
especially, when we do something good as a community, in Google+ I'd
Why not just use WaveWatcher's page?
On Wed, Jul 31, 2013 at 9:32 PM, Ali Lown wrote:
> This seems like a good idea to me.
> As long as we keep multiple comitters as admins, I don't think there should
> be a problem.
>
> Could you first put together a page of guidelines on the wiki? (Like
> Clo
This seems like a good idea to me.
As long as we keep multiple comitters as admins, I don't think there should
be a problem.
Could you first put together a page of guidelines on the wiki? (Like
CloudStack has:
https://cwiki.apache.org/CLOUDSTACK/social-media-guidelines.html)
Ali
On 31 Jul 2013 19
In conjunction with the Hangouts, I'd like to suggest that we create a Page
for Apache Wave on Google+ where announcements could be posted about
Hangouts and which, if desired, could have multiple personal accounts
authorized to manage the page. This would allow us to have stronger Apache
branding
Thanks to Alex North, Ali Lown, Bruno Gonzalez, Jérémy Naegel, and Joseph
Gentle for their active participation in our first Apache Wave team
hangout. We also saw Christian Grobmeier trying to connect briefly, and
some others are listed as having went, but that was the core group online.
You can vi
15 matches
Mail list logo
