Work process
Communication
- We have a Telegram group to have group calls, discuss and ask for reviews
- We do 2 small coordination meetings starting between 9:30 and 10:00, and another one around 15:00.
Versionning
We follow semver (Semantic Versionning), see the specification on semver.org. All versions under 1.0.0 are not to be considered stable, breaking changes can appear in the CLI arguments, keyboard shortcuts, file structure, exo syntax, ... internal Rust code is not exposed externally as it is not a library, so we don't have to consider major changes in the code.
Changelog
We follow the Keep a Changelog convention, we write users oriented changelog at each release to describe changes in a more accessible way that git log outputs between releases.
Commits
We try to follow the Conventionnal commits.
Contribution
We use a standard contribution workflow
- An issue per feature/bug
- A branch to implement a new change
- A PR so the change can be reviewed before merging it to main
More info on how this contribution process is integrated into our CI/CD pipeline can be found here