Uploaded image for project: 'VinePerf'
  1. VinePerf
  2. VINEPERF-489

Add license info to all project files

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Fixed
    • Icon: Major Major
    • Danube 1.0
    • None
    • None

      Original request:

      All,

      During the recent license scan, we noticed that there were a lot of files that are missing license header information. If you need help/examples for license headers, please check out https://wiki.opnfv.org/display/DEV/Contribution+Guidelines

      If you have files (e.g. image files) where license information can not be added, you can add a LICENSE file at the directory level.

      Also a reminder that documentations in OPNFV need to be under the Creative Commons Attribution 4.0 International License (CC 4.0). We did see a number of files under Creative Commons 3.0, so please make sure these are updated to CC 4.0.

      Let me know if you have any questions.

      Thanks,

      Ray

      Following files don't have license headers:

      for a in `git ls-tree --name-only -r HEAD | sort` ; do egrep -i "(copyright|license)" $a &> /dev/null || echo $a ; done 
      CONTRIBUTING.md
      docs/configguide/TCLServerProperties.png
      docs/design/factory_and_loader.png
      docs/design/traffic_controller.png
      docs/design/vsperf.png
      docs/msc/factory_and_loader.msc
      docs/msc/traffic_controller.msc
      docs/msc/vsperf.msc
      docs/requirements/ietf_draft/draft-ietf-bmwg-vswitch-opnfv-00.xml
      docs/requirements/ietf_draft/draft-ietf-bmwg-vswitch-opnfv-01.xml
      docs/requirements/ietf_draft/draft-vsperf-bmwg-vswitch-opnfv-00.xml
      docs/requirements/ietf_draft/draft-vsperf-bmwg-vswitch-opnfv-01.xml
      docs/requirements/ietf_draft/draft-vsperf-bmwg-vswitch-opnfv-02.xml
      docs/requirements/vm2vm_alternative_benchmark.png
      docs/requirements/vm2vm_benchmark.png
      docs/requirements/vm2vm_hypervisor_benchmark.png
      docs/requirements/vm2vm_virtual_interface_benchmark.png
      fuel-plugin-vsperf/deployment_scripts/deploy.sh
      fuel-plugin-vsperf/deployment_scripts/puppet/manifests/vsperf-install.pp
      fuel-plugin-vsperf/deployment_tasks.yaml
      fuel-plugin-vsperf/environment_config.yaml
      fuel-plugin-vsperf/node_roles.yaml
      fuel-plugin-vsperf/pre_build_hook
      fuel-plugin-vsperf/README.md
      fuel-plugin-vsperf/repositories/centos/.gitkeep
      fuel-plugin-vsperf/repositories/ubuntu/.gitkeep
      fuel-plugin-vsperf/tasks.yaml
      fuel-plugin-vsperf/vagrant/build_fuel_plugin.sh
      fuel-plugin-vsperf/vagrant/README.md
      fuel-plugin-vsperf/vagrant/Vagrantfile
      .gitignore
      .gitreview
      INFO
      jobs/README
      onboarding.txt
      packages.txt
      README.md
      requirements.txt
      src/mk/README
      src/package-list.mk
      src/README
      systems/README
      systems/ubuntu/16.04
      systems/ubuntu/16.10
      testcases/README
      tools/README
      tools/report/__init__.py
      tools/report/report_foot.rst
      tools/report/report.jinja
      tools/report/report_rst.jinja
      vswitches/README
      

      Following files at artifactory don't have any license information:

      vswitchperf/vnf/vloop-vnf-ubuntu-14.04_20151216.qcow2
      vswitchperf/vnf/vloop-vnf-ubuntu-14.04_20160303.qcow2
      vswitchperf/vnf/vloop-vnf-ubuntu-14.04_20160804.qcow2
      vswitchperf/vnf/vloop-vnf-ubuntu-14.04_20160823.qcow2
      vswitchperf/vnf/vsperf-yardstick-image.qcow2
      

      TBD: What license should be added to these VM images? It is in general configured Ubuntu 14.04 image. So we can hardly put there our own license. It is also not clear if artifactory elements should be also licensed or not.

            mgoldammer Martin Goldammer
            mklozik Martin Klozik
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: