From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: <linux-iio@vger.kernel.org>
Cc: <lars@metafoo.de>, Hartmut Knaack <knaack.h@gmx.de>,
"Peter Meerwald-Stadler" <pmeerw@pmeerw.net>,
Daniel Baluta <daniel.baluta@gmail.com>
Subject: Potential IIO meeting / future directions discussion at ELCE 2018 - Edinburgh 22-24 Oct
Date: Thu, 28 Jun 2018 15:24:25 +0100 [thread overview]
Message-ID: <20180628152425.00007abc@huawei.com> (raw)
Hi All,
I know at least a few IIO developers are likely to be at the Embedded Linux
Conference Europe in a few months time. Hence this email is exploring the
possibility of us doing something we have never done for IIO before and have
a formal meet up. I would propose the topics to discuss would be loosely
around future directions for IIO development. This might consist of actual
proposals or simply discussion of pain points.
I'm not sure how long a session would be sensible, but one possibility is
to propose it as a BoF as that fits in their standard schedule without needing
any additional organization - I think by default that only gives us an hour or
so. However, the deadline to propose one of those is this Sunday so things are
little tight. We don't need a fully planned schedule but it would be good to
have made a start. If we decide to do this I'll write an abstract and submit it.
So I'm looking for topics and some idea of who is going to be there
or might be persuaded to make the trip!
Chances are we won't actually 'finish' any non trivial discussions, but it is
a lot easier to make progress on topics that you've at least outlined in person.
Please forward to anyone who may be interested and might not see it on the list
before Sunday. Obviously Sunday isn't a cut off for discussion, it's just when
I have hope to be able to draw together a proposal!
Jonathan
p.s. I'm planning to put a normal talk session proposal in as well. It'll trawl
through a bit of the history of IIO (it's 10 years old this year!), lessons learned
etc. Not a tutorial, but an analysis of some more general useful stuff with
just enough description of IIO to let the uninitiated know what we are talking
about! I'll also touch on encouraging new contributors etc. No idea if the
committee will like that approach, so who knows ;)
next reply other threads:[~2018-06-28 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 14:24 Jonathan Cameron [this message]
2018-06-28 17:11 ` Potential IIO meeting / future directions discussion at ELCE 2018 - Edinburgh 22-24 Oct Lars-Peter Clausen
2018-06-29 7:48 ` Daniel Baluta
2018-07-01 11:09 ` Jonathan Cameron
2018-07-01 15:16 ` Lars-Peter Clausen
2018-07-01 17:07 ` Jonathan Cameron
2018-07-01 17:27 ` Jonathan Cameron
2018-08-19 19:39 ` Jonathan Cameron
2018-07-02 0:08 ` Matt Ranostay
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=20180628152425.00007abc@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=daniel.baluta@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.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.