-
Notifications
You must be signed in to change notification settings - Fork 11
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
Comments
@llorllale/z please, pay attention to this issue |
@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/z please, pay attention to this issue |
@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! |
@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: |
@yegor256 WDYT about dropping date ranges from the copyright notice and just leave the original publication date? |
@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? |
Job |
Let's update Copyright notice to 2019.
The text was updated successfully, but these errors were encountered: