I contributed R as a language to https://pre-commit.com, and we are improving it currently so that infrastructure generated with renv::init() is distributed as part of pre-commit (which is MIT licenced like renv) in certain cases and used in tests. That raises the question of the license of these files. The same question arises in any project that uses {renv} and contains artefact files such as renv/activate.R and friends that is public (at least I think it does). To be on the safe side here, we decided to come here and ask if it's possible to include these files in the distribution of pre-commit and how they should be licensed. I notice that in {vctrs}, certain files were unlicensed to make it unambiguously clear that c/p is fine. Maybe that's an approach worth taking into consideration? Thanks.
I contributed R as a language to https://pre-commit.com, and we are improving it currently so that infrastructure generated with
renv::init()is distributed as part of pre-commit (which is MIT licenced like renv) in certain cases and used in tests. That raises the question of the license of these files. The same question arises in any project that uses {renv} and contains artefact files such asrenv/activate.Rand friends that is public (at least I think it does). To be on the safe side here, we decided to come here and ask if it's possible to include these files in the distribution of pre-commit and how they should be licensed. I notice that in {vctrs}, certain files were unlicensed to make it unambiguously clear that c/p is fine. Maybe that's an approach worth taking into consideration? Thanks.