6 ms·

Yes, but this is exactly the point: These companies want to start open and free, to get as many people as possible to use their product. And then, later, they w

Yes, but this is exactly the point: These companies want to start open and free, to get as many people as possible to use their product. And then, later, they want to make money from it. This is the "bait & switch". It is planned right from the beginning, the tricky part is that you need to make the "it's completely free" phase as long as possible (using borrowed cash, investor money, whatever) to have as large a userbase as possible. And THEN switch. It's literally the definition of "bait & switch"

LtWorf 4y ago
You can't change license of published work. They are changing license of the new stuff. You are free to keep using whatever you were using forever. It's the same as a maintainer just abandoning a project and you having to take over.
- kazinator 4y ago
  The copyright holder can absolutely change the license of a published work. The FOSS license thereby becomes unavailable; no new users can become licensees. If the FOSS license was such that it didn't restrict use, but only redistribution, then only the existing redistributors are licensees. The existing users have no rights. If the new license says that unlicensed use is not allowed, then the users are now infringing. They didn't agree to any license in order to use the program when it was free and therefore they are not in any agreement that can be grandfathered. Even if a license says that it's irrevocable (or some doctrine applies which makes it so, regardless) it can only be irrevocable to those users who have entered into the license. Those users may enjoy the continued right to redistribute the program. However, new users receiving the program do not benefit from the irrevocability; they have no existing license contract that can be grandfathered. If a program has gone from FOSS to "cannot redistribute or use", the situation is like that existing licensees are allowed to give away copies, but the new users receiving them aren't allowed to do anything with those copies. Software whose copyright holder has expressed revocation of a FOSS license should be regarded by all parties as a piece of radioactive or biohazardous waste. Don't even think about maintaining a fork or anything of the sort.
  - jjav 4y ago
    > The FOSS license thereby becomes unavailable No, that's not how it works. If libfoo 2.0 was released under an open source license, it remains so into the future. If a company was the owner of that source code and decides the libfoo 2.1 is now suddenly proprietary and no longer open source they can certainly do that. But libfoo 2.0 remains open source and can be forked by the community or whoever wants. There are many examples of this, for example Open Solaris. When Oracle bought Sun they quickly reverted Solaris back to closed source. But not even the (arguably) most lawyered-up tech company in the world can change history and change the license on the the previous Open Solaris releases. That's how Solaris forked into the proprietary Solaris which Oracle still keeps alive and the open source descendants of Open Solaris (Illumos, etc.)
    - kazinator 4y ago
      > If libfoo 2.0 was released under an open source license, it remains so into the future. I would trust that only if the copyright holder makes it clear that they are not revoking the license for libfoo 2.0, but that libfoo 2.0.1 will be under a different license. If they indicate that they wish to revoke the license for previously released libfoo 2.0, it seems they have the right to do that; I don't want to be the one testing it in court. I don't know about the details of the Solaris/Oracle situation, but I doubt it hinged around it simply not being possible to revert a license, as such.
      - jjav 4y ago
        I probably can't convince you (that's fine), but no, a company can't rewrite history just because they want to. A company as aggressively litigious as Oracle would love nothing more than to kill off all Open Solaris forks. But Sun released Open Solaris with an open source license so it's not something they can change. Consult a lawyer whenever you need to use an open source project, their opinion carries weight that mine does not.
        kazinator 4y ago
        You're not going to convince anyone with that Oracle Solaris example mainly because there is likely a reason they couldn't retract the license: tons of code in there for which they are not the sole copyright holders. At best they could take back the 100% Oracle-owned parts. The community would have to build to fill in the gaps. They couldn't revoke any files that have, say, a BSD license, even if Oracle (or Sun, before them) had modified them and added their own copyright notice, simply because they would need to contact the original authors and act in concert with them; those authors would likely refuse. I'm mainly talking about situations when the revoking party is actually 100% copyright holder to the majority of the files implementing the payload functionality, without which there is no software. I don't see how you the copyright holder would not have the right to revoke a FOSS license over it. Based on what? None of the existing licensees have a signed contract of any kind, nor has any exchange of value taken place; allowing free redistribution and use was an uncompensated, unilateral action. Even if there were a doctrine that existing redistributors were grandfathered forever, so they could continue making copies and giving it away, the license would not actually be available to the recipients, who are not existing licensees. The U.S. Copyright Act indeed has the concept of termination: https://cdas.com/copyright-termination-prime/ https://cdas.com/copyright-termination-prime/ There are limitations to it for various obvious reasons, like that you can't terminate the copyright assignment implicit in a work for hire. (Because, doh, you were paid.)
- dark-star 4y ago
  I never claimed that they change the license on the published work. The argument still stands: Nobody wants to use the old, possibly unmaintained version so everyone is buying the new commercial versions. At least that's their hope. And 90% of customers probably do, if they have reached a critical mass by that time. * Bait = get as many people to use your software as possible * Switch = THEN change the license (for new additions) so that as few people as possible jump ship. Bonus points if you do it shortly before adding a cool new feature that lots of people are waiting for Sometimes it works. Sometimes, Amazon is quicker and offers a product based on your version. The trick is to get the timing right...
  - LtWorf 4y ago
    > The argument still stands it doesn't. It's a completely different argument. You want support buy support.

