useless-wait-list 0.0.1 → 0.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: fc84a97d0172c93a1555fd35edb5607cca70ad01
-  data.tar.gz: 7c39cee2a9e741b6e54f16ea7c0f0d9539a8f437
+  metadata.gz: acf3ad7bf2fd27f864f7ec9b3ab551c878bed013
+  data.tar.gz: e99e8e1c64ba5b4f2ae0988966657f3c6abb26aa
 SHA512:
-  metadata.gz: ed3ad1512718a839c7233b5ffa2f25cb32346048b70b7785152cdad94202cd69e5f2729a0d09a77d660feed1e5b6b97a1a3dd635ad6f4ac2f2d026386af92516
-  data.tar.gz: 99f04f0d33a9bb88d2f3789b139d5b745ef5e824a1a136b22719b40e5cfef4db29ff3d5629de98c65f606e031c42804dc662aaa3b5c8376de7c2464c50379261
+  metadata.gz: 2787c9e01b6bb479429a8d379a07efff3bbb79d6cbafae815a51df274bfae50ba82974693d2f6e7a8cc7b07ffdf643099c4933f09b10a68046fa0dae02a6164f
+  data.tar.gz: a39141772f80efc93a58bec013e7dc004470a2adba18a6252ad79eaec4a05871922bee92a4b5c4b3d1c4c697f9142e919c6d0c72f8a69bde7124ab7bb368657e

data/lib/useless/wait_list.rb

@@ -4,20 +4,64 @@ require 'useless/doc/server/sinatra'
 
 module Useless
   class WaitList < Sinatra::Base
-    require 'useless/wait_list/version'
-
     register Useless::Doc::Server::Sinatra
 
     doc 'Wait List' do
       url 'http://wait-list.useless.io'
 
+      concept 'Chris Nace'
+      specification 'In Progress', 'Kevin Hyland'
+      implementation 'Pending', 'Kevin Hyland'
+
       description <<-DESC
-        The Wait List API is an idealized specification of how a restaurant
-        should be able to manage its wait list. The big idea is that
-        potential patrons should be able to remotely add themselves to the
-        wait list.
+        It is becoming increasingly common for restaurants, especially popular
+        ones, to not accept reservations. Instead, they choose to maintain a
+        first-come, first-served wait list.
+
+        Algorithmically, this makes a lot of sense. The wait list can be
+        modeled as a set of queues, one per available table size. The
+        reservation, however, requires some scheduling algorithm. Queues, in
+        general, are easier than scheduling.
+
+        This is reflected in the real world. Reservations force the restaurant
+        to commit to an explicit time that the table will be available, which
+        is difficult to do accurately. The simplicity of the wait list, though,
+        allows both patron and proprietor to better understand the real time
+        that a table will be available.
+
+        And although patrons appreciate more realistic expectations, the
+        overall quality of their experience is decreased when compared to
+        reservations. If you live in a neighborhood where most restaurants do
+        not take reservations, and you're looking for a restaurant, it's not
+        uncommon to walk to a bunch of places and then ultimately walk back to
+        the one that had the shortest wait list. The best way to get a good
+        spot on a particularly popular wait list is to show up in the early
+        afternoon. But it doesn't have to be that way!
+
+        The goal of the **Wait List API** is to make the process of getting and
+        being on a wait list _better_ than that of making a reservation. The
+        main idea, of course, is that if a wait list is represented as an
+        intuitive JSON API, then there a few ways that the patron experience
+        can be signifcantly improved:
+
+        1.  A patron could browse all the wait lists of all the restaurants in
+            his area, ordering them by the estimated time that a table will
+            be available for his party size. He could then put himself on the
+            wait list that works best.
+
+        2.  Once on a wait list, the patron could have complete visibility into
+            his position in line. He wouldn't have to arrive at the restaurant
+            until exactly when his table was ready.
+
+        3.  For popular restaurants, there could be a flash sale experience
+            when the wait list opens for that night's dinner. A patron could
+            contend for his position on a wait list from his office computer or
+            on his phone.
 
