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

Add copyright header to all source files #24

Closed
brooke-hamilton opened this issue Feb 24, 2021 · 1 comment · Fixed by #36
Closed

Add copyright header to all source files #24

brooke-hamilton opened this issue Feb 24, 2021 · 1 comment · Fixed by #36
Assignees

Comments

@brooke-hamilton
Copy link
Contributor

Description
All source files created by Microsoft employees are required to have a copyright header as a comment with the two lines shown below.

# Copyright (c) Microsoft Corporation.
# Licensed under the MIT License.

Note: third party contributors can add their own copyright header so long as they keep all pre-existing copyright notices intact in the files they are contributing. So contributors can add their own copyright header to their original contributions, as well as to files they modify and contribute back to the Microsoft OSS project. Microsoft should not add a Microsoft copyright header to third party contributions to Microsoft OSS projects. We should never remove copyright notices from files.

We should only add Microsoft copyright headers to files coded by Microsoft employees. If Microsoft employees modify third party code they may (but are not required to) add a Microsoft copyright header to the file so long as we keep intact all pre-existing copyright notices in the file.

Acceptance Criteria

  • All files have the two lines of copyright code text above as a comment.
@brooke-hamilton brooke-hamilton self-assigned this Feb 24, 2021
@brooke-hamilton
Copy link
Contributor Author

@glennmusa, @Breanna-Stryker, @Phydeauxman, @kyle-hoyer
FYI on this issue as we work on code in this repo.

@brooke-hamilton brooke-hamilton linked a pull request Feb 25, 2021 that will close this issue
This issue was closed.
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

Successfully merging a pull request may close this issue.

1 participant