Author: britter
Date: Tue Jan 27 20:20:11 2015
New Revision: 1655144
URL: http://svn.apache.org/r1655144
Log:
Add autogenerated README and CONTRIBUTING files for github contributors
Added:
commons/proper/validator/trunk/CONTRIBUTING.md
Modified:
commons/proper/validator/trunk/README.md
Added: commons/proper/validator/trunk/CONTRIBUTING.md
URL:
http://svn.apache.org/viewvc/commons/proper/validator/trunk/CONTRIBUTING.md?rev=1655144&view=auto
==============================================================================
--- commons/proper/validator/trunk/CONTRIBUTING.md (added)
+++ commons/proper/validator/trunk/CONTRIBUTING.md Tue Jan 27 20:20:11 2015
@@ -0,0 +1,97 @@
+<!---
+ 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.
+-->
+<!---
+ +======================================================================+
+ |**** ****|
+ |**** THIS FILE IS GENERATED BY THE COMMONS BUILD PLUGIN ****|
+ |**** DO NOT EDIT DIRECTLY ****|
+ |**** ****|
+ +======================================================================+
+ | TEMPLATE FILE: contributing-md-template.md |
+ | commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
+ +======================================================================+
+ | |
+ | 1) Re-generate using: mvn commons:contributing-md |
+ | |
+ | 2) Set the following properties in the component's pom: |
+ | - commons.jira.id (required, alphabetic, upper case) |
+ | |
+ | 3) Example Properties |
+ | |
+ | <properties> |
+ | <commons.jira.id>MATH</commons.jira.id> |
+ | </properties> |
+ | |
+ +======================================================================+
+--->
+Contributing to Apache Commons Validator
+======================
+
+You have found a bug or you have an idea for a cool new feature? Contributing
code is a great way to give something back to
+the open source community. Before you dig right into the code there are a few
guidelines that we need contributors to
+follow so that we can have a chance of keeping on top of things.
+
+Getting Started
+---------------
+
++ Make sure you have a [JIRA account](https://issues.apache.org/jira/).
++ Make sure you have a [GitHub account](https://github.com/signup/free).
++ If you're planning to implement a new feature it makes sense to discuss
you're changes on the [dev list](https://commons.apache.org/mail-lists.html)
first. This way you can make sure you're not wasting your time on something
that isn't considered to be in Apache Commons Validator's scope.
++ Submit a ticket for your issue, assuming one does not already exist.
+ + Clearly describe the issue including steps to reproduce when it is a bug.
+ + Make sure you fill in the earliest version that you know has the issue.
++ Fork the repository on GitHub.
+
+Making Changes
+--------------
+
++ Create a topic branch from where you want to base your work (this is usually
the master/trunk branch).
++ Make commits of logical units.
++ Respect the original code style:
+ + Only use spaces for indentation.
+ + Create minimal diffs - disable on save actions like reformat source code
or organize imports. If you feel the source code should be reformatted create a
separate PR for this change.
+ + Check for unnecessary whitespace with git diff --check before committing.
++ Make sure your commit messages are in the proper format. Your commit message
should contain the key of the JIRA issue.
++ Make sure you have added the necessary tests for your changes.
++ Run all the tests with `mvn clean verify` to assure nothing else was
accidentally broken.
+
+Making Trivial Changes
+----------------------
+
+For changes of a trivial nature to comments and documentation, it is not
always necessary to create a new ticket in JIRA.
+In this case, it is appropriate to start the first line of a commit with
'(doc)' instead of a ticket number.
+
+Submitting Changes
+------------------
+
++ Sign the [Contributor License Agreement][cla] if you haven't already.
++ Push your changes to a topic branch in your fork of the repository.
++ Submit a pull request to the repository in the apache organization.
++ Update your JIRA ticket and include a link to the pull request in the ticket.
+
+Additional Resources
+--------------------
+
++ [Contributing patches](https://commons.apache.org/patches.html)
++ [Apache Commons Validator JIRA project
page](https://issues.apache.org/jira/browse/VALIDATOR)
++ [Contributor License Agreement][cla]
++ [General GitHub documentation](https://help.github.com/)
++ [GitHub pull request
documentation](https://help.github.com/send-pull-requests/)
++ [Apache Commons Twitter Account](https://twitter.com/ApacheCommons)
++ #apachecommons IRC channel on freenode.org
+
+[cla]:https://www.apache.org/licenses/#clas
Modified: commons/proper/validator/trunk/README.md
URL:
http://svn.apache.org/viewvc/commons/proper/validator/trunk/README.md?rev=1655144&r1=1655143&r2=1655144&view=diff
==============================================================================
--- commons/proper/validator/trunk/README.md (original)
+++ commons/proper/validator/trunk/README.md Tue Jan 27 20:20:11 2015
@@ -21,7 +21,7 @@
|**** DO NOT EDIT DIRECTLY ****|
|**** ****|
+======================================================================+
- | TEMPLATE FILE: mail-lists-template.xml |
+ | TEMPLATE FILE: readme-md-template.md |
| commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
+======================================================================+
| |
@@ -44,18 +44,18 @@ Apache Commons Validator
===================
Apache Commons Validator provides the building blocks for both client side
validation and server side data validation.
-It may be used standalone or with a framework like Struts.
+ It may be used standalone or with a framework like Struts.
Documentation
-------------
-More information can be found on the
[homepage](http://commons.apache.org/proper/commons-validator).
-The [JavaDoc](http://commons.apache.org/proper/commons-validator/apidocs) can
be browsed.
+More information can be found on the
[homepage](https://commons.apache.org/proper/commons-validator).
+The
[JavaDoc](https://commons.apache.org/proper/commons-validator/javadocs/api-1.4.1)
can be browsed.
Questions related to the usage of Apache Commons Validator should be posted to
the [user mailing list][ml].
Where can I get the latest release?
-----------------------------------
-You can download source and binaries from our [download
page](http://commons.apache.org/proper/commons-validator/download_validator.cgi).
+You can download source and binaries from our [download
page](https://commons.apache.org/proper/commons-validator/download_validator.cgi).
Alternatively you can pull it from the central Maven repositories:
@@ -75,24 +75,25 @@ There are some guidelines which will mak
+ No tabs! Please use spaces for indentation.
+ Respect the code style.
+ Create minimal diffs - disable on save actions like reformat source code or
organize imports. If you feel the source code should be reformatted create a
separate PR for this change.
-+ Provide JUnit tests for your changes and make sure your changes don't break
any existing tests by running ```mvn clean verify```.
++ Provide JUnit tests for your changes and make sure your changes don't break
any existing tests by running ```mvn clean test```.
-If you plan to contribute on a regular basis, please consider filing a
[contributor license agreement](http://www.apache.org/licenses/#clas).
+If you plan to contribute on a regular basis, please consider filing a
[contributor license agreement](https://www.apache.org/licenses/#clas).
+You can learn more about contributing via GitHub in our [contribution
guidelines](CONTRIBUTING.md).
License
-------
-Code is under the [Apache Licence
v2](http://www.apache.org/licenses/LICENSE-2.0.txt).
+Code is under the [Apache Licence
v2](https://www.apache.org/licenses/LICENSE-2.0.txt).
Donations
---------
-You like Apache Commons Validator? Then [donate back to the
ASF](http://www.apache.org/foundation/contributing.html) to support the
development.
+You like Apache Commons Validator? Then [donate back to the
ASF](https://www.apache.org/foundation/contributing.html) to support the
development.
Additional Resources
--------------------
-+ [Apache Commons Homepage](http://commons.apache.org/)
++ [Apache Commons Homepage](https://commons.apache.org/)
+ [Apache Bugtracker (JIRA)](https://issues.apache.org/jira/)
+ [Apache Commons Twitter Account](https://twitter.com/ApacheCommons)
+ #apachecommons IRC channel on freenode.org
-[ml]:http://commons.apache.org/proper/commons-validator/mail-lists.html
+[ml]:https://commons.apache.org/mail-lists.html
