README.md in gems-0.7.0 vs README.md in gems-0.7.1
- old
+ new
@@ -1,14 +1,29 @@
-# Gems [][travis] [][gemnasium]
-Ruby wrapper for the RubyGems.org API.
+# Gems
+[][gem]
+[][travis]
+[][gemnasium]
+[gem]: https://rubygems.org/gems/gems
[travis]: http://travis-ci.org/rubygems/gems
[gemnasium]: https://gemnasium.com/rubygems/gems
+Ruby wrapper for the RubyGems.org API.
+
## Installation
gem install gems
+To ensure the code you're installing hasn't been tampered with, it's
+recommended that you verify the signature. To do this, you need to add my
+public key as a trusted certificate (you only need to do this once):
+
+ gem cert --add <(curl -Ls https://gist.github.com/sferik/4701180/raw/public_cert.pem)
+
+Then, install the gem with the high security trust policy:
+
+ gem install gems -P HighSecurity
+
## Documentation
[http://rdoc.info/gems/gems](http://rdoc.info/gems/gems)
# Usage Examples
require 'rubygems'
@@ -38,13 +53,10 @@
Gems.unyank 'bills', '0.0.1'
# Return an array of version details for coulda.
Gems.versions 'coulda'
- # Return an array of version details for coulda.
- Gems.versions 'coulda'
-
# Return the total number of downloads for rails_admin 0.0.1.
# (Defaults to the latest version if no version is specified.)
Gems.total_downloads 'rails_admin', '0.0.1'
# Returns an array containing the top 50 downloaded gem versions for today.
@@ -105,53 +117,9 @@
# By default, we load your API key from ~/.gem/credentails
# You can override this default by specifying a custom API key.
Gems.configure do |config|
config.key '701243f217cdf23b1370c7b66b65ca97'
end
-
-## Contributing
-In the spirit of [free software](http://www.fsf.org/licensing/essays/free-sw.html), **everyone** is encouraged to help improve this project.
-
-Here are some ways *you* can contribute:
-
-* by using alpha, beta, and prerelease versions
-* by reporting bugs
-* by suggesting new features
-* by writing or editing documentation
-* by writing specifications
-* by writing code (**no patch is too small**: fix typos, add comments, clean up
- inconsistent whitespace)
-* by refactoring code
-* by closing [issues](https://github.com/rubygems/gems/issues)
-* by reviewing patches
-
-## Submitting an Issue
-We use the [GitHub issue tracker](https://github.com/rubygems/gems/issues) to
-track bugs and features. Before submitting a bug report or feature request,
-check to make sure it hasn't already been submitted. When submitting a bug
-report, please include a [Gist](https://gist.github.com/) that includes a stack
-trace and any details that may be necessary to reproduce the bug, including
-your gem version, Ruby version, and operating system. Ideally, a bug report
-should include a pull request with failing specs.
-
-## Submitting a Pull Request
-1. [Fork the repository.][fork]
-2. [Create a topic branch.][branch]
-3. Add specs for your unimplemented feature or bug fix.
-4. Run `bundle exec rake spec`. If your specs pass, return to step 3.
-5. Implement your feature or bug fix.
-6. Run `bundle exec rake spec`. If your specs fail, return to step 5.
-7. Run `open coverage/index.html`. If your changes are not completely covered
- by your tests, return to step 3.
-8. Add documentation for your feature or bug fix.
-9. Run `bundle exec rake doc:yard`. If your changes are not 100% documented, go
- back to step 8.
-10. Add, commit, and push your changes.
-11. [Submit a pull request.][pr]
-
-[fork]: http://help.github.com/fork-a-repo/
-[branch]: http://learn.github.com/p/branching.html
-[pr]: http://help.github.com/send-pull-requests/
## Supported Ruby Versions
This library aims to support and is [tested against][travis] the following Ruby
implementations: