Note that this covers the past year or two, and I'd mention in advance that most of these contributions were selfishly-motivated, because they helped other proj

Note that this covers the past year or two, and I'd mention in advance that most of these contributions were selfishly-motivated, because they helped other projects that I've been relying on: - html2canvas: because it met 99% of a feature's requirements (to support in-browser screenshots for users to attach with web-based feedback), except that font-awesome CSS icons weren't rendering correctly. - Google Lighthouse: because there was a false-positive-ish result when auditing one of my applications that seemed resolvable by updating a dependency version. Long story short; it turned out to involve more than simply updating a version number. - GitLab: because I managed to add a "deploy freeze" to a GitLab repository using the web UI, and then couldn't find a way to remove it again without making a curl request -- so I figured I'd save someone else the hassle and go ahead and implement the deletion UI; also a slightly longer journey than expected (but, as with all of these, enjoyable and satisfying learning and problem-solving). - grocy: because I posted it to HN a-year-and-a-half ago, and then (after that post gained some traction) began to feel a slight burden of responsibility for anyone using the project's provided container image, and decided I'd take on some maintenance and cleanup of it to (hopefully) help. - frozen-flask: generating static landing pages may or may not be a good idea (and may or may not be an attempt to game SEO), but either way, I wanted to try it out, and frozen-flask mostly worked in the project's environment aside from some small Python-version compatibility issues that were a good puzzle to solve. In almost all cases here, "working on" means fixing a bug or two that have blocked me in some other, often more feature-oriented, context. Often it has also included surveying previous knowledge of the issues and previous and/or in-progress attempts to fix them. (and often, the integration context has been https://www.reciperadar.com https://www.reciperadar.com - itself AGPLv3 licensed)