My question in FOSS is whether, or how the license applies, if anyone can clarify it for me. I’m not going into a legal battle, I just am having issues rectifying the licensing with my expectations.

Also, ia most FOSS is written this way, with an expectation that organizations have to pay for licensing to use the software?

The issue below is for AGPL and PDFCreator. AGPL, if I read it correctly, seems to restrict restrictions on the license.

I work as MSP for an entity who uses PDFCreator, quite possibly based on a previous license.

I can’t otherwise explain the use or make changes myself, other than it is used as a PDF printer on user desktops to create digital documents.

What I can say is that we had recently attempted to automate the process of installing it with new computers. We ran into a minor hiccup and contacted their support for assistance. The response was that the program is not intended for free use in a corporate environment and that we will need to purchase licenses.

While I take issue with their determination and restriction of the use, it is their software and they make the rules. I’m not sure if they are violating the GPL, but I’d like some understanding if anything has a different interpretation.

We will most likely just use the built in PDF creator. A loss for the FOSS footprint, but not something I can control.

  • rentar42@kbin.social
    link
    fedilink
    arrow-up
    10
    ·
    1 year ago

    Note that they said “not intended” and not “not allowed”. you are perfectly within your right to use the program under the GPL without licensing it otherwise.

    But the company would prefer if you paid for a license (and support). If you weren’t allowed the use you do, they would have said as much, but they didn’t.

    This is a common business practice with open source software and I don’t particularly think it s “wrong”, but the fact that they are apparently trying to use confusion to make it look like you have to buy a license for commercial use is very icky in my opinion (but is unfortunately also very common).

    • PullUpCircuit@iusearchlinux.fyiOP
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      This is how I expected FOSS to function. If you get a chance, check out their license page, which directs prospective users to the AGPL and also has further restrictions on what users may not do.

      • rentar42@kbin.social
        link
        fedilink
        arrow-up
        5
        ·
        1 year ago

        I just checked it out. That licensing documentation is a mess. They say that it’s released under the AGPL, but not all of it? So what they are saying is that the whole product is not actually under the AGPL. I wonder if their “freeware” part can actually be removed without major loss of functionality. Because if that’s possible, then you could simply rebundle that one.

        But I suspect it exists exactly to “taint” the open source nature of the product.

        • PullUpCircuit@iusearchlinux.fyiOP
          link
          fedilink
          arrow-up
          4
          ·
          1 year ago

          I suspect most of it leans heavily on ghostscript, so they are required to provide AGPL. They would like to obtain support contracts, so support requests are considered out of compliance unless they are paid. I find it interesting that they basically have AGPL+ were plus is whatever they have on their license page in addition to AGPL.