Workshops are an opportunity to teach practical skills, often through hands-on instruction. Workshops sometimes feature writing topics, such as building magical worlds or forming an effective critique group, but we welcome presenters tackling different topics for different audiences: how to plan a book club, where to find resources for library collection development, or how to create a feminist course curriculum based on fantasy reading.

Afternoon classes are also an opportunity to teach skills through hands-on instruction, though these skills tend to be of interest to fantasy readers—but may not be connected directly to literature or other media. Topics may be as eclectic as battle weaponry, self-defense, historical dress or dance, and costume construction.

Audience size for both workshops and afternoon classes will be 25–40 people, depending on available room size.

The boundary between a workshop and an afternoon class can be thin, so please email us at (programming at sirensconference.org) for guidance.

Co-taught workshops or afternoon classes are welcome. Collaborators who have similar or complementary expertise may wish to present together, either to maximize the opportunity for hands-on instruction or to present different skills related to the topic (such as clothing construction and embroidery).

Materials, if needed, must be provided by the presenters. If your workshop or afternoon class is accepted, you are welcome to request a small donation from audience members to defray costs. Please write to (programming at sirensconference.org) for assistance in framing the wording for your summary.

Workshops are always 50 minutes long. If you have a topic that’s shorter than 50 minutes, you might consider finding a collaborator to present on some other element of the topic. Presenters should strongly consider hands-on elements and time for audience questions.

Afternoon classes can range from 50 to 90 minutes. Often these topics require additional time for instruction or practice (or, to provide one past example, taking turns stabbing a bale of hay with battle weaponry). We also often schedule afternoon classes in larger spaces, particularly if they’re demonstration-based or require room to move (such as martial arts or dancing).

Proposal requirements include a presenter biography (50–100 words), a presentation summary (50–100 words), and a detailed abstract (300–500 words). We will publish the biography and the summary on our website and in our program book to help attendees navigate our programming and decide which presentations they’d like to attend. If more than one person will be leading the class or workshop, each presenter must provide a biography, though no supplemental abstract is required for additional presenters. The abstract is for the vetting board. It should explain your topic and approach and be far more in depth than your summary. Presenters of workshops and afternoon classes may present a traditional abstract or, if they prefer, a detailed lesson plan.

Room set-up will depend heavily on the content and design of your presentation, as well as the available room. Set-up often includes tables and chairs with space for audience members to write or craft, though if your topic is physical, we will help clear the room so you have space to work. Projection equipment and a small dry erase board or easel may be available as well (though we will ask you to specify how you will use projection equipment so that we can prioritize it for presentations that particularly need it, and make sure to clear it away if it might be damaged). If the room size warrants, we will provide a microphone (and if we do, we require that you use it, as it makes your presentation more accessible to the audience).

Looking for programming help or inspiration?

• Free Topics: Over the next several weeks, we’ll be tweeting programming topics that are free for you to take, develop, and use in your programming proposal. You might take them as is, you might use them as inspiration, or you might find that they get your brain moving! Follow us on Twitter @sirens_con or check out #SirensBrainstorm.

• More Questions: Email us! You can contact our programming team at (programming at sirensconference.org).

Examples of summaries of past workshops and afternoon classes from Sirens:

• Siren with a Sword: Fencing 101 by Manda Lewis and Marie Brennan: Have you always wanted to join your favorite character on the training grounds where she first picks up a blade? Have you wished yourself in her place as she readies for the attack? This class will provide you the opportunity to do just that! Join us as we explore the history, terminology, and rules of the sport of fencing. Then you’ll take up a foil and practice what you’ve learned with your fellow attendees. You will see that fencing is not simply about overpowering your opponent, it’s about planning and strategy. We recommend wearing comfortable or athletic clothing.

