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 like it that people have the "+Apache Wave" link embeddable in their posts. It's a badge - and we need to promote that badge as a plus for developers, IMO. Both brands - WaveWatchers and Apache Wave - can help to amplify one another, but you need two equally promoted brands in order to do that.
John On Wed, Jul 31, 2013 at 2:34 PM, Yuri Z <vega...@gmail.com> wrote: > Why not just use WaveWatcher's page? > > > On Wed, Jul 31, 2013 at 9:32 PM, Ali Lown <a...@lown.me.uk> 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 > > CloudStack has: > > https://cwiki.apache.org/CLOUDSTACK/social-media-guidelines.html) > > > > Ali > > On 31 Jul 2013 19:26, "John Blossom" <jblos...@gmail.com> wrote: > > > > > 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 for Hangout events and would make it easier for us to enable > > > multiple people to act as hosts for the events. It would also enable > > people > > > to add links to our branded Page presence on Google+, which could help > to > > > promote participation in the community and to provide information about > > the > > > project and links to the official project Web site. > > > > > > Thoughts? It's very easy to set up, BTW. > > > > > > All the best, > > > > > > John Blossom > > > > > >
