how_is 8.0.0 → 9.0.0

data/lib/how_is/report/pdf.rb

@@ -1,78 +1,78 @@
-require 'prawn'
-require 'how_is/chart'
-
-module HowIs
-  class PdfReport < BaseReport
-    def format
-      :pdf
-    end
-
-    attr_accessor :pdf
-
-    def title(_text)
-      pdf.pad_bottom(10) {
-        pdf.text(_text, size: 25)
-      }
-    end
-
-    def header(_text)
-      pdf.pad_top(15) {
-        pdf.pad_bottom(3) {
-          pdf.text _text, size: 20
-        }
-      }
-    end
-
-    def link(_text, url)
-      # TODO: Actually have links.
-      _text
-    end
-
-    def horizontal_bar_graph(data)
-      filename_base = "./issues-per-label"
-      dat_file = filename_base + '.dat'
-      png_file = filename_base + '.png'
-
-      File.open(dat_file, 'w') do |f|
-        data.each_with_index do |(label, n, link), i|
-          f.puts "#{i}\t#{n}\t\"#{label}\""
-        end
-      end
-
-      Chart.gnuplot(label_font_size: 10,
-                    font_size: 16,
-                    data_file: dat_file,
-                    png_file: png_file)
-     Chart.rotate(90, png_file)
-
-      pdf.image png_file
-    end
-
-    def text(_text)
-      pdf.text _text
-    end
-
-    # Prawn (afaict) doesn't let you export to a binary blob.
-    # So export to a file, then read the file.
-    def export(&block)
-      # TODO: Use actual temporary file.
-      export!('temp.pdf', &block)
-
-      open('temp.pdf').read
-    end
-
-    def export!(file, &block)
-      _self = self
-
-      Prawn::Document.generate(file) do |pdf|
-        _self.pdf = pdf
-
-        pdf.font("Helvetica")
-
-        pdf.span(450, position: :center) do
-          _self.instance_eval(&block)
-        end
-      end
-    end
-  end
-end
+require 'prawn'
+require 'how_is/chart'
+
+module HowIs
+  class PdfReport < BaseReport
+    def format
+      :pdf
+    end
+
+    attr_accessor :pdf
+
+    def title(_text)
+      pdf.pad_bottom(10) {
+        pdf.text(_text, size: 25)
+      }
+    end
+
+    def header(_text)
+      pdf.pad_top(15) {
+        pdf.pad_bottom(3) {
+          pdf.text _text, size: 20
+        }
+      }
+    end
+
+    def link(_text, url)
+      # TODO: Actually have links.
+      _text
+    end
+
+    def horizontal_bar_graph(data)
+      filename_base = "./issues-per-label"
+      dat_file = filename_base + '.dat'
+      png_file = filename_base + '.png'
+
+      File.open(dat_file, 'w') do |f|
+        data.each_with_index do |(label, n, link), i|
+          f.puts "#{i}\t#{n}\t\"#{label}\""
+        end
+      end
+
+      Chart.gnuplot(label_font_size: 10,
+                    font_size: 16,
+                    data_file: dat_file,
+                    png_file: png_file)
+     Chart.rotate(90, png_file)
+
+      pdf.image png_file
+    end
+
+    def text(_text)
+      pdf.text _text
+    end
+
+    # Prawn (afaict) doesn't let you export to a binary blob.
+    # So export to a file, then read the file.
+    def export(&block)
+      # TODO: Use actual temporary file.
+      export!('temp.pdf', &block)
+
+      open('temp.pdf').read
+    end
+
+    def export!(file, &block)
+      _self = self
+
+      Prawn::Document.generate(file) do |pdf|
+        _self.pdf = pdf
+
+        pdf.font("Helvetica")
+
+        pdf.span(450, position: :center) do
+          _self.instance_eval(&block)
+        end
+      end
+    end
+  end
+end

data/lib/how_is/version.rb

@@ -1,3 +1,3 @@
-module HowIs
-  VERSION = "8.0.0"
-end
+module HowIs
+  VERSION = "9.0.0"
+end

data/roadmap.markdown