• Ballads and Marching Songs by Ellen Kushner and Ysabeau Wilce: “It don’t mean a thing if it ain’t got that swing!” said Duke Ellington. As authors, we are very aware of how sound and rhythm inform good writing, and so we heartily agree! We also draw on music, particularly traditional music of the fireside and the parade ground, to inspire and support our work. And so: Ellen will sing some of the traditional ballads that inspired her novel Thomas the Rhymer, and Ysabeau will counter with some of the military ditties that form the backdrop to the campfires, parade grounds, and blind tigers of her Califa series. We’ll then turn around and show participants how to create a fresh ballad or marching song that fits the needs of an original fantasy novel.

• Tools and Techniques for the Reluctant Rewriter by B R Sanders: Masterpieces are rarely written perfectly the first time around. Revision, rewriting, and editing are key steps in the writing process, but they aren’t always fun, and they aren’t always easy to master. For many of us, learning to write first drafts is more straightforward and easier than picking up the skills necessary to polish those first drafts. In this workshop, we’ll explore a variety of techniques writers can use to structure their revision and rewriting process to get the most out of it. Writers at all stages of their career and of all levels of expertise are welcome.

• Chainmail 101 and the Steampunk Maker Ethos by Fred Loucks-Schultz and Rebecca Loucks-Schultz: From Bilbo’s mithril shirt to Red Sonja’s infamous bikini, and from steampunk retro-futurism to post-apocalyptic Hollywood movies, chain mail has long been a staple of fantasy literature. Learn about the Maker side of Steampunk, the cross-cultural history of mail both as armor and decoration, the tools and techniques for making modern mail accessories, and then build your own key fob or bracelet in this hands-on workshop.

For more examples of past programming, visit our archive.

Today, we have general programming information, how to find help from real people, tips and tricks for proposing programming, and answers to frequently asked questions about our programming process. Here we go!

Conference General Information

• We will open for proposals mid-April and accept submissions through May 15. All proposals must be submitted in full, including any supplemental abstracts for panels, by May 15, and all presenters must have “checked in” by following the links in emails that we send out when a main presenter indicates there will be a co-presenter.

• The Sirens vetting board will make decisions by June 15. All accepted presenters must be registered and paid for Sirens by July 10.

• We will have three scholarships (a 2021 Sirens registration and round-trip shuttle ticket) available for exemplary programming proposals. We also have one Sabrina Chin “Braver Than You Think” Memorial Scholarship available for a first-time presenter. You can apply for these scholarships as part of the submissions process.

• You can propose programming in a number of formats: papers or lectures (including as a set of pre-empaneled papers/lectures on a single topic), panels, roundtable discussions, workshops, afternoon classes, or a combination of multiple formats. (Please consult with the programming team before you submit a combination, though!)

• You are welcome to present with co-presenters, except for roundtables, which may have only a single moderator. Please note that the person submitting the proposal will be our main contact for the proposal (and in the case of a panel, will be the moderator). Again, please make sure that your collaborators are aware that they will need to confirm their participation by May 15—and in the case of panels and pre-empaneled papers, will need to submit a 300–500-word abstract of their own (note that the vetting board will review all abstracts in determining whether to select a proposal).

• All communication is via email. Please use an email address to which you’ll have access throughout 2021, and that you check regularly.

• Programming is reviewed and approved by an independent vetting board. All proposals are kept confidential.

• Additional information can be found in Sirens’s official Call for Proposals.

Conference Programming Help from Real People

• Free Topics: Over the next several weeks, we’ll be tweeting programming topics that are free for you to take, develop, and use in your programming proposal. You might take them as is, you might use them as inspiration, or you might find that they get your brain moving! Follow us on Twitter @sirens_con or check out #SirensBrainstorm.

• More Questions: Email us! You can contact our programming team at (programming at sirensconference.org). They can’t guarantee your acceptance, but they’re full of helpful advice, and are glad to help you figure out the best format for your proposal, answer questions about the process, and so on.

Conference Programming Tips and Tricks

