gemcutter

Awesome RubyGem hosting.

Purpose

• Provide a better API for dealing with gems
• Create more transparent and accessible project pages
• Enable the community to improve and enhance the site

Links

Mailing List
FAQ
IRC: #gemcutter on irc.freenode.net

Contributions

Gemcutter has a ‘commit-bit’ policy, much like the Rubinius project. Submit a patch that is accepted, and you can get full commit access to the project. All you have to do is ask us on #gemcutter on Freenode or bug qrush in a message and he’ll add you as a collaborator on the main repository. Feel free to fork the project though and have fun in your own sandbox.

Please read up on the GitHub Wiki for the latest contribution guidelines.

To get setup, please check out the Development Setup page on the wiki. It’s on the wiki so anyone can edit it, so please fix it if you have trouble getting set up!

Organization

Gemcutter consists of a few major parts:

• Rails app: To manage users and allow others to view gems, etc.
• Sinatra app (Hostess): the gem server, lives in app/middleware/hostess.rb.
• RubyGem: The gemcutter client gem that interacts with the site, lives in gem/.
• Gem processor: Handles incoming gems and storing them in S3 (production) or on the filesystem in server/ (development). Lives in lib/gemcutter.rb, lib/indexer.rb, lib/vault.rb.

License

Gemcutter uses the MIT license. Please check the LICENSE file for more details.