[FOSDEM] [Valgrind-developers] Virtual Valgrind Fosdem Devroom

[Mark Wielaard]

Hi Valgrind Hackers,

A reminder that Valgrind will participate in the Virtual Fosdem on
Sunday 6 February 2022 https://fosdem.org/2022/schedule/track/valgrind/

We are still accepting talk proposals, but will have to finalize the
schedule next week. Please submit a talk proposal asap at
https://penta.fosdem.org/submission/FOSDEM22 Please select the
"Valgrind Devroom" Track.  If you have any trouble creating a penta
login or cannot immediate create a full submission please contact
Julian and me with your proposal so we can still schedule your talk.

More information in the original call for participation below.

On Mon, Dec 13, 2021 at 06:04:33PM +0100, Mark Wielaard wrote:
> Hi valgrind hackers,
> 
> Valgrind will participate in the Virtual Fosdem on Sunday 6 February
> 2022 https://fosdem.org/2022/schedule/track/valgrind/
> 
> We would like to invite people to propose talks on valgrind by
> submitting a talk proposal to 
> https://penta.fosdem.org/submission/FOSDEM22
> Please select the "Valgrind Devroom" Track.
> (If you have any trouble creating a penta login or submission please
> contact Julian and me with your proposal.)
> 
> Because Fosdem will be virtual this year we will likely ask talks to be
> pre-recorded in advance and after playing your presentation we will do
> a live Q/A session using Jitsi and Matrix.
> 
> Please pick a time that includes the length of your (recorded) talk
> plus ~15 minutes Q/A.
> 
> We would like to finalize the schedule the first week of January so
> that people have enough time to record their talk, so please submit
> your proposals before the end of year (31 December 2021).
> 
> Some possible topics for talks/discussions are:
> 
> - New (or recently added) ports.
> - New CPU (instruction) support.
> - New (ideas/prototypes) of valgrind tools.
> - Valgrind release/bugfixing strategy/policy.
> - Advances in gdbserver and the GDB remote serial protocol.
> - DWARF, debuginfo, symbols and debuginfod servers.
> - Using valgrind with "safe" languages (Rust).
> - Adding/Testing Valgrind syscalls support.
> - Infrastructure changes (speedups) to the Valgrind JIT framework.
> - Your interesting use case with Valgrind.
> 
> Sincerely,
> 
> Mark & Julian