Put stuff in the README and added LICENSE

LICENSE

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (C) 2012 Jared Koumentis
+
+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.

README.textile

@@ -0,0 +1,31 @@
+h1. zbv-parser - The simple Zetaback Violator report parser.
+
+By Jared Koumentis
+
+h2. What it does.
+
+  * Hand it a plain text file in the format of a Zetaback violator report.
+  * Use the output to focus your work.
+
+h2. Why it exists.
+
+  * In my work, I have to review Zetaback violator reports. These are used to ensure our backups are up to date.
+  * Any backup that is "stale", that is older than 14 days, ends up in the report.
+  * The objective is to allow you to use the report and determine what you should look at and ensure that your backups are working properly.
+  * Unfortunately, the way it reports, it will not take into consideration that a Full backup is dependent on an Incremental that has not gone stale. However, it will still report the Full backup as "stale".
+  * These false positives suck and make my job harder. So, this exists to trim out these false positives.
+
+h2. How to use it.
+
+  * Call the program.
+  * Tell it where to find your Zetaback violator report.
+  * It will then parse your log, finding actual violations, and output a new file with the actual violators.
+  * Take care of the violators while enjoying the fact that you don't have to attempt to manually parse through all the false positives.
+
+h2. Requirements.
+
+  * Ruby ~> 1.9
+
+h2. License
+
+  * MIT license. See LICENSE for details.