Skip to content

Maintenance: Use correct license #116

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.

Sign up for GitHub

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

Jump to bottom
Closed
saragerion opened this issue Jul 16, 2021 · 1 comment · Fixed by #117
Closed

Maintenance: Use correct license #116

saragerion opened this issue Jul 16, 2021 · 1 comment · Fixed by #117
Assignees
@dreamorosi
Labels
completed This item is complete and has been merged/shipped documentation Improvements or additions to documentation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Milestone
beta-release

Comments

@saragerion
Copy link
Contributor

Bug description

Right now the repo is referencing the wrong license.
This one should be used instead (also important for consistency):
https://github.com/awslabs/aws-lambda-powertools-python/blob/develop/LICENSE

Expected Behavior

Licenses are consistent across languages

Current Behavior

A wrong license is referenced.

Possible Solution

Steps to Reproduce

Go to: https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/LICENSE

Environment

  • Powertools version used:
  • Packaging format (Layers, npm):
  • AWS Lambda function runtime:
  • Debugging logs:

Related issues, RFCs
@saragerion saragerion added the bug Something isn't working label Jul 16, 2021
@saragerion saragerion changed the title Use correct licence Use correct license Jul 16, 2021
@saragerion saragerion added this to the beta-release milestone Jul 16, 2021
@dreamorosi dreamorosi mentioned this issue Jul 16, 2021
Merged
12 tasks
@github-actions
Copy link
Contributor

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@dreamorosi dreamorosi added documentation Improvements or additions to documentation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) and removed bug Something isn't working labels Nov 13, 2022
@dreamorosi dreamorosi changed the title Use correct license Maintenance: Use correct license Nov 14, 2022
@dreamorosi dreamorosi added the completed This item is complete and has been merged/shipped label Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dreamorosi dreamorosi

Labels
completed This item is complete and has been merged/shipped documentation Improvements or additions to documentation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Projects
None yet
Milestone
beta-release
Development

Successfully merging a pull request may close this issue.

chore: change license aws-powertools/powertools-lambda-typescript
3 participants
@dreamorosi @saragerion @alan-churley