RubyForge: RubyForge API: open-discussion

Discussion Forums: open-discussion

RE: What functionality to do first? [ reply ]
2009-06-16 22:40

The rubyforge gem hits /frs/?group_id=5 to get a list of package and release ids, so we'll need to implement those too. So far we've got:

GroupsController#show
UsersController#show
PackagesController#create

Coming along slowly... next up, PackagesController#index (/groups/5/packages).

Tom

By: Tom Copeland

RE: What functionality to do first? [ reply ]
2009-06-04 01:18

Let's see, here are the functions I see:

===============
def logout
def login
def create_package(group_id, package_name)
def post_news(group_id, subject, body)
def delete_package(group_id, package_id)
def add_release(group_id, package_id, release_name, *files)
def add_file(group_name, package_name, release_name, userfile)
===============

So add Forum to the list of resources we need to expose. Ara, am I missing any there?

Maybe we can do Package#create first... that'll force us to do authentication/authorization....

Yours,

Tom

By: Tom Copeland

RE: What functionality to do first? [ reply ]
2009-06-04 00:30

Cool, ok, thanks for the suggestions! Yeah, somebody twittered a while back "if you can't do interact with an API using curl, it's not a good API" Pretty true, I think. Yeah, basic auth and JSON, that sounds like a plan.

And this is the latest version of the code, is that right?

http://codeforpeople.rubyforge.org/svn/rubyforge/

Thanks,

Tom

By: ara howard

RE: What functionality to do first? [ reply ]
2009-06-04 00:04

yeah i own/maintain it. it's been stable and robust for quite some time. reading the code is good insight into what's needed - every function is heavily used.

thoughts:

. *please* json over xml
. http basic auth for widest user agent support

By: Tom Copeland

What functionality to do first? [ reply ]
2009-06-03 23:48

Hi all -

I'm thinking that we should do enough to let someone release a file through the API. That would mean doing authentication, authorization, rate limits, FRSFile, FRSRelease, FRSPackage, Group... would be a good start.

Eventually, I'd say let's try to do everything that the "rubyforge" gem supports, bit by bit, and then submit patches to migrate that gem over to using the API. I think Ara Howard owns that gem... the codeforpeople project owns that namespace, anyhow.

Yours,

Tom