Want a nice _and_ reliable #calendar application for #GNOME and #Linux desktops (& #mobile!) in general, based on the @EvolutionGnome data server?
Know some #C #programming and looking for a well-scoped challenge to get your feet wet and put those skills to use in #opensource?
#GNOMECalendar could really use your help to write unit tests, so that we can use #TestDrivenDevelopment #TDD #CI for #refactoring all timezones-related code and make it reliable. Now is the time!
https://fortintam.com/blog/call-for-help-writing-gnome-calendar-compliance-unit-tests/
If anyone is wondering why the GNOME Calendar codebase looks scared of automated tests: it _should_ be. ️
The goal is that maintainers hunting and eliminating timezone/DST/spec-compliance-related bugs should have to fly through this crazy network of defensive lasers, er, tests, before landing mission-critical code in the future: https://www.youtube.com/watch?v=Lx81lV3smNY&t=156s
@nekohayo My biggest hope: that the annoying alarm at 11:00 (10:00 DST, or the other way around) bug is finally found and fixed.
@nekohayo Hmm, evolution-data-server's CI just seems to build the flatpak, which runs the test suite and that's that.
It may be useful to get some coverage information... there's cmake/modules/CodeCoverageGCOV.cmake at least.
@nekohayo @EvolutionGnome evolution is my preferred calendaring app due to the fact that it's the only fucking thing that actually works with all of my work stuff. I honestly wish I could take it with me on my phone, which currently doesn't run Linux...