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
{{ message }}
This repository has been archived by the owner on Apr 29, 2024. It is now read-only.
I think if configuration files are needed to make the software work, most licenses consider them as source code.
More over they are a few tools that work with configuration as code, in this case the configuration file is also considered source code. Typically CI pipelines.
And I think that if a project finds a solution to drive a software via such configuration file, this has to be protected by license.
I am not a lawyer, but big project tend to apply the notice header on such files as well.
E.g. the JDK :
I think supporting TOML, properties, XML, YAML would be really useful. Basically these file have two types of comments
#
<!--
/-->
, but must happen after<?xml version="1.0" standalone="no"?>
I don't know about other file types, but leaving the ability to declare them might like
licensesnip
might help support them without too much work.The text was updated successfully, but these errors were encountered: