Just saw the discussion around the Haier Home Assistant takedown and thought it would be good to materialize the metaphorical blacklist.

  • thesmokingman@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    10 months ago

    It’s probably a good idea to have a stronger definition and mission. Here are a few scenarios you should consider.

    • FSF defines anything that’s not copyleft as hostile. That’s most companies. I personally don’t think I can tell my users what to do with my software other than remove my liability so I vehemently disagree with Stallman.
    • Mongo wrote the SSPL and MariaDB wrote the BSL. Both licenses are seen as regressions. I personally respect the MariaDB case and have been harassed by too many Mongo salespeople to say the same about them.
    • Platforms like AWS are the reason companies like CockroachDB and Elastic implemented restrictive licenses.
    • IBM has been gutting open source through its acquisition of Red Hat. This is a common story; Oracle has been screwing *nix longer.
    • Protecting trademarks causes a lot of consternation from users. The Rust Foundation is the most recent example of this I remember blowing up the FOSS community.

    I like your idea a lot. I think it needs some definition to be very successful!

    • qaz@lemmy.worldOP
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      10 months ago

      FSF defines anything that’s not copyleft as hostile. That’s most companies. I personally don’t think I can tell my users what to do with my software other than remove my liability so I vehemently disagree with Stallman.

      I’m not planning on counting that as hostile behavior. Organizations can choose a license for their software (and I can choose not to buy/use it). This collection is mostly focused on companies that hurt existing Open Source software. Such as sending a cease and desist to an unofficial plugin/extension or closing down software that was originally open source.