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

license: removes copyright year and uses SPDX ID #257

Merged
merged 1 commit into from
Mar 5, 2024
Merged

Conversation

codefromthecrypt
Copy link
Member

As a small project, we have to conserve resources and not sign up for work that isn't required. I've recently realized many commercial and/or CNCF projects both use SPDX IDs and also don't bother with copyright year. If their legal team is ok with this, surely a volunteer team without access to one should be, too!

Doing so accomplishes the following, all of which help volunteers:

  • significantly increases readability of files, particularly small ones
  • removes beginning of year maintenance, which cause a lot of FUD last year. IIRC some deployment failed and hours were spent in spite of docs.
  • eliminates the need to do a full source check out, just to satisfy the license plugin. This means we can use actions/checkout defaults.

As a small project, we have to conserve resources and not sign up for
work that isn't required. I've recently realized many commerical and/or
CNCF projects both use SPDX IDs and also don't bother with copyright
year. If their legal team is ok with this, surely a volunteer team
without access to one, should be, too! Doing so accomplishes the
following:

* significantly increases readability of files, particularly small ones
* removes beginning of year maintenance, which cause a lot of FUD last
  year. IIRC some deployment failed and hours were spent in spite of docs.
* eliminates the need to do a full source check out, just to satisfy the
  license plugin. This means we can use actions/checkout defaults.

Signed-off-by: Adrian Cole <adrian@tetrate.io>
@@ -32,7 +32,6 @@ jobs:
# Prevent use of implicit GitHub Actions read-only token GITHUB_TOKEN.
# We push Javadocs to the gh-pages branch on commit.
token: ${{ secrets.GH_TOKEN }}
fetch-depth: 0 # allow build-bin/idl_to_gh_pages to get the full history
Copy link
Contributor

Choose a reason for hiding this comment

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

Didn't check the code just doublechecking this is fine the comment isn't about "license check"

Copy link
Member Author

Choose a reason for hiding this comment

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

I should have self-commented. this repo doesn't have a script like this, so it is fuzz

Copy link
Contributor

Choose a reason for hiding this comment

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

Well I guess it's copy pasta from a different repo :D

Copy link
Member Author

Choose a reason for hiding this comment

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

yeah the dreaded zipkin-api repo ;)

