You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Carol Frampton (Created) (JIRA)" <ji...@apache.org> on 2012/02/24 21:11:48 UTC
[jira] [Created] (LEGAL-127) Questions from the Apache Flex podling
about copyrights
Questions from the Apache Flex podling about copyrights
-------------------------------------------------------
Key: LEGAL-127
URL: https://issues.apache.org/jira/browse/LEGAL-127
Project: Legal Discuss
Issue Type: Question
Reporter: Carol Frampton
I'm in the process of fixing copyrights in the some of the Flex code Adobe is about to contribute to ASF. Adobe Legal will not allow us to contribute the code until all the copyrights have been updated. I've read thru all the ASF legal docs I can find but the answers to these questions aren't obvious to me.
1) Many of the tools print out a one-line copyright similar to:
Adobe Flex Compiler (mxmlc)
Version 4.6.0 build 0
Copyright (c) 2004-2011 Adobe Systems, Inc. All rights reserved.
or we have localized strings like this which need a one-line copyright:
StartMessage=Adobe ASDoc \n${buildMessage}\nCopyright (c) 2004-2011 Adobe Systems, Inc. All rights reserved.\n
I couldn't find the equivalent in the Apache license information but I did find in https://issues.apache.org/jira/browse/LEGAL-124 the suggestion of
"Copyright (C) 2012 The Apache Software Foundation. Subject to Apache License 2.0.".
What should I use?
2) We have some Batik and Velocity files, under Apache license, which we've modified. Currently the code has the original ASF license as well as an Adobe copyright.. How should this case be handled?
3) We have some old unmodified Apache sources which have an older Apache license (pre 2.0). Do we leave the old license or should it be upgraded to a 2.0 license?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
[jira] [Commented] (LEGAL-127) Questions from the Apache Flex
podling about copyrights
Posted by "Roy T. Fielding (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LEGAL-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216116#comment-13216116 ]
Roy T. Fielding commented on LEGAL-127:
---------------------------------------
Hi Carol,
Should I have a conversation with Adobe Legal? There seems to be some confusion over what Adobe needs in the contribution. Notices certainly aren't needed. We typically place one notice in the NOTICE file about the original developer and the rest of the headers are removed or replaced with the standard Apache header. For example, see the last two lines of
http://svn.apache.org/viewvc/jackrabbit/trunk/NOTICE.txt?view=markup
where the bit about Day Software is noted. That can be an actual copyright notice, if desired, and it applies to the entire source tree, builds, derivative work, etc.
There is no need for (C) to appear after Copyright in the notice.
For (1), either "Copyright 2012 The Apache Software Foundation"
or "See NOTICE for copyrights; Licensed under the Apache License 2.0"
For (2), it depends on how the changes are noted within the files. If the
changes are clearly delineated from the original Apache code, then just note
them as changes made by Adobe -- these are now contributed under the CCLA.
If they are entire files from Apache with only small changes made by Adobe and
then an Adobe copyright notice slapped on top of the whole file, please remove
the Adobe notice because it is invalid (and thus illegal).
For (3), just leave them as is until after the import. The Apache project can
figure out what to do with them later.
Cheers,
....Roy T. Fielding
> Questions from the Apache Flex podling about copyrights
> -------------------------------------------------------
>
> Key: LEGAL-127
> URL: https://issues.apache.org/jira/browse/LEGAL-127
> Project: Legal Discuss
> Issue Type: Question
> Reporter: Carol Frampton
>
> I'm in the process of fixing copyrights in the some of the Flex code Adobe is about to contribute to ASF. Adobe Legal will not allow us to contribute the code until all the copyrights have been updated. I've read thru all the ASF legal docs I can find but the answers to these questions aren't obvious to me.
> 1) Many of the tools print out a one-line copyright similar to:
> Adobe Flex Compiler (mxmlc)
> Version 4.6.0 build 0
> Copyright (c) 2004-2011 Adobe Systems, Inc. All rights reserved.
> or we have localized strings like this which need a one-line copyright:
> StartMessage=Adobe ASDoc \n${buildMessage}\nCopyright (c) 2004-2011 Adobe Systems, Inc. All rights reserved.\n
> I couldn't find the equivalent in the Apache license information but I did find in https://issues.apache.org/jira/browse/LEGAL-124 the suggestion of
> "Copyright (C) 2012 The Apache Software Foundation. Subject to Apache License 2.0.".
> What should I use?
> 2) We have some Batik and Velocity files, under Apache license, which we've modified. Currently the code has the original ASF license as well as an Adobe copyright.. How should this case be handled?
> 3) We have some old unmodified Apache sources which have an older Apache license (pre 2.0). Do we leave the old license or should it be upgraded to a 2.0 license?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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