prag_events 0.0.1

data/.gitignore

@@ -0,0 +1,4 @@
+.DS_Store
+results.html
+pkg
+html

data/.rvmrc

@@ -0,0 +1 @@
+rvm use 1.9.3-p0@prag_events --create

data/Gemfile

@@ -0,0 +1,4 @@
+source "http://rubygems.org"
+
+# Specify your gem's dependencies in prag_events.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,61 @@
+PATH
+  remote: .
+  specs:
+    prag_events (0.0.1)
+      gem-man
+      methadone (~> 1.0.0)
+
+GEM
+  remote: http://rubygems.org/
+  specs:
+    aruba (0.4.11)
+      childprocess (>= 0.2.3)
+      cucumber (>= 1.1.1)
+      ffi (>= 1.0.11)
+      rspec (>= 2.7.0)
+    builder (3.0.0)
+    childprocess (0.3.2)
+      ffi (~> 1.0.6)
+    cucumber (1.1.9)
+      builder (>= 2.1.2)
+      diff-lcs (>= 1.1.2)
+      gherkin (~> 2.9.0)
+      json (>= 1.4.6)
+      term-ansicolor (>= 1.0.6)
+    diff-lcs (1.1.3)
+    ffi (1.0.11)
+    gem-man (0.3.0)
+    gherkin (2.9.3)
+      json (>= 1.4.6)
+    hpricot (0.8.6)
+    json (1.6.6)
+    methadone (1.0.0)
+      bundler
+    mustache (0.99.4)
+    rake (0.9.2.2)
+    rdiscount (1.6.8)
+    rdoc (3.12)
+      json (~> 1.4)
+    ronn (0.7.3)
+      hpricot (>= 0.8.2)
+      mustache (>= 0.7.0)
+      rdiscount (>= 1.5.8)
+    rspec (2.9.0)
+      rspec-core (~> 2.9.0)
+      rspec-expectations (~> 2.9.0)
+      rspec-mocks (~> 2.9.0)
+    rspec-core (2.9.0)
+    rspec-expectations (2.9.1)
+      diff-lcs (~> 1.1.3)
+    rspec-mocks (2.9.0)
+    term-ansicolor (1.0.7)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  aruba
+  prag_events!
+  rake (~> 0.9.2)
+  rdoc
+  ronn

data/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed 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.

data/README.md

@@ -0,0 +1,84 @@
+prag_events(1) -- Generate XML for your events to make Michael Swaine's life easy
+=================================================================================
+
+## SYNOPSIS
+
+`prag_events --you YOUR_NAME --talk TALK_TITLE --conference CONFERENCE --date DATE`
+
+`prag_events --who YOUR_NAME --what TALK_TITLE --where CONFERENCE --when DATE`
+
+## INSTALL
+
+    $ gem install prag_events
+
+## DESCRIPTION
+
+**prag_events** generates the XML format that Michael Swaine uses when creating the "events" section of the "PragPub" monthly magazine.  You simply run this program with the right inputs and copy the given XML into an email to Michael.
+
+This is probably not useful unless you are an author for the Pragmatic Programmers and on the private mailing list.
+
+## OPTIONS
+
+* `--conference CONFERENCE`, `--where CONFERENCE`:
+  Where the event will be held.  This is likely the conference name with some HTML that links
+  to the conference's website.
+
+* `--you YOUR_NAME`, `--who YOUR_NAME`:
+  Who is presenting, likely you.  This should contain a **very** brief bio (i.e. what book(s) you wrote) along with a 
+  link, in HTML
+
+* `--talk TALK_TITLE`, `--what TALK_TITLE`:
+  Title of the talk or presentation you are given at the conference.
+
+* `--date DATE`, `--when DATE`:
+  When the event takes place.  This can be simple, like "Nov 5"
+
+* `--version`:
+  Show help/version info
+
+## FILES
+
+Default options, namely your bio, can be placed in `~/.prag_events.rc` and should be a YAML file that looks like this:
+
+    ---
+    :who: 'Your name, and <a href="www.example.com">Some HTML</a> to your book.
+
+Note that we specifically do **not** grab your name from the environment because you really should include more than just your name here.
+
+## EXAMPLES
+
+My talk at OSCON 2012, using my bio in `~./prag_events.rc`
+
+    prag_events --where '<a href="http://www.oscon.com">OSCON 2012</a>' --when 'Jul 19' --what 'Threads and JRuby, the Simple Alternative to Evented'
+    <event>
+            <when>Jul 19</when>
+            <what>Threads and JRuby, the Simple Alternative to Evented</what>
+            <who>David Copeland, Author of <a href="http://pragprog.com/book/dccar">Build Awesome Command-Line Applications in Ruby</a></who>
+            <where><a href="http://www.oscon.com">OSCON 2012</a></where>
+    </event>
+
+## AUTHOR
+
+David Copeland, davec (at) naildrivin5.com
+
+## COPYRIGHT
+
+prag_events is copyright(c) 2012 by David Copeland, released under the Apache license.
+
+## SEE ALSO
+
+  * Source on github: https://github.com/davetron5000/prag_events
+
+
+[SYNOPSIS]: #SYNOPSIS "SYNOPSIS"
+[INSTALL]: #INSTALL "INSTALL"
+[DESCRIPTION]: #DESCRIPTION "DESCRIPTION"
+[OPTIONS]: #OPTIONS "OPTIONS"
+[FILES]: #FILES "FILES"
+[EXAMPLES]: #EXAMPLES "EXAMPLES"
+[AUTHOR]: #AUTHOR "AUTHOR"
+[COPYRIGHT]: #COPYRIGHT "COPYRIGHT"
+[SEE ALSO]: #SEE-ALSO "SEE ALSO"
+
+
+[prag_events(1)]: prag_events.1.html

data/Rakefile

@@ -0,0 +1,44 @@
+require 'bundler'
+require 'rake/clean'
+
+require 'rake/testtask'
+
+require 'cucumber'
+require 'cucumber/rake/task'
+gem 'rdoc' # we need the installed RDoc gem, not the system one
+require 'rdoc/task'
+
+include Rake::DSL
+
+Bundler::GemHelper.install_tasks
+
+
+Rake::TestTask.new do |t|
+  t.pattern = 'test/tc_*.rb'
+end
+
+
+CUKE_RESULTS = 'results.html'
+CLEAN << CUKE_RESULTS
+Cucumber::Rake::Task.new(:features) do |t|
+  t.cucumber_opts = "features --format html -o #{CUKE_RESULTS} --format pretty --no-source -x"
+  t.fork = false
+end
+
+Rake::RDocTask.new do |rd|
+  
+  rd.main = "README.rdoc"
+  
+  rd.rdoc_files.include("README.rdoc","lib/**/*.rb","bin/**/*")
+end
+
+task :man do 
+  sh 'ronn --markdown --roff man/prag_events.1.ronn'
+  mv 'man/prag_events.1.markdown','README.md'
+end
+
+CLEAN << 'man/hl.1'
+CLEAN << 'man/hl.1.html'
+
+task :default => [:test,:features,:man]
+

data/bin/prag_events

@@ -0,0 +1,40 @@
+#!/usr/bin/env ruby
+
+require 'optparse'
+require 'methadone'
+require 'prag_events'
+
+class App
+  include Methadone::Main
+  include Methadone::CLILogging
+
+  main do 
+    %w(when what where).each do |option|
+      help_now!("--#{option} is required") if String(options[option]) == ''
+    end
+    if String(options['who']) == ''
+      error = "--who is required if you don't have it in your config file
+You can default this by creating ~/.prag_events.rc to contain:
+---
+:who: Your Name, and other bio stuff here"
+      help_now!(error)
+    end
+      
+    puts "<event>"
+    %w(when what who where).each do |option|
+      puts "\t<#{option}>#{options[option]}</#{option}>"
+    end
+    puts "</event>"
+  end
+
+  on("--conference","--where CONFERENCE","Where the event will be held")
+  on("--you"       ,"--who YOUR_NAME"   ,"Who is presenting")
+  on("--talk"      ,"--what TALK_TITLE" ,"Title of the talk or presentation")
+  on("--date"      ,"--when DATE"       ,"When the event takes place")
+
+  version PragEvents::VERSION
+
+  defaults_from_config_file '.prag_events.rc'
+
+  go!
+end

data/features/prag_events.feature

