OODT
  1. OODT
  2. OODT-3

Update source code to use ASL headers and add NOTICE, etc.

    Details

      Description

      Now that OODT-1 and OODT-2 are taken care of, we need to update the source code to use Apache style license headers. We also need to add a NOTICE.txt, a LICENSE.txt file, and it would be good to add a CHANGES.txt as well.

      1. deps.csv
        9 kB
        David Woollard
      2. oodt966905rat.txt
        450 kB
        David Woollard

        Issue Links

          Activity

          Hide
          Chris A. Mattmann added a comment -

          Thanks to:

          smcclees, ahart, woollard, mattmann, kelly, pramirez and all the other folks who worked on this long and bloated issue!

          I'm calling it done. I think we've got RAT in place and an understanding in place for how to maintain compliance.

          I'm going to wrap up pushpull now. Let's make sure the catalog stuff aligns with this.

          Show
          Chris A. Mattmann added a comment - Thanks to: smcclees, ahart, woollard, mattmann, kelly, pramirez and all the other folks who worked on this long and bloated issue! I'm calling it done. I think we've got RAT in place and an understanding in place for how to maintain compliance. I'm going to wrap up pushpull now. Let's make sure the catalog stuff aligns with this.
          Hide
          David Woollard added a comment -

          I wrote up a quick script to grab all the build dependencies and I have listed a very initial cut at licensing info for each dependency. There are a couple that we should handle and I will file issues for removing the obvious ones...

          Show
          David Woollard added a comment - I wrote up a quick script to grab all the build dependencies and I have listed a very initial cut at licensing info for each dependency. There are a couple that we should handle and I will file issues for removing the obvious ones...
          Hide
          Chris A. Mattmann added a comment -

          Hey Dave:

          Thanks for pushing forward on this! Comments below:

          1) The CPP version of Metadata currently depends on a GPL XML parser. The suggestion from Chris is to move this over to Xerces CPP.

          +1.

          2) The curator uses JTidy and we should shift this over to apache commons.

          +1

          3) Currently, the following Category A licensed software is included:

          • The webapp uses the "WebAppers Progress Bar" which is released under the Creative Commons license. Source is at webapp/workflow/src/main/webapp/js/progress/progress.js
          • The webapp uses the "Prototype JavaScript framework" which is MIT licensed. Source is at /Users/woollard/Desktop/apache-oodt/webapp/workflow/src/main/webapp/js/prototype/prototype.js
          • The curator use JQuery extensively. This is both Cat A (MIT) and also GPL.
            {quote]

          See my recent email reply on oodt-dev@ for the next steps on this...

          Thanks!

          Cheers,
          Chris

          Show
          Chris A. Mattmann added a comment - Hey Dave: Thanks for pushing forward on this! Comments below: 1) The CPP version of Metadata currently depends on a GPL XML parser. The suggestion from Chris is to move this over to Xerces CPP. +1. 2) The curator uses JTidy and we should shift this over to apache commons. +1 3) Currently, the following Category A licensed software is included: The webapp uses the "WebAppers Progress Bar" which is released under the Creative Commons license. Source is at webapp/workflow/src/main/webapp/js/progress/progress.js The webapp uses the "Prototype JavaScript framework" which is MIT licensed. Source is at /Users/woollard/Desktop/apache-oodt/webapp/workflow/src/main/webapp/js/prototype/prototype.js The curator use JQuery extensively. This is both Cat A (MIT) and also GPL. {quote] See my recent email reply on oodt-dev@ for the next steps on this... Thanks! Cheers, Chris
          Hide
          David Woollard added a comment -

          The RAT report for r966905.

          Show
          David Woollard added a comment - The RAT report for r966905.
          Hide
          David Woollard added a comment -

          As of r966905, we are doing pretty well on apache licensing. While there are a number of files that we can ignore (examples), the following are issues to be resolved:

          1) The CPP version of Metadata currently depends on a GPL XML parser. The suggestion from Chris is to move this over to Xerces CPP.

          2) The curator uses JTidy and we should shift this over to apache commons.

          3) Currently, the following Category A licensed software is included:

          • The webapp uses the "WebAppers Progress Bar" which is released under the Creative Commons license. Source is at webapp/workflow/src/main/webapp/js/progress/progress.js
          • The webapp uses the "Prototype JavaScript framework" which is MIT licensed. Source is at /Users/woollard/Desktop/apache-oodt/webapp/workflow/src/main/webapp/js/prototype/prototype.js
          • The curator use JQuery extensively. This is both Cat A (MIT) and also GPL.
            We should make sure we are following the process for including their licensing correctly.
          Show
          David Woollard added a comment - As of r966905, we are doing pretty well on apache licensing. While there are a number of files that we can ignore (examples), the following are issues to be resolved: 1) The CPP version of Metadata currently depends on a GPL XML parser. The suggestion from Chris is to move this over to Xerces CPP. 2) The curator uses JTidy and we should shift this over to apache commons. 3) Currently, the following Category A licensed software is included: The webapp uses the "WebAppers Progress Bar" which is released under the Creative Commons license. Source is at webapp/workflow/src/main/webapp/js/progress/progress.js The webapp uses the "Prototype JavaScript framework" which is MIT licensed. Source is at /Users/woollard/Desktop/apache-oodt/webapp/workflow/src/main/webapp/js/prototype/prototype.js The curator use JQuery extensively. This is both Cat A (MIT) and also GPL. We should make sure we are following the process for including their licensing correctly.
          Hide
          David Woollard added a comment -

          In chatting with Justin Erenkrantz, it seems the answers to my questions are:

          1) Do xml-based config files and pom files need a license?
          yes

          2) Do examples and test data used in unit tests need a license?
          sometimes, based on our judgement. input to unit test, probably not. examples, possibly depending on if they are raw output that needs to be matched, etc. etc.

          Dave

          Show
          David Woollard added a comment - In chatting with Justin Erenkrantz, it seems the answers to my questions are: 1) Do xml-based config files and pom files need a license? yes 2) Do examples and test data used in unit tests need a license? sometimes, based on our judgement. input to unit test, probably not. examples, possibly depending on if they are raw output that needs to be matched, etc. etc. Dave
          Hide
          David Woollard added a comment -

          To which portions of the code-base does this issue apply? Specifically, I have the following questions:
          1) Do xml-based config files and pom files need a license?
          2) Do examples and test data used in unit tests need a license?

          Thanks!
          Dave

          Show
          David Woollard added a comment - To which portions of the code-base does this issue apply? Specifically, I have the following questions: 1) Do xml-based config files and pom files need a license? 2) Do examples and test data used in unit tests need a license? Thanks! Dave
          Hide
          Chris A. Mattmann added a comment -

          I think this is basically done. However, just to be safe, can someone please run Rat [1] on the OODT source code and see what they come up with? Please attach the report here...

          Cheers,
          Chris

          [1] http://incubator.apache.org/rat/

          Show
          Chris A. Mattmann added a comment - I think this is basically done. However, just to be safe, can someone please run Rat [1] on the OODT source code and see what they come up with? Please attach the report here... Cheers, Chris [1] http://incubator.apache.org/rat/
          Hide
          Sean McCleese added a comment -

          All *.java files are finished. The only remaining TODO are the supporting files (xml, etc)

          Show
          Sean McCleese added a comment - All *.java files are finished. The only remaining TODO are the supporting files (xml, etc)

            People

            • Assignee:
              Chris A. Mattmann
              Reporter:
              Chris A. Mattmann
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development