almanack 1.1.0 → 1.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 36561f3e881264748d47b04e9de372d25905b2c53709bda4a530ea3cf5809ea4
-  data.tar.gz: 74e534189d15e9e8f39955651b2c08919dd2a14238f0852d5883a71cee7921c8
+  metadata.gz: 2e9c8e19af0ef162e6f9e3e154d37ebc9ec06d94c90bee6e350c2c77fbe558a8
+  data.tar.gz: 18beec7707391e14788dbd5e3e64266a9402a6b45e34c92a98568441be75754b
 SHA512:
-  metadata.gz: b84d3617993a8a8db288b9f50b45e19ccb5579dedc0106ff88fa9f7d3ccaff59ee2bd9177b54aed43b8e5c2ecf41dab88b72b85b4148560cd7661bffdce2fd7d
-  data.tar.gz: 3936b45f7086f3a91efba12742f477b85184e0bd9547a35b3707204b36125313b2789d96949bc65514655edb332fd2010f57297d2799d06c2fd1d3c2479b8d54
+  metadata.gz: a8e0ba960c3f2f2fa050ea6c75bd425cd8c64bd424ab6e07caa4cb1afd1889f65c2fdc5e1cf587ba41077d2d6f6d551fbabb44bbdb28021492799d63f0326ca2
+  data.tar.gz: 318e59d914fd4861a02e3575f596bac00d8e575f0742ea39033a4f10d3a5b0f82c39f852c7f7f68307368d669337e1a495d925b5ba87e9dc8a0e5780c222fcf1

data/.gitignore

@@ -1,18 +1,13 @@
-*.gem
-*.rbc
-.bundle
-.config
-.yardoc
-Gemfile.lock
-InstalledFiles
-_yardoc
-coverage
-doc/
-lib/bundler/man
-pkg
-rdoc
-spec/reports
-test/tmp
-test/version_tmp
-tmp
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+
 .sass-cache/
+
+# rspec failure tracking
+.rspec_status

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.travis.yml

@@ -1,9 +1,11 @@
+sudo: false
 language: ruby
 cache: bundler
 rvm:
 - 2.4.5
 - 2.5.3
 - 2.6.2
+before_install: gem install bundler -v 2.0.1
 addons:
   code_climate:
     repo_token:

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at aupajo@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

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

data/Gemfile.lock

