Template for proposing a session at the unconference

[SusanneWenzel]

* This should go to the readme **

Future Challenges: an Unconference

Helmholtz AI and Helmholtz Imaging Conferences 2023

👉 For the conferences full programme visit Helmholtz AI Conference 2023 and Helmholtz Imaging Conference 2023

The idea of an unconference is to form a programme together 🤝 Please post ideas for sessions as issues. You need to have a GitHub account in order to do so.

💡 Feel free to start a rough description of your idea as a new git issue and discuss with potential collaborators. 📜 Rule 1: One issue per potential unconference session 🍒 Comment on existing issues if you have any thoughts or questions about it. You can also mention how you could contribute or anything else relevant to the idea.

📜 Rule 2: At the end there should be an abstract addressing the following items.

• Title
• Description, pointing out, e.g.
  • Question to be addressed
  • Task to be solved
  • Final outcome or even product, e.g., a blog post, a draft for a white paper, an outline for a software prototype, a list of rules to follow, a list of answers to specific questions
• Organizer(s) in best case also name a representative. Don't forget to add contact information, i.e. email or github ID
• Speakers, if applicable In case the format foresees an introduction, short talks etc.
• Format E.g., talks followed by open discussion, hackathon like format, world café, etc. You can find a list of common unconference formats here. But at the end its up to the organizers
• Timeframe Specify the time you foresee for this session, e.g., 30min, 1h, ..., up to 3h
• Number of participants Define the minimal number of participants you need to work on the specified task. Is there a limit to the number of people who attend this session?

📜 Rule 3: Please make sure that your session ideas are understandable to everyone. We come from different fields. Use as little jargon as possible. 💁

to be discussed We will review proposals in a two-stage process. On May 15 no more new issues are accepted. Until May 29 the existing proposals for sessions can still be discussed, merged, closed, or finalized. We will decide on the final program based on what we have after this second deadline.

If you run into any problems with this process, please contact the program chairs tbd and/or tbd.

Many thanks for inspiration and help in setting this up to the team of deRSE23 unconference breakouts, Heidi Seibold, Robert Speck, Guido Juckeland

• Typical unconference formats
• Helpfull tips

** This will go to the issue template ***

Title

Description

pointing out, e.g.

• Question to be addressed
• Task to be solved
• Final outcome or even product, e.g., a blog post, a draft for a white paper, an outline for a software prototype, a list of rules to follow, a list of answers to specific questions

  Organizational

  Organizer(s)

  In best case also name a representative. Don't forget to add contact information, i.e. email or github ID

  Speakers

  if applicable In case the format foresees an introduction, short talks etc.

  Format

  E.g., talks followed by open discussion, hackathon like format, world café, etc. You can find a list of common unconference formats here. But at the end its up to the organizers

  Timeframe

  Specify the time you foresee for this session, e.g., 15min, 30min, 1h, ..., up to 3h tbd

  Number of participants

  Define the minimal number of participants you need to work on the specified task. Is there a limit to the number of people who attend this session?

[HeidiSeibold]

This can be done even more automated: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

[SusanneWenzel]

Perfect! Good to know. Then let's discuss the content and then I'll transfer it to the settings

[helenehoffmann]

• Why two names for organizers? From my point of view, one is enough.
• I think I would rather say: Title, Description, Desired Outcome instead of abstract
• I think a timeslot of 15 minutes is too short, maybe start with 30 min.

I think most points are fine. These are just some minor additions ;)

[SusanneWenzel]

1. then organizer plus representative (I'd like to have a backup, but I'm also ok with one)
2. ok, also though about description instead
3. we said 15 min in our discussion, but I'm fine with 30 min, too. What about the max length?

[helenehoffmann]

3 h is OK I think, only if we have a lot of contributions we might need to shorten some.

[ikurecic]

Notes from the meeting:

• Should include information to issue authors that they'll be expected to give a <1' pitch at the start of the event.
• Should note to issue authors they will need to write a summary/conclusion of their session by the end of it (it would allow us to track successes, but also give a chance to people who didn't attend to potentially join the new team's plans).

[SusanneWenzel]

Readme and template for issues are setup. Thank you for the discussion