Return-Path: Delivered-To: apmail-harmony-commits-archive@www.apache.org Received: (qmail 21228 invoked from network); 5 May 2007 14:38:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 May 2007 14:38:13 -0000 Received: (qmail 47464 invoked by uid 500); 5 May 2007 14:38:03 -0000 Delivered-To: apmail-harmony-commits-archive@harmony.apache.org Received: (qmail 47001 invoked by uid 500); 5 May 2007 14:37:58 -0000 Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list commits@harmony.apache.org Received: (qmail 46980 invoked by uid 99); 5 May 2007 14:37:58 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 May 2007 07:37:58 -0700 X-ASF-Spam-Status: No, hits=-99.5 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO eris.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 May 2007 07:37:46 -0700 Received: by eris.apache.org (Postfix, from userid 65534) id 054B21A9838; Sat, 5 May 2007 07:37:26 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r535532 [1/11] - in /harmony/standard/site: docs/ docs/documentation/ docs/subcomponents/buildtest/ docs/subcomponents/classlibrary/ docs/subcomponents/drlvm/ docs/subcomponents/jchevm/ docs/subcomponents/stresstest/ xdocs/stylesheets/ Date: Sat, 05 May 2007 14:37:21 -0000 To: commits@harmony.apache.org From: tellison@apache.org X-Mailer: svnmailer-1.1.0 Message-Id: <20070505143726.054B21A9838@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: tellison Date: Sat May 5 07:37:18 2007 New Revision: 535532 URL: http://svn.apache.org/viewvc?view=rev&rev=535532 Log: Update ApacheCon logo Modified: harmony/standard/site/docs/auth_cont_quest.html harmony/standard/site/docs/auth_cont_quest.txt (contents, props changed) harmony/standard/site/docs/bulk_contribution_checklist.html harmony/standard/site/docs/bulk_contribution_checklist.txt (contents, props changed) harmony/standard/site/docs/code_scan_tools.html harmony/standard/site/docs/contribution_policy.html harmony/standard/site/docs/contributors.html harmony/standard/site/docs/documentation/build_website.html harmony/standard/site/docs/documentation/conventions.html (contents, props changed) harmony/standard/site/docs/documentation/dev_eclipse.html harmony/standard/site/docs/documentation/site.css (props changed) harmony/standard/site/docs/downloads.html harmony/standard/site/docs/faq.html harmony/standard/site/docs/get-involved.html harmony/standard/site/docs/guidelines.html harmony/standard/site/docs/hdk.html (contents, props changed) harmony/standard/site/docs/index.html harmony/standard/site/docs/issue_resolution_guideline.html (contents, props changed) harmony/standard/site/docs/license.html harmony/standard/site/docs/mailing.html harmony/standard/site/docs/newshistory.html harmony/standard/site/docs/performance.html (contents, props changed) harmony/standard/site/docs/quickhelp_contributors.html harmony/standard/site/docs/quickhelp_users.html harmony/standard/site/docs/related.html harmony/standard/site/docs/roadmap.html harmony/standard/site/docs/sitemap.html (contents, props changed) harmony/standard/site/docs/status.html harmony/standard/site/docs/subcomponents/buildtest/index.html harmony/standard/site/docs/subcomponents/classlibrary/agreements.html harmony/standard/site/docs/subcomponents/classlibrary/asn1_framework.html harmony/standard/site/docs/subcomponents/classlibrary/awt.html harmony/standard/site/docs/subcomponents/classlibrary/compat.html harmony/standard/site/docs/subcomponents/classlibrary/dns_support.html harmony/standard/site/docs/subcomponents/classlibrary/index.html harmony/standard/site/docs/subcomponents/classlibrary/java2d.html harmony/standard/site/docs/subcomponents/classlibrary/pkgnaming.html harmony/standard/site/docs/subcomponents/classlibrary/regexp.html harmony/standard/site/docs/subcomponents/classlibrary/rmi_provider.html (contents, props changed) harmony/standard/site/docs/subcomponents/classlibrary/ser_testing.html harmony/standard/site/docs/subcomponents/classlibrary/status.html harmony/standard/site/docs/subcomponents/classlibrary/testing.html harmony/standard/site/docs/subcomponents/drlvm/DoxygenStart.html (contents, props changed) harmony/standard/site/docs/subcomponents/drlvm/EM.html (contents, props changed) harmony/standard/site/docs/subcomponents/drlvm/JIT.html (contents, props changed) harmony/standard/site/docs/subcomponents/drlvm/JIT_PMF.html (contents, props changed) harmony/standard/site/docs/subcomponents/drlvm/JVMTI-PopFrame.html (contents, props changed) harmony/standard/site/docs/subcomponents/drlvm/TM.html harmony/standard/site/docs/subcomponents/drlvm/debugging_VM_and_JIT.html harmony/standard/site/docs/subcomponents/drlvm/developers_guide.html harmony/standard/site/docs/subcomponents/drlvm/emguide.html harmony/standard/site/docs/subcomponents/drlvm/encoder_library.html (contents, props changed) harmony/standard/site/docs/subcomponents/drlvm/gc-howto.html harmony/standard/site/docs/subcomponents/drlvm/getting_started.html harmony/standard/site/docs/subcomponents/drlvm/index.html harmony/standard/site/docs/subcomponents/drlvm/internal_profiler.html (contents, props changed) harmony/standard/site/docs/subcomponents/drlvm/kernel_classes.html harmony/standard/site/docs/subcomponents/drlvm/site.css (props changed) harmony/standard/site/docs/subcomponents/jchevm/index.html harmony/standard/site/docs/subcomponents/stresstest/index.html harmony/standard/site/docs/svn.html harmony/standard/site/xdocs/stylesheets/site.vsl Modified: harmony/standard/site/docs/auth_cont_quest.html URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/auth_cont_quest.html?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/auth_cont_quest.html (original) +++ harmony/standard/site/docs/auth_cont_quest.html Sat May 5 07:37:18 2007 @@ -56,9 +56,9 @@ - - ApacheCon Europe 2007 + + ApacheCon US 2007 Modified: harmony/standard/site/docs/auth_cont_quest.txt URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/auth_cont_quest.txt?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/auth_cont_quest.txt (original) +++ harmony/standard/site/docs/auth_cont_quest.txt Sat May 5 07:37:18 2007 @@ -1,288 +1,288 @@ - The Apache Software Foundation - Apache Harmony Project - Authorized Contributor Questionnaire - v1.0 - - -Please Note : This document and your answers are considered public information, -and shall be part of the Apache Harmony project public records. - -Part I : Identification - - Please provide the following information - - Name : ___________________________________________ - E-mail : ___________________________________________ - - Mailing address : - ___________________________________________ - ___________________________________________ - ___________________________________________ - ___________________________________________ - - Employer : ___________________________________________ - -Part II: Access to Repositories - - The Project is committed to producing an implementation of Java that - can be licensed freely under the Apache License. To do this, - we wish to know what, if any, previous exposure you have had - to the source for any of the parts of a Java implementation - including virtual machines, class libraries, tooling, etc. - - The following activities are not considered "accessing the - source code" and would not generally disqualify you from - committing to the related repository here at Apache Harmony - - a) Having a copy of src.jar (or equivalent) on a computer as long as you - never viewed or edited the contents of the file. - - b) While running a debugger on a Java language program, having - had occasion to step into the source code for the implementation - as long as you did not attempt to understand or debug the - implementation code itself. - - c) Having implemented "plug-ins" or other component software which - interact with an implementation, but doing so only with reference - to the published service provider interfaces. - - d) Have written or executed test cases that probed the behavior - of an implementation as long as you did so with reference - only to published specifications and interfaces. - - The following is a list of the components of the project each - labeled with an ID (ex. JVM-1): - - VM - -- - VM-1 VM core (including JVMPI, JVMDI, JDWP, JVMTI, JNI, - JIT, Memory Management/GC, OS Portabillity, - Threading, etc) - VM-X other ____________________________________________ - - - Classlibrary - ------------ - CL-1 Applet (java.applet) - CL-2 Archive (java.util.zip, java.util.jar) - CL-3 Beans (java.beans) - CL-4 Core (incl. lang, util, net, io, annotation, concurrent, - NIO-channels, NIO-charset, text, javax.net - where not covered elsewhere in list) - CL-5 Image IO (javax.imageio) - CL-6 Instrument (java.lang.instrument) - CL-7 JMX (javax.management) - CL-8 Lang-management (java.lang.management) - CL-9 Logging (java.util.logging) - CL-10 Math (java.math) - CL-11 ORB (javax.activity, javax.rmi.*, javax.transaction.*, org.omg.*) - CL-12 Prefs (java.util.prefs) - CL-13 Print (javax.print.*) - CL-14 Regex (java.util.regex) - CL-15 RMI (java.rmi.*) - CL-16 Security (java.security.*, javax.security.*, org.ietf.jgss, - javax.crypto) - CL-17 Sound (javax.sound) - CL-18 SQL (java.sql, javax.sql.*) - CL-19 Swing / AWT (java.awt.*, javax.swing.*, javax.accessibility) - CL-20 XML (javax.xml.*, org.w3c.*, org.xml.*) - CL-21 JNDI (javax.naming.*) - CL-X other ____________________________________________ - - Tools & Misc - ------------ - T-1 launcher (e.g. java.exe) - T-2 javah - T-3 javap - T-4 javac - T-5 jdb - T-6 javadoc - T-7 jar - T-8 browser plugins - T-X other ____________________________________________ - - -Part III : General Exposure - - With the above activities a)-d) in mind, have you done any of the following - to an implementation of one or more of the components listed above. If the - question doesn't apply to you, please write "N/A". If it does, please list - the components by the above-listed IDs, and provide details : - - 1. Read some or all the source code for an implementation? - - [ ] Yes [ ] No - - Components : ________________________________________________________ - Details : ___________________________________________________________ - _____________________________________________________________________ - - 2. Fixed defects or performed other maintenance activity on an - implementation? - - [ ] Yes [ ] No - - Components : ________________________________________________________ - Details : ___________________________________________________________ - _____________________________________________________________________ - - - 3. Enhanced the source code for an implementation with additional function, - performance or other qualities of service? - - [ ] Yes [ ] No - - Components : ________________________________________________________ - Details : ___________________________________________________________ - _____________________________________________________________________ - - - 4. Ported an implementation to a different operating system or hardware - platform? - - [ ] Yes [ ] No - - Components : ________________________________________________________ - Details : ___________________________________________________________ - _____________________________________________________________________ - - 5. Reverse compiled or otherwise reverse engineered an implementation? - - [ ] Yes [ ] No - - Components : ________________________________________________________ - Details : ___________________________________________________________ - _____________________________________________________________________ - - - If you have answered yes to any question above, and that implementation is - not available under a recognized Open Source license, you may not be an - contributor to the related component of Apache Harmony unless the - copyright owner of that implementation either: - - a) submits the implementation to this project under the Software Grant or - the Corporate Contribution License Agreement (the CCLA); - - b) if the copyright owner is your current employer, signs a CCLA and - lists you as a designated employee; or - - c) if the copyright owner is not your current employer, submits - a written authorization disclaiming any copyright or confidentiality - interest in your current or future contributions to this project. - - 6. For each of the components listed above, please indicate either that you - will not be an Authorized Contributor for those components at Apache - Harmony, or indicate how you will resolve the issue of previous - exposure : - - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - - -Part IV : Confidential Exposure - - 1. Have you had access to any information regarding a proprietary - implementation of a component that could be considered - confidential? - - [ ] Yes [ ] No - - If so, you may be a Authorized Contributor for that component only - if the owner of that potential confidential information submits - a written authorization disclaiming any confidentiality interest - in your current or future contributions to this project. - - 2. For each of the components listed above for which you have had access - to such information, please indicate either that you will not - be an Authorized Contributor for those components at Apache Harmony, or - indicate how you will resolve the issue : - - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - - -Part V : Non-Compete Restrictions - - 1. Are you subject to a non-compete agreement that covers the - development of software? - - [ ] Yes [ ] No - - 2. Would the restrictions of that non-compete agreement prevent - you from working on any of the technology in or potentially - in Apache Harmomy? If yes, please provide details. - - [ ] Yes [ ] No - - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - - If so, you may be an Authorized Contributor for those areas - only if the other party submits a written authorization acknowledging that - your participation in the project is not in conflict with the - non-compete agreement. - - 3. Please indicate either that you will not be an Authorized Contributor for - those applicable components at Apache Harmony, or indicate how you will - resolve the issue : - - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - _____________________________________________________________________ - -Part VI : ICLA - - 1. Please execute a Individual Contributor License Agreement (ICLA). - - [ ] Yes, I have executed an ICLA - -Part VII : Employment Limitations - - 2. Are you employed as a programmer, systems analyst, or other - IT professional? - - [ ] Yes [ ] No - - If so, we encourage you to have your employer either : - - a) sign a Corporate Contribution License Agreement with Apache - and lists you as a designated employee or - - b) submits a written authorization for your participation in this - project and disclaims any copyright or confidentiality interest - in your current or future contributions to this project. - - - - - Signature : ___________________________________________ -Print Name : ___________________________________________ - Date : ___________________________________________ - - -v1.0 20060622 + The Apache Software Foundation + Apache Harmony Project + Authorized Contributor Questionnaire + v1.0 + + +Please Note : This document and your answers are considered public information, +and shall be part of the Apache Harmony project public records. + +Part I : Identification + + Please provide the following information + + Name : ___________________________________________ + E-mail : ___________________________________________ + + Mailing address : + ___________________________________________ + ___________________________________________ + ___________________________________________ + ___________________________________________ + + Employer : ___________________________________________ + +Part II: Access to Repositories + + The Project is committed to producing an implementation of Java that + can be licensed freely under the Apache License. To do this, + we wish to know what, if any, previous exposure you have had + to the source for any of the parts of a Java implementation + including virtual machines, class libraries, tooling, etc. + + The following activities are not considered "accessing the + source code" and would not generally disqualify you from + committing to the related repository here at Apache Harmony + + a) Having a copy of src.jar (or equivalent) on a computer as long as you + never viewed or edited the contents of the file. + + b) While running a debugger on a Java language program, having + had occasion to step into the source code for the implementation + as long as you did not attempt to understand or debug the + implementation code itself. + + c) Having implemented "plug-ins" or other component software which + interact with an implementation, but doing so only with reference + to the published service provider interfaces. + + d) Have written or executed test cases that probed the behavior + of an implementation as long as you did so with reference + only to published specifications and interfaces. + + The following is a list of the components of the project each + labeled with an ID (ex. JVM-1): + + VM + -- + VM-1 VM core (including JVMPI, JVMDI, JDWP, JVMTI, JNI, + JIT, Memory Management/GC, OS Portabillity, + Threading, etc) + VM-X other ____________________________________________ + + + Classlibrary + ------------ + CL-1 Applet (java.applet) + CL-2 Archive (java.util.zip, java.util.jar) + CL-3 Beans (java.beans) + CL-4 Core (incl. lang, util, net, io, annotation, concurrent, + NIO-channels, NIO-charset, text, javax.net + where not covered elsewhere in list) + CL-5 Image IO (javax.imageio) + CL-6 Instrument (java.lang.instrument) + CL-7 JMX (javax.management) + CL-8 Lang-management (java.lang.management) + CL-9 Logging (java.util.logging) + CL-10 Math (java.math) + CL-11 ORB (javax.activity, javax.rmi.*, javax.transaction.*, org.omg.*) + CL-12 Prefs (java.util.prefs) + CL-13 Print (javax.print.*) + CL-14 Regex (java.util.regex) + CL-15 RMI (java.rmi.*) + CL-16 Security (java.security.*, javax.security.*, org.ietf.jgss, + javax.crypto) + CL-17 Sound (javax.sound) + CL-18 SQL (java.sql, javax.sql.*) + CL-19 Swing / AWT (java.awt.*, javax.swing.*, javax.accessibility) + CL-20 XML (javax.xml.*, org.w3c.*, org.xml.*) + CL-21 JNDI (javax.naming.*) + CL-X other ____________________________________________ + + Tools & Misc + ------------ + T-1 launcher (e.g. java.exe) + T-2 javah + T-3 javap + T-4 javac + T-5 jdb + T-6 javadoc + T-7 jar + T-8 browser plugins + T-X other ____________________________________________ + + +Part III : General Exposure + + With the above activities a)-d) in mind, have you done any of the following + to an implementation of one or more of the components listed above. If the + question doesn't apply to you, please write "N/A". If it does, please list + the components by the above-listed IDs, and provide details : + + 1. Read some or all the source code for an implementation? + + [ ] Yes [ ] No + + Components : ________________________________________________________ + Details : ___________________________________________________________ + _____________________________________________________________________ + + 2. Fixed defects or performed other maintenance activity on an + implementation? + + [ ] Yes [ ] No + + Components : ________________________________________________________ + Details : ___________________________________________________________ + _____________________________________________________________________ + + + 3. Enhanced the source code for an implementation with additional function, + performance or other qualities of service? + + [ ] Yes [ ] No + + Components : ________________________________________________________ + Details : ___________________________________________________________ + _____________________________________________________________________ + + + 4. Ported an implementation to a different operating system or hardware + platform? + + [ ] Yes [ ] No + + Components : ________________________________________________________ + Details : ___________________________________________________________ + _____________________________________________________________________ + + 5. Reverse compiled or otherwise reverse engineered an implementation? + + [ ] Yes [ ] No + + Components : ________________________________________________________ + Details : ___________________________________________________________ + _____________________________________________________________________ + + + If you have answered yes to any question above, and that implementation is + not available under a recognized Open Source license, you may not be an + contributor to the related component of Apache Harmony unless the + copyright owner of that implementation either: + + a) submits the implementation to this project under the Software Grant or + the Corporate Contribution License Agreement (the CCLA); + + b) if the copyright owner is your current employer, signs a CCLA and + lists you as a designated employee; or + + c) if the copyright owner is not your current employer, submits + a written authorization disclaiming any copyright or confidentiality + interest in your current or future contributions to this project. + + 6. For each of the components listed above, please indicate either that you + will not be an Authorized Contributor for those components at Apache + Harmony, or indicate how you will resolve the issue of previous + exposure : + + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + + +Part IV : Confidential Exposure + + 1. Have you had access to any information regarding a proprietary + implementation of a component that could be considered + confidential? + + [ ] Yes [ ] No + + If so, you may be a Authorized Contributor for that component only + if the owner of that potential confidential information submits + a written authorization disclaiming any confidentiality interest + in your current or future contributions to this project. + + 2. For each of the components listed above for which you have had access + to such information, please indicate either that you will not + be an Authorized Contributor for those components at Apache Harmony, or + indicate how you will resolve the issue : + + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + + +Part V : Non-Compete Restrictions + + 1. Are you subject to a non-compete agreement that covers the + development of software? + + [ ] Yes [ ] No + + 2. Would the restrictions of that non-compete agreement prevent + you from working on any of the technology in or potentially + in Apache Harmomy? If yes, please provide details. + + [ ] Yes [ ] No + + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + + If so, you may be an Authorized Contributor for those areas + only if the other party submits a written authorization acknowledging that + your participation in the project is not in conflict with the + non-compete agreement. + + 3. Please indicate either that you will not be an Authorized Contributor for + those applicable components at Apache Harmony, or indicate how you will + resolve the issue : + + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + _____________________________________________________________________ + +Part VI : ICLA + + 1. Please execute a Individual Contributor License Agreement (ICLA). + + [ ] Yes, I have executed an ICLA + +Part VII : Employment Limitations + + 2. Are you employed as a programmer, systems analyst, or other + IT professional? + + [ ] Yes [ ] No + + If so, we encourage you to have your employer either : + + a) sign a Corporate Contribution License Agreement with Apache + and lists you as a designated employee or + + b) submits a written authorization for your participation in this + project and disclaims any copyright or confidentiality interest + in your current or future contributions to this project. + + + + + Signature : ___________________________________________ +Print Name : ___________________________________________ + Date : ___________________________________________ + + +v1.0 20060622 Propchange: harmony/standard/site/docs/auth_cont_quest.txt ------------------------------------------------------------------------------ svn:eol-style = native Modified: harmony/standard/site/docs/bulk_contribution_checklist.html URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/bulk_contribution_checklist.html?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/bulk_contribution_checklist.html (original) +++ harmony/standard/site/docs/bulk_contribution_checklist.html Sat May 5 07:37:18 2007 @@ -56,9 +56,9 @@ - - ApacheCon Europe 2007 + + ApacheCon US 2007 Modified: harmony/standard/site/docs/bulk_contribution_checklist.txt URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/bulk_contribution_checklist.txt?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/bulk_contribution_checklist.txt (original) +++ harmony/standard/site/docs/bulk_contribution_checklist.txt Sat May 5 07:37:18 2007 @@ -1,144 +1,144 @@ - The Apache Software Foundation - Apache Harmony Project - Bulk Contribution Checklist - v 1.1 20051114 - -The Apache Harmony project is dedicated to producing a codebase that -has clear IP pedigree and protects the IP rights of others. As part -of this effort, we ask the following questions of all contributions -of software that has been created outside of the project. Our goal is -to provide clear and consistent oversight of the project codebase, as -well as encourage our contributors to carefully examine their -contributions before bringing to the project. - -Please Note : This document and your answers are considered public -information, and shall be part of the Apache Harmony project public -records. - - -Part I : Identification - - Please provide the following information - - Name : ___________________________________________ - E-mail : ___________________________________________ - - Mailing address : - ___________________________________________ - ___________________________________________ - ___________________________________________ - ___________________________________________ - - Employer : ___________________________________________ - - -Part II : Description - - Please describe the contribution : - - - - - -Part III : Statement of Origination - -a) Have you personally written all of the code or other material - that you are intending to contribute to this project, and if so, - are you an Authorized Contributor for all parts of the contribution? - - [ ] Yes - [ ] No - - If "yes", you're done with Part III, skip to Part IV - If "no" please continue with the rest of Part III - -b) Have you verified the development history of the code to - identify ALL of the authors? - - Please list the other authors: - - -c) Do you have a written agreement with all of the authors that - either gives you ownership of the material or otherwise provides - you sufficient rights to submit this material to the project - on their behalf. - - Please provide the details of this agreement: - - -d) Are all of the authors Authorized Contributors for the part of - the contribution written/created by each author? - - [ ] Yes Ð if "yes", you're done with Part III, skip to Part IV. - [ ] No Ð if "no", please continue with the rest of part III - - -e) Was the code written prior to May 2005 (when the Harmony Project - was initiated)? - - [ ] Yes - [ ] No - - (i) If No, you must provide Authorized Contributor Questionnaires - for the authors of the code created after May 2005 such that - those authors are classified as Authorized Contributors for - the portions of the contribution written by them - after May 2005. - -f) Did any of the authors of the code have access to third - party implementations of similar technology while developing the - contribution? - - [ ] Yes - [ ] No - - If "yes", please give details below : - - - - -g) Was the code developed in accordance with a development - process which was designed to prevent unauthorized inclusion - of third party intellectual property rights into the code? - (e.g., does the process require that developers not have - concurrent access to third party implementations of similar - technology during development?) - - [ ] Yes - [ ] No - - If "no", the code isn't eligible for the Harmony Project. - - If "yes", please provide short description of the process, - focusing on protections related to third party intellectual - property : - - - - -Note : The Apache Harmony project generally performs additional -scans of it's codebase, including bulk contributions, to help -confirm code pedigree. Prior to submitting any contribution, -we strongly encourage you to verify that the contribution is -acceptable. Please see http://harmony.apache.org/code_scan_tools.html -for more information. - - - - -Part IV : Checklist - - [ ] Contribution is licensed under the Apache License v2.0 - - [ ] Software Grant or Corporate Contributor License Agreement and Software - Grant executed and submitted - - - Signature : ___________________________________________ -Print Name : ___________________________________________ - Date : ___________________________________________ - - - -v1.1 20051114 - + The Apache Software Foundation + Apache Harmony Project + Bulk Contribution Checklist + v 1.1 20051114 + +The Apache Harmony project is dedicated to producing a codebase that +has clear IP pedigree and protects the IP rights of others. As part +of this effort, we ask the following questions of all contributions +of software that has been created outside of the project. Our goal is +to provide clear and consistent oversight of the project codebase, as +well as encourage our contributors to carefully examine their +contributions before bringing to the project. + +Please Note : This document and your answers are considered public +information, and shall be part of the Apache Harmony project public +records. + + +Part I : Identification + + Please provide the following information + + Name : ___________________________________________ + E-mail : ___________________________________________ + + Mailing address : + ___________________________________________ + ___________________________________________ + ___________________________________________ + ___________________________________________ + + Employer : ___________________________________________ + + +Part II : Description + + Please describe the contribution : + + + + + +Part III : Statement of Origination + +a) Have you personally written all of the code or other material + that you are intending to contribute to this project, and if so, + are you an Authorized Contributor for all parts of the contribution? + + [ ] Yes + [ ] No + + If "yes", you're done with Part III, skip to Part IV + If "no" please continue with the rest of Part III + +b) Have you verified the development history of the code to + identify ALL of the authors? + + Please list the other authors: + + +c) Do you have a written agreement with all of the authors that + either gives you ownership of the material or otherwise provides + you sufficient rights to submit this material to the project + on their behalf. + + Please provide the details of this agreement: + + +d) Are all of the authors Authorized Contributors for the part of + the contribution written/created by each author? + + [ ] Yes Ð if "yes", you're done with Part III, skip to Part IV. + [ ] No Ð if "no", please continue with the rest of part III + + +e) Was the code written prior to May 2005 (when the Harmony Project + was initiated)? + + [ ] Yes + [ ] No + + (i) If No, you must provide Authorized Contributor Questionnaires + for the authors of the code created after May 2005 such that + those authors are classified as Authorized Contributors for + the portions of the contribution written by them + after May 2005. + +f) Did any of the authors of the code have access to third + party implementations of similar technology while developing the + contribution? + + [ ] Yes + [ ] No + + If "yes", please give details below : + + + + +g) Was the code developed in accordance with a development + process which was designed to prevent unauthorized inclusion + of third party intellectual property rights into the code? + (e.g., does the process require that developers not have + concurrent access to third party implementations of similar + technology during development?) + + [ ] Yes + [ ] No + + If "no", the code isn't eligible for the Harmony Project. + + If "yes", please provide short description of the process, + focusing on protections related to third party intellectual + property : + + + + +Note : The Apache Harmony project generally performs additional +scans of it's codebase, including bulk contributions, to help +confirm code pedigree. Prior to submitting any contribution, +we strongly encourage you to verify that the contribution is +acceptable. Please see http://harmony.apache.org/code_scan_tools.html +for more information. + + + + +Part IV : Checklist + + [ ] Contribution is licensed under the Apache License v2.0 + + [ ] Software Grant or Corporate Contributor License Agreement and Software + Grant executed and submitted + + + Signature : ___________________________________________ +Print Name : ___________________________________________ + Date : ___________________________________________ + + + +v1.1 20051114 + Propchange: harmony/standard/site/docs/bulk_contribution_checklist.txt ------------------------------------------------------------------------------ svn:eol-style = native Modified: harmony/standard/site/docs/code_scan_tools.html URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/code_scan_tools.html?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/code_scan_tools.html (original) +++ harmony/standard/site/docs/code_scan_tools.html Sat May 5 07:37:18 2007 @@ -56,9 +56,9 @@ - - ApacheCon Europe 2007 + + ApacheCon US 2007 Modified: harmony/standard/site/docs/contribution_policy.html URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/contribution_policy.html?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/contribution_policy.html (original) +++ harmony/standard/site/docs/contribution_policy.html Sat May 5 07:37:18 2007 @@ -56,9 +56,9 @@ - - ApacheCon Europe 2007 + + ApacheCon US 2007 Modified: harmony/standard/site/docs/contributors.html URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/contributors.html?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/contributors.html (original) +++ harmony/standard/site/docs/contributors.html Sat May 5 07:37:18 2007 @@ -56,9 +56,9 @@ - - ApacheCon Europe 2007 + + ApacheCon US 2007 Modified: harmony/standard/site/docs/documentation/build_website.html URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/documentation/build_website.html?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/documentation/build_website.html (original) +++ harmony/standard/site/docs/documentation/build_website.html Sat May 5 07:37:18 2007 @@ -56,9 +56,9 @@ - - ApacheCon Europe 2007 + + ApacheCon US 2007 Modified: harmony/standard/site/docs/documentation/conventions.html URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/documentation/conventions.html?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/documentation/conventions.html (original) +++ harmony/standard/site/docs/documentation/conventions.html Sat May 5 07:37:18 2007 @@ -1,398 +1,398 @@ - - - - - - - - - - - - - - - - - - - - - - - - Apache Harmony - Conventions - - - - - - - - - - - - - -
- - -
- -Apache Harmony -
- 		- - ApacheCon Europe 2007 -
- - - - - - - - - - - - -
-
-
- - - - - - - - -

