Nordic RSE Group
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Help
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    --- tags: unconference --- # Unconference talk preparation (for speakers) Thanks for offering a talk at the Nordic-RSE unconference. This gives some ideas, based on our experiences and expectations. The main thing to remember is that our talks are less formal and hopefully more interactive. This means that you may not need to prepare as much as for other academic talks (and certainly need less effort on fancy graphics). A good outline of some points to cover and then a demo is plenty. ## Audience interaction This is the most importart part which everything else is build around, so lets start with this. We have found that using HackMD is a great way to do this: it's an online interactive document a lot like Google Docs and so on, but with markdown. You can give it a try here: https://hackmd.io/new . All talks will have some HackMD to go along with them (provided by us, or you can make one specific for your talk). People will ask questions/give comments, and perhaps someone else in the audience will answer. You can discuss by voice anything interesting, too. HackMD can also be used to share links with the audience. The advantages of HackMD is that we aren't limited to one person talking at a time (or biasing towards people who are more willing to interrupt others). There is also the opportunity for more answers. Of course, you should always accept questions by voice, too - during the discussion time it tends to become a combination of both. We recommend that you keep it where you can view it at all times while you are presenting. If you share on your screen itself during discussion times (or a little bit during the talk itself) it can encourage people to interact that way. https://coderefinery.github.io/manuals/hackmd-mechanics/ If you create a new HackMD for your session, please make sure to reference it from https://hackmd.io/@nordic-rse/unconference and also make sure it is editable by others. ## Preparation You have probably practiced giving some events via Zoom, so likely there is not much technical difficulty. It is perfectly fine and normal to ignore "slides" and have free-scrolling text as your main points. When coupled with demo and screen-sharing, this will make a great event. With the Zoom client application, you can "share a portion of the screen" (under advanced). If you can, it is good to not share your full screen, but only half, vertically. This allows the audience to view your demo at the same time they have half of their screen available for their own work/follow-along/hackmd/etc. If you present a demo in the browser or terminal or editor, please make sure to check the font size and contrast. It can be also useful to share your [terminal history](https://coderefinery.github.io/manuals/instructor-tech-setup/#terminal-history-window). ## Content We generally like to have lots of discussion, and for longer sessions it would generally be a good idea to plan for half of the time for your presentation and half for discussion. It's good if the content is available online so that anyone can see it. You are probably the expert here, so we don't need to say much. ## Mentoring/help preparing If you would like help preparing, the best is to ask everyone! If you sign up for the Nordic-RSE chat and give your drafts, people will comment. Don't worry, it's normal that we ask for feedback on work-in-progress things. You can learn about the Nordic-RSE chat here (combined with the CodeRefinery chat) here: https://coderefinery.github.io/manuals/chat/ . We recommend that you ask in the #nordic-rse stream, make a new topic and ask away! You could also ask someone to take a look in private, but public is probably better overall. If you are still in the planning phase, you could (for example) either chat with your thoughts or write your ideas somewhere (HackMD is good if no where else) and then ask for feedback. If you do have some content already, make that available for browsing and you can get feedback that way. We have also scheduled a general call/mentoring session where you can join and talk about things, which all presenters are invited to. You can join there for discussion on content and a tech check, if you want. It is at https://uit.zoom.us/j/63566985867 at 13:00 CEST on Thursday 2021-06-24. We hope to see you there! ## Dynamic schedule adjustments We might already schedule your talk in advance, but also it is likely to be scheduled dynamically during the unconference, too, after we see all possible submissions. In addition, the point of an unconference that we can add new sessions during the event. For example, a short talk can turn into a medium discussion on the next day. Perhaps some sessions can spawn other session ideas.

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully