New Snap!Con 2025 Proposal

Call for Proposals

The call for contributions is now open! Tell us your ideas, show us your projects, share with us your insights and materials, spread the wisdom, the gimmicks and the awesomeness!

We’re interested in your

  • Talks - 15 mins + 5 Q&A
  • Lightning talks - 5 mins, Q&A at the end of the session
  • Workshops / discussions - 90 mins, interactive & collaborative, not a talk (!)
  • Projects - 3 mins (Snap! projects only, no slides)
  • BoFs - informal discussions about a shared topic - 30 mins, not a talk (!)

You can submit proposals for Birds of a Feather (BoF)s, Show Us Your Projects, Workshops, Talks, and Lightning Talks. The submission period is open from Thursday, April 3. 2025 and closes Thursday, May 15. 2025. That means you have 32 days left! Snap!Con 2025 will only be as good as the content you present.
Submit early, submit often!

Create a Snap!Con Account Already have a Snap!Con account?
*
*
*

or sign in using

Can't login?

Proposal Information

*
The people responsible for the event. You can only select existing users.
Events are understandable for everyone without knowledge of the topic.
Events require a basic understanding of the topic.
Events require expert knowledge of the topic.

Submission Type and Details

Please select a submission type, then fill in the abstract and extended details.

Description

BOFs are "organic" Birds of a Feather events, with topics proposed dynamically throughout the conference by attendees to spark conversation among the community. BOFs should be a shared conversation among participants; there should not be one person talking the whole time. We are being proactive to collect topics ahead of time, but will still be accepting topics throughout the conference. If you choose to propose a topic, please also describe what the topic is about and suggest a format for a structured and inclusive conversation.

Description

A three minute demo of a Snap! project. No slides, just code :) We’ll also have time for spontaneous project presentations during the Show Us Your Project session, but having submissions helps us to plan ahead.

Description

Workshops provide an opportunity to practice a topic of interest to the Snap! Community. A successful workshop provides materials and ideas that are immediately useful to the workshop’s participants.

We are looking for a well-planned activity in which participants are given a scaffolded framework, e.g., a project to remix, so that they can realistically complete the activity within the hour. It should be interactive, hands-on practice. We encourage a structured lesson that could be “ready for reuse.” The activity should be something that a participant can take away.

Description

A talk is 15 minutes long plus 5 minutes of Q&A.

Please share some implementation of your idea in a proposal (e.g., project), and how you will present your talk. We strongly encourage live demos over slides.

Description

Lightning Talks describe works in progress, new and untested ideas, or opportunities for collaborative work. The purpose of a Lightning Talk can be to start a discussion, find collaborators, or receive input and critique about an idea. We're looking for quick and exciting talks about anything Snap! related, usually but not limited to a Snap! demo.

Describe your talk in more detail. It will be helpful for reviewers to know why you are excited about the topic, and why you think others will be interested too. Outline how you plan to present your topic in 5 minutes. Lightning talks are expected to explore tentative or preliminary work, or even ideas for possible work.

Instructions

Please submit the following items.

  • Title: A title for the Lightning Talk.
  • Abstract: A summary of the Lightning Talk.
  • Description: Describe your talk in more detail. It will be helpful for reviewers to know why you are excited about the topic, and why you think others will be interested too. Outline how you plan to present your topic in 5 minutes. Lightning talks are expected to explore tentative or preliminary work, or even ideas for possible work. Presentations of mature work will not be considered.

Submission Abstract

The abstract is reviewed by the committee and included in the conference program. You are encouraged to include links or other references as appropriate.

Please look at Markdown Syntax to format your text

You have used 0 words. Abstracts must be between 0 and 250 words.

Extended Information

This part of the submission is intended only for the conference committee.

Please use the following as the template for your submission. This will help the conference committee review your submission with all the details they need.

