Generate LICENSE file when scaffolding a new command
danielbachhuber opened this issue · comments
We should make sure each scaffolded package includes a proper LICENSE file
From wp-cli/restful#97
Similarly, we should include mention of the license in the README
How do you envision this being implemented?
Should templates for common licenses be bundled? Or maybe use an API like GitHub Licenses?
Should a name/author option be added for licenses like MIT? Or should the license be added as-is, allowing the author to replace the various placeholders on their own?
What about cases where some obscure/unsupported license is requested by the user? A blank license file that they have to manually fill in? Or no license file at all?
It might be nice to add this functionality to the primary scaffold-command as well for plugins and themes.
How do you envision this being implemented?
I don't have any strong opinions at this point, other than to generally follow the pattern of other commands.
Should templates for common licenses be bundled? Or maybe use an API like GitHub Licenses?
Probably bundled. We don't need to support that many, and they don't change very often.
Should a name/author option be added for licenses like MIT? Or should the license be added as-is, allowing the author to replace the various placeholders on their own?
No strong preference.
What about cases where some obscure/unsupported license is requested by the user? A blank license file that they have to manually fill in? Or no license file at all?
No license file at all, I think.