As an open scientist I strive to use open source software and open tools whenever possible. But sometimes I choose a more efficient tool over the open tool. When and why? Let's break it down! |
It is no secret that I am an open source enthusiast. I've been working with R since 2009 and the wonderful R community has shown me the path to Open Science. But at the same time I am using commercial tools like this newsletter service. I use Miro for teaching and Google Docs for collaborating on documents. Since working on my self-employment and the Digital Research Academy, the decisions between open tools and other tools have become more and more difficult. Sometimes there are no good open source options available, but sometimes I just want to use a closed tool, because it is just so good at what I want to do. So I've decided that I need to somehow at least be clear with myself and the team, what I think is a good strategy. Let's see what they say ๐๐ . Heidi's rules for deciding on tools (WIP):
Ok, so this list is a work in progress. I am very much looking forward to your thoughts! How do you make those kinds of decisions? โ In other newsOpen Science Retreat 2024I am so excited to announce that there will be a second edition of the Open Science Retreat. Edition 2024 is co-organised by OSC-NL: the bottom up, community-led, social infrastructure of Open Science Communities in the Netherlands, and will take place on the sea side, again amidst nature in a secluded setting. Hope to see you in the Dutch dunes next March!
Updates on the Digital Research AcademyOur Train-the-Trainer (TTT) pilots were successful and we are currently working on the plans for the next TTTs. You can find the materials from both TTT pilots on the OSF:
Want to get involved, too? There's a mailing list, where we will let you know about next meetups, TTTs, and more:
Interested in receiving training? We on-boarded 11 trainers and everyone is excited to get started ๐ค. Get in touch and receive targeted training โ . โ That's all for today. Hope you enjoyed it! If you did, consider forwarding this post to your friends and colleagues. All the best, Heidi P.S. If you're enjoying this newsletter, please consider supporting my work by leaving a tip.
|
Heidi Seibold, MUCBOOK Clubhouse, Elsenheimerstr. 48, Munich, 81375 |
https://heidiseibold.com
All things open and reproducible data science.
What are good strategies to develop an Open Science Policy? Here's our opinionated guide. This post was co-created with Sander Bosch, Open Science Programme Coordinator at VU Amsterdam. At the Open Science Retreat 2024 Sander and I had a conversation about his experience in policy development. Since we believe that his experience is valuable for a lot of people out there, we decided to write down three simple rues to create an Open Science policy: Develop output policies first and combine...
Guest post: Meet Dr Elisabeth Kugler, director of Zeeks โ Art for Geeks. In this post she will share her career path and how her work connects with open science now that she is an entrepreneur. I am Dr Elisabeth Kugler, director of Zeeks โ Art for Geeks โ a company that transforms how people think about data. We achieve this by data analysis, visualization, and communication. And our speciality is image-based data and strategies. In this article, I aim to discuss Zeeks' perspective on open...
Making your research or code project FAIR (Findable, Accessible, Interoperable, Reusable) and reproducible can feel like a chore. But if you have access to the right templates and resources, it can be quite the simple and rewarding task. Let's make it easy for ourselves to do the right thing! So today let me share some templates for setting up #FAIR and #reproducible projects. I asked folks on social media what suggestions they had and got so many that I was not able to put them all here...