• Everyone is welcome to propose programming! Sirens is a conference where readers and students present alongside authors and scholars, who present alongside librarians, educators, and publishing professionals. Everyone’s voice is valid, valuable, and necessary to our conversations and our community!

• Look at past programming schedules. Our vetting board knows what topics have been presented in past years—and you should, too, so you don’t repeat them! New topics, or brand-new takes on old topics, will be considered more favorably. We make all our past programming available in our conference archive.

• Go beyond introductory topics and analysis. Sirens is over ten years old, and we assure you, most Sirens attendees are well-versed in basic topics like “Reclaiming Fairy Tales” and “What is Diversity?” Push the sophistication of your topic and your analysis further.

• Consider what type of presentation suits your topic best. We’ll be doing a deeper dive on each of these in the coming weeks, but here’s a preview: papers and lectures are good for experts to convey information or frame an argument; panels are suitable for rigorous debate among experts with differing expertise or opinions; roundtable discussions are great for topics where every audience member will have an opinion or contribution; and workshops and afternoon classes are perfect for hands-on explorations of practical topics.

• Focus on one or two proposals rather than several. This will help ensure your proposals are well-prepared and well-argued—and will increase their likelihood of acceptance.

• Choose your co-presenters wisely. We strongly encourage you to seek out co-presenters with a variety of expertise, perspectives, and identities. Differences in expertise can bring additional thoughts and approaches to your work, while different perspectives and identities can enrich discussion and debate over your topic. (Bonus tip: If your topic is for people with complementary expertise to present information, we strongly encourage you to consider a paper or lecture with co-presenters, rather than a panel; the panel format is best suited for discussion and debate among panelists with different perspectives.)

• Leave enough time to write a thoughtful summary and abstract. Since these descriptions are what the vetting board will judge your proposal on and will determine fellow attendees’ interest in your topic, it behooves you to not wait until the last minute! This is especially true for pre-empaneled papers and panels, where co-presenters must also submit an abstract by May 15.

• You are not required to present on this year’s theme of villains. Proposal topics must be relevant to Sirens, but do not need to address our theme for this year. Please do be sure that, at minimum, you’ve mentioned how your topic relates to fantasy!

Conference Programming Frequently Asked Questions

What are the requirements for being a presenter at Sirens?
The only requirement is that you must be a Sirens attendee, which also means you have to be 18 years old by October 21, 2021. Otherwise, everyone is welcome to propose programming—and if accepted, to present it!

How can I find co-presenters or panelists?
You can tweet @sirens_con or post on the unofficial Sirens Attendees Facebook group. You might also be able to find co-presenters or co-panelists at our programming chats.

How many proposals can I submit?
There is technically no limit, but we recommend focusing on one or two as it usually makes for better-prepared (and better-received) proposals. If you already had programming accepted for presentation at Sirens 2020, we ask that you not submit additional proposals during the 2021 submission period.

Can I change my proposal later?
Before the May 15 deadline, you can submit a correction or contact us to withdraw and resubmit the proposal. Following May 15, however, we will pass your proposal on to the vetting board and you can no longer make changes.

Can I contact the vetting board about my proposal?
Please direct any questions to (programming at sirensconference.org) instead. Vetting board members only review proposals, and we ask them to keep their reviews confidential.

Can I request a specific day and time to present?
The schedule depends on our ability to track presentations by type, theme, and audio-visual needs, so we can’t accommodate schedule preferences. If you have an immovable conflict, such as your grandmother’s 100th birthday party, please write to us at (programming at sirensconference.org).

I have more questions!
We have more answers! Write us at (programming at sirensconference.org).

How to Propose Programming for Sirens

Let’s start at the beginning, shall we?

Programming, for Sirens, is the dozens of hours of papers, lectures, panels, workshops, roundtables, and afternoon classes that make up the heart of the conference. While a thousand conversations happen at Sirens every year, the true vanguards of those discussions are the brave and brilliant individuals who share their wisdom and expertise as part of our programming. See the archives to find out more about the kinds of topics and discussions that have been presented in the past.