@@ -0,0 +1,68 @@
+Feature: I can generate an event XML
+  In order to not have to remember the XML for events
+  I can run this app and generate the event XML
+  To make Michael Swaine's life a lot easier.
+
+  Scenario: General UI
+    When I get help for "prag_events"
+    Then the exit status should be 0
+    And the banner should be present
+    And the banner should document that this app takes options
+    And the following options should be documented:
+      |--version|
+      |--when|
+      |--what|
+      |--who|
+      |--where|
+    And the banner should document that this app takes no arguments
+
+  Scenario: when is required
+    When I run `prag_events --who 'foo' --where 'foo' --what 'foo'`
+    Then the exit status should not be 0
+    And the stderr should contain "--when is required"
+  Scenario: who is required
+    When I run `prag_events --when 'foo' --where 'foo' --what 'foo'`
+    Then the exit status should not be 0
+    And the stderr should contain "--who is required"
+    And the stderr should contain:
+    """
+    You can default this by creating ~/.prag_events.rc to contain:
+    ---
+    :who: Your Name, and other bio stuff here
+    """
+  Scenario: what is required
+    When I run `prag_events --who 'foo' --where 'foo' --when 'foo'`
+    Then the exit status should not be 0
+    And the stderr should contain "--what is required"
+  Scenario: where is required
+    When I run `prag_events --who 'foo' --when 'foo' --what 'foo'`
+    Then the exit status should not be 0
+    And the stderr should contain "--where is required"
+
+  Scenario: Generate XML Event
+    When I successfully run `prag_events --when 'Nov 5' --who 'David Copeland' --where 'Ruby Midwest' --what 'Make Awesome Command-Line Applications with Ruby'`
+    Then the output should contain exactly:
+    """
+    <event>
+    	<when>Nov 5</when>
+    	<what>Make Awesome Command-Line Applications with Ruby</what>
+    	<who>David Copeland</who>
+    	<where>Ruby Midwest</where>
+    </event>
+
+    """
+
+  Scenario: Generate XML Event using config file
+    Given a config file in my home directory containing "---\n:who: David Copeland, Author of Build Awesome Command-Line Applications in Ruby\n"
+    When I successfully run `prag_events --when 'Nov 5' --where 'Ruby Midwest' --what 'Make Awesome Command-Line Applications with Ruby'`
+    Then the output should contain exactly:
+    """
+    <event>
+    	<when>Nov 5</when>
+    	<what>Make Awesome Command-Line Applications with Ruby</what>
+    	<who>David Copeland, Author of Build Awesome Command-Line Applications in Ruby</who>
+    	<where>Ruby Midwest</where>
+    </event>
+
+    """
+

data/features/step_definitions/prag_events_steps.rb

@@ -0,0 +1,6 @@
+# Put your step definitions here
+Given /^a config file in my home directory containing "([^"]*)"$/ do |contents|
+  File.open(File.join(ENV['HOME'],'.prag_events.rc'),'w') do |file|
+    file.puts contents.gsub('\n',"\n")
+  end
+end

data/features/support/env.rb

@@ -0,0 +1,23 @@
+require 'aruba/cucumber'
+require 'methadone/cucumber'
+require 'fileutils'
+
+ENV['PATH'] = "#{File.expand_path(File.dirname(__FILE__) + '/../../bin')}#{File::PATH_SEPARATOR}#{ENV['PATH']}"
+LIB_DIR = File.join(File.expand_path(File.dirname(__FILE__)),'..','..','lib')
+
+Before do
+  # Using "announce" causes massive warnings on 1.9.2
+  @puts = true
+  @original_rubylib = ENV['RUBYLIB']
+  ENV['RUBYLIB'] = LIB_DIR + File::PATH_SEPARATOR + ENV['RUBYLIB'].to_s
+  @original_home = ENV['HOME']
+  @fake_home = File.join("/tmp","fakehome")
+  FileUtils.rm_rf @fake_home
+  FileUtils.mkdir @fake_home
+  ENV['HOME'] = @fake_home
+end
+
+After do
+  ENV['RUBYLIB'] = @original_rubylib
+  ENV['HOME'] = @original_home
+end

data/lib/prag_events/version.rb

@@ -0,0 +1,3 @@
+module PragEvents
+  VERSION = "0.0.1"
+end

data/lib/prag_events.rb

@@ -0,0 +1,5 @@
+require "prag_events/version"
+
+module PragEvents
+  # Your code goes here...
+end

data/man/prag_events.1

