Login
You're viewing the functional.cafe public feed.
  • Oct 15, 2026, 1:53 PM

    Free Software projects should endeavor to make successful contribution approachable for people "scratching an itch" instead of demanding perfection. Otherwise eventually there will be no pool of future contributors. Too many projects (seemingly ones with mostly paid developers) forget this and suffer for it, eventually.

    💬 6🔄 15⭐ 1

Replies

  • Oct 15, 2026, 2:09 PM

    @neal Circle of life, really. Projects either find a way to rejuvenate themselves, or they wither away. Important things get replaced, if people care enough.

    💬 0🔄 0⭐ 0
  • Oct 15, 2026, 2:14 PM

    @jzb This sort of came out of reading an LWN article and a recent experience by a friend on another highly "supported" open source project. It feels like a lot of these people have forgotten what it's like to be an unfunded contributor.

    💬 1🔄 0⭐ 0
  • Oct 15, 2026, 2:44 PM

    @neal entirely possible. I wonder really if it’s possible for a project that’s largely run by funded individuals to accommodate the needs of unfunded individuals.

    The reverse is true too: a project that’s a few unfunded people isn’t going to fit well for the corporate folks. Air-dropping a paid contributor in is not going to go well, prolly.

    I have, as you might imagine, quite a few thoughts on this. 💀

    Sometimes I think that there’s a need for an LF-type org, but funded entirely by hobbyists, enthusiasts, small businesses (e.g. the MNT Reform types) and only aimed at non-corporate users. Hoping that the big corps will make space for individuals tends to end in disappointment.

    Not because the big companies are inherently hostile (sometimes), but because the competing interests are too great. “Why didn’t you get XYZ done this week?” “I was busy mentoring.” “Not your job: knock it off.”

    💬 0🔄 0⭐ 3
  • Oct 15, 2026, 2:52 PM

    @jzb @neal Independent individuals on a project can be a huge help to corporate employees who want to do things the right way, though.

    There's always corporate pressure to "ship it" even if still in a risky state. An employee can't directly resist but can often use "upstream" as an excuse to get it right

    💬 0🔄 0⭐ 2
  • Oct 15, 2026, 2:56 PM

    @dmarti @neal if the balance is right, sure. Helps a lot if the mix of paid people comes from a bunch of organizations and not just one vendor.

    💬 0🔄 0⭐ 2
  • Oct 15, 2026, 3:07 PM

    @jzb @neal Yes, good point. If everyone who needs to approve a release is an employee of the same company, then the project is an extended job interview for that company (which some contributors might be happy with). Outside people who depend on the project's actual software artifacts will get rugpulled at some point.

    💬 0🔄 0⭐ 1
  • Oct 22, 2026, 4:51 PM

    @dmarti @jzb No, I disagree. The Linux kernel is great evidence this isn't true. What actually matters is the project culture and leadership view on contribution. What *really* matters is if there's a culture of care between maintainers and contributors. Without that, it just blows up eventually.

    💬 0🔄 0⭐ 0
  • Oct 15, 2026, 2:20 PM

    @neal I think there's a big difference between "I've scratched my itch, and now I'm considering putting in effort that would compensate others who deal with my itch", and "I've scratched my itch, and now I want someone else to maintain it for the rest of eternity". the former, I'm interested in; the latter, I don't really care about

    💬 1🔄 0⭐ 0
  • Oct 15, 2026, 2:32 PM

    @whitequark @neal It was "'my' itch was for a trivial use case to work with macos, which involved a one line change to fix a spec compliance bug". The response was silence for 4 months, followed by false accusations when I promoted a bug attachment proposed patch to a PR, and demands for elaborate synthetic testing on Windows for hypothetical out of scope situations, all with an attitude.

    💬 1🔄 0⭐ 1
  • Oct 15, 2026, 2:33 PM

    @lina @neal I wouldn't describe a spec compliance bugfix as "scratching an itch" regardless of context, at least personally. certainly it is not something that increases maintenance burden (my issue with some 'drive-by contributions')

    💬 1🔄 0⭐ 0
  • Oct 15, 2026, 4:08 PM

    @whitequark @lina I legitimately do not care if you're a drive-by contributor or not. I would endeavor that if you come to one of my projects and do a drive-by contribution, that you might find it useful to stick around and do more, but deprioritizing drive-by contributors messes up the whole pipeline longer term.

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Oct 15, 2026, 5:59 PM

    @neal @lina it's the same logic as that beind rejecting LLM-generated patches. it takes far less effort to propose a kludge than it takes to review, test, and later maintain it. not recognizing this is completely unsustainable

    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Oct 15, 2026, 4:33 PM

    @craftyguy Generally, yes. But I think it's reasonable to ask for minor changes as part of review. Keeping the codebase clean and consistent is part of keeping it approachable.

    What you don't want to do is get a new contributor stuck in the middle of a nitpick fight between maintainers. Conflicting code review comments, especially over tiny things, is a good way to get a new contributor to run away scared.

    @neal

    💬 1🔄 1⭐ 0
  • Oct 15, 2026, 4:51 PM

    @gfxstrand @neal oh ya, I definitely meant the second half of your comment, not the first. Sorry for being too concise, and nice job summarizing it 😅

    💬 1🔄 0⭐ 0
  • Oct 15, 2026, 4:57 PM

    @craftyguy @neal No worries! Being concise is good.

    And this is something I genuinely struggle with, especially when one of the reviewers is also a newbie. I want new people to get involved in review! And often other new people’s patches make for easy, approachable reviews. But then sometimes the new reviewer is wrong and what they saw in one part of the project is not actually how we do things in general but I don’t want the even newer contributor to feel caught in a maintainer fight and… Gah! Community building is hard. 😅

    💬 0🔄 0⭐ 0
  • Oct 15, 2026, 3:54 PM

    @neal
    I'm a drive-by contributor.

    I use some software for years, find a bug that annoys me, investigate it, make a patch, then if I'm not particularly tired, send it upstream. If it gets merged, I'll continue to happily contnue use that software for years without sending more patches.

    I don't think any maintaner has any reason to invest their time guidng me through the contribution process, even though I appreciate when they do.

    1/

    💬 1🔄 0⭐ 0
  • Oct 15, 2026, 3:59 PM

    @neal
    In the abstract I would like to become a regular contributor to some project, but no single project felt interesting, and I doubt I'd have the energy to contribute long-term.

    I think there are many drive-by contributors like me.

    Do you think I still in some sense count towards a future contributor pool?

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 16, 2026, 4:41 AM

    @neal on the other hand, I’ve enjoyed how contributing to open source has helped me learn how to write better code, thanks to the constructive feedback of others.

    💬 0🔄 0⭐ 0