Skip to content

Home

Jump to bottom
jamierumbelow edited this page Aug 7, 2010 · 20 revisions

Motivation

Let’s admit it. RubyForge sucks. It’s been the same for years, has features we don’t need, and is simply not fun to work with. Gemesis is the answer to these problems. What’s needed for gem hosting done right:

  1. A community-driven effort so it can be constantly improved
  2. A way to browse gems and download them
  3. An easy API to access information and upload/publish gems

Brainstorming

Let’s use this section for planning out the features of the site, the API, and how it will look.

API Concepts/Specs

I suggest we go for a RESTful interface.

  1. /gems/show/my_gem – View the gem “My Gem”
  2. /gems/create – Create a new gem (HTTP POST)

Obviously we would need some kind of authenticity set up, but I suppose you could work with a session-based system, where the user of the API logs in, and gets given a session key for future requests.

Clone this wiki locally