Users Guide

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. SOFTWARE 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 (SGA) with the ASF. Typically, this is done after negotiating approval with the ASF Incubator 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 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 [e-mail]. 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 [e-mail]. 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. 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. PROVENANCE Source code (including machine-readable
documentation, release notes, guides, test cases, run books, and scripts) in Apache repositories falls into three classifications
(solely for the purpose of this discussion): CODE DEVELOPED AT APACHE UNDER APACHE GOVERNANCE, LICENSED TO
APACHE BY ITS DEVELOPERS UNDER A CONTRIBUTOR LICENSE AGREEMENT, DISTRIBUTED BY APACHE, AND LICENSED
TO DOWNSTREAM USERS UNDER THE APACHE LICENSE This represents most code at Apache. The code contains a
standard Apache license header which refers to the standard Apache license in the distribution. CODE DEVELOPED
ELSEWHERE, LICENSED TO APACHE UNDER A SOFTWARE GRANT AGREEMENT, INCORPORATED INTO APACHE
PROJECTS, DISTRIBUTED BY APACHE, AND LICENSED TO DOWNSTREAM USERS UNDER THE APACHE LICENSE This is
code that is being brought into Apache for future development as part of an Apache project. The headers on all files are
changed to the standard Apache header. Most incubator projects start as externally-developed code and the Intellectual
Property Clearance process is done as part of incubation. Code that is originally developed elsewhere and is being brought into
Apache for future development as part of an existing project must have the Intellectual Property Clearance process done
explicitly by the PMC of the receiving project, under the auspices of the Incubator PMC which must approve the process. CODE
DEVELOPED ELSEWHERE, RECEIVED UNDER A CATEGORY A LICENSE, INCORPORATED INTO APACHE PROJECTS,
DISTRIBUTED BY APACHE, AND LICENSED TO DOWNSTREAM USERS UNDER ITS ORIGINAL LICENSE This code retains its
external identity and is being incorporated into an Apache project for convenience, to avoid referencing an external repository
whose contents are not under control of the project. The code retains its original license; and distribution as part of the Apache
project explicitly calls out the license. The code retains its original header which refers to its own license in the distribution. If
changes are made to the code while at Apache, the standard Apache header is prepended to each changed file. Additionally, any
legally-required notices related to the code are published in the distribution. EXPORT RESTRICTIONS For export restriction
information, please consult our ASF Export Classifications page. TRADEMARK AND LOGO USAGE For ASF trademark and logo
usage information, please consult our ASF Trademark Use Policy page. QUESTIONS? For answers to frequently asked licensing
questions, please consult our Licensing Frequently Asked Questions page.
MIT
The MIT License SPDX short identifier: MIT Further resources on the MIT License Copyright Permission is hereby granted, free
of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the
Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following
conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Third party licenses
61