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

Let's update Copyright notice to 2019. #87

Closed
fabriciofx opened this issue Jan 1, 2019 · 8 comments
Closed

Let's update Copyright notice to 2019. #87

fabriciofx opened this issue Jan 1, 2019 · 8 comments

Comments

@fabriciofx
Copy link

Let's update Copyright notice to 2019.

@0crat
Copy link
Collaborator

0crat commented Jan 1, 2019

@llorllale/z please, pay attention to this issue

@0crat
Copy link
Collaborator

0crat commented Jan 1, 2019

@fabriciofx/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!

@0crat
Copy link
Collaborator

0crat commented Jan 1, 2019

@llorllale/z please, pay attention to this issue

@0crat
Copy link
Collaborator

0crat commented Jan 1, 2019

@fabriciofx/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!

@llorllale
Copy link
Collaborator

@fabriciofx I don't understand why we should be maintaining a range of dates for the copyright notice. As far as I am aware, the really important date is the one when the work was published (the start date). You may add a "revised date" to the notice if a file's contents changes "significantly", but do we really need to? Guava certainly doesn't do it. I'm guessing the hassle isn't worth it.

Sources:

@llorllale
Copy link
Collaborator

@yegor256 WDYT about dropping date ranges from the copyright notice and just leave the original publication date?

@fabriciofx
Copy link
Author

@llorllale I agree with you. Let's wait for @yegor256 opinion. But let me know if you would like to close this issue and open another or just rename the title (and the others, like cactoos/#985, ok?

@0crat
Copy link
Collaborator

0crat commented Jun 26, 2023

Job gh:zold-io/java-api#87 is not assigned, can't get performer

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

No branches or pull requests

4 participants