add rse section

_toc.yml

@@ -26,6 +26,10 @@ chapters:
   - file: content/04_cluster/1_access
   - file: content/04_cluster/2_jupyterhub
   - file: content/04_cluster/3_slurm
+- file: content/07_rse/00_intro
+  sections:
+  - file: content/03_vscode/01_software_licenses
+  - file: content/03_vscode/02_software_publication
 - file: content/05_projects/0_intro
 - file: content/06_vr/0_intro
   sections:

content/07_rse/00_intro.md

+# Research Software Engineering
+
+
+- [Software Licenses](01_software_licenses)
+- [Software Publication](02_software_publication)
\ No newline at end of file

content/07_rse/01_software_licenses.md

+# Software Licenses
+
+
+## What is a software license?
+
+REUSE Compliant: https://reuse.software/
\ No newline at end of file

content/07_rse/02_software_publication.md

+# Software Publication
+
+Publishing your software provides open access, increasing visibility and facilitating collaboration within the research community. Assigning a DOI to your software enables proper citation, enhancing your academic and professional recognition. 
+
+
+## Where to publish?
+While der are many platforms avaiable, we currently suggest to publish your software on [zenodo](https://zenodo.org).
+The platform supports versioning, ensuring users can access the latest updates while preserving earlier versions for reference. Zenodo's commitment to long-term preservation aligns with the requirements of funding agencies and institutions, offering a stable and accessible repository for your software.
+Additionally zenodo offers a [GitHub integration](https://guides.github.com/activities/citable-code/) which allows you to automatically create a new version of your software on zenodo whenever you create a new release on GitHub.
+
+## Publish your software on zenodo manually
+Publishing software on zenodo is easy. However, it is recommended to automatize the process, when it comes to publishing new versions of your software. This is discussed in the next section.
+To publish your software on zenodo, you need to create an account. Afterwards you can log in, create a new upload, and upload your software as a zip file. Zenodo will automatically create a DOI for your software.
+
+## Automate the publication of your software on zenodo from github
+### Add Citation file to your repository
+To automate the publication of your software on zenodo, you need to add a citation file to your repository. This can be done by creating a file called `CITATION.cff` in the root directory of your repository. The file should at least contain the authors information. More information about the citation file format can be found [here](https://citation-file-format.github.io/). This nice thing about this file format is that GitHub also uses it to display the citation information of your repository. You can find the documentation [here](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)
+
+### Give zenodo access to your github repository
+To automate the publication of your software on zenodo, you need to connect your zenodo to github [here](https://zenodo.org/account/settings/linkedaccounts/). 
+If you want to publish the code from an organization's repositories, zenodo needs to get access. This can be done by clicking on "Authorize GitHub" and then selecting the organization. If you want to publish the code from your personal repositories, you need to click on "Authorize GitHub" and then select your username.
+
+### Enable repository on zenodo
+After giving zenodo access to your github repositories, you see the list of your public repositories [here](https://zenodo.org/account/settings/github/). Switch the toggle button to "on" for the repository you want to publish on zenodo.
+
+### Create a new release on github
+You need to create a new GitHub release. This can be done by clicking on the "Releases" tab in your GitHub repository and then clicking on "Draft a new release". You can then upload your software as a zip file and create the release. After creating the release, you can click on "Edit" and then on "Publish release". This will trigger the zenodo GitHub integration and create a new version of your software on zenodo. After the publication, you are not able to change the source code of the software on zenodo. Whenever you want to publish a new version of your software, you need to create a new release on GitHub.
+
+### Curating the meta data
+After the publication you are still able to edit the meta data of your software on zenodo. This can be done by clicking on "Edit" on the zenodo page of your software.
+
+### Publishing from Gitlab (git.rz.tu-bs.de) using a Mirror
+Currently zenodo does not allow to publish software directly from gitlab to zenodo. However, you can use a the mirror feature of gitlab to mirror your gitlab repository to GitHub. You can then use the GitHub integration of zenodo to publish your software on zenodo.
+To mirror your repository from gitlab to github we recommand to follow the steps:
+1. Create a new public and empty repository on GitHub (no README, no license, no .gitignore)
+2. Go to your gitlab repository and click on "Settings" -> "Repository" -> "Mirroring repositories" -> "add new"
+    - Enter the URL of your GitHub repository: E.g. for https://github.com/irmb/virtualfluids it would be `ssh://git@github.com/irmb/virtualfluids.git`
+    - Click "detect host keys" and choose "Authentication method: SSH public key"
+    - Leave "username" empty and choose "Mirror repository: only protected branches"
+    - Click "Mirror repository"
+3. On the page "Mirroring repositories" copy the SSH key by clicking on the copy button:
+![Alt text](image-1.png)
+3. Go to your GitHub repository and click on "Settings" -> "Deploy keys" -> "Add deploy key"
+    - Enter a title for the key
+    - Paste the SSH key from gitlab into the "Key" field
+    - Choose "Allow write access"
+    - Click "Add key"
+3. On the page "Mirroring repositories" click on "Update now" to mirror your repository from gitlab to github
+
+Done! gitlab will automatically mirror your protected branches and also tags based on this branch to github. The last thing you need to do to get the zenodo publication is to create a new Release on GitHub manually.
\ No newline at end of file