[
https://issues.apache.org/jira/browse/SOLR-15929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477220#comment-17477220
]
Jan Høydahl commented on SOLR-15929:
------------------------------------
Thought: Could we somehow make a script that *generates* our main LICENSE and
NOTICE files?
Something like
{code:java}
for each LICENSE and NOTICE file in solr/licenses:
if notice-file-is-empty:
parse_copyright_from_license_file and append to main LICENSE, with a
pointer to licenses fodler
else:
parse_copyright_from_notice_file and append to main NOTICE, with a pointer
to licenses folder{code}
We also have several (C) statements in NOTICE about js libs in Admin UI. We
could perhaps assemble those in a new solr/webapp/licenses/ folder, and append
that to the end of the auto-generated files.
However we choose to do this, we need a thorough manual review that the
resulting files are correct.
> Clean up NOTICE and LICENSE files for Solr
> ------------------------------------------
>
> Key: SOLR-15929
> URL: https://issues.apache.org/jira/browse/SOLR-15929
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Jan Høydahl
> Priority: Major
>
> Spinoff from SOLR-15862 and SOLR-2406:
> We need a total cleanup of both these files
> * Move lots of (C) notices from NOTICE to LICENSE file
> * Cross-check that we list all dependencies, and that removed deps (such as
> for DIH etc) are removed from NOTICE/LICENSE
> I wonder if
> [https://github.com/apache/solr/blob/main/solr/licenses/README.committers.txt]
> should also be relocated to either `dev-docs/` or `help/` to make it easier
> to find. It is hard to get the license/notice stuff right, so we need a good
> guide for committers!
> See [https://infra.apache.org/licensing-howto.html] for the requirements. PS:
> Any preference whether we should rename the files without {{.txt}} suffix?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
