commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COMMONSSITE-21) commons-parent-6 pom changes
Date Fri, 04 Jan 2008 19:01:38 GMT

    [ https://issues.apache.org/jira/browse/COMMONSSITE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556022#action_12556022
] 

Dennis Lundberg commented on COMMONSSITE-21:
--------------------------------------------

Trying to summarize what has been established so far, regarding LICENSE and NOTICE files:

1. There is no policy regarding whether or these files need to be in svn. Until such a policy
exists it is up to the PMC to decide if we want them in svn or not.
2. Is the PMC decides that these files should be in svn, there is no policy regarding where
they should be stored. It is up to the PMC to decide.
3. There is policy (preference[1]) that the files should be called LICENSE and NOTICE, without
the .txt suffix
4. We agree to disagree on the usefulness of the maven-remote-resources-plugin. Therefor it
is up to the component developers to decide if they want to use it or not. *If* it is used,
the PMC can vote -1 on a release if the generated NOTICE file is not deemed good enough.

And a couple of my own thoughts, not sure if there is consensus about them:

A. There is a policy [2] that all source files should contain the ASF header, which includes
a link to the license. Therefor I do not see the need for a LICENSE file in svn as long as
a copy of the ASF license in included in all distributions.

B. Because the current naming of these files in Commons differ from the ones generated by
maven-remote-resources-plugin, there is a possibility of duplicate files being inserted into
the distributions. If a component wants to use maven-remote-resources-plugin and want to have
these files present in svn, the component should rename the files to LICENSE and NOTICE respectively
to avoid this.


[1] http://apache.org/dev/apply-license.html#license-file-name
[2] http://apache.org/legal/src-headers.html#headers

> commons-parent-6 pom changes
> ----------------------------
>
>                 Key: COMMONSSITE-21
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-21
>             Project: Commons All
>          Issue Type: Improvement
>          Components: Commons Parent Pom
>            Reporter: Niall Pemberton
>         Attachments: commons-valdiator-generated-NOTICE.txt, COMMONSSITE-21-commons-parent-pom-v1.patch,
COMMONSSITE-21-commons-parent-pom-v2.patch
>
>
> Opening this ticket to discuss changes for Version 6 of the commons-parent pom.
> See thread: http://tinyurl.com/39eo9z for related discussion/issues

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message