-        More to come.
+        Restaurants would benefit as well. First of all, the task of managing
+        the wait list is simplified since the patrons are doing it on their
+        own. Secondly, they would have access to all the data captured by the
+        API.
       DESC
     end
   end

data/useless-wait-list.gemspec

@@ -1,25 +1,24 @@
 # coding: utf-8
 $LOAD_PATH.unshift(File.expand_path('../lib', __FILE__))
-require './lib/useless/wait_list'
+# require 'useless/wait_list/version'
 
 Gem::Specification.new do |spec|
-  spec.name          = 'useless-wait-list'
-  spec.version       = Useless::WaitList::VERSION
-  spec.authors       = ['Kevin Hyland']
-  spec.email         = ['khy@me.com']
-  spec.description   = 'For restaurants that don\'t take reservations'
-  spec.summary       = 'An idealized restaurant wait list API.'
-  spec.homepage      = 'http://wait-list.useless.io'
-  spec.license       = 'MIT'
+  spec.name           = 'useless-wait-list'
+  spec.version        = '0.0.2'
+  spec.authors        = ['Kevin Hyland']
+  spec.email          = ['khy@me.com']
+  spec.summary        = 'For restaurants that don\'t take reservations'
+  spec.description    = 'An idealized restaurant wait list API.'
+  spec.homepage       = 'http://wait-list.useless.io'
+  spec.license        = 'MIT'
 
-  spec.files         = `git ls-files`.split($/)
-  spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
-  spec.test_files    = spec.files.grep(%r{^spec/})
-  spec.require_paths = ['lib']
+  spec.files          = `git ls-files`.split($/)
+  spec.test_files     = spec.files.grep(%r{^spec/})
+  spec.require_paths  = ['lib']
 
   spec.add_runtime_dependency 'sinatra', '~> 1.4.2'
   spec.add_runtime_dependency 'useless', '~> 0.2.0'
-  spec.add_runtime_dependency 'useless-doc', '~> 0.6.1'
+  spec.add_runtime_dependency 'useless-doc', '~> 0.6.4'
 
   spec.add_development_dependency 'bundler', '~> 1.3'
   spec.add_development_dependency 'rake', '~> 0.9'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: useless-wait-list
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.0.2
 platform: ruby
 authors:
 - Kevin Hyland
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-03-29 00:00:00.000000000 Z
+date: 2013-04-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: sinatra
@@ -44,14 +44,14 @@ dependencies:
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
-        version: 0.6.1
+        version: 0.6.4
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - ~>
       - !ruby/object:Gem::Version
-        version: 0.6.1
+        version: 0.6.4
 - !ruby/object:Gem::Dependency
   name: bundler
   requirement: !ruby/object:Gem::Requirement
@@ -122,7 +122,7 @@ dependencies:
     - - ~>
       - !ruby/object:Gem::Version
         version: 2.0.10
-description: For restaurants that don't take reservations
+description: An idealized restaurant wait list API.
 email:
 - khy@me.com
 executables: []
@@ -135,7 +135,6 @@ files:
 - README.md
 - Rakefile
 - lib/useless/wait_list.rb
-- lib/useless/wait_list/version.rb
 - spec/documentation_spec.rb
 - spec/spec_helper.rb
 - useless-wait-list.gemspec
@@ -162,7 +161,7 @@ rubyforge_project:
 rubygems_version: 2.0.0
 signing_key: 
 specification_version: 4
-summary: An idealized restaurant wait list API.
+summary: For restaurants that don't take reservations
 test_files:
 - spec/documentation_spec.rb
 - spec/spec_helper.rb

data/lib/useless/wait_list/version.rb

@@ -1,5 +0,0 @@
-module Useless
-  class WaitList
-    VERSION = '0.0.1'
-  end
-end