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

Apply and enforce file-level license headers #952

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

lieut-data
Copy link
Member

Summary

Use mattermost-govet and eslint's header/header to ensure each file begins with the appropriate header, then fix all instances for built source code. (e2e code excepted)

// Copyright (c) 2015-present Mattermost, Inc. All Rights Reserved.
// See LICENSE.txt for license information.

Note that this renames LICENSE to LICENSE.txt purely to align on the copyright messaging across repos. For this repo, I also aligned any existing license declarations with different dates to the singular 2015-present directive in use everywhere else.

Ticket Link

None

@lieut-data lieut-data force-pushed the updated-license-header branch 2 times, most recently from 33a0ed6 to 48e7ff2 Compare January 21, 2025 08:22
Use `mattermost-govet` and `eslint`'s `header/header` to ensure each
file begins with the appropriate header, then fix all instances for
built source code. (e2e code excepted)

```
// Copyright (c) 2015-present Mattermost, Inc. All Rights Reserved.
// See LICENSE.txt for license information.
```

Note that this renames `LICENSE` to `LICENSE.txt` purely to align on the
copyright messaging across repos.
@lieut-data lieut-data force-pushed the updated-license-header branch from 48e7ff2 to 5ef0484 Compare January 21, 2025 08:34
@streamer45
Copy link
Collaborator

Is it legal to retroactively add a license date to a piece of software created well past that date?

@lieut-data
Copy link
Member Author

Is it legal to retroactively add a license date to a piece of software created well past that date?

Thanks for poking at that, @streamer45: I'm checking with legal on requirements.

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 this pull request may close these issues.

2 participants