General

- -

Community

- -

Development

- -

Documentation

- - 		-

- Conventions -

-

The DRL (dynamic run-time layer) documentation set uses the following conventions.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Convention - - Explanation - - Example -
- - monospace - - - Filenames - - - ippsapi.h -
- - monospace - - - Directory names and pathnames - - - \alt\include -
- - monospace - - - Commands and command-line options - - - ecl -O2 -
- - monospace - - - Function names, methods, classes, data structures in - running text - - - Use the okCreateObjs function to ... -
- - monospace - - - Parameters or other placeholders - - - ippiMalloc(int widthPixels, ...)
- int* pStepBytes -
- - - - monospace bold - - - - - User input - - - - - [c:] dir - - -
- - - italics - - - - Emphasis; introducing or defining terms - - - - The term access takes as its subject ... - -
- - [ ] - - - Optional items - - - - -Fa[c] Indicates these command-line - options: -Fa and -Fac - -
- - { | } - - - - Choice of one item from a selection of two or more - items. - - - - - -aX{K | W | P} Indicates these command-line - options:
- -aXK
- -aXW
-aXP -
-

Back to top

- -
-
-
-
- Copyright © 2003-2007, The Apache Software Foundation -
-
- - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + Apache Harmony - Conventions + + + + + + + + + + + + + +
+ + +
+ +Apache Harmony +
+ 		+ + ApacheCon US 2007 +
+ + + + + + + + + + + + +
+
+
+ + + + + + + + +