So how does Sirens create its programming?

We don’t create the Sirens programming. You do! We don’t want Sirens to be limited by the interests, knowledge, and networking of our staff, so we invite our attendees — readers, scholars, librarians, authors, and more — to propose programming for our schedule. And each year, dozens of individuals answer the call: they create, craft, propose, and present the lectures, papers, panels, workshops, roundtables, and afternoon classes that become the programming at Sirens.

A special note: We want our programming to represent a broad range of perspectives, experiences, and identities: readers, scholars, librarians, educators, publishing professionals, and authors, of course, but also individuals of different genders, sexualities, races, religions, and abilities. Similarly, we hope that, regardless of your vocation, your level of experience, or how many years you’ve attended Sirens, you’ll take a crack at sharing your thoughts and expertise as part of our programming. Every voice is important at Sirens, including yours.

And how does Sirens choose its programming?

Each year, an independent vetting board—a diverse group of tremendous individuals who know and love Sirens—review the proposals for thoughtfulness, relevance, and inclusiveness, and then select which ones to include on that year’s programming schedule.

• Thoughtfulness: This means the vetting board considers the research, logic, and sophistication of the arguments. Is the proposal well-conceived? Is the proposal well-argued? Is it interesting? Is it innovative?

• Relevance: Is the topic relevant to Sirens’s overarching topic of gender and fantasy literature? The topic doesn’t need to specifically address the theme of any given year, and doesn’t have to be about gender and fantasy and literature (but if your proposal doesn’t address at least two of the three, you might want to consider how you can make your topic more relevant to the Sirens audience).

• Inclusiveness: Sirens values diverse perspectives, experiences, and identities. Does your topic address an inclusive selection of literature? Do your co-presenters represent a variety of perspectives, experiences, and identities, whenever possible?

In crafting your presentation, please also consider the following:

• Audience: You are likely to find your presentation audience composed of voracious, critical readers, as well as accomplished scholars, librarians, educators, authors, and publishing professionals. Further, Sirens attendees tend to be quite experienced in discussing women in fantasy literature, as well as related topics such as feminism, social sciences (and occasionally hard sciences), and writing. Please plan the sophistication and complexity of your proposal accordingly.

• Repetition of Past Presentation Topics: The vetting board is familiar with programming presented at Sirens in the past, and duplicative topics are often considered less relevant. Please make sure that you have reviewed our archive page before deciding on your topic and that, if you intend to propose a similar topic, you highlight the innovation of your work in your proposal.

How does someone propose programming?

Sirens operates its own proposals system specifically for programming proposals. We’ll open this system on mid-April and close it May 15, which is this year’s deadline for proposals. After May 15, our vetting board goes to work.

You need five things for a proposal:

• Personal information: Your name, contact information, and a third-person biography that we can use on our website and in our program book;

• A summary: 50–100 words about your topic and approach, which we’ll also publish on our website and in our program book (see our 2019 summaries for examples)

• An abstract: 300–500 words explaining your presentation and approach to the vetting board; this should be far more in depth and should demonstrate your research, analysis, and conclusion on the topic

• Audiovisual requests: Information on your requested audiovisual equipment for your presentation, if any

• Contact information for any co-presenters: Your co-presenters will then receive an email asking them to provide their personal information and, in the case of panels, a supplemental abstract of 300–500 words demonstrating the perspectives and expertise that they will bring to the panel

So let’s do this!

We know that the proposal process can be intimidating, especially for those new to Sirens. It takes a lot of courage to put your thoughts and analysis out there, first to a review board and then at Sirens itself. But each year, dozens of individuals screw their courage to the proverbial sticking place and, in doing so, make Sirens smarter, more thoughtful, more interesting, and just plain better.

We hope that that will include you this year!