All of lore.kernel.org
 help / color / mirror / Atom feed
From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Fwd: (Feb 21, 4pm) LTSI Workshop @ ELC Portland
Date: Mon, 20 Feb 2017 15:25:29 -0800	[thread overview]
Message-ID: <58AB7AE9.6090101@codethink.co.uk> (raw)
In-Reply-To: <CAFo+snXyhq4bexWnfLU_Q2Z++5=3_oh23DJbdJRUj4N=t+NrEA@mail.gmail.com>

Hi,

On 20/02/17 13:16, Noriaki Fukuyasu wrote:
> Hi
>
> Please let me forward below.

I will attend to the LTSI workshop.

>
> Regards
>
> Nori
>
>
> ---------- Forwarded message ---------
> From: Noriaki Fukuyasu <fukuyasu@linuxfoundation.org
> <mailto:fukuyasu@linuxfoundation.org>>
> Date: 2017?1?25?(?) 5:29
> Subject: (Feb 21, 4pm) LTSI Workshop @ ELC Portland
> To: ltsi-dev at lists.linuxfoundation.org
> <mailto:ltsi-dev@lists.linuxfoundation.org>
> <ltsi-dev@lists.linuxfoundation.org
> <mailto:ltsi-dev@lists.linuxfoundation.org>>
>
>
> Hi LTSI developers!
>
>
> We are going to have another LTSI Workshop next month at ELC Portland.
>
> If you are attending ELC, please come join!
>
> (If you are interested in joining the workshop, please send me a note. )
>
>
> Date: Feb 21st, 2017
>
> Time: 4pm to 6pm
>
> Venue: Director's Suite on the 3rd floor.
>
>
> Agenda:
>
>   * Brief Status Update & LTSI Development Schedule
>   * Exchange thoughts ?Upstream First? (*1). There will be 2-3 guest
>     speakers to talk about their experiences and thoughts on "Upstream
>     First" to kick the discussions.
>
>
> NOTE (*1):  This year, LTSI would like to spend sometime on gathering
> the information of how companies are taking advantage of upstream
> development. Particularly, we are interested in the following questions:
>
>   * What is the business value
>   * What are the challenges
>   * What makes it successful (from the real company experiences) etc
>
> We are planning to write up a white paper on this subject later this
> year based on the information we gather from the workshop.
>
>
> See you there!!
>
>
> regards
>
>
> Noriaki Fukuyasu
>
>
>
> --
> Noriaki Fukuyasu
>
> The Linux Foundation
> Mail: fukuyasu at linuxfoundation.org <mailto:fukuyasu@linuxfoundation.org>
> Tel: +81-80-4350-1133
> Twitter: nori_fukuyasu
> Facebook: linuxfoundationjp
>
> Please visit our web sites:
> http://www.linuxfoundation.jp
> http://events.linuxfoundation.jp
> http://jp.linux.com
>
> --
> Noriaki Fukuyasu
>
> The Linux Foundation
> Mail: fukuyasu at linuxfoundation.org <mailto:fukuyasu@linuxfoundation.org>
> Tel: +81-80-4350-1133
> Twitter: nori_fukuyasu
> Facebook: linuxfoundationjp
>
> Please visit our web sites:
> http://www.linuxfoundation.jp
> http://events.linuxfoundation.jp
> http://jp.linux.com
>
>
>
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
>

-- 
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk

      reply	other threads:[~2017-02-20 23:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFo+snXizTfpdtu7Wiuxhd3H-7BQLuqRUuMpw21h6wp+37Rc8A@mail.gmail.com>
2017-02-20 21:16 ` [cip-dev] Fwd: (Feb 21, 4pm) LTSI Workshop @ ELC Portland Noriaki Fukuyasu
2017-02-20 23:25   ` Agustin Benito Bethencourt [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=58AB7AE9.6090101@codethink.co.uk \
    --to=agustin.benito@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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.