License templates when creating a LICENSE file

When creating a LICENSE file, we should suggest templates for the LICENSE.

cc @sytses @dzaporozhets @jschatz1

This is something that should be on priority, copying the license from elsewhere is a serious pain point.

mentioned in merge request !3029 (closed)

Perhaps useful:

• https://developer.github.com/v3/licenses/
• https://github.com/benbalter/licensee/blob/master/lib%2Flicensee%2Flicense.rb#L15

It may also be interesting to make this generic so it can be used for all kinds of files (LICENSE, .gitignore, .gitlab-ci.yml, etc.) There's little reason why licenses should be treated specially.

@DouweM Thanks for links, they was very helpful for me!

mentioned in issue #3785 (closed)

It may also be interesting to make this generic so it can be used for all kinds of files (LICENSE, .gitignore, .gitlab-ci.yml, etc.) There's little reason why licenses should be treated specially.

A logical extension of that would be to let admins write their own template files when self-hosting GitLab.

Added ~164274 label

If using a license template list, please consider using the SPDX license list, see:

• https://spdx.org/licenses/
• http://git.spdx.org/?p=license-list.git;a=summary

Added ~122770 label

Reassigned to @rymai

mentioned in merge request !3660 (merged)

This is a really cool idea!

Though do remember that GitHub and SPDX put a lot of emphasis on open-source licenses. While brilliant for s/w that should be open source it's less useful for s/w that should not be. WRT @dougthor42 mention of allowing admins to add their own license templates to a default listwould be a good way of allowing self-hosted installs of facilitating closed licensing.

Just my 2c

Status changed to closed by commit 3d4875f8

mentioned in commit 3d4875f8

mentioned in commit 69821f1a

Mentioned in issue #12708 (closed)