Most active commenters

    ←back to thread

    1125 points CrankyBear | 17 comments | | HN request time: 1.575s | source | bottom
    Show context
    phkahler ◴[] No.45891830[source]
    From TFA this was telling:

    Thus, as Mark Atwood, an open source policy expert, pointed out on Twitter, he had to keep telling Amazon to not do things that would mess up FFmpeg because, he had to keep explaining to his bosses that “They are not a vendor, there is no NDA, we have no leverage, your VP has refused to help fund them, and they could kill three major product lines tomorrow with an email. So, stop, and listen to me … ”

    I agree with the headline here. If Google can pay someone to find bugs, they can pay someone to fix them. How many time have managers said "Don't come to me with problems, come with solutions"

    replies(8): >>45891966 #>>45891973 #>>45893060 #>>45893320 #>>45896629 #>>45898338 #>>45902990 #>>45906281 #
    skrebbel ◴[] No.45891966[source]
    How could ffmpeg maintainers kill three major AWS product lines with an email?
    replies(5): >>45891984 #>>45892034 #>>45892354 #>>45895260 #>>45899217 #
    zxspectrum1982 ◴[] No.45891984[source]
    Easy: ffmpeg discontinues or relicenses some ffmpeg functionality that AWS depends on for those product alines and AWS is screwed. I've seen that happen in other open source projects.
    replies(3): >>45892090 #>>45892103 #>>45894363 #
    NewsaHackO ◴[] No.45892103[source]
    But if it gets relicensed, they would still be able to use the current version. Amazon definitely would be able to fund an independent fork.
    replies(6): >>45892164 #>>45892171 #>>45892460 #>>45894578 #>>45894811 #>>45900051 #
    1. wewtyflakes ◴[] No.45892164[source]
    Sounds like it would be a lot of churn for nothing; if they can fund a fork, then they could fund the original project, no?
    replies(5): >>45892193 #>>45892545 #>>45894433 #>>45895761 #>>45901951 #
    2. arrowleaf ◴[] No.45892193[source]
    If they can fund a fork, they can continue business as usual until the need arises
    replies(1): >>45892544 #
    3. zrm ◴[] No.45892544[source]
    A fork is more expensive to maintain than funding/contributing to the original project. You have to duplicate all future work yourselves, third party code starts expecting their version instead of your version, etc.
    replies(1): >>45898966 #
    4. cortesoft ◴[] No.45892545[source]
    They COULD, but history has shown they would rather start and maintain their own fork.

    It might not make sense morally, but it makes total sense from a business perspective… if they are going to pay for the development, they are going to want to maintain control.

    replies(2): >>45892610 #>>45895069 #
    5. edoceo ◴[] No.45892610[source]
    If they want that level of control, reimburse for all the prior development too. - ie: buy that business.

    As it stands, they're just abusing someone's gift.

    Like jerks.

    replies(2): >>45893243 #>>45894018 #
    6. rolandog ◴[] No.45893243{3}[source]
    There should be a "if you use this product in a for-profit environment, and you have a yearly revenue of $500,000,000,000+ ... you can afford to pay X * 100,000/yr" license.
    replies(2): >>45893342 #>>45893707 #
    7. renewiltord ◴[] No.45893342{4}[source]
    That's the Llama license and yeah, a lot of people prefer this approach, but many don't consider it open source. I don't either.

    In fact, we are probably just really lucky that some early programmers were kooky believers in the free software philosophy. Thank God for them. So much of what I do owes to the resulting ecosystem that was built back then.

    replies(1): >>45896236 #
    8. zrm ◴[] No.45893707{4}[source]
    There is also the AGPL.
    9. LexiMax ◴[] No.45894018{3}[source]
    I always like to point out that "Open Source" was a deliberate watering-down of the moralizing messaging of Free Software to try and sell businesses on the benefits of developing software in the open.

    > We realized it was time to dump the confrontational attitude that has been associated with "free software" in the past and sell the idea strictly on the same pragmatic, business-case grounds that motivated Netscape.

    https://web.archive.org/web/20021001164015/http://www.openso...

    replies(1): >>45896787 #
    10. 6510 ◴[] No.45894433[source]
    With a bit of needless work the fixes could be copied and they would still end up funding them.
    11. pstuart ◴[] No.45895069[source]
    Do they want control or do they really want something that works that they don't have to worry about?

    The only reason for needing control would be if it was part of their secret sauce and at that point they can fork it and fuck off.

    These companies should be heavily shamed for leaching off the goodwill of the OSS community.

    12. zdragnar ◴[] No.45895761[source]
    Funding ffmpeg also essentially funds their competitors, but a closed fork in-house doesn't. Submitting bugs costs less than both, hence why they still use ffmpeg in the first place.
    13. bigiain ◴[] No.45896236{5}[source]
    I reckon this is an impedance mismatch between "Open Source Advocacy" and Open Source as a programming hobby/lifestyle/itch-to-scratch that drives people to write and release code as Open Source (of whatever flavour they choose, even if FSS and/or OSF don't consider that license to qualify as "Open Source").

    I think Stallmann's ideological "allowing users to run, modify, and share the software without restrictions" stance is good, but I think for me at least that should apply to "users" as human persons, and doesn't necessarily apply to "corporate personhood" and other non-human "users". I don't see a good way to make that distinction work in practice, but I think it's something that if going to become more and more problematic as time goes on, and LLM slop contributions and bug reports somehow feed into this too.

    I was watching MongoDB and Redis Labs experiments with non-OSF approved licences clearly targeted at AWS "abusing" those projects, but sadly neither of those cases seemed to work out in the long term. Also sadly, I do not have any suggestions of how to help...

    14. KingMob ◴[] No.45896787{4}[source]
    I like FS, but it's always had kind of nebulous morality, though. It lumps in humans with companies, which cannot have morals, under the blanket term "users".

    This is the same tortured logic as Citizens United and Santa Clara Co vs Southern Pacific Railroad, but applied to FS freedoms instead of corporate personhood and the 1st Amendment.

    I like the FS' freedoms, but I favor economic justice more, and existing FS licenses don't support that well in the 21st c. This is why we get articles like this every month about deep-pocketed corporate free riders.

    replies(1): >>45897275 #
    15. spookie ◴[] No.45897275{5}[source]
    Agree in some ways. Still, discussing the nitty gritty is superfluous, the important underlying message you are making is more existential.

    Open source software is critical infrastructure at this point. Maintainers should be helped out, at least by their largest users. If free riding continues, and maintainers' burden becomes too large, supply chain attacks are bound to happen.

    16. rs186 ◴[] No.45898966{3}[source]
    Nobody said the fork cannot diverge from the original project.
    17. xxs ◴[] No.45901951[source]
    They can't - it's LGPL 2.1. So the fork would be public essentially.