Primary Goals
Monitor pipeline on Salsa-CI itself, and some projects using it – react immediately if there are any regressions.
Monitor new and updated MRs – provide reviews, facilitate contributions
Implement Ubuntu images for Salsa-CI as a PoC that is run and maintained for 3 months.
Decouple the CI from the scheduler
- Working on it will enable us to use Salsa CI in our local machines
- If refactoring is done well, the long-term maintenance of Salsa-CI will be easier and the barrier for new contributors will be lowered as it is easier to reason and test scripts that are easily run locally.
- Lower the barrier of entry for new contributors and improve long-term maintainability of Salsa-CI by improving documentation.
- Make more resources (wiki pages / videos) for newcomers who wants to contribute to Salsa CI and doesn't have background about Debian Development and/or CI.
- Describe setting up development environment and mentioning recommended resources for learning things related to Salsa CI development.
- Describe various ways of contributing (documenting, testing, issueing bugs, reviewing MRs, etc).
- Participate in the maintenance of 3 packages to get experience of packaging (to later become a Debian Developer) and also to see Salsa-CI in action for individual packages and experience the Salsa-CI "customer point of view":
- C/C++ package: MariaDB
- Python package: python-mkdocs
- Go package: Not decided yet
- Electron: VSCodium
In addition to the packages you help maintain, also monitor the top-10 most widely used Debian packages that their Salsa-CI stays consistently green.