HV-1464 Remove requirement for CLA

Author: gsmet

CONTRIBUTING.md

@@ -1,19 +1,32 @@
 Guidelines for contributing to Hibernate Validator
 ====
+
 Contributions from the community are essential in keeping Hibernate Validator strong and successful.
 This guide focuses on how to contribute back to Hibernate Validator using GitHub pull requests.
 If you need help with cloning, compiling or setting the project up in an IDE please refer to
 [this page](http://hibernate.org/validator/contribute/).
 
+## Legal
+
+All original contributions to Hibernate Validator are licensed under the
+[Apache License version 2.0](https://www.apache.org/licenses/LICENSE-2.0),
+or, if another license is specified as governing the file or directory being
+modified, such other license. The Apache License text is included verbatim in the [license.txt](license.txt) file
+in the root directory of the repository.
+
+All contributions are subject to the [Developer Certificate of Origin (DCO)](https://developercertificate.org/).
+The DCO text is also included verbatim in the [dco.txt](dco.txt) file in the root directory of the repository.
+
 ## Getting Started
+
 If you are just getting started with Git, GitHub and/or contributing to Hibernate Validator there are a
 few prerequisite steps:
 
 * Make sure you have a [Hibernate JIRA account](https://hibernate.atlassian.net)
 * Make sure you have a [GitHub account](https://github.com/signup/free)
-* [Fork](http://help.github.com/fork-a-repo) the Hibernate Validator [repository](https://github.com/hibernate/hibernate-validator).
+* [Fork](https://help.github.com/articles/fork-a-repo/) the Hibernate Validator [repository](https://github.com/hibernate/hibernate-validator).
 As discussed in the linked page, this also includes:
-    * [Setting](https://help.github.com/articles/set-up-git) up your local git install
+    * [Setting](https://help.github.com/articles/set-up-git/) up your local git install
     * Cloning your fork
 
 ## Create a test case
@@ -27,6 +40,7 @@ projects](https://github.com/hibernate/hibernate-test-case-templates).
 Just fork this repository, build your test case and attach it as an archive to a JIRA issue.
 
 ## Create a topic branch
+
 Create a "topic" branch on which you will work.  The convention is to name the branch
 using the JIRA issue key.  If there is not already a JIRA issue covering the work you
 want to do, create one.  Assuming you will be working from the master branch and working
@@ -77,7 +91,7 @@ git pull --rebase upstream master
 ```
 
 ## Submit
-* Sign the [Contributor License Agreement](https://cla.jboss.org/) for the Hibernate Validator project.
+
 * Push your changes to a topic branch in your fork of the repository.
-* Initiate a [pull request](http://help.github.com/send-pull-requests/).
+* Initiate a [pull request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/).
 * Update the JIRA issue, adding a comment including a link to the created pull request.

dco.txt

@@ -0,0 +1,37 @@
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+1 Letterman Drive
+Suite D4700
+San Francisco, CA, 94129
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.