Gem project in order to new maintainer. [admin]

Author: trans

.gitignore

@@ -1,7 +1,10 @@
-.reap/digest
+.ergo/digest
 .yardoc
-doc
-log
-pkg
-tmp
-web
+doc/
+log/
+pkg/
+tmp/
+web/
+*.gem
+*.lock
+

.index

@@ -2,7 +2,8 @@
 revision: 2013
 type: ruby
 sources:
-- var
+- Index.yml
+- Gemfile
 authors:
 - name: Trans
   email: transfire@gmail.com
@@ -14,29 +15,25 @@ organizations:
 - name: Rubyworks
 requirements:
 - groups:
-  - build
-  development: true
-  name: detroit
+  - test
+  version: '>= 0'
+  name: microtest
 - groups:
-  - build
-  development: true
-  name: ergo
+  - test
+  version: '>= 0'
+  name: ae
 - groups:
   - test
-  development: true
+  version: '>= 0'
   name: rubytest
 - groups:
   - test
-  development: true
+  version: '>= 0'
   name: rubytest-cli
 - groups:
-  - test
-  development: true
-  name: microtest
-- groups:
-  - test
-  development: true
-  name: ae
+  - build
+  version: '>= 0'
+  name: indexer
 conflicts: []
 alternatives: []
 resources:
@@ -60,23 +57,20 @@ categories: []
 copyrights:
 - holder: Rubyworks
   year: '2009'
+  license: BSD-2
 - holder: K. Kodama
   year: '2001'
 customs: []
 paths:
   lib:
   - lib
-created: '2001-03-10'
-summary: Queue of Prioritized Elements
+name: pqueue
 title: PQueue
 version: 2.0.2
-name: pqueue
-description: ! 'A priority queue is like a standard queue, except that each inserted
-  elements
-
-  is given a certain priority, based on the result of the comparison block given
-
-  at instantiation time. Retrieving an element from the queue will always return
-
-  the one with the highest priority.'
-date: '2013-03-10'
+summary: Queue of Prioritized Elements
+description: A priority queue is like a standard queue, except that each inserted
+  elements is given a certain priority, based on the result of the comparison block
+  given at instantiation time. Retrieving an element from the queue will always return
+  the one with the highest priority.
+created: '2001-03-10'
+date: '2014-04-15'

.travis.yml

@@ -3,8 +3,7 @@ script: "bundle exec rubytest"
 rvm:
   - 1.8.7
   - 1.9.3
+  - 2.0.0
   - jruby
-  - jruby-19mode
   - rbx
-  - rbx-19mode
 

CONTRIBUTE.md

@@ -0,0 +1,55 @@
+# CONTRIBUTING
+
+## Testing
+
+We are using the Microtest framework which is a very simple test
+framework built to mimic the original Test::Unit but build on
+Ruby Test, the slick meta-testing framework.
+
+Thanks to the configuration in `etc/test.rb` running test should
+be as simple as:
+
+```
+$ rubytest
+```
+
+## Releasing
+
+When releasing a new version there a few things that need to done.
+First, of course, make sure the version number is correct by editing
+the `Index.yml` file. Then update the canonical `.index` file via:
+
+```
+$ index -u Index.yml Gemfile
+```
+
+Also, don't forget to add an entry to the `HISTORY.md` file for the
+new release.
+
+Though it is not likely to be needed for this project, ensure the MANIFEST
+is up to date:
+
+```
+$ mast -u
+```
+
+Now build the gem:
+
+```
+$ gem build .gemspec
+```
+
+To release simply use:
+
+```
+$ gem push pqueue-x.x.x.gem
+```
+
+Finally, don't forget to add a tag for the release. I always use the
+description of the release from the HISTORY file as the tag message
+(excluding the changes list).
+
+```
+$ gem tag -a x.x.x
+```
+

Gemfile

@@ -1,2 +1,13 @@
-source :rubygems
-gemspec
+source "https://rubygems.org"
+
+group "test" do
+  gem "microtest"
+  gem "ae"
+  gem "rubytest"
+  gem "rubytest-cli"
+end
+
+group :build do
+  gem "indexer"
+end
+

MANIFEST

@@ -1,7 +1,8 @@
 #!mast .ruby .yaropts bin lib man qed spec test [A-Z]*.*
-.ruby
 lib/pqueue.rb
 test/test_pqueue.rb
-HISTORY.rdoc
-README.rdoc
-COPYING.rdoc
+CONTRIBUTE.md
+Index.yml
+README.md
+HISTORY.md
+LICENSE.txt