CppCon 2022 Program Submission

Use this form for main conference program submissions.

Presentation Delivery

CppCon 2022 has both onsite and online sessions. Most sessions are onsite, but a number of sessions will be accepted for individuals that cannot attend in person.

Onsite: Sessions delivered onsite may be "re-broadcast" online on a delayed basis. Presenters delivering onsite sessions may be asked to join an online "chat room" while their session is shown online, to host an online Q&A session, and/or to engage with online attendees in other ways.
Online: Presenters delivering online sessions will be expected to attend a "dry-run/tech rehearsal" session in the week before the conference.
What is your preference?

Presenters

Please only include presenters that will present. Co-authors and other contributors not presenting can be recognized in your presentation.

Add Presenter

As you would like it to appear in the conference program.

For conference use only. We will not share this with third parties except as required to run the conference.
We strongly recommend using a personal email address because employment situations change and companies' spam filters sometimes reject our messages to you.
Please use this email consistently for submission, conference registration, Sched.com, etc. If you use different email addresses, our software gets confused and cries itself to sleep at night.

(Optional) We will include this when tweeting about your session.
We need your twitter handle, not the name associated with your account. (Hint: Twitter handels do not contain whitespace.)
We support multiple handles seperated by spaces, so you can do this: "my_handle company_handle" or "@my_handle @company_handle"

The submitter's school, company, or other affiliation. If you are unaffiliated, just enter your own name.

Your home country.

Please use the third person, avoiding "I" or "me."
Use your full name (once) in the first paragraph and your first name once in each subsequent paragraph. Otherwise use your pronouns.
Aurora Argento graduated from Sapienza University of Rome where her focus was robotics.
Since graduating, Aurora has worked for Altar.io where she is now a Cloud Computing Senior Developer.

Each submitter will be given the opportunity to edit their conference bio to include a photo, website, and public social media contacts. For now, we just ask to help the Program Committee better understand your background.

Please enter the URL of a headshot appropriate for the conference program.
If you leave this blank, we'll use what we find on the net and/or nag you ceaselessly to supply a photo.

Mentoring responses are not used by the Program Committee when evaluating submissions.

Demographic information is optional and is not used by the Program Committee when evaluating submissions.

Financial assistance is available for accepted submitters to offset some of the costs associated with attending in person.

Submission Info

The information in this section is directed to attendees and must be suitable for the conference web site.

Please use AP style title case. Acronyms should be all uppercase. Code elements such as keywords, function names, etc that appear in your title should have the case they would have when written in code. Subtitles should be set off with colons, not dashes, using a space after, but not before the colon. See also Boost library naming rules.
For example, "My Adventures With Boost.Asio: return to Sender"

Please include a comma separated list of tags for your session.
Tags are used by the scheduler to avoid concurrent sessions with strong audience overlap.
Think of tags as tracks and list the tracks that your session best fits in.
Strive for the general, not the specific: "testing," rather than "unit tests."
Use lower case except for proper nouns and acronyms. Spell out acronyms unless they are more likely to be understood as acronyms: "artificial intelligence" rather than "AI" and "GUI" rather than "graphical user interface."
For example, "games,cross platform,I/O,C compatibility,HTML"
For additional information, see our tagging guide.

Select a session type or enter your own.

Standard sessions are 60 minutes. Preferred, min, and max can all be the same value.

Audience

If your presentation spans levels, such as intermediate to advanced, check all that apply.

Examples: library authors, application developers, game developers, etc. A quality description helps your audience find your submission. Please keep it short and sweet. Full sentence not required.

Abstract

As it should appear in the program. About one to three paragraphs.
This is your pitch to both the Program Committee and to potential attendees about why they should see your presentation. (Use the "Comments" field below for remarks intended only for the PC.)
Try to answer the reader's questions, What will I learn? and Why is this important to me?

To facilitate a double-blind review process, please avoid statements that remove all uncertainty about who you are: Instead of: This presentation is a follow-on to <previous presentation>, my talk last year. consider: This presentation builds on <previous presentation>, from last year’s conference. It isn’t necessary to make it impossible to guess who you are, but please allow for some uncertainty.
Note: Conference organizers do not modify abstracts without a submitter’s consent, but we reserve the right to make appropriate edits for anonymization purposes.
Note also: After a submission has been accepted, presenters can edit their abstract as desired without this restriction.

To the organizers

The information in this section is not published on the website as part of the conference program, but is intended only for the Program Committee and/or other conference organizers.


Encouraged, but not required. Note that videos will be sponsored (with pre-roll, etc.).


Discouraged, unless required by employer. Holding a recording may significantly increase the deployment time of your session's recording.

List material that you will submit to the public conference repository: (slides, source code, etc.)

Support requirements are not used by the Program Committee when evaluating submissions.

Specify any special (AV or other) requirements for your session.

For onsite presentations, you may assume HDMI connectors as well as power.
Please let us know how we can accomodate any accessibility requirements you have.

You'll not be held to this—we understand that this is a snapshot in time.
Feel free to include any comments that will help the Program Committee understand what you intend to present (and/or omit).

If you’ve presented this submission before, please tell us where and when.
We do accept submissions of sessions presented at other conferences.
Repeats of sessions from a previous CppCon are accepted, but, because sessions are recorded, the bar for repeats is higher than for new sessions.
Repeats of successful workshops (session during which audience members perform exercises and/or write code) are always welcome.

Please include the URL of a video of you giving a technical presentation (as similar as possible to your proposal).
We do accept submissions from first time presenters, so this is optional, but if you have a recording of yourself presenting, it helps the PC evaluate your presentation abilities.
You may use a video that you've made and posted yourself. If no such video exists, consider a link to a slide deck that you've created.
Feel free to add any comments you feel necessary about this material.

Anything you'd like the Program Committee to know about your talk.
This would be a good place let reviewers know your pronouns.
If you are making multiple submissions, but don't want all of them to be accepted, please let us know your limit and if you have any preferences about which are accepted.

If you feel that your submission is appropriate for one of the conference's specified tracks, (the Back to Basics Track, the Embedded Track, the Scientific Computing, the Software Design Track, or the Tooling Track) please note that here.