incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Evan Hughes <ehu...@gmail.com>
Subject Re: Coming Months
Date Sat, 11 Apr 2015 16:49:29 GMT
looks like the 6pm UTC on the first day is pretty good for everyone that
has filled in the doodle except ajr13 unfortunately. We just need to
confirm the time so people can make plans to be available. Unfortunately I
was not present during the last hangout so some information on how the
"calling" process happened would be helpful.

@Grobmeier:
 - Agreed
 - Seems the 6pm (UTC) sessions early in the week are pretty common
 - Sounds like a good idea, more information the better

On 11 April 2015 at 22:12, Christian Grobmeier <grobmeier@apache.org> wrote:

> Just checked the doodle and had this on mind:
>
> - we should make sure that as many committers as possible are there. In
> example. I consider Ali a very important person to participate
>
> - from mentor perspective, I think it's ok if at least one of us can
> participate. I would be sad if I can't meet you all, but if there is a
> time when everybody except could make it, chose it.
>
> - I would like to suggest a Q&A -after- the official Wave meeting for
> people, who are interested in working with Wave but are concerned
> because they don't know what Apache is. What I want to say is: do you
> have any questions on the ASF, would like to learn how it works, or
> anything else, we could clarify this after the first part. That said, it
> would interesting to know if there are any folks who would like to see
> there ASF related questions answered, even when they are not related to
> Wave.
>
> Cheers
>
> On Tue, Apr 7, 2015, at 10:16, Upayavira wrote:
> > Thanks for this, Evan.
> >
> > Given it was you that proposed the Hangout, it would seem reasonable
> > that we try to accommodate you. Anyone here have any objections to an
> > earlier concall, say, 2pm UTC? Are there any Pacific time participants?
> >
> > Regarding the document, we need to keep it *really* simple. To be quite
> > frank, when you are trying to restart someone’s heart, you don’t worry
> > much about a sore on their leg. We need to be looking for the absolute
> > simplest things we can do that might make this project more accessible.
> > They have to be small enough that someone here can undertake them with a
> > reasonable certainty of completion and success. The main resource we
> > lack at the moment is people to actually do the work, so we need to
> > identify small, manageable tasks that will help draw in new resources
> > which might, in turn, allow us to take on larger tasks.
> >
> > Upayavira
> >
> > On Tue, Apr 7, 2015, at 04:43 AM, Evan Hughes wrote:
> > > Google Doc full of talking points, available for anyone to edit as they
> > > see
> > > fit. Its a combination of the summary Mr Grobmeier made from the other
> > > thread and some person thoughts.
> > >
> > > Talking points for hangout
> > > <
> https://docs.google.com/document/d/1_7wraANGg6XKfvENPwEgEn7_umlU0Y1eA5CjQcuvhxU/edit?usp=sharing
> >
> > >
> > > Need to make sure the hangout is recorded as for myself 12am 2am & 4am
> is
> > > 50/50 shot ill be able to stay awake to watch it live haha.
> > >
> > > On 7 April 2015 at 05:26, Ali Lown <ali@lown.me.uk> wrote:
> > >
> > > > Times are whatever you set the doodle timezone to be (Top right).
> > > >
> > > > Ali
> > > > On 6 Apr 2015 20:17, "Upayavira" <uv@odoko.co.uk> wrote:
> > > >
> > > > > I presume times are UTC?
> > > > >
> > > > > On Mon, Apr 6, 2015, at 02:39 AM, Ali Lown wrote:
> > > > > > Here is a fairly large Doodle poll to see see when may work
as a
> good
> > > > > > date/time for a hangout.
> > > > > >
> > > > > > http://doodle.com/uz9vq9qiwyuqigsa
> > > > > >
> > > > > > Let me know if you want more time options.
> > > > > >
> > > > > > Ali
> > > > > >
> > > > > > On 4 April 2015 at 07:28, Michael MacFadden <
> > > > michael.macfadden@gmail.com
> > > > > >
> > > > > > wrote:
> > > > > > > I would be happy to participate.  Perhaps the first thing
to
> know
> > > > is..
> > > > > What time zones people are all in.  I am in US Pacific Time Zone
> (UTC
> > > > > -7:00).
> > > > > > >
> > > > > > > ~Michael
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 4/2/15, 7:40 AM, "Evan Hughes" <ehugh1@gmail.com>
wrote:
> > > > > > >
> > > > > > >>sure, just need to know what time of day is suitable
for the
> speakers
> > > > > as we
> > > > > > >>should keep a record of it for people to view whenever.
Thanks
> to the
> > > > > other
> > > > > > >>threads there's plenty of stuff to compile a list of
talking
> points,
> > > > > I'll
> > > > > > >>put something together over the next week.
> > > > > > >>
> > > > > > >>On 2 April 2015 at 23:33, Ali Lown <ali@lown.me.uk>
wrote:
> > > > > > >>
> > > > > > >>> I think another hangout would be a great thing
to have.
> > > > > > >>>
> > > > > > >>> @Evan: Are you happy to organise this?
> > > > > > >>>
> > > > > > >>> Ali
> > > > > > >>>
> > > > > > >>> On 1 April 2015 at 16:23, John Blossom <jblossom@gmail.com>
> wrote:
> > > > > > >>> > Id be glad to listen in, but since I am not
a technical
> > > > > contributor, I
> > > > > > >>> will
> > > > > > >>> > try mostly just to monitor.
> > > > > > >>> >
> > > > > > >>> > All the best,
> > > > > > >>> >
> > > > > > >>> > John Blossom
> > > > > > >>> >
> > > > > > >>> > email: jblossom@gmail.com
> > > > > > >>> > phone: 203.293.8511
> > > > > > >>> > google+: google.com/+JohnBlossom
> > > > > > >>> >
> > > > > > >>> > On Mon, Mar 30, 2015 at 11:26 PM, Evan Hughes
<
> ehugh1@gmail.com>
> > > > > wrote:
> > > > > > >>> >
> > > > > > >>> >> Hey all,
> > > > > > >>> >>
> > > > > > >>> >> could we get a Google hangout of the Mentors
and
> contributors to
> > > > > > >>> solidify
> > > > > > >>> >> the direction which wave will be heading
and pointing out
> what
> > > > > needs to
> > > > > > >>> be
> > > > > > >>> >> done other than just thoughts on the mailing
list.
> > > > > > >>> >>
> > > > > > >>>
> > > > > > >
> > > > >
> > > >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message