Skip to content

Commit

Permalink
add info for session-leaders
Browse files Browse the repository at this point in the history
  • Loading branch information
sujaikumar committed Jul 26, 2023
1 parent 479c57c commit c8a1ac2
Show file tree
Hide file tree
Showing 2 changed files with 67 additions and 0 deletions.
Binary file added docs/assets/BGA23_logo_transparent_325.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
67 changes: 67 additions & 0 deletions docs/session-leaders.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
---
title: Information for Session Leaders
description: Information for Session Leaders at Biodiversity Genomics Academy 2023
---

> Find all our [planned and proposed sessions here](../sessions)
## Stage 1

1. Choose your time slot between 1st and 30th September
2. Confirm your session title

I will send you the link to a google sheet where all current sessions are listed (more will be added)

- Please copy and paste your session to your preferred slot as long as you leave an hour between sessions.
- You can take 1 hour or 2 hour slots (even if you only need 1.5 hours). Or you can take 1hr slots across 2 days if you prefer (I've shown BlobToolKit across two days as a tentative example)
- If you can only do a slot that is already taken, please [contact me](mailto:sujai.kumar@sanger.ac.uk)
- The slot times are UTC, so [please adjust for your time zone](https://www.timeanddate.com/worldclock/meetingtime.html?iso=20230915&p1=224&p2=41&p3=45&p4=4&p5=37&p6=170&p7=176&p8=33&p9=240&p10=22){:target="_blank"}
- Weekdays are preferered, but weekends are fine too as this is a global online audience
- The order of sessions is approximately the order of these tools/resources in a genome project
- Ideally, we would like the final scheduling in this order too, eg keep GoaT/Smudgeplots/BUSCO in the first weeks, Ensembl Annotation/ENA/EBI towards the end. But this is a nice-to-have, not a must-have

## Stage 2

To be finished by 25th August (ideally). I will send reminders, but please [email me](mailto:sujai.kumar@sanger.ac.uk) at any time if you have questions/thoughts about any of these :-)

1. Decide format - zoom meeting or webinar
2. Get session materials ready - slides/text/examples
3. Set up GitPod, if needed
4. Choosing a repeat session format (live or recorded)

### 1. Decide format

- By default we want to have zoom meetings where participants are free to ask questions in an interactive environment.
- However, if we end up with, say, more than 30 registrations, then we will ask you if you want to restrict attendance, or switch to a webinar format where only you will be talking live, but participants can ask questions in real time using a text format (Discord or GitHub Discussions or a combination, to be decided).
- Only registered participants can join live sessions and ask questions.
- I will be on hand to coordinate and assist with all formats. So you don’t have to worry about setting up rooms, monitoring questions or chats etc.

### 2. Get session materials ready

- For each session, we will have a GitHub repository at github.com/bgacademy23/SESSION which will also show up publicly at BGA23.org/SESSION and you will have full write access to this repo.
- This page will have standard basic info such as Title, Description, Who is it for, What you will be able to do by the end of the session, Session Leader / Affiliation, How to register/connect etc.
- This page will also be the place to put/link your training materials. If you already have a preferred format for sharing session materials (google slides, powerpoint, pdf, website, etc) then that’s absolutely fine and we will simply link out to them.
- However, if you want to use markdown files (one or more) that will automatically get turned into web pages at BGA23.org/SESSION, then I can walk you through that. Or if you’d like to do that but don’t have time to figure out, then I’m happy to upload/transform everything to markdown for you.

### 3. Set up GitPod

If your session requires linux command line access. I will help create a .gitpod.yml in the repo, which will allow users to start a server with software already installed and example files ready to go

For example, for BlobToolKit, I created a [.gitpod.yml](https://github.com/bgacademy23/blobtoolkit/blob/main/.gitpod.yml){:target="_blank"} file for installing the dependencies (conda) and pip installing the code, and also added code for starting the docker containers for the API and viewer, which is also nice for end users as they can see what they need to do on their own desktops/HPC server accounts.

To try it out:

- Click on [https://gitpod.io/#https://github.com/bgacademy23/blobtoolkit](https://gitpod.io/#https://github.com/bgacademy23/blobtoolkit){:target="_blank"}
- It will ask you to sign in using GitHub, and for permission to create a gitpod account using your github credentials (this is safe, it asks for read-only access to your GitHub public profile)
- Then it will ask you to launch a workspace (defaults are fine)
- The workspace should take less than a minute to start and will give you a command prompt, where you can run the `blobtools` command to see that everything is installed.

The longest time in any hands-on bioinformatics training/demo session is often installing software, or even getting people to ssh into custom servers which takes some set up - and is not as useful to the end users because it may not reflect their lack of root access on an HPC/workstation set up. The advantage with gitpod is that people can start the session right away in a browser, AND they can see all the steps that were used to set up the machine. I try to do everything in user space without requiring root access (though of course gitpod machines allow you to be root), so that participants can copy the instructions for installing software on a cluster

I will be on hand to create a .gitpod.yml for your session, which you are obviously free to use in all future training materials as well.

### 4. Repeat session

- As BGA23 has a global audience, each session will be repeated at least once to make it accessible to other time zones. We would love for you to do a second live session in a complementary time zone but we realise that that’s a big ask. If you can’t do a second live session, we would like for you to specify a day that you/your team are available to take part in asynchronous text discussions (on discord/ GitHub Discussions) with repeat session participants who will have already viewed a recording of your first session.
- You don’t need to specify live/recorded, or the day/time of your repeat session right away but please keep this in mind when submitting your preference for the main live session.
- Just to clarify - we typically expect all session materials/video recordings to be fully public, in the FAIR / sharing spirit of the Earth Biogenome Project. But if this is a problem for any reason, please let me know and we'll think of a workaround.

0 comments on commit c8a1ac2

Please sign in to comment.