General

+ +

Community

+ +

Development

+ +

Documentation

+ + 		+

+ Conventions +

+

The DRL (dynamic run-time layer) documentation set uses the following conventions.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Convention + + Explanation + + Example +
+ + monospace + + + Filenames + + + ippsapi.h +
+ + monospace + + + Directory names and pathnames + + + \alt\include +
+ + monospace + + + Commands and command-line options + + + ecl -O2 +
+ + monospace + + + Function names, methods, classes, data structures in + running text + + + Use the okCreateObjs function to ... +
+ + monospace + + + Parameters or other placeholders + + + ippiMalloc(int widthPixels, ...)
+ int* pStepBytes +
+ + + + monospace bold + + + + + User input + + + + + [c:] dir + + +
+ + + italics + + + + Emphasis; introducing or defining terms + + + + The term access takes as its subject ... + +
+ + [ ] + + + Optional items + + + + -Fa[c] Indicates these command-line + options: -Fa and -Fac + +
+ + { | } + + + + Choice of one item from a selection of two or more + items. + + + + + -aX{K | W | P} Indicates these command-line + options:
+ -aXK
+ -aXW
-aXP +
+

Back to top

+ +
+
+
+
+ Copyright © 2003-2007, The Apache Software Foundation +
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + Propchange: harmony/standard/site/docs/documentation/conventions.html ------------------------------------------------------------------------------ svn:eol-style = native Modified: harmony/standard/site/docs/documentation/dev_eclipse.html URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/documentation/dev_eclipse.html?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/documentation/dev_eclipse.html (original) +++ harmony/standard/site/docs/documentation/dev_eclipse.html Sat May 5 07:37:18 2007 @@ -56,9 +56,9 @@ - - ApacheCon Europe 2007 + + ApacheCon US 2007 Propchange: harmony/standard/site/docs/documentation/site.css ------------------------------------------------------------------------------ svn:eol-style = native Modified: harmony/standard/site/docs/downloads.html URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/downloads.html?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/downloads.html (original) +++ harmony/standard/site/docs/downloads.html Sat May 5 07:37:18 2007 @@ -56,9 +56,9 @@ - - ApacheCon Europe 2007 + + ApacheCon US 2007 Modified: harmony/standard/site/docs/faq.html URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/faq.html?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/faq.html (original) +++ harmony/standard/site/docs/faq.html Sat May 5 07:37:18 2007 @@ -56,9 +56,9 @@ - - ApacheCon Europe 2007 + + ApacheCon US 2007 Modified: harmony/standard/site/docs/get-involved.html URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/get-involved.html?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/get-involved.html (original) +++ harmony/standard/site/docs/get-involved.html Sat May 5 07:37:18 2007 @@ -56,9 +56,9 @@ - - ApacheCon Europe 2007 + + ApacheCon US 2007 Modified: harmony/standard/site/docs/guidelines.html URL: http://svn.apache.org/viewvc/harmony/standard/site/docs/guidelines.html?view=diff&rev=535532&r1=535531&r2=535532 ============================================================================== --- harmony/standard/site/docs/guidelines.html (original) +++ harmony/standard/site/docs/guidelines.html Sat May 5 07:37:18 2007 @@ -56,9 +56,9 @@ - - ApacheCon Europe 2007 + + ApacheCon US 2007