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

Example code files lack the necessary copyright/license statements #1441

Open
scottslowe opened this issue Jun 20, 2023 · 0 comments
Open

Example code files lack the necessary copyright/license statements #1441

scottslowe opened this issue Jun 20, 2023 · 0 comments
Labels
area/examples kind/engineering Work that is not visible to an external user size/L Estimated effort to complete (up to 10 days).

Comments

@scottslowe
Copy link
Contributor

What happened?

In examining a number of examples, I noticed inconsistency in the use of copyright/license statements at the top of the code files:

  • Some files have a single line: Copyright 2016-2023, Pulumi Corporation. All rights reserved.
  • Some files have a longer, Apache 2.0-based copyright/license statement (see files in the kubernetes-ts-multicloud example)
  • Some files have no copyright/license statement at all

There needs to be consistent use of copyright/license statements for all examples.

Expected Behavior

I expected the files to have consistent copyright/license statements.

Steps to reproduce

  1. Open the files in the kubernetes-ts-multicloud example. Note the Apache 2.0-based copyright/license statement at the top of the TypeScript files.
  2. Open the files in the aws-ts-vpc-with-ecs-fargate-py example. Note there is no copyright/license statement in the files.
  3. Open the files in the aws-ts-voting-app example. Note the single line copyright statement.

Output of pulumi about

N/A

Additional context

N/A

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@scottslowe scottslowe added area/examples kind/engineering Work that is not visible to an external user size/L Estimated effort to complete (up to 10 days). labels Jun 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/examples kind/engineering Work that is not visible to an external user size/L Estimated effort to complete (up to 10 days).
Projects
None yet
Development

No branches or pull requests

1 participant