LtWorf 4y ago

You can't change license of published work. They are changing license of the new stuff. You are free to keep using whatever you were using forever. It's the same as a maintainer just abandoning a project and you having to take over.

kazinator 4y ago
The copyright holder can absolutely change the license of a published work. The FOSS license thereby becomes unavailable; no new users can become licensees. If the FOSS license was such that it didn't restrict use, but only redistribution, then only the existing redistributors are licensees. The existing users have no rights. If the new license says that unlicensed use is not allowed, then the users are now infringing. They didn't agree to any license in order to use the program when it was free and therefore they are not in any agreement that can be grandfathered. Even if a license says that it's irrevocable (or some doctrine applies which makes it so, regardless) it can only be irrevocable to those users who have entered into the license. Those users may enjoy the continued right to redistribute the program. However, new users receiving the program do not benefit from the irrevocability; they have no existing license contract that can be grandfathered. If a program has gone from FOSS to "cannot redistribute or use", the situation is like that existing licensees are allowed to give away copies, but the new users receiving them aren't allowed to do anything with those copies. Software whose copyright holder has expressed revocation of a FOSS license should be regarded by all parties as a piece of radioactive or biohazardous waste. Don't even think about maintaining a fork or anything of the sort.
- jjav 4y ago
  > The FOSS license thereby becomes unavailable No, that's not how it works. If libfoo 2.0 was released under an open source license, it remains so into the future. If a company was the owner of that source code and decides the libfoo 2.1 is now suddenly proprietary and no longer open source they can certainly do that. But libfoo 2.0 remains open source and can be forked by the community or whoever wants. There are many examples of this, for example Open Solaris. When Oracle bought Sun they quickly reverted Solaris back to closed source. But not even the (arguably) most lawyered-up tech company in the world can change history and change the license on the the previous Open Solaris releases. That's how Solaris forked into the proprietary Solaris which Oracle still keeps alive and the open source descendants of Open Solaris (Illumos, etc.)
  - kazinator 4y ago
    > If libfoo 2.0 was released under an open source license, it remains so into the future. I would trust that only if the copyright holder makes it clear that they are not revoking the license for libfoo 2.0, but that libfoo 2.0.1 will be under a different license. If they indicate that they wish to revoke the license for previously released libfoo 2.0, it seems they have the right to do that; I don't want to be the one testing it in court. I don't know about the details of the Solaris/Oracle situation, but I doubt it hinged around it simply not being possible to revert a license, as such.
    - jjav 4y ago
      I probably can't convince you (that's fine), but no, a company can't rewrite history just because they want to. A company as aggressively litigious as Oracle would love nothing more than to kill off all Open Solaris forks. But Sun released Open Solaris with an open source license so it's not something they can change. Consult a lawyer whenever you need to use an open source project, their opinion carries weight that mine does not.
      - kazinator 4y ago
        You're not going to convince anyone with that Oracle Solaris example mainly because there is likely a reason they couldn't retract the license: tons of code in there for which they are not the sole copyright holders. At best they could take back the 100% Oracle-owned parts. The community would have to build to fill in the gaps. They couldn't revoke any files that have, say, a BSD license, even if Oracle (or Sun, before them) had modified them and added their own copyright notice, simply because they would need to contact the original authors and act in concert with them; those authors would likely refuse. I'm mainly talking about situations when the revoking party is actually 100% copyright holder to the majority of the files implementing the payload functionality, without which there is no software. I don't see how you the copyright holder would not have the right to revoke a FOSS license over it. Based on what? None of the existing licensees have a signed contract of any kind, nor has any exchange of value taken place; allowing free redistribution and use was an uncompensated, unilateral action. Even if there were a doctrine that existing redistributors were grandfathered forever, so they could continue making copies and giving it away, the license would not actually be available to the recipients, who are not existing licensees. The U.S. Copyright Act indeed has the concept of termination: https://cdas.com/copyright-termination-prime/ https://cdas.com/copyright-termination-prime/ There are limitations to it for various obvious reasons, like that you can't terminate the copyright assignment implicit in a work for hire. (Because, doh, you were paid.)
dark-star 4y ago
I never claimed that they change the license on the published work. The argument still stands: Nobody wants to use the old, possibly unmaintained version so everyone is buying the new commercial versions. At least that's their hope. And 90% of customers probably do, if they have reached a critical mass by that time. * Bait = get as many people to use your software as possible * Switch = THEN change the license (for new additions) so that as few people as possible jump ship. Bonus points if you do it shortly before adding a cool new feature that lots of people are waiting for Sometimes it works. Sometimes, Amazon is quicker and offers a product based on your version. The trick is to get the timing right...
- LtWorf 4y ago
  > The argument still stands it doesn't. It's a completely different argument. You want support buy support.