Remaster Gemspec and Gemfile

- align with rails 5
- remove httpclient from gemfile as it's in the gemspec
- Fix authors, summary and desc

Gemfile

@@ -1,14 +1,13 @@
-source "http://rubygems.org"
+source "https://rubygems.org"
+git_source(:github) { |repo| "https://github.com/#{repo}.git" }
 
 # Declare your gem's dependencies in floristry.gemspec.
 # Bundler will treat runtime dependencies like base dependencies, and
 # development dependencies will be added by default to the :development group.
 gemspec
 
-gem 'httpclient'
-
+# All this is used by the dummy app used for test/specs
 group :test do
-  # All this is used by the dummy app used for test/specs
   gem 'simple_form', '~> 3.1'
   gem 'statesman', '~> 2.0.1'
   gem 'statesman-events', '~> 0.0.1'
@@ -22,5 +21,5 @@ end
 # Git. Remember to move these dependencies to your gemspec before releasing
 # your gem to rubygems.org.
 
-# To use debugger
-# gem 'ruby-debug'
+# To use a debugger
+# gem 'byebug', group: [:development, :test]

floristry.gemspec

@@ -1,4 +1,4 @@
-$:.push File.expand_path('../lib', __FILE__)
+$:.push File.expand_path("lib", __dir__)
 
 # Maintain your gem's version:
 require 'floristry/version'
@@ -7,22 +7,23 @@ require 'floristry/version'
 Gem::Specification.new do |s|
   s.name        = 'floristry'
   s.version     = Floristry::VERSION
-  s.authors     = ['Danny Fullerton']
-  s.email       = ['[email protected]']
-  s.homepage    = 'https://github.com/northox/floristry'
-  s.summary     = %q{What ActiveRecord is to database but for Flor workflow engine.}
-  s.description = %q{Represent complete Flor workflows using standard rails facilities, e.g. render, partials, etc.}
+  s.authors     = ['Danny Fullerton', 'Jean-Francois Rioux']
+  s.email       = ['[email protected]', '[email protected]']
+  s.homepage    = 'https://github.com/mantor/floristry'
+  s.summary     = %q{Visualize and interact with Flor's workflow engine through Rails facilities.}
+  s.description = %q{Floristry brings the Rails web framework as a UI to Flor's workflows engine. You can represent workflows using standard Rails facilities (e.g. partials, helpers) and interact with tasks just like any other form using ActiveRecord. Think of it like Facebook's timeline but instead of being linear, the backend is a workflow engine - actually a full workflow programming language with concurrence, loops and conditions.}
+  s.license	= "GPL2"
 
-  s.files = Dir["{app,config,lib}/**/*"] + %w(LICENSE Rakefile README.md)
+  s.files = Dir["{app,config,db,lib}/**/*"] + %w(LICENSE Rakefile README.md)
   s.test_files = Dir["spec/**/*"]
 
   s.add_runtime_dependency 'rails', '>= 4.2.8'
   s.add_runtime_dependency 'thor', '0.19.1'
-  s.add_runtime_dependency 'protected_attributes', '>= 1.0.7' # TODO switch to strong_parameters
+  s.add_runtime_dependency 'protected_attributes', '>= 1.0.7'
   s.add_runtime_dependency 'active_attr'
   s.add_runtime_dependency 'flor'
   s.add_runtime_dependency 'httpclient'
 
   s.add_development_dependency 'rspec-rails', '~> 3'
   s.add_development_dependency 'rspec-activemodel-mocks'
-end
+end