4 ms·

License AGPL3 https://github.com/makeplane/plane/blob/develop/LICENSE.txt https://github.com/makeplane/plane/blob/develop/LICENSE.txt

• kissgyorgy 3y ago
  As a user, that's the best for a software like this, because it means it cannot be ever closed source!
  • dspillett 3y ago
    > cannot be ever closed source Cannot be closed source unless the maintainer dual licenses and stops making OS (assuming a single maintainer or group that all agree, or that other contributors have signed a relevant copyright waiver). (though what has already been released can't be retracted)
    • stavros 3y ago
      > (though what has already been released can't be retracted) This is the only relevant bit. A license can't force people to do work for free in the future.
      • deleted 3y ago
        [deleted]
    • remram 3y ago
      Not the maintainer, all the copyright holders. If you accept contributions without a CLA, that closes that avenue. I couldn't find any outside contribution in the repo yet, we'll see how they go.
      • dspillett 3y ago
        Hence all my bits in brackets…
  • jillesvangurp 3y ago
    It has that in common with essentially all other open source license. And it only extends to the version given to you under the license. The copyright holder(s) retain the right to change their mind. Which is a reason AGPL v3 is popular with companies that are looking to sell commercial licenses for their software. There are quite a few startups out there that attempted to keep control whose primary business model is providing a way out from the many restrictions the AGPL v3 imposes on users by offering a commercial license. In this case, it looks like Plane is not requiring copyright transfers. So that cuts off the practicality of them ever re-licensing their software (commercially or otherwise). That's a good thing as it means it is indeed not likely the license will ever change. The bad thing is that it would be hard to build a company around this project. The AGPLv3 is just very strict about having to open source any and all bundled features and imposes a lot of restrictions and requirements.
    • rapnie 3y ago
      What if a project has a plugin architecture and plugins are compiled files that can be dropped in at runtime? Those plugins can be any license then, is it not?
      • voakbasda 3y ago
        Plug-ins are generally considered a derived work, if directly written to use a specific API. You would need to build a module that works for many different systems and only uses the Plane APIs as a shim. Even then, the shim might be argued to be infected, and thus the rest of the module too. In that case, you still could be facing an expensive and risky lawsuit, because I don’t think there are any precedents to predict how those winds will blow.
      • maxloh 3y ago
        No. Those plugins call functions from AGPL's codebase and they are designed only to be combined with AGPL's work into a larger work, so they are derivative works. But there is a chance that CSS and svg icons are not required to be GPL. See WordPress clarification on themes' licensing: https://wordpress.org/news/2009/07/themes-are-gpl-too/ https://wordpress.org/news/2009/07/themes-are-gpl-too/
• goodpoint 3y ago
  Excellent!
• skwashd 3y ago
  Until last month they used the Apache license. https://github.com/makeplane/plane/commit/a3f6d61347ef98171f17d6b59bd4cacf8ebaf14f https://github.com/makeplane/plane/commit/a3f6d61347ef98171f...
  • hardwaresofton 3y ago
    Good catch thanks for pointing this out