@@ -0,0 +1,99 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "PRAG_EVENTS" "1" "April 2012" "" ""
+.
+.SH "NAME"
+\fBprag_events\fR \- Generate XML for your events to make Michael Swaine\'s life easy
+.
+.SH "SYNOPSIS"
+\fBprag_events \-\-you YOUR_NAME \-\-talk TALK_TITLE \-\-conference CONFERENCE \-\-date DATE\fR
+.
+.P
+\fBprag_events \-\-who YOUR_NAME \-\-what TALK_TITLE \-\-where CONFERENCE \-\-when DATE\fR
+.
+.SH "INSTALL"
+.
+.nf
+
+$ gem install prag_events
+.
+.fi
+.
+.SH "DESCRIPTION"
+\fBprag_events\fR generates the XML format that Michael Swaine uses when creating the "events" section of the "PragPub" monthly magazine\. You simply run this program with the right inputs and copy the given XML into an email to Michael\.
+.
+.P
+This is probably not useful unless you are an author for the Pragmatic Programmers and on the private mailing list\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-\-conference CONFERENCE\fR, \fB\-\-where CONFERENCE\fR
+Where the event will be held\. This is likely the conference name with some HTML that links to the conference\'s website\.
+.
+.TP
+\fB\-\-you YOUR_NAME\fR, \fB\-\-who YOUR_NAME\fR
+Who is presenting, likely you\. This should contain a \fBvery\fR brief bio (i\.e\. what book(s) you wrote) along with a link, in HTML
+.
+.TP
+\fB\-\-talk TALK_TITLE\fR, \fB\-\-what TALK_TITLE\fR
+Title of the talk or presentation you are given at the conference\.
+.
+.TP
+\fB\-\-date DATE\fR, \fB\-\-when DATE\fR
+When the event takes place\. This can be simple, like "Nov 5"
+.
+.TP
+\fB\-\-version\fR
+Show help/version info
+.
+.SH "FILES"
+Default options, namely your bio, can be placed in \fB~/\.prag_events\.rc\fR and should be a YAML file that looks like this:
+.
+.IP "" 4
+.
+.nf
+
+\-\-\-
+:who: \'Your name, and <a href="www\.example\.com">Some HTML</a> to your book\.
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Note that we specifically do \fBnot\fR grab your name from the environment because you really should include more than just your name here\.
+.
+.SH "EXAMPLES"
+My talk at OSCON 2012, using my bio in \fB~\./prag_events\.rc\fR
+.
+.IP "" 4
+.
+.nf
+
+prag_events \-\-where \'<a href="http://www\.oscon\.com">OSCON 2012</a>\' \-\-when \'Jul 19\' \-\-what \'Threads and JRuby, the Simple Alternative to Evented\'
+<event>
+        <when>Jul 19</when>
+        <what>Threads and JRuby, the Simple Alternative to Evented</what>
+        <who>David Copeland, Author of <a href="http://pragprog\.com/book/dccar">Build Awesome Command\-Line Applications in Ruby</a></who>
+        <where><a href="http://www\.oscon\.com">OSCON 2012</a></where>
+</event>
+.
+.fi
+.
+.IP "" 0
+.
+.SH "AUTHOR"
+David Copeland, davec (at) naildrivin5\.com
+.
+.SH "COPYRIGHT"
+prag_events is copyright(c) 2012 by David Copeland, released under the Apache license\.
+.
+.SH "SEE ALSO"
+.
+.IP "\(bu" 4
+Source on github: https://github\.com/davetron5000/prag_events
+.
+.IP "" 0
+

data/man/prag_events.1.ronn

@@ -0,0 +1,70 @@
+prag_events(1) -- Generate XML for your events to make Michael Swaine's life easy
+=================================================================================
+
+## SYNOPSIS
+
+`prag_events --you YOUR_NAME --talk TALK_TITLE --conference CONFERENCE --date DATE`
+
+`prag_events --who YOUR_NAME --what TALK_TITLE --where CONFERENCE --when DATE`
+
+## INSTALL
+
+    $ gem install prag_events
+
+## DESCRIPTION
+
+**prag_events** generates the XML format that Michael Swaine uses when creating the "events" section of the "PragPub" monthly magazine.  You simply run this program with the right inputs and copy the given XML into an email to Michael.
+
+This is probably not useful unless you are an author for the Pragmatic Programmers and on the private mailing list.
+
+## OPTIONS
+
+* `--conference CONFERENCE`, `--where CONFERENCE`:
+  Where the event will be held.  This is likely the conference name with some HTML that links
+  to the conference's website.
+
+* `--you YOUR_NAME`, `--who YOUR_NAME`:
+  Who is presenting, likely you.  This should contain a **very** brief bio (i.e. what book(s) you wrote) along with a 
+  link, in HTML
+
+* `--talk TALK_TITLE`, `--what TALK_TITLE`:
+  Title of the talk or presentation you are given at the conference.
+
+* `--date DATE`, `--when DATE`:
+  When the event takes place.  This can be simple, like "Nov 5"
+
+* `--version`:
+  Show help/version info
+
+## FILES
+
+Default options, namely your bio, can be placed in `~/.prag_events.rc` and should be a YAML file that looks like this:
+
+    ---
+    :who: 'Your name, and <a href="www.example.com">Some HTML</a> to your book.
+
+Note that we specifically do **not** grab your name from the environment because you really should include more than just your name here.
+
+## EXAMPLES
+
+My talk at OSCON 2012, using my bio in `~./prag_events.rc`
+
+    prag_events --where '<a href="http://www.oscon.com">OSCON 2012</a>' --when 'Jul 19' --what 'Threads and JRuby, the Simple Alternative to Evented'
+    <event>
+            <when>Jul 19</when>
+            <what>Threads and JRuby, the Simple Alternative to Evented</what>
+            <who>David Copeland, Author of <a href="http://pragprog.com/book/dccar">Build Awesome Command-Line Applications in Ruby</a></who>
+            <where><a href="http://www.oscon.com">OSCON 2012</a></where>
+    </event>
+
+## AUTHOR
+
+David Copeland, davec (at) naildrivin5.com
+
+## COPYRIGHT
+
+prag_events is copyright(c) 2012 by David Copeland, released under the Apache license.
+
+## SEE ALSO
+
+  * Source on github: https://github.com/davetron5000/prag_events