Birds of a Feather (BoF) Template

  • Significance and Relevance of the Topic: Please include information about any trends in relation to the topic and possibly describe (or cite) evidence to that effect. Your objective here is to explain why the topic is significant. You should also justify how your BOF will engage participants in group discussion and enhance future connections between attendees.

  • Expected Audience: Briefly describe the nature and size of the expected audience. If you expect a particularly large or small audience, please explain why. If you have a rough estimate of attendees based on previous years, please include it here. This information can help determine the schedule.

  • Discussion Leader(s): Although correspondence will be with the proposer above, it will be the discussion leader(s) who will be mentioned in the program. Please list any additional such names (besides the proposer) and affiliations here. Be certain that you have their commitments to attend Snap!Con. All discussion leaders must register for Snap!Con and be present for the BOF session.

  • Expertise of Discussion Leader(s): Give a summary of the qualifications of the discussion leader(s) as it relates to the BOF topic being proposed.

  • Proposed Activity during BOF: Provide a brief description of the activities you intend to engage in during the online BOF.

  • Any comments for the committee?: Let us know about anything that may be important.

You may want to use this if you have changed the submission type.

Use this space to include any additional inforrmation that is helpful in reviewing your submission.

Please use the following as the template for your submission. This will help the conference committee review your submission with all the details they need.

Workshop Template

  • Other Helpers for Participants during the Activity: Names and affiliations of any presenters other than the proposer. All presenters must register for Snap!Con and be present for the workshop session, so be certain that you have their commitments before listing them.

  • Significance and Relevance of the Topic: Describe (preferably cite evidence) the significance, timeliness, and relevance of the topic.

  • Rough Agenda for the Workshop: Explain how you will budget the time, including time for attendee interaction. There must be at most 15 minutes of 'front of the room' presentation, with at least 30 minutes of hands-on activities and at least 10 minutes at the end for discussion. The agenda should include details on how participants will be supported in the virtual mode.

  • Expected Audience: State the target audience (e.g., high school teachers, those who teach CS1, research proposal authors, etc). Also, estimate the number of likely participants.

  • Participant Equipment Requirements: What are the needs to fully participate in the workshop?

    • Equipment Required. Participants must have equipment during the workshop in order to achieve the learning outcomes.
    • Equipment Recommended. Participants are more likely to fully achieve the learning outcomes if they have equipment during the workshop.
    • Equipment Optional. Participants may learn more about the topic if they have equipment during the workshop, but having it is not required to achieve the learning outcomes.
    • Equipment Not Required. Having equipment during this workshop is not likely to help participants learn more about the topic.
    • The kind of equipment (hardware and software) participants need (if appropriate).

  • Other Critical Information: Include any other notes that will facilitate assessment of the Workshop proposal.

You may want to use this if you have changed the submission type.

Please use the following as the template for your submission. This will help the conference committee review your submission with all the details they need.

Talk Template

  • Why is a longer format necessary?: How will you use the additional time in your presentation, compared to a lightning talk?

  • If necessary, would you be willing to present this topic as a lightning talk?: We expect to have many more slots for lightning talks than longer talks. If it is the case that we have too many submissions for longer talks, we may offer you the opportunity to present this as a lightning talk.

  • Summary: Provide an expanded summary of the talk’s goals, intended audience, and relevance to the Snap! community.

  • Any comments for the committee?: Let us know about anything that may be important.

You may want to use this if you have changed the submission type.

Please use the following as the template for your submission. This will help the conference committee review your submission with all the details they need.

Lightning Talk Template

  • Description: Describe your talk in more detail. It will be helpful for reviewers to know why you are excited about the topic, and why you think others will be interested too. Outline how you plan to present your topic in 5 minutes. Lightning talks are expected to explore tentative or preliminary work, or even ideas for possible work. Presentations of mature work will not be considered.

  • Project or Demo Link: Include a link to a Snap! Project or demo if you have one you're showing off.

  • Any comments for the committee?: Let us know about anything that may be important.

You may want to use this if you have changed the submission type.

Please look at Markdown Syntax to format your text

Please include any scheduling constraints.

e.g. Are you only attending certain days?

Sign In

or sign in using

Need Help?