Thank you for creating sphinx-jinja. We've been using at the Rubin Observatory for projects like pipelines.lsst.io, and its been tremendously useful.
This PR is simply to add a LICENSE file to the Git repository that reflects the metadata already in setup.cfg. I've checked, and the LICENSE file will also be part of the distribution to PyPI.
The issue of a license file came up in our effort to redistribute sphinx-jinja on conda-forge (https://github.com/conda-forge/staged-recipes/pull/10614), which is intended to give the community of Conda users easier access to sphinx-jinja. Having the license file here in the primary repository means that the Conda package can automatically consume the "official" license here (once there is a new release to PyPI, of course).
Thank you for creating
sphinx-jinja
. We've been using at the Rubin Observatory for projects like pipelines.lsst.io, and its been tremendously useful.This PR is simply to add a
LICENSE
file to the Git repository that reflects the metadata already insetup.cfg
. I've checked, and the LICENSE file will also be part of the distribution to PyPI.The issue of a license file came up in our effort to redistribute
sphinx-jinja
on conda-forge (https://github.com/conda-forge/staged-recipes/pull/10614), which is intended to give the community of Conda users easier access tosphinx-jinja
. Having the license file here in the primary repository means that the Conda package can automatically consume the "official" license here (once there is a new release to PyPI, of course).Thank you again!