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 #985

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

Let's update Copyright notice to 2019 #985

fabriciofx opened this issue Jan 1, 2019 · 27 comments

Comments

@fabriciofx
Copy link
Contributor

Let's update Copyright notice to 2019.

@0crat
Copy link
Collaborator

0crat commented Jan 1, 2019

@llorllale/z please, pay attention to this issue

@llorllale
Copy link
Contributor

@llorllale
Copy link
Contributor

@yegor256 should we maintain 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
Contributor

@yegor256 ping

@yegor256
Copy link
Owner

yegor256 commented May 5, 2019

@llorllale let's do a years range, this is what we do in all other projects

@llorllale
Copy link
Contributor

@0crat in

@0crat 0crat added the scope label May 10, 2019
@0crat
Copy link
Collaborator

0crat commented May 10, 2019

@0crat in (here)

@llorllale Job #985 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented May 10, 2019

Bug was reported, see §29: +15 point(s) just awarded to @fabriciofx/z

@0crat
Copy link
Collaborator

0crat commented Jun 22, 2019

The job #985 assigned to @aivinog1/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

@aivinog1
Copy link
Contributor

aivinog1 commented Jun 23, 2019

@llorllale I found out that dates already changed by @yegor256 in 100885a. But dates verification is not working and I add a new TODO.

aivinog1 added a commit to aivinog1/cactoos that referenced this issue Jun 23, 2019
aivinog1 pushed a commit to aivinog1/cactoos that referenced this issue Jun 25, 2019
aivinog1 added a commit to aivinog1/cactoos that referenced this issue Jun 25, 2019
aivinog1 added a commit to aivinog1/cactoos that referenced this issue Jun 25, 2019
aivinog1 pushed a commit to aivinog1/cactoos that referenced this issue Jun 25, 2019
@aivinog1
Copy link
Contributor

@0crat wait #1148

@0crat 0crat added the waiting label Jun 25, 2019
@0crat
Copy link
Collaborator

0crat commented Jun 25, 2019

@0crat wait #1148 (here)

@aivinog1 The impediment for #985 was registered successfully by @aivinog1/z

aivinog1 added a commit to aivinog1/cactoos that referenced this issue Jun 25, 2019
aivinog1 added a commit to aivinog1/cactoos that referenced this issue Jun 25, 2019
aivinog1 pushed a commit to aivinog1/cactoos that referenced this issue Jun 25, 2019
@aivinog1
Copy link
Contributor

@0crat continue

@aivinog1
Copy link
Contributor

@llorllale I assume that we can close this.

@0crat 0crat removed the waiting label Jun 25, 2019
@0crat
Copy link
Collaborator

0crat commented Jun 25, 2019

@0crat continue (here)

@aivinog1 @aivinog1/z continued working on job #985

@llorllale
Copy link
Contributor

@aivinog1 ask the ticket's reporter

@aivinog1
Copy link
Contributor

@llorllale Thanks.

@fabriciofx Can you close this ticket?

@aivinog1
Copy link
Contributor

@llorllale I remind you about #1148. Can you fix my reputation?

@fabriciofx
Copy link
Contributor Author

@llorllale I'll close this issue now. @aivinog1 good work! Congratulations!

@0crat
Copy link
Collaborator

0crat commented Jun 26, 2019

Job #985 is not in the agenda of @aivinog1/z, can't inspect

@0crat
Copy link
Collaborator

0crat commented Jun 26, 2019

@sereshqua/z please review this job completed by @aivinog1/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

@0crat 0crat removed the scope label Jun 26, 2019
@0crat
Copy link
Collaborator

0crat commented Jun 26, 2019

The job #985 is now out of scope

aivinog1 added a commit to aivinog1/cactoos that referenced this issue Jun 26, 2019
aivinog1 added a commit to aivinog1/cactoos that referenced this issue Jun 26, 2019
aivinog1 pushed a commit to aivinog1/cactoos that referenced this issue Jun 26, 2019
@sereshqua
Copy link

@aivinog1 please make sure that you start all your message with the name of the user they are addressed to, see

@aivinog1
Copy link
Contributor

@sereshqua done, thanks.

@sereshqua
Copy link

@0crat quality acceptable

@0crat
Copy link
Collaborator

0crat commented Jun 26, 2019

Quality review completed: +4 point(s) just awarded to @sereshqua/z

@0crat
Copy link
Collaborator

0crat commented Jun 26, 2019

Order was finished, quality is "acceptable": +30 point(s) just awarded to @aivinog1/z

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

6 participants