Axis2-C
  1. Axis2-C
  2. AXIS2C-915

Axis2/C licensing issue with it's dependencies

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.0
    • Fix Version/s: 1.3.0
    • Component/s: None
    • Labels:
      None

      Description

      Need to figure out how to handle licensing of Axis2/C dependencies properly.

      1. LICENSE
        15 kB
        Dinesh Weerapurage

        Issue Links

          Activity

          Hide
          Dinesh Weerapurage added a comment -

          I included licenses of the libxml2 and libcurl into LICENSE file. I think, those are the only dependencies that we are directly depend on. Please review attached license file, then we could commit it to svn trunk.

          Show
          Dinesh Weerapurage added a comment - I included licenses of the libxml2 and libcurl into LICENSE file. I think, those are the only dependencies that we are directly depend on. Please review attached license file, then we could commit it to svn trunk.
          Hide
          Dinesh Weerapurage added a comment -

          added zlib license too

          Show
          Dinesh Weerapurage added a comment - added zlib license too
          Hide
          Senaka Fernando added a comment -

          I don't think that we need to add the GPL license since we include the configure script generated by autoconf. However, it is required that we make sure that all such configure scripts inside subdirectories such as util, tests, tools etc are shipped. That is a key criteria.

          Regards,
          Senaka

          Show
          Senaka Fernando added a comment - I don't think that we need to add the GPL license since we include the configure script generated by autoconf. However, it is required that we make sure that all such configure scripts inside subdirectories such as util, tests, tools etc are shipped. That is a key criteria. Regards, Senaka
          Hide
          Senaka Fernando added a comment -

          We also need to attribute dependent apache projects including their usefulness.

          Regards,
          Senaka

          Show
          Senaka Fernando added a comment - We also need to attribute dependent apache projects including their usefulness. Regards, Senaka
          Hide
          Dinesh Weerapurage added a comment -

          Senaka,
          I don't think that we need to mention Apache projects we are using in License file since we already have Apache2.0 license in it.

          Show
          Dinesh Weerapurage added a comment - Senaka, I don't think that we need to mention Apache projects we are using in License file since we already have Apache2.0 license in it.
          Hide
          Samisa Abeysinghe added a comment -

          We do not need to include other Apache projects in license file, but it would be good to mention them in the Credits file

          Show
          Samisa Abeysinghe added a comment - We do not need to include other Apache projects in license file, but it would be good to mention them in the Credits file
          Hide
          Samisa Abeysinghe added a comment -

          Are we all set to resolve this issue, or do we have any other stuff to fix?
          Can we prepare a checklist on the things to be check for verifying compliance based on the knowhow we gained while solving this issue?

          Show
          Samisa Abeysinghe added a comment - Are we all set to resolve this issue, or do we have any other stuff to fix? Can we prepare a checklist on the things to be check for verifying compliance based on the knowhow we gained while solving this issue?
          Hide
          Dinesh Weerapurage added a comment -

          +1 , That sounds good to me.

          Show
          Dinesh Weerapurage added a comment - +1 , That sounds good to me.
          Hide
          Senaka Fernando added a comment -

          +1 for making a check-list.

          We need to be sure to attribute code that has been copied. Especially on examples found in specifications. This includes .wsdl files that have attributions, code copied from rfcs etc. I think it is better to get all devs involved in the process, so that they'd be responsible for attributing code from external sources that they've written, used etc.

          Regards,
          Senaka

          Show
          Senaka Fernando added a comment - +1 for making a check-list. We need to be sure to attribute code that has been copied. Especially on examples found in specifications. This includes .wsdl files that have attributions, code copied from rfcs etc. I think it is better to get all devs involved in the process, so that they'd be responsible for attributing code from external sources that they've written, used etc. Regards, Senaka
          Hide
          Senaka Fernando added a comment -

          The presence of the configure script, if we are using code generated by autotools is a major item on the checklist.

          Regards,
          Senaka

          Show
          Senaka Fernando added a comment - The presence of the configure script, if we are using code generated by autotools is a major item on the checklist. Regards, Senaka
          Hide
          Dinesh Weerapurage added a comment -

          Does somebody has an idea about how to deal with licensing with IIS module ?

          Show
          Dinesh Weerapurage added a comment - Does somebody has an idea about how to deal with licensing with IIS module ?
          Hide
          Dinesh Weerapurage added a comment -

          I look into preparing check list for addressing licensing issue. After looking into details , I realize that that checklist will be more or less same as this document [1], we need to get almost all details from it. Therefore I think , it is better to use this document as our checklist or guideline document. AFAIU, It explains well all the issues that we need to address.

          Thoughts ??

          1. http://people.apache.org/~cliffs/3party.html

          Show
          Dinesh Weerapurage added a comment - I look into preparing check list for addressing licensing issue. After looking into details , I realize that that checklist will be more or less same as this document [1] , we need to get almost all details from it. Therefore I think , it is better to use this document as our checklist or guideline document. AFAIU, It explains well all the issues that we need to address. Thoughts ?? 1. http://people.apache.org/~cliffs/3party.html

            People

            • Assignee:
              Dinesh Weerapurage
              Reporter:
              Dinesh Weerapurage
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development