[
https://issues.apache.org/jira/browse/FOR-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley updated FOR-855:
-------------------------------
Description:
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.
was:
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
Added task "C) Remove any author tags." This has been done in the past (e.g.
FOR-123) but it is a continual monitoring job.
There is one tool to list them, in the "commiiters" repository in the "tools'
section.
Here is the Board recommendation:
http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_09_22.txt
and the issue has been discussed many times on various mail lists, if people
want to search to learn the rationale.
> 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.
