The links to Apache Wave resources in this message are largely broken, as
well as some key ones at the Apache project site.
Thanks, Dan, I think that the other links were due to a temporary router
issue on my end, I see the same state you do now. Looking forward to the
provisioning of the new page on the Apache site.
e for more full-blown implementation and
propagation.
Thanks!
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Thu, May 23, 2013 at 4:33 PM, Justin Beals wrote:
> Hi all,
>
> I've been lurking on this list for a little bit and am really glad to see
> some activity. I th
.
Presumed goodwill should be the order of the day for everyone in this
process.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Sat, May 25, 2013 at 4:17 AM, Christian Grobmeier wrote:
> Hello John,
>
> On Thu, May 2
interested, but I want to make sure that this
particular thread stays vital to develop a broader consensus on how to
proceed within the Apache community.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Sat, May 25, 2013 at 9:11
uld, also.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Sat, May 25, 2013 at 10:18 AM, Pratik Paranjape <
pratikparanj...@gmail.com> wrote:
> I had studied this point a while back, and for all practical purposes,
omplement and amplify the Apache
community's efforts. We have much to learn from all of you and look forward
to building one big, beautiful and amazing Wave.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Sat, May 25, 2013
forward with the protocol via the Apache community, which I am sure
will welcome additional contributors.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Sat, May 25, 2013 at 4:40 PM, Michael MacFadden <
michael.mac
Angus,
Thanks so much to you and Michael, I appreciate your help with this
transition. I am tapping on some requirements specs, when it's appropriate
I would love to share them with this community.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+:
also be welcome. Thank you for
your kind attention. I look forward to what you may have as thoughts
regarding the future of Wave in response to this presentation.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
I'd like the Apache community to comment for now but I appreciate the
sentiment. Best, J
On May 28, 2013 5:24 PM, "Alain Levesque" wrote:
> The slide deck should be extended to public. Bravo John
>
>
> On Tue, May 28, 2013 at 4:21 PM, John Blossom wrote:
>
> &
g forward to additional input, let's keep the discussion moving.
Thanks.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Tue, May 28, 2013 at 6:04 PM, Upayavira wrote:
> John,
>
> You've made some large scale
how
that might be able to be realized for Wave. Its conversational data model
and potential for independent data ownership across multiple UIs and apps
should be right in the thick of everything that's happening in the cloud
and in the mobile Web.
Thank you again, I look forward to continuing the conversation.
Best,
John Blossom
>
> Ali
>
to Apache servers, I am not sure exactly where this all stands. Who
might be the best person to engage on these sorts of questions?
John
On Tue, May 28, 2013 at 8:23 PM, John Blossom wrote:
> Thank you, Ali, for your thoughtful comments. I have some responses below
> (which would loo
to address the huge
opportunities that those requirements present.
Thanks,
John
On Tue, May 28, 2013 at 9:54 PM, Dave wrote:
> John,
>
> I'm not a committer, but I have some familiarity with the wave stack.
>
>
> On 29/05/13 01:23, John Blossom wrote:
>
>> People need t
ceiving seem to confirm where the
> >architecture needs to adapt to modern requirements and performance
> >expectations. Hopefully we can all work together to address the huge
> >opportunities that those requirements present.
> >
> >Thanks,
> >
> >John
> >
>
_client_ (supporting off-line access etc.) doesn't exist
> yet.
>
> Over the years there have been a few discussions about formalising the
> client/server protocols within wiab - but so far there hasn't been the
> manpower to implement it.
>
>
> Dave
>
>
>
Bruno,
Thanks so much for sharing your experience. No doubt there is someone who
has succeeded with federation and uses it, but I cannot think of anyone
offhand. The existing commercially oriented products don't use it, AFAIK.
Especially if some form of federation powers peer-to-peer mobile sharin
rojects best interests. Again
> > if
> > >> we have a roadmap and people who feel strongly about working on those
> > >> areas, we can divide and concours.
> > >
> > >
> > >
> > > Thanks for acknowledging
> > > this
> &g
ebase is largely a proof of concept. It has some
> > > >> potential, but I think most of us would agree that some time spent
> > > >> re-architecting how we want things to work and morphing the code
> base
> > > into
> > > >> that (or rewriti
ill use the lib. This gives client developers a lot more
> options.
>
> The only downside would be ports would be need to be made for Native
> clients. But thats pretty unavoidable whatever we do.
>
>
>
> On 29 May 2013 16:59, John Blossom wrote:
>
> > Thomas,
> &
t be made in
> > Javascript.
> > GWT clients would have to make a wrapper for it (but this is a easy
> task),
> > meanwhile by having the library j/s means people not wanting to use GWT
> for
> > web apps can still use the lib. This gives client developers a lot more
> &
e:
> On Wed, May 29, 2013, at 05:06 PM, John Blossom wrote:
> > Michael,
> >
> > Sounds like we're all starting to sync up on this bit by bit. The
> > SMTP/IMAP
> > analogy is correct, though with different services, of course.
> >
> > I am certai
ogether to make it happen. If I can be of service to this
effort, that is good.
Best,
John
On Wed, May 29, 2013 at 2:24 PM, Upayavira wrote:
>
>
> On Wed, May 29, 2013, at 07:04 PM, John Blossom wrote:
> > Upayavira,
> >
> > You raise a very interesting point with Op
Thanks very much, Ali, this is very interesting information. It would seem
to be very important for being able to communicate clearly to people about
Apache Wave's management that it is completely free of all potential
encumbrances from Google. Otherwise, that may set up a negative psychology
in po
Hello,
Looking through some documentation on Wave-derived products, I am seeing
that there is some good use of Node.JS coding for server-side functions.
Why would it not be appropriate to replace some or all of the demo-model
code from Google on the server side with a light and powerful language s
27;s a part of the ASF spirit, I know. But I don't want
success by accident. I want success by design.
So yes, we need committers. For what?
Solve for x.
Thanks,
John Blossom
On May 30, 2013 5:55 AM, "Christian Grobmeier" wrote:
> On Thu, May 30, 2013 at 9:09 AM, Bruno
like renaming packages and module structure and there was
> little to no feedback from the community. This was more than enough for (at
> least) me to think there was no common interest in what me and Michael were
> doing and therefore I stopped.
>
> > Perhaps
> > then we re
sayin'.
John
All the best,
John Blossom
On Thu, May 30, 2013 at 1:08 PM, Thomas Wrobel wrote:
> Is there any suggested way to organize volunteers?
>
> I know the current method is basically a "todo" list isnt it? which is fine
> in itself.
> But possibly havin
email server with Wave for
collaborative communications whilst synchronising with those who are still
on email servers and b) I don't have to duplicate data sets to get more
value - I just use different components of a given wave, sometimes with
other UIs.
All the best,
John Blossom
On Thu, May 3
,
John Blossom
Today's Web is changing like it never has before. More than a billion
people use it today and a billion more will be using it in just a few years
- mostly on mobile devices. Those Web users will live in a world that is
being transformed by the mobile Web. Trillions of sensors
Thomas, That certainly seems like the right paradigm. J
On Fri, May 31, 2013 at 8:23 AM, Thomas Wrobel wrote:
> At the moment, I think so yes. I dont think its possible to communicate
> directly with any arbitrary Wave server like you can with a email server.
>
> I think, untill we have that cli
June and will be recorded on YouTube. Event link:
https://plus.google.com/events/cboctmpnt5503f0km2b0s5iritk
It would be great if committers who participated in this release could join
in the discussion so that we can all celebrate this milestone and the
future of Wave.
Thanks!
John Blossom
Hi,
Just reminding folks of our On-Air Hangout tomorrow, if you have some time
please join us for the discussion, event page at:
https://plus.google.com/events/cboctmpnt5503f0km2b0s5iritk
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com
That does seem to be the one that's referenced in the rights page. I am not
sure where they stand in clarifying the rights ownership transfer with
Google, but either way it seems to be the right one.
All the best,
John Blossom
at 6:20 AM, Yuri Z wrote:
> Yep, I think we have rights
en a legal document
> should be in someone's archive.
>
> Wave On.
>
> http://alfredo.abambres.com
>
> *"Moving, always moving, and living inside movement". Rainer Maria Rilke*
>
>
> On Tue, Jun 4, 2013 at 12:10 PM, John Blossom wrote:
>
> >
How about platform@ ?
On Jun 5, 2013 4:59 PM, "Upayavira" wrote:
> Except, this isn't for users of WIAB, it is for general discussion about
> Wave, so user@ doesn't really fit. There are other general@ lists, so
> there's precedence there.
>
> The other issue though, is that mailing lists work wh
ld personally love to
> see/hear
> >> > tomorrow:
> >> > Besides Christian, I think Upayavira, Ali Lown (the person leading the
> >> > release of 0.4 version) and Yuri Zelikov (the only maintainer I know
> of
> >> a *sort
> >> > of* publ
t; can do with it. It is important to recognise that logos are kind of a
> special case in open source.
>
> Upayavira
>
> On Wed, Jun 5, 2013, at 02:23 PM, John Blossom wrote:
> > Copyright is claimed for the logo by Google but the word Wave is too
> > generic and u
t dozens of e-mails just because of logo stuff
> > and such, no matter how important the subject is. And yes, I can use
> > filters, but still they're not perfect and are PITA to maintain.
> >
> > PP
> >
> > On Jun 6, 2013, at 1:58 PM, "John Blossom - Sh
Not sure what needs to be done but let me know if I can help. J
On Jun 8, 2013 3:02 AM, "Christian Grobmeier" wrote:
> Hello,
>
> please see below - changing the subject for better visibility.
>
> Cheers
> Christian
>
>
> -- Forwarded message --
> From: Upayavira
> Date: Sat, Jun
Looks like this was covered, sorry for the delay. I understand the
procedure, now.
Thanks,
John
On Sat, Jun 8, 2013 at 3:01 AM, Christian Grobmeier wrote:
> Hello,
>
> please see below - changing the subject for better visibility.
>
> Cheers
> Christian
>
>
> -- Forwarded message --
we have the core of a community that can help
us to move in that direction. I will weigh in on the "how" from time to
time, but overall I am most interested in the "x" - it's your solution.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: h
micro-optimizations and obfuscation which practically,
> manually can't be done
>
> 2) Except for Webworkers, everything in HTML5 can be used in GWT. I am
> using it, I am sure others are using them too. Even webworkers are usable,
> but its not as straightforward.
>
>
>
I agree, Joseph, just trying to give you a target to shoot at. I am here to
help you gain a market, and hopefully your decisions are market-worthy.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Wed, Jun 12, 2013 at 4:08 PM
this thread. I hope
that this energy can be channeled towards maximum market impact. I don't
want Wave to be just great - I want it to rock the world, top to bottom.
All the best,
John Blossom
On Wed, Jun 12, 2013 at 3:48 PM, Michael MacFadden <
michael.macfad...@gmail.com> wrote:
>
Github+Apache+Wave=awesomeness.
John
On Thu, Jun 13, 2013 at 11:56 AM, Scott Wilson <
scott.bradley.wil...@gmail.com> wrote:
>
> On 12 Jun 2013, at 22:08, Upayavira wrote:
>
> > All I can say is, "well said". We need to consider Wave as a young
> > project - one that really doesn't yet have anyt
own
right, having at least a mirror of the code in that environment certainly
can't hurt.
All the best,
John Blossom
On Fri, Jun 14, 2013 at 4:17 AM, Christian Grobmeier wrote:
> On Fri, Jun 14, 2013 at 3:27 AM, John Blossom wrote:
> > Github+Apache+Wave=awesomeness.
> >
&g
Michael, Joseph,
I am reading this part of the thread with great interest. It sounds as is
the OT paradigms that you and Joseph are suggesting might support different
types of formats for different messages/blips within a common
document/wavelet. That would seem to be an important objective,
poten
Christian,
You're preaching to the choir. I understand clearly.
John
On Fri, Jun 14, 2013 at 2:48 PM, Christian Grobmeier wrote:
> On Fri, Jun 14, 2013 at 4:46 PM, John Blossom wrote:
> > Christian,
> >
> > I leave it up to the developers to make those decisions. W
Sounds like a good idea to have multiple experiments moving forward. Lots
of great ideas floating around now that are worth trying out. Fast-fail is
the order of the day for the moment, which should allow us to decide things
such as what goes on which side of the API, etc. John
On Fri, Jun 14, 201
Christian,
Thanks for clarifying this. One of the factors which I hope that the
developers new to Apache consider is that just because one calls their
product open source does not mean that you have the resources to manage an
open source program in a way that will lead to successful product
implem
s, it's a sub-project that may help to attract more developers
to Wave technologies.
All the best,
John Blossom
does this, but i kept
> going back to wave because it was actually more responsive, featurefull,
> and actually crashed less.
>
>
>
>
> On Sat, Jun 15, 2013 at 9:29 AM, John Blossom wrote:
>
> > I had the down-the-road thought just now that I wanted to put into
> >
o a front facing page to share with people
> >>who
> >> > didnt feel like registering on my wave server.
> >> >
> >> > an openoffice for wave would be extremely usefull, and could have an
> >> > extremely large impact imo. wave is also already
Thanks, Rob, it seems that this opens up interesting doors for
down-the-road variants of OpenOffice based on Wave editing models and data
models. The challenge and the opportunity is that Wave's OT model acts on
the body of a document, so conversations and collaborations can become the
body of a mo
:
> > Totally agree with all, we need to get better and do more to just became
> > bigger and better.
> >
> >
> > 2013/6/15 John Blossom
> >
> >> Christian,
> >>
> >> Thanks for clarifying this. One of the factors which I hope that the
ve is not necessarily the same in terms of data models.
All the best,
John Blossom
On Sun, Jun 16, 2013 at 6:50 PM, Rob Weir wrote:
> Adding Svante Schubert to the thread, from the ODF Toolkit project.
> He also chairs the subcommittee at OASIS that has been looking at OT
> for change t
ick a number. John
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Sun, Jun 16, 2013 at 8:15 PM, Joseph Gentle wrote:
> Sounds interesting. Where is this going to be held? It might be
> interesting for a few people o
lusive.
> Therefore, please use them with restraint, and keep as much discussion,
> and all decisions, here on the list.
>
> Thanks! Upayavira
>
> On Mon, Jun 17, 2013, at 01:37 PM, John Blossom - Shore Communications
> Inc. wrote:
> > In-person would be great. I am NYC/Bo
>>> wrote:
> > > > >>>
> > > > >>>> @Fleeky, Yuri actually added some
> > > > >>>> code<
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > &g
Thanks for the diagram, Dave, it helps me to visualize Wave's components.
How much is the "wave bus" a reality as opposed to a potential division in
programming? That is, in terms of how one binds/opens the bus, does it
really function as an API.
John Blossom
On Sun, Jun 16, 2
Joseph,
This is exactly the sort of transformational architecture that I have been
hoping that you and others would pursue. Being fundamentally P2P but
readily adaptable for scalable client-server architecture seems to fit
today's mobile Web well. The three options that you outline might not wind
ncy issues will not be so
severe.
Things to think about, I will look at this more carefully later today.
All the best,
John Blossom
On Fri, Jun 21, 2013 at 8:05 AM, Bruno Gonzalez (aka stenyak) <
sten...@gmail.com> wrote:
> Following Joseph's "A Very Wavey Plan (P2P!)" thre
Glad to participate as requested, though this is primarily the developers'
discussion. John B
On Thu, Jun 20, 2013 at 4:31 AM, Upayavira wrote:
> Perfect.
>
> On Thu, Jun 20, 2013, at 03:57 AM, Michael MacFadden wrote:
> > Upayavira,
> >
> >
> > We will put a wiki page together. We will also h
Thanks so much, Michael, that's a great help. If we can get some funding
for Wave project development perhaps some of the funding can be reserved
for open source hosting services on an ongoing basis via a nonprofit entity.
All the best,
John Blossom
On Fri, Jun 21, 2013 at 6:20 PM, Mi
I've appreciated your help and insight, glad to have you aboard. Best, John
On Fri, Jun 21, 2013 at 12:19 PM, Christian Grobmeier
wrote:
> Hello Wave'rs,
>
> as you might know, I am Apache Member and involved in various
> projects. I also have mentored a bunch of podlings, like for example
> Open
a, in order to "open the eyes" of those drawn to this mailing
> >list, might it be beneficial to build up a wiki page of accepted use
> >cases so that everyone can read them and take them into account when
> >considering different ideas? That'd facilitate discussio
y wasn't possible to
> >communicate between two browsers without a sever between them.
> >
> >or does p2p mean something different in this context?
> >
> >On 22 June 2013 18:53, John Blossom wrote:
> >> Michael,
> >>
> >> I like that way
It's perhaps superficial, but if you call these "working groups" then
perhaps that takes away some of the hoop-jumping perception. These are
sub-communities which try to attract people who can help to solve specific
problems. I like the scheme.
On Joseph's point 1a, I think that it would be accept
we're to support
history/playback readily, but I suppose that's the fun of the challenge. If
we crack with with P2P in tow, then we've really got something.
All the best,
John Blossom
On Mon, Jun 24, 2013 at 6:36 PM, Joseph Gentle wrote:
> On Mon, Jun 24, 2013 at 2:30 PM, Ali L
Thank you! Glad to have your help.
BTW, how does one add oneself to be an editor of the wiki? Anyone? Thanks.
John Blossom
On Tue, Jun 25, 2013 at 5:01 AM, Christian Grobmeier wrote:
> Thanks all!
>
> I have subscribed myself now
>
> On Sat, Jun 22, 2013 at 6:45 PM, John
Michael, I do have a confluence login on the Apache Wave wiki, thanks for
your help
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Tue, Jun 25, 2013 at 11:23 AM, Michael MacFadden <
michael.macfad...@gmail.com>
Thank you, Michael, for my new vast, cosmic powers! ;-)
On Thu, Jun 27, 2013 at 9:04 PM, Michael MacFadden <
michael.macfad...@gmail.com> wrote:
> John,
>
> I have given you wiki permissions!
>
> ~Michael
>
>
>
Hello,
As some of you may be aware, one of the platforms from which I am
advocating for the renewal of Apache Wave development is to devise
communications that will be well-configured for "the next billion people"
coming online. The specific project that I am starting to gear up towards
this end i
Ingenious, Torben, certainly adds efficiency. John
On Mon, Jul 1, 2013 at 4:38 AM, Torben Weis wrote:
> 2013/6/25 Joseph Gentle
>
> >
> > >> When peers connect, they send each other missing ops. Figuring out
> > >> which ops are missing can be surprisingly tricky - but we'll figure
> > >> that
ys glad to communicate in this
channel as project protocol requires, as well as other channels which may
help to accelerate the efficiency of this channel.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
Ali,
Thanks so much, thoughts below. Best, John
On Mon, Jul 8, 2013 at 10:28 AM, Ali Lown wrote:
> Heh. This saves us having to write an [ANNOUNCE] for you...
>
FIRST! Tee hee.
>
> > One key thing that I'd like to chip away at is getting our Web presences
> > sussed out a bit more. Web sites/ow
Especially in the latter case of developing nations - but also for mobile
users in general - enabling offline modes with synchronisation after an
indefinite period is a must.
John
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
iting
announcements fairly soon. Time to change the world with Wave!!!
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Tue, Jul 16, 2013 at 1:58 PM, Joseph Gentle wrote:
> I've had a busy few weeks - gearing up to launch o
Great, Michael, find a date that works for you that seems to match with
others' interests and I will be glad to arrange for this. We can have the
link available but not make public, if that helps to encourage constructive
participation.
All the best,
John Blossom
email: jblos...@gmail.com
., ET is UTC+4 right now.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Wed, Jul 17, 2013 at 5:57 PM, Ali Lown wrote:
> I agree that another hangout sounds fun.
>
> John, how about setting up a Doodle for us to m
le of invitees.
I Have Joseph's ID already and I believe Ali and Michael also, but if you
have a doubt, just send it along. If you don't make the hangout itself, I
will be sure to share the link here for the common record.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
1200 ET, btw - bad math.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Tue, Jul 23, 2013 at 9:53 AM, John Blossom wrote:
> OK, the consensus time/date for the hangout seems to be Wednesday, 31
> July, 1600 UTC (10
events comments to clarify the context. I am hoping that this will be
sufficient - the listserv itself is not the most effective meeting
scheduler.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Tue, Jul 23, 2013 at 11:44 AM
best ways to use a tool like Google Hangouts effectively that fits in with
project guidelines.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Tue, Jul 23, 2013 at 11:44 AM, Christian Grobmeier
wrote:
> Hi folks,
>
>
I am all in for that, Joseph, absolutely. The sooner that we get a
project/Apache consensus for "eating our own dogfood," the better. Apache
Wave has the potential to become a killer project management tool.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
goog
ching developers and tech product teams.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Tue, Jul 23, 2013 at 3:17 PM, Joseph Gentle wrote:
> Speaking of which, I'd like to start actually using wave in this
> community.
forward to more visibility and awareness. That will help to attract more
developers, projects, etc.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Tue, Jul 23, 2013 at 7:27 PM, Zachary “Gamer_Z.” Yaro
wrote:
> I also supp
Thanks, Michael, Ali, if you could please confirm that you'll be able to
attend, that would be great. Any concerns, please don't hesitate to bring
them up now, thanks.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
O
Yes, Joseph, the goal is to use the disciplines of Apache open source
development to build a platform that will rock the world. The disciplines
are important, but a sustainable, maintainable platform is the real goal
that the disciplines facilitate.
All the best,
John Blossom
email: jblos
Michael, will you be able to join us on the Hangout this Wednesday?
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: https://google.com/+JohnBlossom
On Thu, Jul 25, 2013 at 11:06 PM, Michael MacFadden <
michael.macfad...@gmail.com> wrote:
> Looks l
Yes, the community needs to buy in to common communication. That said,
everyone's invited to view or participate in Wednesday's Hangout and the
results will be posted here, just as with any other interaction in the
project.
All the best,
John Blossom
email: jblos...@gmail
know that a Hangout is the place to solve that,
this is probable the best place to start. In the meantime, I will be glad
to help create a new "office hours" event on Hangout and have people decide
what they want to discuss. Thanks to everyone who participated, the
logistics seem to have
t and links to the official project Web site.
Thoughts? It's very easy to set up, BTW.
All the best,
John Blossom
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 20
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" wrote:
>
> > In conjunction with the Hangouts, I'd like to suggest t
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 guideli
On Wed, Jul 31, 2013 at 4:14 PM, Christian Grobmeier wrote:
> 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.o
1 - 100 of 150 matches
Mail list logo