data/prag_events.gemspec

@@ -0,0 +1,27 @@
+# -*- encoding: utf-8 -*-
+$:.push File.expand_path("../lib", __FILE__)
+require "prag_events/version"
+
+Gem::Specification.new do |s|
+  s.name        = "prag_events"
+  s.version     = PragEvents::VERSION
+  s.authors     = ["Dave Copeland"]
+  s.email       = ["davetron5000@gmail.com"]
+  s.homepage    = "https://github.com/davetron5000/prag_events"
+  s.summary     = %q{Generate XML for your events to make Michael Swaine's life easy when he creates PragPub each month}
+  s.description = %q{prag_events generates the XML format that Michael Swaine uses when creating the "events" section of the "PragPub" monthly magazine.  You simply run this program with the right inputs and copy the given XML into an email to Michael.}
+
+  s.rubyforge_project = "prag_events"
+
+  s.files         = `git ls-files`.split("\n")
+  s.test_files    = `git ls-files -- {test,spec,features}/*`.split("\n")
+  s.executables   = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
+  s.require_paths = ["lib"]
+
+  s.add_development_dependency('rdoc')
+  s.add_development_dependency('aruba')
+  s.add_development_dependency('rake','~> 0.9.2')
+  s.add_development_dependency('ronn')
+  s.add_dependency('methadone', '~>1.0.0')
+  s.add_dependency('gem-man')
+end

data/test/tc_something.rb

@@ -0,0 +1,7 @@
+require 'test/unit'
+
+class TestSomething < Test::Unit::TestCase
+  def test_truth
+    assert true
+  end
+end

metadata

@@ -0,0 +1,136 @@
+--- !ruby/object:Gem::Specification
+name: prag_events
+version: !ruby/object:Gem::Version
+  version: 0.0.1
+  prerelease: 
+platform: ruby
+authors:
+- Dave Copeland
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2012-04-22 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: rdoc
+  requirement: &70244329415460 !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: *70244329415460
+- !ruby/object:Gem::Dependency
+  name: aruba
+  requirement: &70244329415000 !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: *70244329415000
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: &70244329414480 !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: 0.9.2
+  type: :development
+  prerelease: false
+  version_requirements: *70244329414480
+- !ruby/object:Gem::Dependency
+  name: ronn
+  requirement: &70244329414040 !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: *70244329414040
+- !ruby/object:Gem::Dependency
+  name: methadone
+  requirement: &70244329413440 !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: 1.0.0
+  type: :runtime
+  prerelease: false
+  version_requirements: *70244329413440
+- !ruby/object:Gem::Dependency
+  name: gem-man
+  requirement: &70244329412820 !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: *70244329412820
+description: prag_events generates the XML format that Michael Swaine uses when creating
+  the "events" section of the "PragPub" monthly magazine.  You simply run this program
+  with the right inputs and copy the given XML into an email to Michael.
+email:
+- davetron5000@gmail.com
+executables:
+- prag_events
+extensions: []
+extra_rdoc_files: []
+files:
+- .gitignore
+- .rvmrc
+- Gemfile
+- Gemfile.lock
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/prag_events
+- features/prag_events.feature
+- features/step_definitions/prag_events_steps.rb
+- features/support/env.rb
+- lib/prag_events.rb
+- lib/prag_events/version.rb
+- man/prag_events.1
+- man/prag_events.1.ronn
+- prag_events.gemspec
+- test/tc_something.rb
+homepage: https://github.com/davetron5000/prag_events
+licenses: []
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: prag_events
+rubygems_version: 1.8.10
+signing_key: 
+specification_version: 3
+summary: Generate XML for your events to make Michael Swaine's life easy when he creates
+  PragPub each month
+test_files:
+- features/prag_events.feature
+- features/step_definitions/prag_events_steps.rb
+- features/support/env.rb
+- test/tc_something.rb