From: "Jose E. Marchesi" <jemarch@gnu.org>
To: poke-devel@gnu.org
Cc: nickc@redhat.com, mattias.wadman@gmail.com, mnabipoor@gnu.org,
indu.bhagat@oracle.com, david.faust@oracle.com, positron@gnu.org,
darnir@gnu.org, binutils@sourceware.org,
Simon Marchi <simark@simark.ca>, Pedro Alves <pedro@palves.net>,
Mark Wielaard <mark@klomp.org>,
Dodji Seketeli <dodji@seketeli.org>,
guillermo.e.martinez@oracle.com, monnier@iro.umontreal.ca
Subject: Binary Tools track at FOSDEM
Date: Fri, 14 Oct 2022 16:55:10 +0200 [thread overview]
Message-ID: <87ilkmbgkx.fsf@gnu.org> (raw)
Hello people!
I just submitted a proposal for FOSDEM 2023 (Brussels, February 4 and 5
2023) for a "Binary Tools" devroom. The aim of the devroom is similar
to of the Binary Tools Summit [1] we did remotely earlier this year: to
get together developers of tools that manipulate binary data, such as
assemblers, binary editors, reverse-engineering suites,
encoders/decoders generators, etc.
mnabipoor agreed to be the co-organizer.
We are asking for a full day.
The aim of the conference is to have three kind of activities:
1) Talks/activities for developers of the tools.
2) Talks/activities/little workshops for users of the tools.
3) Activities to increase cooperation between the tools.
I am reaching out to the following projects for prospective
participation and talks:
- GNU poke (obviously ;))
- radare2
- kaitai struct
- binwalk
- wireshark
- GNU binutils
Suggestions on other projects/people to contact? (Or feel free to do it
yourself pointing them to this email/to us!.)
If this devroom gets approved, I promise you we are gonna have TONS of
fun ;)
Salud!
[1] https://binary-tools.net/summit.html
reply other threads:[~2022-10-14 14:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87ilkmbgkx.fsf@gnu.org \
--to=jemarch@gnu.org \
--cc=binutils@sourceware.org \
--cc=darnir@gnu.org \
--cc=david.faust@oracle.com \
--cc=dodji@seketeli.org \
--cc=guillermo.e.martinez@oracle.com \
--cc=indu.bhagat@oracle.com \
--cc=mark@klomp.org \
--cc=mattias.wadman@gmail.com \
--cc=mnabipoor@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nickc@redhat.com \
--cc=pedro@palves.net \
--cc=poke-devel@gnu.org \
--cc=positron@gnu.org \
--cc=simark@simark.ca \
/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).