@@ -44,31 +44,6 @@ Here's an example of a snapshot deploy with specified credentials.
$ export GPG_TTY=$(tty) && GPG_PASSPHRASE=whackamole SONATYPE_USER=adrianmole SONATYPE_PASSWORD=ed6f20bde9123bbb2312b221 build-bin/build-bin/maven/maven_deploy
```

## First release of the year
Copy link
Contributor

Choose a reason for hiding this comment

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

💪 💪

@codefromthecrypt codefromthecrypt merged commit 16686ce into master Mar 5, 2024
3 checks passed
@codefromthecrypt codefromthecrypt deleted the SPDX branch March 5, 2024 08:21
@codefromthecrypt
Copy link
Member Author

thanks for advice and the review @anuraaga

codefromthecrypt pushed a commit to openzipkin/zipkin-dependencies that referenced this pull request Apr 14, 2024
As a small project, we have to conserve resources and not sign up for
work that isn't required. I've recently realized many commerical and/or
CNCF projects both use SPDX IDs and also don't bother with copyright
year. If their legal team is ok with this, surely a volunteer team
without access to one, should be, too! Doing so accomplishes the
following:

* significantly increases readability of files, particularly small ones
* removes beginning of year maintenance, which cause a lot of FUD last
  year. IIRC some deployment failed and hours were spent in spite of docs.
* eliminates the need to do a full source check out, just to satisfy the
  license plugin. This means we can use actions/checkout defaults.

Same as openzipkin/zipkin-reporter-java#257

Signed-off-by: Adrian Cole <adrian@tetrate.io>
codefromthecrypt pushed a commit to openzipkin/zipkin-gcp that referenced this pull request Apr 14, 2024
As a small project, we have to conserve resources and not sign up for work that isn't required. I've recently realized many commercial and/or CNCF projects both use SPDX IDs and also don't bother with copyright year. If their legal team is ok with this, surely a volunteer team without access to one, should be, too! Doing so accomplishes the following:

* significantly increases readability of files, particularly small ones
* removes beginning of year maintenance, which cause a lot of FUD last year. IIRC some deployment failed and hours were spent in spite of docs.
* eliminates the need to do a full source check out, just to satisfy the license plugin. This means we can use actions/checkout defaults.

Same as openzipkin/zipkin-reporter-java#257

Signed-off-by: Adrian Cole <adrian@tetrate.io>
codefromthecrypt pushed a commit to openzipkin/zipkin-aws that referenced this pull request Apr 14, 2024
As a small project, we have to conserve resources and not sign up for work that isn't required. I've recently realized many commercial and/or CNCF projects both use SPDX IDs and also don't bother with copyright year. If their legal team is ok with this, surely a volunteer team without access to one, should be, too! Doing so accomplishes the following:

* significantly increases readability of files, particularly small ones
* removes beginning of year maintenance, which cause a lot of FUD last year. IIRC some deployment failed and hours were spent in spite of docs.
* eliminates the need to do a full source check out, just to satisfy the license plugin. This means we can use actions/checkout defaults.

Same as openzipkin/zipkin-reporter-java#257

Signed-off-by: Adrian Cole <adrian@tetrate.io>
codefromthecrypt added a commit to openzipkin/zipkin-dependencies that referenced this pull request Apr 14, 2024
As a small project, we have to conserve resources and not sign up for
work that isn't required. I've recently realized many commerical and/or
CNCF projects both use SPDX IDs and also don't bother with copyright
year. If their legal team is ok with this, surely a volunteer team
without access to one, should be, too! Doing so accomplishes the
following:

* significantly increases readability of files, particularly small ones
* removes beginning of year maintenance, which cause a lot of FUD last
year. IIRC some deployment failed and hours were spent in spite of docs.
* eliminates the need to do a full source check out, just to satisfy the
license plugin. This means we can use actions/checkout defaults.

Same as openzipkin/zipkin-reporter-java#257

---------

Signed-off-by: Adrian Cole <adrian@tetrate.io>
codefromthecrypt pushed a commit to openzipkin/brave-example that referenced this pull request Apr 14, 2024
This project wasn't using the license plugin, but had some copy-paste
license that should be coherent with other projects. Similarly, we don't
need to specify default fetch-depth on checkout.

See openzipkin/zipkin-reporter-java#257

Signed-off-by: Adrian Cole <adrian@tetrate.io>
codefromthecrypt added a commit to openzipkin/brave-example that referenced this pull request Apr 14, 2024
This project wasn't using the license plugin, but had some copy-paste
license that should be coherent with other projects. Similarly, we don't
need to specify default fetch-depth on checkout.

See openzipkin/zipkin-reporter-java#257

Signed-off-by: Adrian Cole <adrian@tetrate.io>
codefromthecrypt added a commit to openzipkin/zipkin-aws that referenced this pull request Apr 14, 2024
As a small project, we have to conserve resources and not sign up for work that isn't required. I've recently realized many commercial and/or CNCF projects both use SPDX IDs and also don't bother with copyright year. If their legal team is ok with this, surely a volunteer team without access to one, should be, too! Doing so accomplishes the following:

* significantly increases readability of files, particularly small ones
* removes beginning of year maintenance, which cause a lot of FUD last year. IIRC some deployment failed and hours were spent in spite of docs.
* eliminates the need to do a full source check out, just to satisfy the license plugin. This means we can use actions/checkout defaults.

Same as openzipkin/zipkin-reporter-java#257

Signed-off-by: Adrian Cole <adrian@tetrate.io>
codefromthecrypt added a commit to openzipkin/zipkin-gcp that referenced this pull request Apr 14, 2024
As a small project, we have to conserve resources and not sign up for work that isn't required. I've recently realized many commercial and/or CNCF projects both use SPDX IDs and also don't bother with copyright year. If their legal team is ok with this, surely a volunteer team without access to one, should be, too! Doing so accomplishes the following:

* significantly increases readability of files, particularly small ones
* removes beginning of year maintenance, which cause a lot of FUD last year. IIRC some deployment failed and hours were spent in spite of docs.
* eliminates the need to do a full source check out, just to satisfy the license plugin. This means we can use actions/checkout defaults.

Same as openzipkin/zipkin-reporter-java#257

Signed-off-by: Adrian Cole <adrian@tetrate.io>
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