As reported in a reddit post and confirmed in a github discussion, Simple Mobile Tools is being sold to ZippoApps which is known for shady business practices.

It is not yet clear whether they will make the app suite closed source (which would infringe the rights of all contributors since they contributed under the GPLv3 license).

In response to that situation, one of the main contributors forked the project under the name FossifyX and will continue to work on it.

  • @[email protected]
    link
    fedilink
    567 months ago

    This is open source at its best: the original developer somehow decided to sell out to the dark side and someone rescued the projects within a couple of days. Brillant!

    And thank goodness for that too: I used SMT Calendar but Etar misses a couple of features I really need that would make it a good replacement, so I’ll be sure to install FossifyX Calendar as soon as F-Droid picks it up.

    • Avid Amoeba
      link
      fedilink
      6
      edit-2
      7 months ago

      Some folks seem to forget this feature of open source when it comes to projects like Chromium. History has plenty of examples of forks of small and large projects. Chromium (Blink) itself is one.

    • @[email protected]
      link
      fedilink
      6
      edit-2
      7 months ago

      I dunno much about these licenses but is it possible the new owners could nullify the GPL rights? Like “no you can no longer fork this code that you could previously”?

      Just trying to figure out exactly what their motive is here…

      • @[email protected]OP
        link
        fedilink
        137 months ago

        (IANAL)

        Since the software is already distributed under the terms of the GPLv3 (which guarantees irrevocable rights) there is no way to forbid any distribution of the current version of the software.

        It is however possible to distribute future works under a different license, but only if you aren’t bound by the GPL yourself. This would be the case if you wrote the code yourself or all contributors grant you the right to do so (eg. using a Contributor License Agreement).

        • Avid Amoeba
          link
          fedilink
          3
          edit-2
          7 months ago

          There are clever ways to split software via different abstractions that allow to avoid some license features from affecting future developments too. That is to add new closed source features without relicensing the existing codebase.

      • @[email protected]
        link
        fedilink
        47 months ago

        Once someone exists publicly as code with an attached valid license it cannot be retroactively removed the right to use it. So only new versions could have different licenses or something.