www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-114) License Header - Short Form?
Date Tue, 11 Jun 2013 16:42:20 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680459#comment-13680459

Dennis E. Hamilton commented on LEGAL-114:

I agree that copyright notices should not be removed.  The guidance for handling third-party
ALv2 material and SGA-covered material seems pretty clear that is not to be done, period.

I don't like the lazy way this gets dealt with in reality however.  Projects just go ahead
and change shit while getting snarled up about what goes in LICENSE and what goes in NOTICE.
 The result is so indefinite that provenance becomes questionable.  And the release packagings
don't tie to the SVN -- there's no obvious trace backward from what is put in people's hands.
 (Hmm.  Note to self.)

The monkey-see monkey-do consequences are not a contribution to the public interest.  (Oh,
I guess that is soapbox #0. [;<).

 - Dennis

<soapbox number="1">
The Symphony contribution to Apache OpenOffice is a case in point, because some of that code
(as imported into the project SVN) has some very restrictive IBM Copyright and proprietary
notices and even special notices about government use.  And most of the code has the original
Sun LGPL notices too.

Instead of having some sort of authorization from IBM or designation of an agent of IBM to
scrub these, derivatives are being created that have no such notices and that do not have
any provenance back to those files in the SVN.  (It seems like some kind of willful ignorance.)

I assume that IBM is not about to sue anybody, and that makes it a trifle.  The problem is
that this behavior also perpetuates silly notions about "relicensing" and thinking that derivatives
are somehow new creations of the deriver.  In this particular case, that also involves noticing
what is different in the IBM code and bringing the difference back to the main code base by
recreating it there.

<soapbox number="2">
I just stepped into a thread where Sam pointed someone to the ALv2 definition of contribution
and the
clause about what recipients are granted to works under ALv2.  I don't understand how it serves
anyone to point at the ALv2 for subject matter on which an ALv2 license and/or the presence
of a contribution has not been asserted.

> License Header - Short Form?
> ----------------------------
>                 Key: LEGAL-114
>                 URL: https://issues.apache.org/jira/browse/LEGAL-114
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Roger Meier
> Hi all
> Today the license headers within files does need ~ 15 lines within a file.
> This needs lot of space at the top of a file, probably too much if you have a small README
> e.g. http://svn.apache.org/viewvc/thrift/trunk/tutorial/README?view=markup
> Is it possible to use a smaller header reflecting the license terms within a source or
README file?
> Can we use something like that one or a shorter one?
> {noformat}
> /*
>  * Copyright (c) The Apache Software Foundation
>  * Licensed to the ASF under one or more contributor license agreements
>  * (see NOTICE file distributed with this work). ASF licenses this file to you
>  * under the following license http://www.apache.org/licenses/LICENSE-2.0
>  * Software distributed is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES
>  * OR CONDITIONS OF ANY KIND, either express or implied.
>  */
> {noformat}
> Should we mention also the License identifier (Apache-2.0) used within spdx standard?
> see http://spdx.org/licenses/
> Thanks,
> Roger

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org

View raw message