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
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
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
10 matches
Mail list logo
