📢 Woohoo! Version v6.1.16 of Firefly III has just been released 🎉. Check it out over at GitHub, Docker, or download it using your favorite package manager.
I'm genuinely curious.. when I make #FOSS applications I always make it work according to my needs instead of thinking about making it usable for everyone else. Is this normal? Am I the only one who does this? #oss
🧵 …although I tend to favour OpenBSD and Linux for personal reasons, I find this decision OK. Certain open source projects lack clear, reasoned positions and decisions.
»NetBSD’s New Policy – No Place for AI-Created Code:
NetBSD bans AI-generated code to preserve clear copyright and meet licensing goals.«
Starting the day by deleting around 200 spam GitHub Discussions. Always a pleasure...
If GitHub's looking for AI topics: it could really help maintainers by spotting spam, blocking accounts, and automatically deleting discussions/issues so they have nothing to do.
Following up on finding open-source projects to contribute to: https://goodfirstissue.dev is another great resource!
It curates easy pickings from popular open-source projects and narrows down projects for new contributors.
Projects must meet criteria like 3+ 'good first issue' labels, 10+ contributors, a README.md with setup instructions, and a CONTRIBUTING.md with guidelines. Projects must also be maintained.
Most of the time, you don’t need to look far to find an open-source project to contribute to. Use a tool regularly and see room for improvement? Consider contributing!
Still can't find a project? Check out aggregators like https://up-for-grabs.net/ for curated lists of projects needing help. Filter by language, difficulty, and more!
food for thought when giving feedback to contributors.
the author reflects on giving feedback in OSS vs corporate.
OSS, you invest in the ppl and give lots of feedback. not in corporate.
and I like this takeaway:
> And so, I’ve learned that a person can absorb only about one piece of feedback per interaction, and then only if it’s labeled very specifically as feedback with the best intentions, and wrapped delicately in a feedback sandwich.
We are proud to announce that @xunit is the May 2024 sponsor project for .NET on AWS! They're generously funding our development efforts for the next 12 months.
I've been helping to investigate a few LLVM and Rust bugs recently, and I keep running into pet peeves with how these bugs are reported, so I'm going to put together some #RulesForBugFiling
I don't want to discourage anyone from filing a bug, please do! But... be aware with how you represent the issue that you're seeing.
I also know that there are folks on here who are vastly more knowledgeable than I am, so feel free to suggest corrections, perhaps by filing some sort of report...
The more specific you can be on when a regression occurred, the better. A range of versions is good, a single version is great, a single commit is amazing.
Tools like git bisect are really helpful for this.
Providing a standalone example that reproduces the issue so that someone else can do that work is also great, with the bonus that it can be added to the regression tests.