[
https://issues.apache.org/jira/browse/FOR-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764941#action_12764941
]
David Crossley commented on FOR-855:
------------------------------------
Over the past few weeks i have been gradually developing a Perl script to
assist with "Task A)". It intends to ensure that every jar has a matching
license file, and that all licenses are referenced in our top-level LICENSE.txt
file. Until we fully use Ivy, that will assist with this issue.
> verify the license situation prior to each release
> --------------------------------------------------
>
> Key: FOR-855
> URL: https://issues.apache.org/jira/browse/FOR-855
> Project: Forrest
> Issue Type: Bug
> Components: Project administration
> Affects Versions: 0.9-dev
> Reporter: David Crossley
> Priority: Blocker
> Fix For: 0.9-dev
>
>
> This should be continually happening anyway, but immediately prior to each
> release we need to verify that our license situation is in order. This issue
> should not ever be closed, rather just move the "Fix for Version" on to the
> next release.
> Here are some of the tasks:
> A) Ensure that all supporting libraries have a corresponding license.
> Basically every jar file or other external package needs to have a
> *.license.txt file. Ensure that any license conditions are met, e.g. for some
> we must add an entry to NOTICE.txt, while for some others we must not.
> Remember to abide by the ASF guidelines (e.g. nothing more restrictive than
> the Apache License).
> B) Scan the whole trunk repository to add missing ASF license headers to
> source files and to ensure that the ASF license headers have not been
> accidently added to external files. See etc/relicense.txt
> C) Remove any author tags.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
