You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by ba...@apache.org on 2019/03/31 18:40:22 UTC
svn commit: r1856682 -
/infrastructure/site/trunk/content/licenses/contributor-agreements.mdtext
Author: bayard
Date: Sun Mar 31 18:40:22 2019
New Revision: 1856682
URL: http://svn.apache.org/viewvc?rev=1856682&view=rev
Log:
Adding a new page to cover CLAs/license-grant. Uses existing text from index for now
Added:
infrastructure/site/trunk/content/licenses/contributor-agreements.mdtext
Added: infrastructure/site/trunk/content/licenses/contributor-agreements.mdtext
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/licenses/contributor-agreements.mdtext?rev=1856682&view=auto
==============================================================================
--- infrastructure/site/trunk/content/licenses/contributor-agreements.mdtext (added)
+++ infrastructure/site/trunk/content/licenses/contributor-agreements.mdtext Sun Mar 31 18:40:22 2019
@@ -0,0 +1,125 @@
+Title: ASF Contributor Agreements
+Notice: Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+ .
+ http://www.apache.org/licenses/LICENSE-2.0
+ .
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+
+# ASF Contributor Agreements
+
+The Apache Software Foundation uses various agreements to
+accept regular contributions from individuals and corporations, and to accept
+larger grants of existing software products.
+
+These agreements help us achieve our goal of providing reliable and
+long-lived software products through collaborative open source software
+development. In all cases, contributors retain full rights to use their
+original contributions for any other purpose outside of Apache while
+providing the ASF and its projects the right to distribute and build upon
+their work within Apache.
+
+# Contributor License Agreements # {#clas}
+
+The ASF desires that all contributors of ideas, code, or documentation to
+any Apache projects complete, sign, and submit via
+email an [Individual Contributor License Agreement](icla.pdf) (ICLA).
+
+The purpose of this agreement is to clearly define the
+terms under which intellectual property has been contributed to the ASF and
+thereby allow us to defend the project should there be a legal dispute
+regarding the software at some future time. A signed ICLA is required to be
+on file before an individual is given commit rights to any ASF project.
+
+For a corporation that has assigned employees to work on an Apache project,
+a [Corporate CLA](cla-corporate.pdf) (CCLA) is available for contributing
+intellectual property via the corporation, that may have been assigned as
+part of an employment agreement.
+
+Note that a Corporate CLA does not remove
+the need for every developer to sign their own ICLA as an individual, which
+covers both contributions which are owned and those that are not owned by the corporation
+signing the CCLA.
+
+The CCLA legally binds the corporation, so it must be signed by a person with
+authority to enter into legal contracts on behalf of the corporation.
+
+The ICLA is not tied to any employer you may have, so it is recommended to
+use one's personal email address in the contact details, rather than an @work
+address.
+
+Your Full name will be published unless you provide an alternative Public name.
+For example if your full name is Andrew Bernard Charles Dickens, but you wish
+to be known as Andrew Dickens, please enter the latter as your Public name.
+
+The email address and other contact details are not published.
+
+If you are submitting an ICLA in response to an invitation from a PMC, be sure to
+identify the project via the form field "notify project". Also, choose a preferred id that
+is not already in use. Apache ids must start with an alphabetic character and contain
+at least two additional alphanumeric characters (no special characters).
+You can check for ids in use [here](http://people.apache.org/committer-index.html).
+
+# Software License Grant # {#grants}
+
+When an individual or corporation decides to donate a body of existing
+software or documentation to one of the Apache projects, they need to
+execute a formal [Software Grant Agreement](software-grant-template.pdf) (SGA) with
+the ASF. Typically, this is done after negotiating approval with the ASF
+[Incubator](http://incubator.apache.org/) or one of the PMCs, since the ASF
+will not accept software unless there is a viable community available to
+support a collaborative project.
+
+# Submitting License Agreements and Grants # {#submitting}
+
+Documents may be submitted by email and signed by hand or by electronic signature.
+Postal mail hard copy and fax are no longer supported.
+
+When submitting by email, please fill the form with a pdf viewer, then
+print, sign, scan all pages into a single pdf file,
+and attach the pdf file to an email to secretary@apache.org.
+
+If possible, send the attachment from the email address in the document.
+Please send only one document per email.
+
+If you prefer to sign electronically, please fill the form, save it locally (e.g. icla.pdf), and sign the
+file by preparing a detached PGP signature. For example,
+
+>gpg --armor --detach-sign icla.pdf
+
+The above will create a file icla.pdf.asc. Send both the file (icla.pdf) and signature
+(icla.pdf.asc) as attachments in the same email to secretary@apache.org. Please send only one
+document (file plus signature) per email. Please do not submit your public key to Apache.
+Instead, please upload your public key to pgpkeys.mit.edu.
+
+The files should be named
+icla.pdf and icla.pdf.asc for individual agreements;
+ccla.pdf and ccla.pdf.asc for corporate agreements;
+software-grant.pdf and software-grant.pdf.asc for grants.
+
+We do not accept Zip files or other archives.
+We do not accept links to files; the files must be attached to the mail.
+
+Please note that typing your name in the field at the bottom of the document is not signing,
+regardless of the font that is used.
+Signing is either writing your signature by hand on a printed copy of the document,
+or digitally signing via gpg. Unsigned documents will not be accepted.
+
+From wikipedia.org: A signature is a handwritten (and often stylized) depiction of someone's name
+or nickname, on documents as a proof of identity and intent.
+
+# Questions? # {#questions}
+
+For answers to frequently asked licensing questions, please consult our
+[Licensing Frequently Asked Questions](/foundation/license-faq.html) page.
+
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org