FOSDEM is a two-day event organised by the FOSS community for FOSS the community. This event aims to gather like-minded professionals to learn, teach, and broaden their knowledge and network. The event is open to thousands of software developers of free and open source software and usually is held in Brussels; however, this year (2021), the fun will continue virtually.
The agenda for the Safety and Open Source devroom
At the Developer Room (devrooms), FOSS software developers can converse and showcase their projects, along with lightning talks, public presentations of the latest directions and more. This is a fun and exciting weekend for the developers and our employees since they are hosting their first devroom this year.
The FOSDEM Safety and Open Source devroom for Saturday 6th February is as follows:
Shaun Mooney will be starting the day at 10:45 explaining “Why we should use Free and Open Source Software for safety applications”.
Joffrey Huguet will be speaking at 11:00 on "Adding contracts to the GCC GNAT Ada standard libraries to strengthen analysis provided by formal verification tools”.
Matthias Valvekens will give insight into "Document security and digital signatures in PDF" at 11:45.
Claire Dross will be speaking on "Proving heap-manipulating programs with SPARK" "The SPARK open-source proof tool for Ada now supports verifying pointer-based algorithms thanks to an ownership policy inspired by Rust.
Shaun Mooney will talk about “ELISA - Advancing Open Source Safety-Critical Systems” at 14:45.
Safety and Open Source is an increasingly important conversation for the open source community because software developed for safety applications typically employs traditional development practices that, although well-used, are increasingly outdated, and the code is often closed source. This is because safety standards are stringent, and safety applications must have rigorous quality assurance practices applied during development. Sadly, this means that using FOSS, which has not been developed to a safety standard from the start, is a real challenge.
Join the conversation about safety-critical software
After the talks, Codethink's devroom will hold a community discussion on "Safety and Open Source". The open forum will be an excellent opportunity to share opinions, debate different perspectives and talk about the latest developments for safety-critical software.
One of our Division Managers, Shaun Mooney, will be opening up this discussion and introducing the aims and goals of the devroom, the areas of focus and how participants will contribute to the discussion. Our director Paul Sherwood will then take over and guide the conversation into the state of safety-critical software in automotive and where that will be in 5 years' time.
Thes fun does not end in the devroom! An hour may not be enough to delve into everything STPA and FOSS so we will be continuing the discussion on gather.town where you will be able to virtually split off into groups and have conversations of interest with like-minded professionals.
This will be an exciting event not to be missed! Make sure you join us for free in this devroom to be part of the conversation >>
Also, join the conversation with us on our Twitter account @codethink and using the hashtag #safetyandopensource.
We will also have a Safety devroom chat where you can get involved >>
Related blog posts:
- Using STPA with software-intensive systems
- Codethink achieves ISO 26262 ASIL D Tool Certification
- RISC-V: running GNOME OS on SiFive hardware for the first time
- Automated Linux kernel testing
- Native compilation on Arm servers is so much faster now
- Higher quality of FOSS: How we are helping GNOME to improve their test pipeline
- RISC-V: A Small Hardware Project
- Why aligning with open source mainline is the way to go
- Build Meetup 2021: The BuildTeam Community Event
- A new approach to software safety
- Does the "Hypocrite Commits" incident prove that Linux is unsafe?
- ABI Stability in freedesktop-sdk
- Why your organisation needs to embrace working in the open-source ecosystem
- RISC-V User space access Oops
- Tracking Players at the Edge: An Overview
- What is Remote Asset API?
- Running a devroom at FOSDEM: Safety and Open Source
- Meet the codethings: Understanding BuildGrid and BuildBox with Beth White
- Streamlining Terraform configuration with Jsonnet
- Bloodlight: Designing a Heart Rate Sensor with STM32, LEDs and Photodiode
- Making the tech industry more inclusive for women
- Bloodlight Case Design: Lessons Learned
- Safety is a system property, not a software property
- RISC-V: Codethink's first research about the open instruction set
- Meet the Codethings: Safety-critical systems and the benefits of STPA with Shaun Mooney
- Why Project Managers are essential in an effective software consultancy
- Meet the Codethings: Ben Dooks talks about Linux kernel and RISC-V
- Here we go 2021: 4 open source events for software engineers and project leaders
- Xmas Greetings from Codethink
- Call for Papers: FOSDEM 2021 Dev Room Safety and Open Source Software
- Building the abseil-hello Bazel project for a different architecture using a dynamically generated toolchain
- Advent of Code: programming puzzle challenges
- Improving performance on Interrogizer with the stm32
- Introducing Interrogizer: providing affordable troubleshooting
- Improving software security through input validation
- More time on top: My latest work improving Topplot
- Cycling around the world
- Orchestrating applications by (ab)using Ansible's Network XML Parser
- My experience of the MIT STAMP workshop 2020
- Red Hat announces new Flatpak Runtime for RHEL
- How to keep your staff healthy in lockdown
- Bloodlight: A Medical PPG Testbed
- Bringing Lorry into the 2020s
- How to use Tracecompass to analyse kernel traces from LTTng
- Fixing Rust's test suite on RISC-V
- The challenges behind electric vehicle infrastructure
- Investigating kernel user-space access
- Consuming BuildStream projects in Bazel: the bazelize plugin
- Improving RISC-V Linux support in Rust
- Creating a Build toolkit using the Remote Execution API
- Trusting software in a pandemic
- The Case For Open Source Software In The Medical Industry
- My experiences moving to remote working
- Impact of COVID-19 on the Medical Devices Industry
- COVID-19 (Coronavirus) and Codethink
- Codethink develops Open Source drivers for Microsoft Azure Sphere MediaTek MT3620
- Codethink partners with Wirepas
- Testing Bazel's Remote Execution API
- Passing the age of retirement: our work with Fortran and its compilers
- Sharing technical knowledge at Codethink
- Using the REAPI for Distributed Builds
- An Introduction to Remote Execution and Distributed Builds
- Gluing hardware and software: Board Support Packages (BSPs)
- Engineering's jack of all trades: an intro to FPGAs
- Bust out your pendrives: Debian 10 is out!
- Why you should attend local open source meet-ups
- Acceptance, strife, and progress in the LGBTIQ+ and open source communities
- Codethink helps York Instruments to deliver world-beating medical brain-scanner
- Codethink open sources part of staff onboarding - 'How To Git Going In FOSS'
- Getting into open source
- How to put GitOps to work for your software delivery
- Open Source Safety Requirements Analysis for Autonomous Vehicles based on STPA
- Codethink engineers develop custom debug solution for customer project
- Codethink contributes to CIP Super Long Term Kernel maintenance
- Codethink creates custom USB 3 switch to support customer's CI/CD pipeline requirements
- Codethink unlocks data analysis potential for British Cycling
- MIT Doctor delivers Manchester masterclass on innovative safety methodology
- Balance for Better: Women in Technology Codethink Interviews
- Introducing BuildGrid
- Full archive