Help the user to make a license choice and make the converted project comply with https://reuse.software/.
Describe alternatives you've considered
Additional context
It seems the copyright framework was put together 2014. Now that https://reuse.software/ exists I think this can be reconsidered.
The question is also how the template itself should/is licensed and what that means for derived projects? Is the assumption that this "skeleton" is in itself not copyrightable? I guess not as you have a LICENSE file. But than I start of with Apache-2.0 license.
Is your feature request related to a problem?
Apache-2.0 is chosen for the user. This choice should be explicit. Additionally this choice should be machine readable and linted.
Describe the solution you'd like
Integrate https://reuse.software/. As this is a template, this means two things:
Describe alternatives you've considered
Additional context
It seems the copyright framework was put together 2014. Now that https://reuse.software/ exists I think this can be reconsidered.
The question is also how the template itself should/is licensed and what that means for derived projects? Is the assumption that this "skeleton" is in itself not copyrightable? I guess not as you have a LICENSE file. But than I start of with Apache-2.0 license.