Skip to content

Instantly share code, notes, and snippets.

@shriram
Last active November 27, 2025 13:42
Show Gist options
  • Select an option

  • Save shriram/45709ed86915fdec46337db9660bb24e to your computer and use it in GitHub Desktop.

Select an option

Save shriram/45709ed86915fdec46337db9660bb24e to your computer and use it in GitHub Desktop.

Call for Papers, Demos, and Discussions

Workshop Title

Dates

URL

Scope

ThEdu is open to all aspects of logic education. This scope ranges both across types of logical tools — proof assistants, model checkers, model finders, rich type systems, property-based testing, and more — as well as forms of education: tools, courses, books, tutoring software, and more. The only (strict!) requirement is that every submission be about education of logic.

Activities

ThEdu will have multiple kinds of activities:

  • Regular paper presentations
  • Plenary demos, where the presenters shows their tool to all the attendees (there is limited time for these)
  • Hands-on demos, akin to a poster session, where participants can visit several tools and interact with each one with the help of the demonstrators (there is time for many more of these)
  • Discussions on challenges and opportunities in logic education, such as: designing usable interfaces, evaluating educational impact, adapting tools to diverse audiences, and integrating tools into curricula

Submissions

In your submission, please make clear what kind of activity you are proposing. (If you propose more than one, please submit each one separately, since they will be considered independently.)

Papers: These should be in the usual form of a scientific paper. Are submissions required to be original unpublished work which has not been submitted for publication elsewhere?

Plenary Demos: These should describe the artifact (tool, Web site, book, etc.) to be demoed. The submission should explain what the presentation is likely to entail. Please note that we may have a very limited number of slots for these; we encourage people requesting plenary demos to also submit a hands-on demo proposal.

Hands-On Demos: These should describe the artifact (tool, Web site, book, etc.) to be demoed. The submission should make clear what a person visiting the demo might do. We recognize that not all of these will necessarily involve the visitor interacting with a computer (especially depending on the nature of the artifact itself); it may be a plenary-style demo but with much more opportunity for human interaction.

Discussions: These should crisply describe the topic and explain why it might lead to an interesting discussion. A topic might either be a statement of a position (asserting some claim) or a question (e.g., asking the community how it has managed to address some problem). Like a good research question, a good discussion topic should ideally not have a binary answer but instead allow for a range of views. Furthermore, a topic on which almost everyone might agree (e.g., that there is insufficient funding) is not likely to be interesting!

Mechanics

All accepted submissions will be made available through the conference site.

Submissions must be between 2 and 10 pages (excluding bibliography and potential appendices). We anticipate that Discussion Topic submissions might be on the shorter end of this range, but all the others will be at least 5 pages long and probably even longer.

Please use the format FILL. Submit using FILL.

At least one of the authors of each accepted submission is expected why not REQUIRED? to attend and present their work.

Important Dates

Extended Abstracts: FILL

Author Notification: FILL

Workshop Day: FILL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment