Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Component/s: SOUL-FI
    • Labels:
      None

      Description

      Hello,

      There a lot of GEs with many different licenses (MIT, AFERO, GPL, MPL).
      If we use GEs with these open source licenses:

      Do we have to make all our source open?
      Is there any obligation in case we use the service under SaaS modality?

      Regards,
      Angel
      Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
      Please, send your messages using the new domain (Fiware-soulfi-coaching@lists.fiware.org) instead of the old one.
      _______________________________________________
      Fiware-soulfi-coaching mailing list
      Fiware-soulfi-coaching@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-soulfi-coaching

      [Created via e-mail received from: Angel Iglesias <aiglesias@eurob.com>]

        Activity

        Hide
        fw.ext.user FW External User added a comment -

        Dear Angel,
        It's true that different GEs have different open source licenses, but this does not affect your product or how you license it, unless you change the GEs source code, in which case you should release the GE changes in certain cases (depending on license).
        Best Regards,
        Sergio.

        ----Mensaje original----
        De: fiware-soulfi-coaching-bounces@lists.fiware.org fiware-soulfi-coaching-bounces@lists.fiware.org En nombre de Angel Iglesias
        Enviado el: 25 November 2015 11:53
        Para: fiware-soulfi-coaching@lists.fiware.org
        Asunto: [Fiware-soulfi-coaching] License

        Hello,

        There a lot of GEs with many different licenses (MIT, AFERO, GPL, MPL).
        If we use GEs with these open source licenses:

        Do we have to make all our source open?
        Is there any obligation in case we use the service under SaaS modality?

        Regards,
        Angel
        Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
        Please, send your messages using the new domain (Fiware-soulfi-coaching@lists.fiware.org) instead of the old one.

        Show
        fw.ext.user FW External User added a comment - Dear Angel, It's true that different GEs have different open source licenses, but this does not affect your product or how you license it, unless you change the GEs source code, in which case you should release the GE changes in certain cases (depending on license). Best Regards, Sergio. ---- Mensaje original ---- De: fiware-soulfi-coaching-bounces@lists.fiware.org fiware-soulfi-coaching-bounces@lists.fiware.org En nombre de Angel Iglesias Enviado el: 25 November 2015 11:53 Para: fiware-soulfi-coaching@lists.fiware.org Asunto: [Fiware-soulfi-coaching] License Hello, There a lot of GEs with many different licenses (MIT, AFERO, GPL, MPL). If we use GEs with these open source licenses: Do we have to make all our source open? Is there any obligation in case we use the service under SaaS modality? Regards, Angel Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost. Please, send your messages using the new domain (Fiware-soulfi-coaching@lists.fiware.org) instead of the old one.
        Hide
        fw.ext.user FW External User added a comment -

        Dear Sergio,
        could you please elaborate a bit more? Do you mean that by including a GE code in our SW we are not affected by the license governing that code?

        It is not enough clear to us, and what from what we have read from the licenses terms, we understand that there are strong implications and differences in each of the following aspects:
        (For clarity view please asume that that we not using the GEs as external components provided by a third party to which we connect, but instead we instantiate them in our servers).

        • To what extend including a GEs (from the different licenses) forces us to release the code, even if we do not modify the code from that GE (for example MIT forces to release the code if you include MIT code as we understood), in case we distribute our SW
        • To what extend running our SW in our servers (ie. Software as a Service) forces us to release the code (AFERO license closing ASP loophole)?
        • Whenever can we sell the code or not are we forced to include the code ?
        • When we include GEs, and specially mix GEs containing different licenses, what is the resulting license of our code??

        And in addition, to the above, what happens if in addition we modify the GE code, not so strange, to adapt it to our needs?

        We (and many projects, from our talks) would very much appreciate a clarification table (document) of what can be done or not with each time of license, in terms of obligation to distribute or not the code, sublicensing, selling SW, running as a service, obligation to include credits/copyrights, resulting license when incorporating several different GEs and a few more related things.

        Many thanks,
        Roberto

        Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
        Please, send your messages using the new domain (Fiware-soulfi-coaching@lists.fiware.org) instead of the old one.
        _______________________________________________
        Fiware-soulfi-coaching mailing list
        Fiware-soulfi-coaching@lists.fiware.org
        https://lists.fiware.org/listinfo/fiware-soulfi-coaching

        Show
        fw.ext.user FW External User added a comment - Dear Sergio, could you please elaborate a bit more? Do you mean that by including a GE code in our SW we are not affected by the license governing that code? It is not enough clear to us, and what from what we have read from the licenses terms, we understand that there are strong implications and differences in each of the following aspects: (For clarity view please asume that that we not using the GEs as external components provided by a third party to which we connect, but instead we instantiate them in our servers). To what extend including a GEs (from the different licenses) forces us to release the code, even if we do not modify the code from that GE (for example MIT forces to release the code if you include MIT code as we understood), in case we distribute our SW To what extend running our SW in our servers (ie. Software as a Service) forces us to release the code (AFERO license closing ASP loophole)? Whenever can we sell the code or not are we forced to include the code ? When we include GEs, and specially mix GEs containing different licenses, what is the resulting license of our code?? And in addition, to the above, what happens if in addition we modify the GE code, not so strange, to adapt it to our needs? We (and many projects, from our talks) would very much appreciate a clarification table (document) of what can be done or not with each time of license, in terms of obligation to distribute or not the code, sublicensing, selling SW, running as a service, obligation to include credits/copyrights, resulting license when incorporating several different GEs and a few more related things. Many thanks, Roberto Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost. Please, send your messages using the new domain (Fiware-soulfi-coaching@lists.fiware.org) instead of the old one. _______________________________________________ Fiware-soulfi-coaching mailing list Fiware-soulfi-coaching@lists.fiware.org https://lists.fiware.org/listinfo/fiware-soulfi-coaching

          People

          • Assignee:
            sergg Sergio Garcia Gomez
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: