From: "Shuah Khan" <skhan@linuxfoundation.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-safety@lists.elisa.tech
Cc: Kate Stewart <kstewart@linuxfoundation.org>,
"lukas.bulwahn@bmw.de" <lukas.bulwahn@bmw.de>,
"devel@lists.elisa.tech" <devel@lists.elisa.tech>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [ANNOUNCE][CFP] Kernel Dependability & Assurance Micro Conference - LPC 2020
Date: Fri, 10 Jul 2020 08:42:08 -0600 [thread overview]
Message-ID: <34aa3ed4-7405-d1b2-f884-30ee5ad279aa@linuxfoundation.org> (raw)
In-Reply-To: <675ed25a-3fa8-e288-1be4-41710a807d1f@linuxfoundation.org>
On 7/9/20 2:58 PM, Shuah Khan wrote:
+ devel@lists.elisa.tech <devel@lists.elisa.tech>
> This is the call for proposals for the Kernel Dependability & Assurance
> Micro Conference at the Linux Plumbers Conference 2020. It will take
> place online during the Linux Plumbers Conference on August 24th-28th,
> 2020.
>
> The Kernel Dependability & Assurance Micro Conference is intended to
> bring the safety-critical systems community and the kernel community
> together to start a dialogue and collaboration on making sure that the
> kernel is fit to be used in safety-critical systems and that questions
> from the safety community and other wrt. software quality can be
> answered adequately.
>
> The goal for this conference is to explore kernel dependability as it
> relates to safety-critical applications in the areas of uptime, tooling,
> and processes. The focus is going to be on the following topics.
>
> - Kernel Quality Assurance beyond Testing and CI?
>
> - Understanding the User's Expectations on Software Quality for
> business-critical systems
>
> - Define safety requirements for overall kernel: features, tests etc.
>
> - Define run-time characteristics and requirements
>
> - Identify missing features necessary to operate in safety critical
> environments.
>
> - Discuss safety features
>
> - Regression Testing for safety: Identify configurations and tests
> critical and important for safety quality and dependability
>
> - Discuss and identify gaps in tests.
>
> - Add tests and add configurations to existing test rings.
>
> - Understanding the Kernel Development Organization and Management
>
> - Assessing, Measuring and Evaluating the Development Process
>
> We encourage submissions that do not present a final solution. Instead,
> that serves to get feedback from the community, to point to action items
> for future development, and that can result in patches for the Linux
> Kernel and Linux ecosystem in the future.
>
> Please submit your proposals on the LPC website at:
>
> https://www.linuxplumbersconf.org/event/7/abstracts/#submit-abstract
>
> And be sure to select "Kernel Dependability & Assurance MC" in the Track
> pulldown menu.
>
> Proposals must be submitted by August 2nd, and submitters will be
> notified of acceptance by August 9th.
>
> thanks,
> -- Shuah
prev parent reply other threads:[~2020-07-10 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 20:58 [ANNOUNCE][CFP] Kernel Dependability & Assurance Micro Conference - LPC 2020 Shuah Khan
2020-07-10 14:42 ` Shuah Khan [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=34aa3ed4-7405-d1b2-f884-30ee5ad279aa@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=devel@lists.elisa.tech \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-safety@lists.elisa.tech \
--cc=lukas.bulwahn@bmw.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).