• oshu@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    6 hours ago

    It seems like the author is confusing open source with Open Source. The latter has a formal definition which includes a lot more than simple access to source code.

    I also agree that no one is entittled to free support or enhancements, bugfizes, etc.

    • rottingleaf@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 hours ago

      Free and open source software. “Open Source” has always been an attempt to attract big fish, hoping they are not evil, just slow. It’s morally obsolete, while FOSS still isn’t.

      And BSD\ISC\MIT understanding of FOSS is even less morally obsolete every day that comes, no expectations that a properly designed virus license will somehow convert the humanity, just letting out seeds of knowledge that will eventually change the world or maybe not. It’s sacrificial, but also very potent.

      Anyway, most of those expecting free support are companies making money on products they haven’t spend a dime improving. Or employees of such companies.

      The whole world is using Java, but where is Sun? The whole world is using Asterisk (ok, maybe not all of it), but its developers are not millionaires AFAIK.

      Entitled script kiddies are just dumb and rude, but I think there’s much less of them than the former group. And they are less persistent, than that former group.

  • tabular@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 hours ago

    Open source is just that

    “Open” is an unspecific, a range of openness from not redistributable to (libre) free software.

  • ambitiousslab@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    ·
    9 hours ago

    I agree with parts about entitlement. The expectation of support and treatment of open source software as if it was proprietary is a real problem.

    But, the authour makes a similar mistake - they conflate open source software with source-available (proprietary) software. As an example, I strongly disagree with this part:

    When software is open-source, it is open-source, not necessarily free and open-source (FOSS), and even if it is FOSS, it might still have a restrictive licence. The code being available in and of itself does not give you a right to take it, modify it, or redistribute it.

    If you replace it with this version, I am happy:

    When software is source-available, it is source-available, not necessarily open source or free and open-source (FOSS). The code being distributed under a source available license does not give you a right to take it, modify it, or redistribute it.

    I think it’s really important that we keep a clear delineation between free/open source software on one side, and source-available (proprietary software) on the other.

    A lot of companies are trying to co-opt and blur the meaning of the term so they can say “seeing the source was always the point, none of the other freedoms mattered”, in order to sell you proprietary licenses.

    Open source gives you the right to take, modify and redistribute it. Source available does not. And that’s ok, just please don’t blur the terms together.

    even if it is FOSS, it might still have a restrictive license

    Likewise, this is definitionally untrue. The whole purpose of FOSS is to give you the four freedoms.

    • masterofn001@lemmy.ca
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 hours ago

      I once had an argument in another community on here about something very similar. And they told me I was wrong. The mods deleted my posts.

      I posted the links and the definition/requirements for FOSS as compared to just open source.

      They kept telling me i was talking about open source and not libre.

      The links and definitions and requirements I posted:

      From Richard Stallman, from the site whose creators developed the rules and requirements for FOSS, GNU.org, and from the itsFOSS site which, indeed, references and links to the first 2.

      The definitions also explicitly state the difference and uniqueness of each and compares them to the nonstandard open source (source available) labels.

      I unjoined that community and found a less ignorant one.

    • snowfalldreamland@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      7 hours ago

      Maybe it sonds a bit like a conspiracy theory but with how often people make this “mistake” i really believe it’s a deliberate effort to undermine the meaning of open-source

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      56 minutes ago

      The code being distributed under a source available license does not give you a right to take it, modify it, or redistribute it.

      I would add in “automatically” there. Source-available licenses could give you the right to modify it and redistribute it, or it may not. For example, the Unreal Engine is proprietary and covered by a source-available model, and you can redistribute it to other license holders (must accept certain terms and conditions), and even then w/ restrictions. So you can take it, modify it, and redistribute it, but there are a handful of very important asterists there.

      Basically, if you don’t recognize the license as one of the major ones (Apache, BSD, MIT, (L|A)GPL, etc), then treat it as source-available w/ no rights other than reading it until you actually read and understand the license.

      even if it is FOSS, it might still have a restrictive license

      Likewise, this is definitionally untrue. The whole purpose of FOSS is to give you the four freedoms.

      That depends on your definition of “restriction.”

      If you use a copyleft license, you could be restricted from using proprietary plugins, since you’d have to release the source of those plugins if a user accesses it in a covered way, and you don’t have the right to do that. That sounds like a restriction to me, and it doesn’t apply to more permissive licenses like BSD or MIT.

  • hperrin@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    10 hours ago

    Good article. As an open source maintainer, I agree. The majority of interactions I have from my users are positive, but every once in a while, some entitled asshat does make unreasonable demands. I usually respond with a stern dressing down, but respectfully. If they continue, I’ll block them from whatever channel.

  • hendrik@palaver.p3x.de
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    10 hours ago

    Yeah, seeking support is notoriously difficult. Everyone working in IT knows this. I feel with open-source, it’s more the projects which aren’t in a classic Free Software domain, who attract beggars. For example the atmosphere of a Github page of a Linux tool will have a completely different atmosphere than a fancy AI tool or addon to some consumer device or service. I see a lot of spam there and demanding tone. While with a lot of more niche projects, people are patient, ask good questions and in return the devs are nice. And people use the thumbsup emoji instead of pinging everyone with a comment…

    I feel, though… I you’re part of an open source project which doesn’t welcome contributions and doesn’t want to discuss arbitrary user needs and wants, you should make that clear. I mean Free Software is kind of the default in some domains. If you don’t want that as a developer, just add a paragraph of text somewhere prominently, detailing how questions and requests are or aren’t welcome. I as a user can’t always tell if discussing my questions is a welcome thing and whether this software is supposed to cater for my needs. Unless the project tells me somehow. That also doesn’t help with the beggars… But it will help people like me not to waste everyone’s time.