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

Standardize copyright headers. #456

Merged
merged 2 commits into from
Feb 22, 2024
Merged

Standardize copyright headers. #456

merged 2 commits into from
Feb 22, 2024

Conversation

xStrom
Copy link
Member

@xStrom xStrom commented Feb 22, 2024

The Linebender standard for copyright headers was decided last year in kurbo#207 as the following:

// Copyright <year of file creation> the <Project> Authors
// SPDX-License-Identifier: Apache-2.0 OR MIT

With Vello 0.1 approaching fast it makes sense to get this done now.

This PR converts all file headers to this standard form, including the standard capitalization.

Additionally, three CPU shader files didn't specify Unlicense in the headers which seems like a mistake. I added the Unlicense identifier to match all the other shaders.

Copy link
Contributor

@waywardmonkeys waywardmonkeys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious, what is the difference between files with 2022 and 2023? Creation date?

@xStrom
Copy link
Member Author

xStrom commented Feb 22, 2024

Yeap, the year marks the creation date.

@xStrom xStrom added this pull request to the merge queue Feb 22, 2024
Merged via the queue into linebender:main with commit 19196d0 Feb 22, 2024
8 checks passed
@xStrom xStrom deleted the copyhead branch February 22, 2024 20:49
@@ -1,3 +1,6 @@
// Copyright 2023 the Vello Authors
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure this is right. It's mostly the work of the egui authors

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! I've created #464 to address this.

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.

3 participants