This SIG focus on our Software Quality & Sustainability expertise. In short, this means tools and practices that help our code be more easily maintained and more robust.
We will try to follow the following agenda:
- 5-10 minutes: Announcements and other short messages
- 20-40 minutes: One or two presentations
- 10-20 minutes: Discussions and input session
Here's our schedule:
| Date | Topic | Presenter | Recording |
|---|---|---|---|
| 2026-03-19 | Software Quality Metrics | Abel Soares Siqueira | link |
| 2026-04-16 | Continuous Localization with Weblate in the Dynamic3D project | Carsten Schnober | link |
| 2026-05-14 | No SIG due to public holiday | - | - |
| 2026-06-11 | Software quality score cards in and beyond OSS | Peter, Jason, Elena | |
| 2026-09-03 | |||
| 2026-10-01 | |||
| 2026-10-29 | |||
| 2026-11-26 |
We will try to have either one or two RSE presentations per session, and some discussion sessions.
If you want to present or suggest a discussion topic, please create an issue on https://github.com/nlesc-sigs/SQS-sig or send an e-mail to the SIG leads. If you can relate it to an existing project, that is better.
Some examples of topics include, but are not limited to:
- (Categories of) tools that improved the quality in your project. E.g., linters in general, pre-commit the tool, etc.;
- (Categories of) practices that improved the quality in your project. E.g., documentation in general, diátaxis the tool, etc.;
- Challenges in achieving quality in your project.
We are still gathering presentations for this year, so please create an issue or send an e-mail to abel.siqueira@esciencecenter.nl if you want to present about some topic. If you can relate it to an existing project, that is better.
For inspiration, here is our list of competences, copy-pasted from our nomenclature, are below:
- Code Review: Peer review of code that helps developers ensure or improve the code quality
- Packaging: Bundling software code and its dependencies into a single file or directory, making it easier to distribute and install
- Provisioning: Setting up and managing software application infrastructure using code, rather than manual configurations
- Rapid prototyping: Dynamic approach that focuses on creating quick and functional models of new software applications
- Software Architecture: A fundamental organization(blueprint) of and a set of structures needed to reason about a software system
- Software Testing: Checking software against a standard, intended objectives and satisfies expectations
- AI-Assisted Coding & Autonomous Development: Use of artificial intelligence agents to augment the software development life cycle
- AI-Driven Test Automation: Integration of AI into the test automation process
- Low-code/No code testing: Automation testing methods for the creation and execution of tests without extensive programming knowledge, often using visual interfaces
- Requirements Engineering: Process of identifying, eliciting, analyzing, specifying, validating, and managing the needs and expectations of stakeholders for a software system
- Version Control: Software engineering practice of controlling, organizing, and tracking different versions in the history of computer files, primarily source code
- Software Documentation: Written text or illustration explaining the software's operation or usage
- Software citation, fairness, and impact: Technologies ensuring the recognition and impact of software
- Community building & Governance: Research software community building and software governance models
Previously in 2019, this SIG was named software-sustainability