5 ms·

This is pretty cool. Will you do any kind of personal variant for gmail refugees?

• hbbio 13y ago
  Thanks. Yes, we are thinking about the following business model for PEPS, which was built for an important account but of which we own the IP. 1. Open source under the AGPL license, so that anyone can host its own instance easily and hopefully we can build a community around the product. 2. Sell support (together with a non-AGPL license for corporations). OR 1. Open source under the MIT license the current product. 2. Sell a complete packaged solution with add-ons for corporate users. Any feedback between the two?
  • angersock 13y ago
    Voting for 2...AGPL is like biohazard level 4 viral.
    • rufugee 13y ago
      How exactly would it be viral in this case? I ask because it's damned confusing. Since this would be an email server, wouldn't it be a drop-in component in most folks' infrastructure? If I understand it correctly, it would just require me to make the source code of the email server/client itself available to my users...not any of my other unrelated infrastructure apps, correct?
      • angersock 13y ago
        I was under the impression that AGPL requires the open-sourcing of everything that touches user data at any point in the pipeline.
        • teddyh 13y ago
          The AGPL is exactly the same as the GPL, except that if there is a button to click to download the source code of the program, you are not allowed to remove that button.
          • angersock 13y ago
            From the AGPL FAQ: If the Program as you received it is intended to interact with users through a computer network and if, in the version you received, any user interacting with the Program was given the opportunity to request transmission to that user of the Program's complete source code, you must not remove that facility from your modified version of the Program or work based on the Program, and must offer an equivalent opportunity for all users interacting with your Program through a computer network to request immediate transmission by HTTP of the complete source code of your modified version or other derivative work." That last part--"derivative work"--is somewhat the rub.
            • belorn 13y ago
              If that part of the informal FAQ worries you that it might be interpreted in some strange way, just look at the actually license and read it. Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version The definition of Corresponding Source code is listed earlier in this HN thread.
      • ensignavenger 13y ago
        This is the problem with the GPL/AGPL- what exactly must be open sourced under what conditions has been debated many times, and different people/groups have come to very different conclusions.
        • belorn 13y ago
          The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. Please point out what exactly the different conclusions are to that text.
          • ensignavenger 13y ago
            I am not an expert on the various points of the debate- I only know it exists. You can Duck Duck Go for "gpl derivative work definition" and find some references to this debate. Perhaps someone else has a specific answer for your question, sorry.
      • riquito 13y ago
        Correct, just the source code of the AGPL application, not of your server.
    • belorn 13y ago
      And WTFPL which you are using is the level 5 of foul language, and the death sentence to software names. See, I can also use offensive language to describe a license. Doesn't that make for a nice conversation here on HN?
      • angersock 13y ago
        To be fair, if you use our code under the WTFPL (and don't, because it's like three versions and two test suites out of date, at this point!) we don't require that you open-source any other part of your stack.
  • airencracken 13y ago
    AGPL would be perfect for such a product.