# 2021 H1 (first half of year) master plan Research Software Hour is a web show about software, data, computing, and everything related to them. Our goal is to complement formal training with a more informal "practical tips and tricks". **You** can help however you want: suggest topics, present topics, advertising, be a helper. Let us know, and we will provide training for you. In this document, we are trying to pre-decide most topics for the spring (7.jan - 17.jun = 24 thursdays), however we certainly don't need to do something every week, or plan every week: some can be ad-hoc. - [name=Radovan] Jan 7 may be too soon, I would really like that we discuss via voice before we announce the first show and that we have enough time to advertise. Another topic for discussion is frequency: weekly vs. every second week. Having a fixed weekly slot makes it easier to not miss an episode. But weekly rhythm can be a lot of work, even if we minimize preparation. ## Our goals The goals for Research Software Hour 2021 H1 include (enter your goals here): - Pre-plan a lot of the sessions, so that there is not much pressure to decide during the time (RD) - Also focus on replay/reference value of both individual episodes and the overall program (RD) - Coordinate with our institutions' other teams, and get this as part of some semi-official training program and use their power to advertise things. ## Involved people Want to be involved? Add your name here, and also add yoru initial under - Richard Darst - Radovan Bast ## Topics Add topics here. We will filter down and order them later, right now it is brainstorming. (we should have 15-20 topics prepared. The order is flexible. "Plans are useless but planning is essential" etc. Add your initials if you are able to help present the episode, we will provide guidance on this.) * Why is Intro to software and scicomp stuff (zen of scicomp?) (RD) * Shell intro (RD, RB) * Data preparation and release (RD) * Our favourite Python libraries (RB) * How to manage code on a research-group level (for group leaders, how to prevent everyone from doing their own things) * How to use SSH and GPG keys (we all need them sooner or later, it is "never" taught, and documentation is often not adapted to non-experts) (RB) * Licensing and sharing: what do you need to know in practice (e.g. How to agree on code and licensing) * shell: advanced tricks we use (RD, RB) * Testing (RD, RB) * Publishing and releasing software (RD, RB), Making your code ready for JOSS (RB) * Renv / Julia environment reproducibility () * Our favourite R libraries () * desktop to cluster (RD) * cluster: working efficiently (RD) * Strategies to parallelize a code (RB) * writing parallel code () * Finding and solving memory bottlenecks, especially in Python (RB) * How to run a Python web service or in other words: what to do when you need more than a static website? () * Containers Ideas: * Long-term data storage (archiving) * conda/virtualenv (RD) ## Decisions * Every other week for the basic topics above * In off-weeks, we can do something very advanced focused on practicing RSEs * Continue in evenings (we can't commit to a consistent time during working hours) * Continue on Thursdays (20:30 CET/ 21:30 EET) * First week: 4.feb * More outreach, made possible by planning more in advance * TODO: dedicated twitter account? * TODO: update webpage, make it clear what is coming up in the future (Radovan, weekend) * TODO: website -> how to get involved. (join chat and talk about us). Make it easier to get involved, more clear process.