All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Developpers' Day 2013
Date: Sat, 26 Oct 2013 00:38:51 +0200	[thread overview]
Message-ID: <526AF2FB.4020601@lucaceresoli.net> (raw)
In-Reply-To: <OF9DE40725.A99AAF8D-ON86257C0F.0078CD97-86257C0F.007997AD@rockwellcollins.com>

Hi Ryan, All,

Ryan Barnett wrote:
> Thomas P,
>
> Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote on 10/25/2013
> 02:18:47 AM:
>
>> Dear Thomas De Schampheleire,
>>
>> On Fri, 25 Oct 2013 08:38:28 +0200, Thomas De Schampheleire wrote:
>>
>>>> Also, do we want to start a Google Hangout session during the
> meeting,
>>>> to allow people to follow the discussions remotely? Is there any
>>>> interest in doing that, from the perspective of people that would be
>>>> interested in participating remotely?
>>> If I have some time, I will certainly join the Hangout, but I cannot
>>> make any promises about if and when this happens.
>>> How does this work, are hangouts 'open' all the time? Is there an
>>> invite needed? Where will you post the reference?
>> So far, I've only done "private" hangouts by inviting a bunch of
>> people. Maybe there is something to make "public" hangouts, but I've
>> never tried. So what I believe we're going to do is that the people who
>> want to join the hangout should say so on IRC, and I'll invite them. I
>> will just name their Google account e-mail to do so.
>   
> So have we decided upon an exact time? Also I haven't seen any google
> hangout invite requests yet. I'm going to assume that we are going to do
> it during Luca's availablity window. This means that it will take place
> around.

The idea is that the session will start as soon as there is people.

>
> 3:00 PM to 5:00 PM CEST
> 2:00 PM to 4:00 PM BST
> 8:00 AM to 10:00 AM CDT

I may be there a bit later, but more or less it is correct.

-- 
Luca

      parent reply	other threads:[~2013-10-25 22:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-13 22:39 [Buildroot] Buildroot Developpers' Day 2013 Yann E. MORIN
2013-10-17 12:32 ` Thomas Petazzoni
2013-10-17 13:25   ` Luca Ceresoli
2013-10-17 13:36     ` Thomas Petazzoni
2013-10-17 13:51   ` Ryan Barnett
2013-10-17 15:17     ` Thomas Petazzoni
2013-10-17 15:28       ` Jesse Cobra
2013-10-17 20:00         ` Yann E. MORIN
2013-10-17 20:17           ` Ryan Barnett
2013-10-17 19:45       ` Ryan Barnett
2013-10-19  7:56         ` Thomas Petazzoni
2013-10-19 19:42           ` Ryan Barnett
2013-10-20 22:14           ` Luca Ceresoli
2013-10-21 22:03             ` Yann E. MORIN
2013-10-21 22:17               ` Ryan Barnett
2013-10-22 14:03             ` Thomas Petazzoni
2013-10-22 14:41               ` Ryan Barnett
2013-10-25  6:38   ` Thomas De Schampheleire
2013-10-25  7:18     ` Thomas Petazzoni
2013-10-25 22:08       ` Ryan Barnett
2013-10-25 22:19         ` Jesse Cobra
2013-10-25 22:38         ` Luca Ceresoli [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=526AF2FB.4020601@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.