@@ -0,0 +1,123 @@
+PATH
+  remote: .
+  specs:
+    almanack (1.1.1)
+      activesupport
+      addressable
+      faraday
+      faraday_middleware
+      rack-contrib
+      ri_cal
+      sass
+      sinatra
+      sinatra-contrib
+      thor
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    activesupport (5.2.3)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (>= 0.7, < 2)
+      minitest (~> 5.1)
+      tzinfo (~> 1.1)
+    addressable (2.6.0)
+      public_suffix (>= 2.0.2, < 4.0)
+    backports (3.14.0)
+    coderay (1.1.2)
+    concurrent-ruby (1.1.5)
+    crack (0.4.3)
+      safe_yaml (~> 1.0.0)
+    diff-lcs (1.3)
+    faraday (0.15.4)
+      multipart-post (>= 1.2, < 3)
+    faraday_middleware (0.13.1)
+      faraday (>= 0.7.4, < 1.0)
+    ffi (1.10.0)
+    hashdiff (0.3.8)
+    i18n (1.6.0)
+      concurrent-ruby (~> 1.0)
+    method_source (0.9.2)
+    mini_portile2 (2.4.0)
+    minitest (5.11.3)
+    multi_json (1.13.1)
+    multipart-post (2.1.0)
+    mustermann (1.0.3)
+    nokogiri (1.10.2)
+      mini_portile2 (~> 2.4.0)
+    pry (0.12.2)
+      coderay (~> 1.1.0)
+      method_source (~> 0.9.0)
+    public_suffix (3.0.3)
+    rack (2.0.7)
+    rack-contrib (2.1.0)
+      rack (~> 2.0)
+    rack-protection (2.0.5)
+      rack
+    rack-test (1.1.0)
+      rack (>= 1.0, < 3)
+    rake (10.5.0)
+    rb-fsevent (0.10.3)
+    rb-inotify (0.10.0)
+      ffi (~> 1.0)
+    ri_cal (0.8.8)
+    rspec (3.8.0)
+      rspec-core (~> 3.8.0)
+      rspec-expectations (~> 3.8.0)
+      rspec-mocks (~> 3.8.0)
+    rspec-core (3.8.0)
+      rspec-support (~> 3.8.0)
+    rspec-expectations (3.8.2)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-mocks (3.8.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-support (3.8.0)
+    safe_yaml (1.0.5)
+    sass (3.7.4)
+      sass-listen (~> 4.0.0)
+    sass-listen (4.0.0)
+      rb-fsevent (~> 0.9, >= 0.9.4)
+      rb-inotify (~> 0.9, >= 0.9.7)
+    sinatra (2.0.5)
+      mustermann (~> 1.0)
+      rack (~> 2.0)
+      rack-protection (= 2.0.5)
+      tilt (~> 2.0)
+    sinatra-contrib (2.0.5)
+      backports (>= 2.8.2)
+      multi_json
+      mustermann (~> 1.0)
+      rack-protection (= 2.0.5)
+      sinatra (= 2.0.5)
+      tilt (>= 1.3, < 3)
+    thor (0.20.3)
+    thread_safe (0.3.6)
+    tilt (2.0.9)
+    timecop (0.9.1)
+    tzinfo (1.2.5)
+      thread_safe (~> 0.1)
+    vcr (4.0.0)
+    webmock (3.5.1)
+      addressable (>= 2.3.6)
+      crack (>= 0.3.2)
+      hashdiff
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  almanack!
+  bundler (~> 2.0)
+  nokogiri
+  pry
+  rack-test
+  rake (~> 10.0)
+  rspec (~> 3.0)
+  timecop
+  vcr
+  webmock
+
+BUNDLED WITH
+   2.0.1

data/LICENSE.txt

@@ -1,22 +1,21 @@
-Copyright (c) 2014 Pete Nicholls
+The MIT License (MIT)
 
-MIT License
+Copyright (c) 2019 Pete Nicholls
 
-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:
+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 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.
+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.

data/README.md

@@ -27,9 +27,19 @@ See a demo running at [http://christchurch.events.geek.nz](http://christchurch.e
 
 ## Installation
 
-Run the following command:
+Almanack is cryptographically signed. You can install it like any other gem, but you can also do so in a way that verifies the gem hasn't been tampered with.
 
-    gem install almanack
+Add my public key (if you haven’t already) as a trusted certificate:
+
+    gem cert --add <(curl -Ls https://raw.github.com/aupajo/almanack/master/certs/aupajo.pem)
+
+Then install the gem:
+
+    gem install almanack -P HighSecurity
+
+All my dependencies are cryptographically signed, so you can use the `HighSecurity` option. [Read more](http://docs.seattlerb.org/rubygems/Gem/Security.html).
+
+Checksums for released gems can be found in `checksums`.
 
 ## Creating a calendar
 
@@ -87,7 +97,7 @@ is already initialized for you when you run `almanack new`):
     git add .
     git commit -m "My awesome calendar"
 
-With the [Heroku Toolbelt](https://toolbelt.heroku.com) installed:
+With the [Heroku CLI](https://devcenter.heroku.com/articles/heroku-cli) installed:
 
     almanack deploy my-awesome-calendar
 
@@ -99,8 +109,16 @@ Subsequent commits can be deployed with just:
 
 ## Contributing
 
+### Getting started
+
+1. Clone the repository
+2. Run `bin/setup`
+3. Run `bin/test`
+
+### Sending patches
+
 1. Fork it ( http://github.com/Aupajo/almanack/fork )
 2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
+3. Commit your changes (`git commit -am 'Add some feature'`) with tests
 4. Push to the branch (`git push origin my-new-feature`)
 5. Create new Pull Request

data/Rakefile

@@ -4,3 +4,19 @@ require "rspec/core/rake_task"
 RSpec::Core::RakeTask.new(:spec)
 
 task :default => :spec
+
+task :checksum do
+  require 'digest/sha2'
+  built_gem_path = Dir["pkg/almanack-*.gem"].sort_by {|f| File.mtime(f) }.last
+  checksum = Digest::SHA512.new.hexdigest(File.read(built_gem_path))
+  gem_name = File.basename(built_gem_path)
+  checksum_path = "checksum/#{gem_name}.sha512"
+  File.write(checksum_path, checksum)
+  puts "Checksum #{checksum} written to #{checksum_path}"
+  system("git add #{checksum_path}")
+  puts "Please commit this file"
+end
+
+Rake::Task['release'].enhance do
+  Rake::Task['checksum'].invoke
+end

data/almanack.gemspec

@@ -1,20 +1,29 @@
 # coding: utf-8
-lib = File.expand_path('../lib', __FILE__)
+lib = File.expand_path("../lib", __FILE__)
 $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
-require 'almanack/version'
+require "almanack/version"
 
 Gem::Specification.new do |spec|
   spec.name          = "almanack"
   spec.version       = Almanack::VERSION
   spec.authors       = ["Pete Nicholls"]
-  spec.email         = ["pete@metanation.com"]
+  spec.email         = ["aupajo@gmail.com"]
   spec.summary       = %q{Combined events calendar for Google Calendar, iCal, Meetup.com and friends.}
   spec.homepage      = Almanack::HOMEPAGE
   spec.license       = "MIT"
 
-  spec.files         = `git ls-files -z`.split("\x0")
-  spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
-  spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
+  # Gem signing
+  spec.cert_chain    = ['certs/aupajo.pem']
+  spec.signing_key = File.expand_path("~/.ssh/gem-private_key.pem") if $0 =~ /gem\z/
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files         = Dir.chdir(File.expand_path('..', __FILE__)) do
+    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
+  end
+
+  spec.bindir        = "exe"
+  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.require_paths = ["lib"]
 
   spec.add_dependency "sinatra"
@@ -28,9 +37,10 @@ Gem::Specification.new do |spec|
   spec.add_dependency "rack-contrib"
   spec.add_dependency "activesupport"
 
+  spec.add_development_dependency "bundler", "~> 2.0"
   spec.add_development_dependency "pry"
-  spec.add_development_dependency "rake"
-  spec.add_development_dependency "rspec"
+  spec.add_development_dependency "rake", "~> 10.0"
+  spec.add_development_dependency "rspec", "~> 3.0"
   spec.add_development_dependency "rack-test"
   spec.add_development_dependency "webmock"
   spec.add_development_dependency "vcr"

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "almanack"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/bin/test

@@ -0,0 +1,2 @@
+#!/usr/bin/env bash
+exec bundle exec rspec "$@"

data/certs/aupajo.pem

@@ -0,0 +1,25 @@
+-----BEGIN CERTIFICATE-----
+MIIEMDCCApigAwIBAgIBATANBgkqhkiG9w0BAQsFADAhMR8wHQYDVQQDDBZhdXBh
+am8vREM9Z21haWwvREM9Y29tMB4XDTE5MDUxMDIzNTU1MFoXDTIwMDUwOTIzNTU1
+MFowITEfMB0GA1UEAwwWYXVwYWpvL0RDPWdtYWlsL0RDPWNvbTCCAaIwDQYJKoZI
+hvcNAQEBBQADggGPADCCAYoCggGBALifHcsBTFzJr4CcSnTsc3X2hjTYHi3CEJYY
+DZmcF4CyWYTzc1yw6D8JmekoZHphceFBaCmWDQdRap4yXuqT3RgW+EotBfkoWSY3
+fp9KmjpvDK1g0uvt9jAUzAHVtWNOwwwSN6cs/L8/AxuvxMC1VJ798T82eruM39SB
+Uq24isPXm8RMEZsChgRlksr4ZwbP7cTLTqecG4XTd+4kVXEQ5xIUrGxSSOfasckB
+I5peEg8PP3DAwMIfh3bM6jyWu5f/WO8lwVOjqQIbsD8llxI2u3vsOwigXkfoe6bd
+3zAsmrmuoqv5WYhgkzz3Te55/Mp1grdDnHv3wWGdlU+1u5K9l54NnlZvMlRbKp+v
+Hjta3M1sCnbNGH25Lasd3cxHd2S5Pf7Gx5vqyAUtDDqRS6lPNHqCVHm93kiR9Vs8
+hI8a33sPpQlAxjpDSdbRyenbZVGDoMh7ckj5Jecl8OWpNtjbiuh8o3wcFMwuq2vg
+pczlifnwXj/mFQrZ8JOVc7GM6I6D9QIDAQABo3MwcTAJBgNVHRMEAjAAMAsGA1Ud
+DwQEAwIEsDAdBgNVHQ4EFgQUKjXKGxvH9cq/vGtrslK9I/Ym/GcwGwYDVR0RBBQw
+EoEQYXVwYWpvQGdtYWlsLmNvbTAbBgNVHRIEFDASgRBhdXBham9AZ21haWwuY29t
+MA0GCSqGSIb3DQEBCwUAA4IBgQB4zcSM0JA0El9w0T6/DHs0qtqqrzMw8vgde4WF
+N3lYtLtOt9HHmbOfBuUSdZVcONDJ59S6Q6xkortWZob7LER/KZw2IBL07HrlvMyP
+2ZivUYvBJqK+osMH2/Efuu/53N1rRRvN7AH4Q+ghFtRESJ3+7yXbvc56dLLnLcxJ
+1mwWlpcraXFnhCyHZxqJWIqumnqhQ9QLyHL99oXJyxp1fyBBUW2/LqVg1bRZeXW8
+HM3NveDgfHtxsN7/xokEqx9dJZLNIquuh/Mkf/feIfaIbd5yvMg5jI0uFaiyGBAn
+5oyawSfYQPqmfb+Kek8nEjX90Ul+HHpwHGCe0OfQ9Bo5lwRW5i9ph9iHwzUCIO7s
+acolbc/fvwdOW4ly/TKaL/1YW/eS3Oi9Yn4RSYTsxSLfVLt2+M3A8Hk1vQFMW/23
+dZpUW6Gfv2VtOtiN0Q3PjLK+TRjHtqYBjbxa771Msax3xs40e2cSVU/dO+OY5NmR
+a61dVmZ1PIJiY+jyzJSb8ohHVx4=
+-----END CERTIFICATE-----

data/lib/almanack/version.rb

@@ -1,6 +1,6 @@
 module Almanack
   CODENAME = "Garlick"
-  VERSION  = "1.1.0"
+  VERSION  = "1.1.1"
   HOMEPAGE = "https://github.com/Aupajo/almanack"
   ISSUES   = "https://github.com/Aupajo/almanack/issues"
 end