List of topics for deRSE25

[gperu]

Topics not yet started

• How to push your Dockerfile to the GitHub registry
• How to package your code for reuse
• How to manage your software project
• How to maintain your research software project
• How to collaborate on an open source software project
• How to develop a software application into a (cloud) software service
• How to establish your software in the community and support this community
• Comparison of tools for automated FAIR software assessment
• Understanding quality metrics and how to use them
• How to refactor your software/code
• How to design software for sustainability
• How to conduct static analysis
• How to conduct dynamic analysis
• How to conduct architectural recovery and reconstruction
• How to add your first GitLab CI
• How to use containers and why should I use them
• How to use design patterns
• How to provide complete bibliographic metadata as a codemeta file
• How to publish your software to contribute to the Scholarly Knowledge Graphs
• Basic security checks for web based software and APIs

Topics with an issue

• Document your Computatonal Workflow #207
• Metadata documenting your Code task #206
• How to publish your software package to a package repository #197
• How to cite your code repository and maintain a Citation File (CFF) #196
• How to structure the files in your software project #195
• How to test and automate the testing of your software project #194
• How to add your first GitHub action  #193

Before creating a pull request:

• Please make sure you have checked contributing guidelines.
• Is there a separate related issue for the fix you are providing or the content you are creating? If not, please add one.
• If you are changing files in data folder (or thing something should be changed in _config.yml in _includes folder) - please make sure you have discussed this with the maintainers in the relevant issue.

In the pull request:

• Add a reference to the issue the PR is addressing - e.g. add a line "Fixes #issue_number (add the relevant issue number)."
• Add a short description of changes proposed in this pull request:
• Provide additional information for the reviewers here (if needed)