-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upload draft blog post to recap UGM and 2024 workshops #404
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thank you so much for putting it all together @jennaswa !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fantastic summary, thanks @jennaswa. I left a few minor comments but LGTM.
The use of branches for different workshops is to be discussed elsewhere.
|
||
### Februrary 28th: Introduction to MDAnalysis and Molecular Nodes (Online) | ||
|
||
Around 40 people joined us live on February 28, 2024 for an online workshop, during which 4 instructors (@fiona-naughton, @lilyminium, @yuxuanzhuang, @BradyAJohnston) introduced the MDAnalysis package and provided an interactive tutorial for visualizing MDAnalysis data in [Molecular Nodes](https://bradyajohnston.github.io/MolecularNodes/); the [recording](https://youtu.be/3zKBjnRnAMg?si=cnGSQxyUmzc9zCDd) is available on our [YouTube](https://www.youtube.com/@mdanalysis3040) channel. All workshop materials and installation instructions are publicly available on the MDAnalysis/MDAnalysisWorkshop2-Intro0.5Day GitHub repository on the ['feb24-ws' branch](https://github.com/MDAnalysis/MDAnalysisWorkshop-Intro0.5Day/tree/feb24-ws). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Non-blocking for this post, and I think I raised this elsewhere (and it is definitely better discussed elsewhere). Using branches makes things complicated to maintain, and hard for users to dig out the actual material (they might accidentally switch branch, or if they use Google they will never land on a branch other than the default one). It would be better to make a proper release for each workshop.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same comment applies to the branches below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, there was some discussion started about this on Discord earlier this year in January: https://discord.com/channels/807348386012987462/817022693676285992/1201343337878265887. I'll also add it to the next business meeting agenda, though there might not be time to get to it, so we don't lose track of trying to reignite the conversation and making a longer term plan.
No description provided.