All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Sangorrin" <daniel.sangorrin@toshiba.co.jp>
To: Tim.Bird@sony.com, fuego@lists.linuxfoundation.org
Subject: Re: [Fuego] Options for Fuego meeting in June, in Tokyo
Date: Thu, 10 May 2018 10:56:59 +0900	[thread overview]
Message-ID: <000001d3e802$2ec38320$8c4a8960$@toshiba.co.jp> (raw)
In-Reply-To: <ECADFF3FD767C149AD96A924E7EA6EAF7C12EAC0@USCULXMSG01.am.sony.com>

Hi Tim,

> -----Original Message-----
> From: fuego-bounces@lists.linuxfoundation.org
> [mailto:fuego-bounces@lists.linuxfoundation.org] On Behalf Of
> Tim.Bird@sony.com
> Sent: Tuesday, May 8, 2018 6:25 AM
> To: fuego@lists.linuxfoundation.org
> Subject: [Fuego] Options for Fuego meeting in June, in Tokyo
> 
> Hello Fuego community,
> 
> There will be a number of Fuego users and developers in Tokyo, Japan
> in June of this year, at the Automotive Linux Summit.  I think it would be
> good to plan a side meeting to discuss the current status and roadmap
> for Fuego, among the interested parties.
> 
> Note that there are already 3 testing talks scheduled for ALS.  They are in
> consecutive sessions in room Hall B-1 on Thursday, June 21.
>  - Fuego Test System Status Update - Tim Bird
>  - Primer: Testing Your AGL - Yocto ptest, Lava Jobs and more - Jan-simon Moeller
>  - Establish an Automated Testing Lab for AGL - Liu Wenlong
> 
> We can either arrange an offsite meeting, at the Sony Creative Lounge at Sony
> headquarters in Shinagawa (which could be up to 4 to 5 hours), or try to schedule a
> meeting
> at the event center (like request an evening BOF or something), for 1 hour.
> 
> Here are the options:
> 1 - have a meeting at Sony Creative Lounge on Tuesday, June 19 (mid-day)

On June 19, I will have a separate meeting during the morning.
Maybe I could attend in the afternoon around 14:00.

> 2 - have a Birds of a Feather session on Thursday, June 21 (evening)
> 3 - have a Birds of a Feather session on Friday, June 22 (evening)
> 4 - have a meeting at the Sony Creative Lounge on Saturday, June 23 (morning)

Any of these three work for me.

> There is an onsite reception Thursday night, so for option 2 we would either have
> to conflict with that, or have our meeting late (starting at 19:00).  Maybe starting
> at 18:00 or 18:30 (overlapping some) would be OK?
> 
> I'm confident I can get the Sony meeting room, but not so sure about the
> evening meeting room at the conference venue.
> 
> Please let me know your preference, and I'll try to arrange a meeting.   My
> preference
> would be to do something at the conference venue. That seems most convenient,
> but gives us less time.  Let me know what you think.

No special preference from my side. Meeting during some break is also fine.

Thanks,
Daniel



  reply	other threads:[~2018-05-10  1:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 21:25 [Fuego] Options for Fuego meeting in June, in Tokyo Tim.Bird
2018-05-10  1:56 ` Daniel Sangorrin [this message]
2018-05-10 17:09   ` Tim.Bird
2018-05-14 18:52   ` Tim.Bird
2018-05-15  1:21     ` Daniel Sangorrin
     [not found]   ` <CGME20180514185253epcas5p43aac882e41cea0e4e3e83c968ac7fa9c@epcms5p6>
2018-05-15  5:01     ` Dhinakar Kalyanasundaram
2018-05-14  8:40 ` Liu, Wenlong
2018-05-14  9:00   ` Khiem Nguyen

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='000001d3e802$2ec38320$8c4a8960$@toshiba.co.jp' \
    --to=daniel.sangorrin@toshiba.co.jp \
    --cc=Tim.Bird@sony.com \
    --cc=fuego@lists.linuxfoundation.org \
    /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.