Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some files in openwhisk-apigateway still have bad headers #108

Closed
daisy-ycguo opened this issue Apr 11, 2018 · 5 comments
Closed

Some files in openwhisk-apigateway still have bad headers #108

daisy-ycguo opened this issue Apr 11, 2018 · 5 comments
Assignees

Comments

@daisy-ycguo
Copy link
Member

We have MIT license and adobe copyright in below files:

  MIT   openwhisk-apigateway/api-gateway.conf
  MIT   openwhisk-apigateway/tests/test_initialization.t
  MIT   openwhisk-apigateway/conf.d/api_gateway_init.conf
  MIT   openwhisk-apigateway/conf.d/management_apis.conf
  MIT   openwhisk-apigateway/conf.d/commons/common-headers.conf
  MIT   openwhisk-apigateway/conf.d/api_gateway_logging.conf
  MIT   openwhisk-apigateway/conf.d/includes/analytics_endpoints.conf
  MIT   openwhisk-apigateway/conf.d/includes/basic_endpoints.conf
  MIT   openwhisk-apigateway/conf.d/managed_endpoints.conf
  MIT   openwhisk-apigateway/conf.d/default.conf
  MIT   openwhisk-apigateway/conf.d/blacklist.conf

We need to decide how to handle them. According to Apache license policy, the copyright owner (or owner's agent) must remove the copyright notice or move them to the NOTICE file, or authorize us to make such modifications.

@daisy-ycguo daisy-ycguo changed the title Some files in openwhisk-apigateway still have bad license headers Some files in openwhisk-apigateway still have bad headers Apr 11, 2018
@houshengbo
Copy link

houshengbo commented Apr 12, 2018

I opened the same issue for apigateway repo: apache/openwhisk-apigateway#288 to raise their concerns.

@mrutkows
Copy link
Contributor

@daisy-ycguo @houshengbo Thanks for writing and merging PR apache/openwhisk-apigateway#239

@mrutkows
Copy link
Contributor

@mrutkows
Copy link
Contributor

@daisy-ycguo @houshengbo please review current source files and see if we can close this issue. Thanks!

@daisy-ycguo
Copy link
Member Author

I checked it with RAT and scan code. I also did a manually check. I think we can close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants