Copyrights in source code

[aaabramov]

In Scala source code there are a lot of headers where copyrights are outdated.
My question is: should we update them with every year?

Example of copyright header:

/*                     __                                               *\
**     ________ ___   / /  ___     Scala API                            **
**    / __/ __// _ | / /  / _ |    (c) 2003-2013, LAMP/EPFL             **
**  __\ \/ /__/ __ |/ /__/ __ |    http://scala-lang.org/               **
** /____/\___/_/ |_/____/_/ | |                                         **
**                          |/                                          **
\*   

I believe I can find some time to write script for such purposes.

[jvican]

Sbt-header does this, I think.

[aaabramov]

@jvican awesome! Than I believe it should be added to the build lifecycle.

[jvican]

Go ahead and open a PR then 😉.

[aaabramov]

@jvican sure! In the requirements of sbt-header I see

Java 8 or higher
sbt 1.0.0 or higher

Is it possible for scala build system? (tip: this is my first contribution to scala, so there are components which I am not familiar with)

[aaabramov]

FYI, @SethTisue

[aaabramov]

See the linked ticket in order to be informed that sbt-header seems to be really incompatible with sbt 0.13.16: sbt/sbt-header#133

[aaabramov]

Okay, I found out that issue was that the author have not published the version to repository yet. So it is fixed now and seems to be working with sbt 0.13.16. Will take case of this during next week.

One question I have: @jvican after processing source code files, should the be committed to VSC (git)? It happens once a year, but nevertheless it is a big change to review.

Also we can add headerCheck to CI system to check that all newly created and updated files contain right copyright header. What do you think?

Thank you.

[som-snytt]

There was another issue or PR about syncing the copyright with git history. I wrote a tool but Jason wanted sbtheader integration. That made me yawn, but recently I considered that scalafix is the better tool. The year should not be updated arbitrarily.

[aaabramov]

@som-snytt so should I spend time on improving this?

[som-snytt]

I don't know. My PR was scala/scala#5201 as a reference. On a tablet pls 4give terse reply.

[aaabramov]

@som-snytt awesome, thank you. So why did you give up with your PR? I see that there are no comments that are against your solution.

[som-snytt]

Comments all on the linked PR by the other fellow. Jason nixes it late in thread.