@@ -1,49 +1,49 @@
-# How_is Roadmap
-
-A brief overview of how_is' goals and current status.
-
-## Goals
-
-How_is is intended to be usable both as a standalone program and a as library, with reports generated as either files or Ruby Strings. Initial export formats supported will be JSON and PDF, with HTML to follow later. When exporting a report, you can use the data from a previous JSON export to avoid making network requests.
-
-Metrics will be divided into two categories during implementation: Simple and Complex. Simple ones will be implementable using only the information gathered from one API call to the issue tracker. Complex metrics require things like cloning the repository or making multiple API requests.
-
-Simple metrics will include:
-
-* number of open Issues,
-* number of open Pull Requests,
-* number of issues associated with each label, as well as the number associated with no label,
-* average Issue age,
-* average Pull Request age,
-* date oldest Issue was opened,
-* date oldest Pull Request was opened.
-
-Complex metrics will include:
-
-* code churn (code change over time),
-* average response time by a team member in the past week,
-* graph of average response time by a team member per week.
-
-These metrics serve to either quantify the state of the repository, quantify the state of the codebase itself, or both. By quantifying the state of the issue tracker and codebase, it will hopefully be easier to decide what needs to be done.
-
-Once HTML export is implemented, a web service is planned to be created which tracks these metrics over time for the RubyGems repository. The details of this have not been fully fleshed out, but I am attempting to design the library in such a way to allow the flexibility required to do this.
-
-## Current Status
-
-As of June 15th 2016, how_is supports exports to JSON or PDF, but not HTML. For JSON and PDF, all Simple metrics have been implemented in some form, although they made need some polish ([#8](https://github.com/duckinator/how_is/issues/8)). HTML export is not implemented, and no Complex metrics are implemented. Tracking the number of issues without labels has also not been implemented ([#1](https://github.com/duckinator/how_is/issues/1)).
-
-Exporting to Ruby Strings that contain valid JSON, PDF, or HTML documents has also not been implemented ([#7](https://github.com/duckinator/how_is/issues/7)).
-
-Authentication is not being used, but will likely be necessary, as it would raise the API rate limits ([#6](https://github.com/duckinator/how_is/issues/6)).
-
-### Requirements for 1.0
-
-Once JSON and PDF exports are fully implemented ([#1](https://github.com/duckinator/how_is/issues/1)) and the README has a proper list of the metrics covered, v1.0 will be released.
-
-### Requirements for 2.0
-
-Once everything required for v1.0 as well as exporting to Strings ([#7](https://github.com/duckinator/how_is/issues/7)) has been implemented, v2.0 will be released.
-
-### Other changes
-
-All other changes ([#8](https://github.com/duckinator/how_is/issues/8), [#6](https://github.com/duckinator/how_is/issues/6), any changes without an accompanying issue) will be grouped together in either the next major release, or a separate minor release.
+# How_is Roadmap
+
+A brief overview of how_is' goals and current status.
+
+## Goals
+
+How_is is intended to be usable both as a standalone program and a as library, with reports generated as either files or Ruby Strings. Initial export formats supported will be JSON and PDF, with HTML to follow later. When exporting a report, you can use the data from a previous JSON export to avoid making network requests.
+
+Metrics will be divided into two categories during implementation: Simple and Complex. Simple ones will be implementable using only the information gathered from one API call to the issue tracker. Complex metrics require things like cloning the repository or making multiple API requests.
+
+Simple metrics will include:
+
+* number of open Issues,
+* number of open Pull Requests,
+* number of issues associated with each label, as well as the number associated with no label,
+* average Issue age,
+* average Pull Request age,
+* date oldest Issue was opened,
+* date oldest Pull Request was opened.
+
+Complex metrics will include:
+
+* code churn (code change over time),
+* average response time by a team member in the past week,
+* graph of average response time by a team member per week.
+
+These metrics serve to either quantify the state of the repository, quantify the state of the codebase itself, or both. By quantifying the state of the issue tracker and codebase, it will hopefully be easier to decide what needs to be done.
+
+Once HTML export is implemented, a web service is planned to be created which tracks these metrics over time for the RubyGems repository. The details of this have not been fully fleshed out, but I am attempting to design the library in such a way to allow the flexibility required to do this.
+
+## Current Status
+
+As of June 15th 2016, how_is supports exports to JSON or PDF, but not HTML. For JSON and PDF, all Simple metrics have been implemented in some form, although they made need some polish ([#8](https://github.com/duckinator/how_is/issues/8)). HTML export is not implemented, and no Complex metrics are implemented. Tracking the number of issues without labels has also not been implemented ([#1](https://github.com/duckinator/how_is/issues/1)).
+
+Exporting to Ruby Strings that contain valid JSON, PDF, or HTML documents has also not been implemented ([#7](https://github.com/duckinator/how_is/issues/7)).
+
+Authentication is not being used, but will likely be necessary, as it would raise the API rate limits ([#6](https://github.com/duckinator/how_is/issues/6)).
+
+### Requirements for 1.0
+
+Once JSON and PDF exports are fully implemented ([#1](https://github.com/duckinator/how_is/issues/1)) and the README has a proper list of the metrics covered, v1.0 will be released.
+
+### Requirements for 2.0
+
+Once everything required for v1.0 as well as exporting to Strings ([#7](https://github.com/duckinator/how_is/issues/7)) has been implemented, v2.0 will be released.
+
+### Other changes
+
+All other changes ([#8](https://github.com/duckinator/how_is/issues/8), [#6](https://github.com/duckinator/how_is/issues/6), any changes without an accompanying issue) will be grouped together in either the next major release, or a separate minor release.

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: how_is
 version: !ruby/object:Gem::Version
-  version: 8.0.0
+  version: 9.0.0
 platform: ruby
 authors:
 - Ellen Marie Dash
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2016-07-28 00:00:00.000000000 Z
+date: 2016-08-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: github_api
@@ -38,6 +38,20 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
+- !ruby/object:Gem::Dependency
+  name: slop
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: prawn
   requirement: !ruby/object:Gem::Requirement
@@ -86,14 +100,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 4.0.1
+        version: 5.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 4.0.1
+        version: 5.0.0
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
@@ -160,6 +174,7 @@ extra_rdoc_files: []
 files:
 - ".gitignore"
 - ".rspec"
+- ".rspec-ignore-tags"
 - ".travis.yml"
 - CODE_OF_CONDUCT.md
 - Gemfile
@@ -175,6 +190,7 @@ files:
 - lib/how_is/analyzer.rb
 - lib/how_is/chart.rb
 - lib/how_is/cli.rb
+- lib/how_is/cli/parser.rb
 - lib/how_is/fetcher.rb
 - lib/how_is/pulse.rb
 - lib/how_is/report.rb
@@ -203,9 +219,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.6.3
+rubygems_version: 2.5.1
 signing_key: 
 specification_version: 4
 summary: Quantify the health of a GitHub repository is.
 test_files: []
-has_rdoc: