CodeRefinery
      • 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
    # NeIC AHM 2021 workshop "about organizing online workshops" ###### tags: `NeIC` :::info ## Resources - This document: https://hackmd.io/@coderefinery/ahm-2021 - Slides: https://cicero.xyz/v3/remark/0.14.0/github.com/coderefinery/neic-ahm-2021/main/slides.md/ - AHM timetable: https://indico.neic.no/event/172/timetable/#20210128 - Blog post: https://coderefinery.org/blog/2020/07/31/mega-coderefinery/ - Presentation at CarpentryCon 2020 (video): https://2020.carpentrycon.org/schedule/#session-32 ::: This document will be archived openly, please don't include identifying information. ## Ice-breaker question **Are online workshops better or worse compared to in-person? Can you name one advantage of online workshops?** (please write here - "pen" button top left of the page) - advantages: - no need to travel - easietr to co-organize workshops with people from other countries - easier to record the presentations - easier to extend the workshop in time and allow for some free hours so that people can get back to other duties a well or use that time to consolidate the material - disadvantages: - harder to *connect* with the participants, tricky at the beginning - when some people were not so used to online tool - all fine now, though - harder to socialize with participants - may be challenging to follow unless one has [at least] one external screen - casual attendance for workshops that you wouldn't invest travel and in-person time to - comfortable chair - advantage: Can attend many events more easily - disadvantage: Can attend many events more easily - ... - in some cases could be more scalable +1 - advantage: no travel, disadvantage: no travel +2 - ... - can attend many more workshops! disadvantage: tiring! - Attendees seem more enclined to ask questions, which they would not dare to do in a face-to-face event +1 :::success ## Outline - (5-10 min) Introduction and icebreaker - Briefly introduce organizers - Introduce hackmd - Icebreaker - (20 min) Presentation - CodeRefinery project (Radovan) - Vision for online training (Radovan) - How we did it (Richard) - Roles (Anne) - (10-15 min) Collaborative work (in breakout rooms) - Share something you do or you have seen which really improved the experience - How can workshops be more inclusive? - List things that often go wrong or are often missing in online meetings/workshops - (15 min) Discussion (back in this room) - (5 min) Feedback about this workshop ::: ## Questions/comments on slide presentation - You can ask questions like this - You'll get an answer like this - Or raised via voice ## Collaborative work Until xx:20 ### Share something you do or you have seen which really improved the experience Our "main" workshop room: - Separate people responsible for content and for zoom and for keeping time and to step things if we go overtime or need a break - Recordings made available - Presentation template specifically for video presentations - Tag/annotate video so that visitors know where in the video to jump to see a particular segment - Icebreakers in intervals, not only at the beginning but also on day 2, day 3, ... Discussion room 1: - having a Zoom host different than the lecturer - small breakout room - having enough breaks +1 - Add some fun sessions! +1 - extra session dedicated for technical details: software installation, Zoom check, ... - I found it complicated to organize my screen to follow the main speaker, do things on my terminal, check the QA until I started to use a 2nd screen (TV) in addition to my PC : that could be a "recommended" option - not to have a full day online meeting - Zoom improved over the last months, in my opinion - Backup for technical zoom problems (links) - Sometimes the Helper was not much /experienced and too shy for sharing his/her screen, which was blocking learners also: maybe "training" a minimum the helpers in advance and giving them instructions about how to start would help - Have a "slide" presenting on how to organize your screen (windows with hackmd, chat, etc.) - if one has one screen only - Icebreaker questions do a good to get participants started being active on e.g. HackMD. - I find it tricky to motivate newbies to use the HackMD. I have been in workshops where one uses Google docs, which may be easier for some - no need to learn an extra syntax - - How to motivate persons to write feedbacks? - Tell your learners which communication channel to use and when - Deliver some kind of "certificate" that is recognized elsewhere (may require the completion of some exercise, or only attendance), especially now that this becomes common (for example with HPC related events) Discussion room 2: - Nerdy t-shirt competition (one of the first types like this that worked!) - Asynchronous discussion in document - Chat in addition to meeting (if doesn't overload...) - Work pages to list other available resources easily - Helpers in breakout rooms - Demonstration and practical examples, share screen. - Enough breaks! - and on time - Partial attendance / attendance with less than full attention (but watch overload) ### How can workshops be more inclusive? Our "main" workshop room: - Easier to ask questions if the questions are asynchronous in chat or document - Recordings allow to rewatch, stop, and revisit - Icebreakers in intervals, not only at the beginning but also on day 2, day 3, ... - Multi-purpose social ice-breakers to also solve Discussion room 1: - I noticed that sometimes people attend but do not have the "correct" technical background, which makes it difficult for them to follow and for others in their breakout room: why not have some kind of "test" or selection with basic questions the candidate participants would have to answer to assess their level and put them in relevant rooms (absolute beginners, "normal", advanced...) - asynchronous participation made possible - good advertisiment - using different channels/email lists, possibility to check the recordings afterwards, if the schedule does not fit or in a different continent - survey prior to the course - pooling into groups. All on same level, or have different levels? - Turn up is often low (many register but do not attend in the end), whereas for paying events that does not happen so much, although the quality of the training provided is second to none: would asking for a financial contribution motivate learners more to attend and participate? Discussion room 2: - Asking question anonymously - downside: record everything and publish it - Better ways to separate attendee questiosn from recording - Prepare agenda carefully, leave enough room for discussion. - ### List things that often go wrong or are often missing in online meetings/workshops Our "main" workshop room: - Not enough breaks and too long sessions - Not always easy to get participants start to speak - Present slides the same way as they would be presented in person (not taking into account small screens) - Recordings - In-person "chit-chat" and networking during breaks/dinners - Clearly communicate consent Discussion room 1: - trickier to help with technical issues - breaks - breaks and social sessions need to be separate - when you have a technical problem (loss of connection, computer crash or similar) you can be lost and never catch up - social interaction, Menti could help though :D - distractions from other things on your computer like banners popping up for incoming email, slack channels and the like. Remind people to put program notifications on snooze. - People tend to join a particular breakout room not based on the topic but on who attends ("important" peopel attract attendance), and they often wait until the last minute to join Discussion room 2: - Long sessions - Connection problems - Not adapting agenda - running too long 9-5 - 2-3 afternoons better than one full - Events back-to-back with no buffer in between - Very hard to get people's attenion when you can do other things at the same time. - ## Feedback List one thing that was particularly good and one thing that should be changed or improved for next time. Good: - very nice overview on how the CodeRefinery team is organizing workshops, I particulary like the distribution of tasks - particularly important for very large workshops - good breakout room discussions +1 - it was really nice to hear how you saw pandemic and lockdowns also as an opportunity for you in CodeRefinery - cool to hear about the large number of participants that attended CodeRefinery workshops - it was really good that the structure of this workshop was something that could be used in our own workshops To improve: - ... - Is it possible to provide advice not tied to the codeerefinery (so others can benefit) - I think a lot of these ideas can be used in other workshops. It is very hard to talk about something that you have not gone through yourself. - the "summary" session was bland and not very summarizing - (both + and -) Tying 1 name to a role in the workshop. It would seem that it is always the same persons with the same roles. But I may have missed part of the presentation.

    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