# Getting Started
**Welcome to the FAIR for Research Software Program!!!** :rocket:

With this program, we aim to assist your journey in the fields of research software with a strong emphasis on its inherent relationship with data.

:::danger
The materials for the FAIR4RS program are available only for participants due to privacy consideration, keep in mind that these guides are accesible online once you have the link but they are not meant to be shared widely.
:::

Our approach leverages the ideas of FAIR (Findable, Accessible, Interoperable, and Reusable), Open Science, and Reproducibility as tools towards achieving better science. These concepts, grounded in principles of empathy and collaboration, foster a scientific ethos and ecosystem that enhances the impact and meaningfulness of science.

To support you on this journey, we have prepared a set of activities that include a tested workshop for research software, the [CodeRefinery](https://coderefinery.github.io/2024-03-12-workshop/), interactive orientation sessions, office hours for requesting help from data managers and research software engineers, and individual project work. **The latter being the most crucial aspect**.

## What Can You Expect by the End of the Program? And What Would We Like to See?
The best way to illustrate this is to share with you an **[example of a final presentation](https://hackmd.io/TF_zmwDzQOiTjXeeeFfc9A?view)** from the previous program. Pay close attention to the "Progress Update" section of the example, which highlights the journey from the starting point to the endpoint.

### Outcomes
We are aiming for two outcomes:
1. **A happy research software developer** By happy, we mean feeling equipped and confident to develop good research software. By good, we mean "good enough" as a baseline. You can always improve and achieve excellence later as these practices become habitual.
2. **A FAIR Software project** that you can share to enable collaboration with colleagues and potential contributors.

## How to Prepare

### Before the Kickoff

1. **Review the [Schedule](https://hackmd.io/@fair4rs/SybbutV26/%2Fue90cUwjRbKMWcxW-z0jhw):** Ensure you are available for the CodeRefinery workshop dates (March 12-14 and 19-21, 09:00 – 13:30 hrs) and the seminar dates (Kickoff – 28 March, Midterm – 25 April, Final Presentations – 31 May). We recommend booking these hours in your calendar if you haven't done so yet.
2. **Make sure to have a project ready to start working on**. By this we mean an actual codebase that will be a git repository and will live soon or is already living on github. We expect this to be sorted out by now, as you applied with a project to the FAIR program.
:::success
**Tip:** If you are not sure you have a project that is ready to start working on it, please get in contact with the instructors of the program as soon as possible.
:::
3. **Set Your Goals:** Reflect on what you aim to achieve through this program based on what you learned during the Coderefinery. Consider which aspects of your research software or data management practices you wish to enhance including other topics that were not covered during the Coderefinery workshop.

### After the kickoff
#### Doing the Mandatory Exercises
:::info
**TODO:** Check during the kickoff how far people are in the exercises already. Maybe some participants already have a license, git repo opened, etc.
:::

:::danger
**We expect you to do the following Mandatory exercises before the midterm:**
- [Fill in post workshop survey if you haven't](https://docs.google.com/forms/d/e/1FAIpQLSfw1s9m1Fk17mMmKYW4BPrAcZBd8o3OI6JTVIPH2I1FZz5w2A/viewform)
- Choose a license
- Share your project openly
- [Book at least one consultation](/9H9Wd8fBT3qbioF-HkYJgw)

Please read [this detailed explanation of the mandatory exercises](https://hackmd.io/5uku5qGbQAiejFROkCwHeQ).

:::

### About the exercises

We have two sets of exercises. The **[basic mandatory exercises](https://hackmd.io/5uku5qGbQAiejFROkCwHeQ)** to comply with minimum FAIR requirements, and **[optional exercises](https://hackmd.io/wOyI9zxQQgGsVeecMqdWaA)** that you can develop based on your priorities.

Most of the mandatory exercises are relatively simple to complete and lay the foundation for the most exciting aspect of your project: development and dissemination. This is where you can go deeper using our consultation hours, and the optional exercises. You can create your own path of development by selecting a handful of optional exercises. Think of it as elements of a roadmap you should create.

The mandatory exercises are designed to be addressed sequentially, each with a specific logic. For example, filling out the survey aims to structure your intentions and focus points, enabling us to assist you better. Choosing a license is a preliminary step before opening your repository, a requirement for sharing your project openly. Another example is adding a README as an entry point to explain what your project is about and how to start using it.

- **Pay attention to the emails we send during the program and the messages in MS Teams.**
- **Engage Actively:** Participate in the workshops and seminars, complete the project work, and interact with peers and experts. MS Teams is the main channel for sharing issues, progress, questions, etc.
- **Keep an eye on the [Schedule](https://hackmd.io/@fair4rs/SybbutV26/%2Fue90cUwjRbKMWcxW-z0jhw).**