search

licenses / lice

Generate license files for your projects
BSD 3-Clause "New" or "Revised" License
506 stars 38 forks source link

Don't render the boilerplate in the license template. #44

Closed lord63 closed 9 years ago

lord63 commented 9 years ago

For example, the gpl-2.0 license, we don't have to render the boilerplate at the end of the license, all we need is just copy the content into a file named LICENSE. Let me know if I was wrong.

lord63 commented 9 years ago

My original meaning is don't render the variables(as I pointed in the url, in line 280)

Copyright (C) {{ year }} {{ organization }}

just let them be.

the change was introduced in 09e327173ac9df8980618cec7b4c69b070fcc537

lord63 commented 9 years ago

By the way, got this information from here

How to apply this license

Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.

ejmr commented 9 years ago

My original meaning is don't render the variables.

As in, don't create output like this?

Copyright (C) 2015 John Doe

lord63 commented 9 years ago

As far as I know, yeah, just let them be, don't render them.

ejmr commented 9 years ago

In my experience, I have always seen years and names explicitly included in the copyright line when using the GPL. I will look for official documentation re. the GPL on that matter, but to give an example, when I started maintaining PHP Mode for Emacs I was told to update the copyright line(s) appropriately like so. So I don't think we should remove them from the template. I think the GPL requires such information, but I could be wrong, so like I said I'll look for any documentation/information on the matter.