thank you very much for sharing on github! Just wanted to be in touch briefly to note a minor issue for users of these packages: the *-notify repos all list BSD licensing via the classification, but you'd typically need to specify a copyright plus an actual License text. For BSD, there are several variants - the commonly used would likely be 'BSD-3-Clause' (https://spdx.org/licenses/BSD-3-Clause.html).
This would help any projects itending to base on your packages understand your original copyright and verify they can and will adhere to the terms you're establishing for the use of your original work.
Dear @rajvantchahal ,
thank you very much for sharing on github! Just wanted to be in touch briefly to note a minor issue for users of these packages: the *-notify repos all list BSD licensing via the classification, but you'd typically need to specify a copyright plus an actual License text. For BSD, there are several variants - the commonly used would likely be 'BSD-3-Clause' (https://spdx.org/licenses/BSD-3-Clause.html).
This would help any projects itending to base on your packages understand your original copyright and verify they can and will adhere to the terms you're establishing for the use of your original work.
If you'd want support on how - or even would like to see a patch adding a hint and a license - I'd actually be happy to assist, but there also is github's own recommendations here: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository - the basics are as easy as adding a LICENSE file containing your choice to each repo :)
Best regards, Jan