You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While this application helpfully allows copying of licenses, it would be useful to allow the user to input their name and/or their project's name into the license which could then be copied wherever.
It would also be fairly trivial to automatically fill in the year or add a field for modifying the year in some licenses.
Both of these features could be added by using a bit of regex to replace <year> and <name of author> inside licenses that have those fields (GNU AGPLv3 and GNU GPLv3).
The Apache 2.0 license has similar fields ([yyyy] and [name of copyright owner]).
The MIT license uses <year> and <copyright holders>.
The year could either be automatically filled in with the current year or the user could input a year or range (e.g. 2015-2020), which could be inserted into the license.
Both the name and year should not be saved across exits to prevent wrong licence texts from being copied and implementing this is fairly easy since no change will be necessary since the license templates are retrieved on every opening already.
The text was updated successfully, but these errors were encountered:
While this application helpfully allows copying of licenses, it would be useful to allow the user to input their name and/or their project's name into the license which could then be copied wherever.
It would also be fairly trivial to automatically fill in the year or add a field for modifying the year in some licenses.
Both of these features could be added by using a bit of regex to replace
<year>
and<name of author>
inside licenses that have those fields (GNU AGPLv3 and GNU GPLv3).The Apache 2.0 license has similar fields (
[yyyy]
and[name of copyright owner]
).The MIT license uses
<year>
and<copyright holders>
.The year could either be automatically filled in with the current year or the user could input a year or range (e.g. 2015-2020), which could be inserted into the license.
Both the name and year should not be saved across exits to prevent wrong licence texts from being copied and implementing this is fairly easy since no change will be necessary since the license templates are retrieved on every opening already.
The text was updated successfully, but these errors were encountered: