From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Rectification: Open Source Leadership Summit slides
Date: Fri, 24 Feb 2017 14:38:20 -0800 [thread overview]
Message-ID: <58B0B5DC.8090706@codethink.co.uk> (raw)
Hi,
during the CIP talk that Nori and I did at the Open Source Leadership
Summit on week 07, I made the following mistake:
Daniel Sangorrin, from Toshiba, has been working the last few weeks on
Fuego. I assigned to him the integration of LAVA and Fuego. The truth is
that this particular feature has been developed by Jan-Simon M?ller,
from the Linux Foundation, within AGL.
I also stated that the effort is ongoing when, in fact, Jan-Simon
already completed it.
This mistake is specially inexplicable given that I am part of the AGL
CIAT group and I am closely following the progress of Fuego.
Apologies to both of you for my wrong attribution. I will change the
slides accordingly.
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next reply other threads:[~2017-02-24 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 22:38 Agustin Benito Bethencourt [this message]
2017-03-08 9:52 ` [cip-dev] Rectification: Open Source Leadership Summit slides Agustin Benito Bethencourt
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=58B0B5DC.8090706@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.