Re: IP clearance for contributed code
Hi Richard, IIUC, yes, the owner of the donated code needs to update the source code. Probably you could send some patch to him and he could apply the patch. When I import AsyncWeb, I just did it by myself because I was a committer of the project. Someone please correct me if I am wrong. HTH, Trustin On Jan 24, 2008 1:28 AM, Richard S. Hall [EMAIL PROTECTED] wrote: I am performing the IP clearance paperwork for some code from Peter Kriens. The IP clearance form here: http://incubator.apache.org/ip-clearance/ip-clearance-template.html Asks me to fill in the date for: Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. The donated code currently does not have ASF copyright, it has Peter's copyright. Is the implication here that Peter is supposed to change the copyright on all source files? I assumed that we would just modify the source files to have the proper header as part of bringing them into our repo, but this implies that this must be done beforehand. Which is the case? Thanks. - richard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Please approve Tuscany SCA Java 1.1-incubating release
I think the NOTICE files in the artifacts that are actually being
distributed are OK. The ${pom.name} is changed by the build process so the
generated artifact has the proper name, for example, the jar built for
wsdl2java ends up with a NOTICE file containing Apache Tuscany SCA
WSDL2Java Tool, see inside:
http://people.apache.org/~slaws/tuscany/1.1-RC3/maven/org/apache/tuscany/sca/tuscany-wsdl2java/1.1-incubating/tuscany-wsdl2java-1.1-incubating.jar
.
The mortgage-loanapproval is only distributed within the src and bin
distributions and the NOTICE file in those distributions does include all
the necessary references so that also looks ok to me.
Including the Derby.log is a mistake, but I don't think its a blocker :)
+1 to release.
...ant
On Jan 23, 2008 10:55 PM, sebb [EMAIL PROTECTED] wrote:
Some of the NOTICE files start with the text:
${pom.name}
e.g.
tools/wsdl2java
and
modules/policy
This does not seem right.
The top-level NOTICE and LICENSE files in demos/mortgage-loanapproval
are the standard ASF ones - however NOTICE and LICENSE.txt in the
demos/mortgage-loanapproval/src/main/resources/META-INF directory
include additional references to Eclipse licenses.
Again, I would expect the top-level LN files for a directory tree to
agree with the lower level ones.
The file apache-tuscany-sca-1.1-incubating-src.tar.gz contains the
file derby.log which perhaps should not be there.
On 23/01/2008, Simon Laws [EMAIL PROTECTED] wrote:
Hi,
The Tuscany project had a vote on [EMAIL PROTECTED] to publish
the
Tuscany SCA Java 1.1-incubating release. The vote thread on tuscany-dev
has
7 +1s and an archive can be found at:
http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg27321.html
The release includes new function and bug fixes. You can see a list of
changes at:
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.1-RC3/distribution/src/main/release/CHANGES
The signed binary and source distributions, the RAT reports, and the
Maven
staging repository are listed at the following links.
SVN Tag:
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.1-RC3/
Stage maven repo:
http://people.apache.org/~slaws/tuscany/1.1-RC3/maven/http://people.apache.org/%7Eslaws/tuscany/1.1-RC3/maven/
http://people.apache.org/%7Eslaws/tuscany/1.1-RC3/maven/
RAT report:
http://people.apache.org/~slaws/tuscany/1.1-RC3/rat-1.1-RC3.txthttp://people.apache.org/%7Eslaws/tuscany/1.1-RC3/rat-1.1-RC3.txt
http://people.apache.org/%7Eslaws/tuscany/1.1-RC3/rat-1.1-RC3.txt
Binary and source distros (zip/gz/asc/md5) :
http://people.apache.org/~slaws/tuscany/1.1-RC3/http://people.apache.org/%7Eslaws/tuscany/1.1-RC3/
http://people.apache.org/%7Eslaws/tuscany/1.1-RC3/
Please review and approve the release. This vote will remain open for at
least 72 hours.
Thanks,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: moving a failed incubation project
Noel J. Bergman [EMAIL PROTECTED] writes: When forking Apache licensed code, one does _not_ need to change the package name, or anything else in the source code. One arguably shouldn't then re-publish the binaries or source as Apache Foo [1], but the code itself can use the same namespace. there is no legal requirement to [rename the package space] Again, unless you've a law degree that I missed recently and are ASF counsel of record, I would suggest that no one attempt to dispense legal advice. Didn't get the law degree yet. :-) Sorry if I came across short to anyone. I _did_ read the whole thread before responding and I have forwarded a note to legal-discuss and prc. The legal committee has previously been tasked with a fork FAQ that would cover this and the PRC team is currently working on a trademarks FAQ that should also cover this. I agree that the proper thing for forks to do is change the namespace and it's reasonable to (politely) request this. However, beyond a request we're on shaky grounds. -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: IP clearance for contributed code
On Jan 24, 2008, at 4:40 AM, Trustin Lee wrote: Hi Richard, IIUC, yes, the owner of the donated code needs to update the source code. Probably you could send some patch to him and he could apply the patch. When I import AsyncWeb, I just did it by myself because I was a committer of the project. Section 1. of http://www.apache.org/legal/src-headers.html#headers addresses this case... --kevan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: moving a failed incubation project
Confirm that we were past the legal hurdles. Community was the issue here with TSIK. thanks, dims On Jan 23, 2008 1:50 PM, Noel J. Bergman [EMAIL PROTECTED] wrote: I don't know anything about the legal side, but it would seem to me to be quite unacceptable to publish new releases with org.apache.* namespace. That namespace belongs to the ASF, and users will expect that anything published under that namespace has the approval of the ASF. Correct, IMO. Further discussion of this should be moved to [EMAIL PROTECTED] Normally, I would suggest that if we have people wanting to work on a project, that we bring it back to life here. But I believe that the IP is tainted (and constrained) for TSIK, which is why it failed in the first place. Dims might know. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: moving a failed incubation project
Michael Wechner wrote: J Aaron Farr wrote: If the fork wishes to do more than patch up the original or wishes to create its own identity unique from the Apache original, then it would be wise to rename the packages, but there is no legal requirement to do so. believing you that there is no legal requirement (I am no lawyer ;-), but that's also my understanding of the ASF license and incubator agreement), then that's how it is for the moment. But for the future I think it's in the best interest of the ASF to think about this more thoroughly, because it can be very misleading if one is using Java packages with org.apache.*, but this code - might have nothing to do with the ASF - might be a fork of existing ASF, but has been changed quite a bit in the meantime This is the nature of open source, so I think we have to suck it up. If someone forks OpenJDK, do you think they are going to change all the package names to something else? We have knowingly allowed this because we think it is the right thing to do. If some company took our code, modified it, and started distributing it as part of a commercial (but freely downloadable) project, we wouldn't complain if they encouraged their customers to write to their modified version of our code as part of their project. So, why would it be any different if someone was only forking and not including it in a project? In both cases, the main thing for us is to make sure they clearly state that it is a fork, not an official Apache project. - richard To me the first step would be to talk to these people and ask them kindly to change the package names. If they will change it, then almost everyone will be happy, except people with dependencies, but that can be fixed by keeping previous versions available and adding a note. The problem is when people don't want to change and this is where the ASF should ask itself do we care (well, I do) and if the ASF does care, then what can be done? Are there legal means? Are there other means? Cheers Michi -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 [1] this is trademark, not copyright issue. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: IP clearance for contributed code
Kevan Miller wrote: On Jan 24, 2008, at 4:40 AM, Trustin Lee wrote: Hi Richard, IIUC, yes, the owner of the donated code needs to update the source code. Probably you could send some patch to him and he could apply the patch. When I import AsyncWeb, I just did it by myself because I was a committer of the project. Section 1. of http://www.apache.org/legal/src-headers.html#headers addresses this case... Cool. So, what form can written approval take? Is it sufficient for him to say yes on the JIRA issue on which he has attached the donated code? If not, I guess I will just ask he to resubmit the modified code. - richard --kevan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: moving a failed incubation project
Michael Wechner wrote: If the fork wishes to do more than patch up the original or wishes to create its own identity unique from the Apache original, then it would be wise to rename the packages, but there is no legal requirement to do so. believing you that there is no legal requirement Don't. (I am no lawyer ;-) Neither is J Aaron. I will say this again. We have a legal committee. We have lawyers. No one here is authorized to make legal claims or provide legal advice on behalf of the ASF. This issue has been brought up on [EMAIL PROTECTED] --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: moving a failed incubation project
J Aaron Farr wrote: The legal committee has previously been tasked with a fork FAQ that would cover this and the PRC team is currently working on a trademarks FAQ that should also cover this. And this is neither of those groups, nor have those other tasks been completed. FWIW, your claim is the exact opposite of what has previously been stated, which is why I agree that we need an FAQ. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Please approve Tuscany SCA Java 1.1-incubating release
On 24/01/2008, ant elder [EMAIL PROTECTED] wrote:
I think the NOTICE files in the artifacts that are actually being
distributed are OK.
Surely the archive bundles are also distributed?
==
There are some discrepancies in the jar files covered by the LICENSE
file - the names mentioned in the LICENSE file don't necessarily
appear in the lib directory (and vice versa)
(LIC=LICENSE, DIR=present in lib directory)
LIC: axis2-adb-codegen-1.3.jar
DIR: axis2-codegen-1.3.jar
LIC: derby-10.1.3.1.jar
DIR: derby-10.1.2.1.jar
LIC: stax-api-1.0.2.jar
DIR: stax-api-1.0-2.jar
The following are mentioned in the LICENSE file, but don't appear to be present:
addressing-1.3.mar
maven-artifact-2.0.2.jar
maven-artifact-manager-2.0.2.jar
maven-error-diagnostics-2.0.2.jar
maven-model-2.0.2.jar
maven-profile-2.0.2.jar
maven-project-2.0.2.jar
maven-repository-metadata-2.0.2.jar
maven-settings-2.0.2.jar
opensaml-1.1.jar
plexus-container-default-1.0-alpha-9.jar
plexus-utils-1.1.jar
rampart-1.3.mar
wagon-file-1.0-alpha-7.jar
wagon-http-lightweight-1.0-alpha-6.jar
wagon-provider-api-1.0-alpha-6.jar
Not sure what dojotoolkit mentioned in the LICENSE file refers to.
It would be useful if the LICENSE file used a standard format for the
jar files names, as is done for the ASF jars. Elsewhere in the file,
jars may be listed without the .jar extension and/or without the
version suffix, and sometimes multiple files are listed in a
paragraph.
The lack of a version suffix is potentially serious, as licenses may
change between releases.
The ${pom.name} is changed by the build process so the
generated artifact has the proper name, for example, the jar built for
wsdl2java ends up with a NOTICE file containing Apache Tuscany SCA
WSDL2Java Tool, see inside:
http://people.apache.org/~slaws/tuscany/1.1-RC3/maven/org/apache/tuscany/sca/tuscany-wsdl2java/1.1-incubating/tuscany-wsdl2java-1.1-incubating.jar
That looks OK.
.
The mortgage-loanapproval is only distributed within the src and bin
distributions and the NOTICE file in those distributions does include all
the necessary references so that also looks ok to me.
Including the Derby.log is a mistake, but I don't think its a blocker :)
Agreed.
Though it reveals something about the builder's PC environment, so
they may wish it was not present ;-)
There are several other derby.log files in the source archive.
There's also some 40GB of log-nnn.dat files in the
tuscany-sca-1.1-incubating-src\itest\jms\activemq-data\localhost\journal
directory in the source archive.
Another smaller log file in:
tuscany-sca-1.1-incubating-src\modules\implementation-openjpa\test\log
There are also 3 db.lck files.
Are these really needed for the source archive?
+1 to release.
...ant
On Jan 23, 2008 10:55 PM, sebb [EMAIL PROTECTED] wrote:
Some of the NOTICE files start with the text:
${pom.name}
e.g.
tools/wsdl2java
and
modules/policy
This does not seem right.
The top-level NOTICE and LICENSE files in demos/mortgage-loanapproval
are the standard ASF ones - however NOTICE and LICENSE.txt in the
demos/mortgage-loanapproval/src/main/resources/META-INF directory
include additional references to Eclipse licenses.
Again, I would expect the top-level LN files for a directory tree to
agree with the lower level ones.
The file apache-tuscany-sca-1.1-incubating-src.tar.gz contains the
file derby.log which perhaps should not be there.
On 23/01/2008, Simon Laws [EMAIL PROTECTED] wrote:
Hi,
The Tuscany project had a vote on [EMAIL PROTECTED] to publish
the
Tuscany SCA Java 1.1-incubating release. The vote thread on tuscany-dev
has
7 +1s and an archive can be found at:
http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg27321.html
The release includes new function and bug fixes. You can see a list of
changes at:
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.1-RC3/distribution/src/main/release/CHANGES
The signed binary and source distributions, the RAT reports, and the
Maven
staging repository are listed at the following links.
SVN Tag:
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.1-RC3/
Stage maven repo:
http://people.apache.org/~slaws/tuscany/1.1-RC3/maven/http://people.apache.org/%7Eslaws/tuscany/1.1-RC3/maven/
http://people.apache.org/%7Eslaws/tuscany/1.1-RC3/maven/
RAT report:
http://people.apache.org/~slaws/tuscany/1.1-RC3/rat-1.1-RC3.txthttp://people.apache.org/%7Eslaws/tuscany/1.1-RC3/rat-1.1-RC3.txt
http://people.apache.org/%7Eslaws/tuscany/1.1-RC3/rat-1.1-RC3.txt
Binary and source distros (zip/gz/asc/md5) :
http://people.apache.org/~slaws/tuscany/1.1-RC3/http://people.apache.org/%7Eslaws/tuscany/1.1-RC3/
http://people.apache.org/%7Eslaws/tuscany/1.1-RC3/
Please review and approve the release. This vote will remain open for at
least 72 hours.
Thanks,
Simon
Re: [VOTE] Please approve Tuscany SCA Java 1.1-incubating release
Hi sebb Thank you for the detailed review. Can you tell me what you mean by On Jan 24, 2008 4:57 PM, sebb [EMAIL PROTECTED] wrote: On 24/01/2008, ant elder [EMAIL PROTECTED] wrote: I think the NOTICE files in the artifacts that are actually being distributed are OK. Surely the archive bundles are also distributed? snip.. Also can you tell me if you consider that the issues you have found to be blocking issues? Thanks Simon
Re: [VOTE] Please approve Tuscany SCA Java 1.1-incubating release
On 24/01/2008, Simon Laws [EMAIL PROTECTED] wrote: Hi sebb Thank you for the detailed review. Can you tell me what you mean by On Jan 24, 2008 4:57 PM, sebb [EMAIL PROTECTED] wrote: On 24/01/2008, ant elder [EMAIL PROTECTED] wrote: I think the NOTICE files in the artifacts that are actually being distributed are OK. Surely the archive bundles are also distributed? I meant that the files in the quote Binary and source distros (zip/gz/asc/md5) : http://people.apache.org/~slaws/tuscany/1.1-RC3/ /quote are actually being distributed. I took Ant Elder's comment to mean that these were not being distributed. snip.. Also can you tell me if you consider that the issues you have found to be blocking issues? Yes, I think the discrepancies in the LICENSE file need to be addressed. Also, comparing the SVN tag with the source archive shows that there are quite a few files and directories that are missing from the source archive. There are several files in the source archive that are not in SVN, which probably should be in SVN, for example: BUILDING CHANGES DISCLAIMER LICENSE NOTICE README RELEASE_NOTES demos/alert-aggregator-webapp/build-dependency.xml demos/xml-bigbank/build-dependency.xml itest/databindings/interop/src/test/java/org/apache/tuscany/sca/itest/sdodatabinding/InteropDatabindingTestCase.java itest/databindings/jaxbgen/src/main/java/org/apache/tuscany/sca/itest/jaxbdatabinding/GreeterService.java itest/databindings/jaxbgen/src/main/java/org/apache/tuscany/sca/itest/jaxbdatabinding/GreeterServiceClient.java itest/databindings/jaxbgen/src/main/java/org/apache/tuscany/sca/itest/jaxbdatabinding/GreeterServiceClientImpl.java itest/databindings/jaxbgen/src/main/java/org/apache/tuscany/sca/itest/jaxbdatabinding/GreeterServiceImpl.java itest/databindings/jaxbgen/src/test/java/org/apache/tuscany/sca/itest/jaxbdatabinding/DatabindingTestCase.java itest/databindings/sdogen/src/main/java/org/apache/tuscany/sca/itest/sdodatabinding/GreeterService.java itest/databindings/sdogen/src/main/java/org/apache/tuscany/sca/itest/sdodatabinding/GreeterServiceClientImpl.java itest/databindings/sdogen/src/main/java/org/apache/tuscany/sca/itest/sdodatabinding/GreeterServiceImpl.java itest/databindings/sdogen/src/test/java/org/apache/tuscany/sca/itest/sdodatabinding/DatabindingTestCase.java samples/calculator-webapp/build.xml samples/calculator-ws-webapp/build.xml samples/chat-webapp/build.xml samples/feed-aggregator-webapp/build.xml samples/helloworld-dojo-webapp/build-dependency.xml samples/helloworld-jsonrpc-webapp/build.xml samples/helloworld-ws-sdo-webapp/build-dependency.xml There are also a lot of files in SVN, which are not in the source archive: demos/alert-aggregator-webapp/alert-aggregator.svg demos/bigbank-account/bigbank.svg demos/bigbank-calculator/src/test demos/secure-bigbank/secure-bigbank-account/bigbank.svg demos/secure-bigbank/secure-bigbank-calculator/src/test demos/xml-bigbank/xml-bigbank.svg distribution/standalone/src/main/resources distribution/tomcat/src/test distribution/webapp/src/test distribution/webapp/src/main/resources itest/admin/src/test/java/test itest/contribution-import-export/export-java/src/test itest/contribution-import-export/export-wsdl/src/test itest/contribution-import-export/export-wsdl/src/main/java itest/contribution-multiple/src/main itest/databindings/config.svg itest/databindings/databinding.svg itest/databindings/interop.svg itest/domain/src/main/java/org itest/interop-soap-client/src/test/resources itest/osgi-contribution/contribution-classes-v2/src/test itest/osgi-contribution/contribution-classes/src/test itest/transaction/src/test/resources itest/wsdl2java/src/main itest/wsdl2java/src/test/java modules/implementation-das modules/binding-dwr/src/test modules/binding-ws-axis2/src/main/assembly modules/binding-ws/src/test modules/contribution-java/src/test/resources modules/contribution-namespace/src/test/resources modules/contribution-osgi/src/test modules/contribution/src/test modules/core-databinding/src/test/java/org/apache/tuscany/core modules/core-spi/src/test modules/data-engine-helper/src/test modules/data-engine-helper/src/main/resources modules/databinding-saxon/src/test modules/definitions/src/test modules/definitions/src/main/resources modules/domain-api/src/test modules/domain/src/test modules/extension-helper/src/test modules/host-http/src/test modules/host-jms-activemq/src/test modules/host-jms/src/test modules/host-osgi/src/test modules/host-osgi/src/main/java modules/host-webapp/src/test modules/implementation-spring/src/test/java/org/apache/tuscany/implementation modules/implementation-xquery/src/test modules/implementation-xquery/src/main/java/org/apache/tuscany/implementation modules/interface-wsdl-java2wsdl/src/main/resources modules/interface-wsdl/src/test modules/node-api/src/test modules/node/src/test modules/node/src/main/resources modules/osgi-runtime/src/test/resources modules/policy-transaction/src/test/resources
[audit] Draft Scripts [WAS Re: Release Oversight]
i've been working on some scripts along the lines discussed before [1]. they still need some tuning, documenting and i have some more glue in mind but i hope that the concepts are clear enough now when the mirrors sync, (boring) example output for today are in [2] the txt is for emailing, the html for web browsing. (should be a little more exciting once there's a new release.) if anyone fancies patching some improvements, it's best to leave the python and ant until they're tidied up but feel free to improve the stylesheets [3] and [4]. the raw data is commit to [5] and is signed. the python scanning script is piped to the server over ssh. i wouldn't be surprised if the scripts fail miserable on windows. i'll take a look at fuller automation later (drive by ant). opinions? - robert [1] http://mail-archives.apache.org/mod_mbox/incubator-general/200801.mbox/[EMAIL PROTECTED] [2] http://incubator.apache.org/audit [3] http://svn.apache.org/repos/asf/incubator/public/trunk/audit/summary-txt.xsl [4] http://svn.apache.org/repos/asf/incubator/public/trunk/audit/summary-web.xsl [5] http://svn.apache.org/repos/asf/incubator/public/trunk/audit/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: IP clearance for contributed code
Kevan Miller wrote: On Jan 24, 2008, at 10:02 AM, Richard S. Hall wrote: Kevan Miller wrote: On Jan 24, 2008, at 4:40 AM, Trustin Lee wrote: Hi Richard, IIUC, yes, the owner of the donated code needs to update the source code. Probably you could send some patch to him and he could apply the patch. When I import AsyncWeb, I just did it by myself because I was a committer of the project. Section 1. of http://www.apache.org/legal/src-headers.html#headers addresses this case... Cool. So, what form can written approval take? Is it sufficient for him to say yes on the JIRA issue on which he has attached the donated code? If not, I guess I will just ask he to resubmit the modified code. Well, IANAL ;-), but I don't think the Grant license to ASF... button gives you permission to remove the copyright. In the past, I've asked the the patch provider to remove the copyright and resubmit the patch. I think that's the best (and easiest). I wasn't referring to the button...I was referring to whether it would be acceptable for him to give written approval as a JIRA comment. Regardless, you are probably correct that it is easier to have him modify it. :-) - richard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: IP clearance for contributed code
On Jan 24, 2008, at 10:02 AM, Richard S. Hall wrote: Kevan Miller wrote: On Jan 24, 2008, at 4:40 AM, Trustin Lee wrote: Hi Richard, IIUC, yes, the owner of the donated code needs to update the source code. Probably you could send some patch to him and he could apply the patch. When I import AsyncWeb, I just did it by myself because I was a committer of the project. Section 1. of http://www.apache.org/legal/src-headers.html#headers addresses this case... Cool. So, what form can written approval take? Is it sufficient for him to say yes on the JIRA issue on which he has attached the donated code? If not, I guess I will just ask he to resubmit the modified code. Well, IANAL ;-), but I don't think the Grant license to ASF... button gives you permission to remove the copyright. In the past, I've asked the the patch provider to remove the copyright and resubmit the patch. I think that's the best (and easiest). --kevan
Re: IP clearance for contributed code
On Jan 25, 2008 3:02 AM, Richard S. Hall [EMAIL PROTECTED] wrote: ...I was referring to whether it would be acceptable for him to give written approval as a JIRA comment... I'd say yes, but to be sure it'd be better to check with [EMAIL PROTECTED] -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
