public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jemarch@gnu.org>
To: binutils@sourceware.org
Subject: [CFP] Binary T00ls Summit 2022
Date: Wed, 02 Feb 2022 19:32:31 +0100	[thread overview]
Message-ID: <8735l1qfuo.fsf@gnu.org> (raw)


The *Binary T00ls Summit 2022* (https://binary-tools.net/summit) is an
informal, technical, online event oriented to authors, users and
enthusiasts of FLOSS programs that deal with binary data.

This includes binary editors, libraries to encode and decode data,
parser generators, binary data description languages and frameworks,
binary formats and encodings, assemblers, debuggers, reverse
engineering suites, and the like.

The goal of this event is for developers to get in touch with each
other, introduce their tools, have interesting and hopefully
productive discussions, and finally what is most important: to have
fun.

The venue of the event will be an instance of the Big Blue Button web
conferencing system, accessible using Firefox, Chromium and other web
browsers.  We will be having a single track that will span for three
days during a weekend.

The summit will be held on the first weekend of March 2022, From Friday
4 to Sunday 6.

If you wish to participate doing a presentation, you are very welcome
to send us a proposal to binary-tools-summit@gnu.org with the
following information:

- Your contact info (name, email, affiliation).
- Name of the presentation.
- Abstract of the presentation; one or two paragraphs.
- How much time would you want to use.  Anything from 30 minutes to
  2 hours is fine.
- Preferred day: Friday, Saturday or Sunday.
- Preferred time of the day: from 16:00 CET to 21:00 CET.

Note that all presentations will be performed live.  It will be
possible to share the screen and do demos/tutorials.

The deadline for sending presentations is Wednesday 16 Feb. 2022.
We will be publishing the schedule the same day.

The event is open for everyone and no registration is needed.
However, if you plan to attend (presenting or not) please consider
letting us know in an email; this will help us to estimate the number
of participants and organize better.

See you soon!

             reply	other threads:[~2022-02-02 18:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 18:32 Jose E. Marchesi [this message]
2022-02-21 10:16 ` Thomas Schwinge
2022-02-21 11:06   ` Jose E. Marchesi

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=8735l1qfuo.fsf@gnu.org \
    --to=jemarch@gnu.org \
    --cc=binutils@sourceware.org \
    /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).