openhatch

Issue468

Title Write public API docs for the /people/ JSON API
Milestone later Priority bug
Waiting On Status chatting
Superseder Nosy List Mark, paulproteus
Assigned To paulproteus Keywords

Created on 2011-07-03.01:59:30 by paulproteus, last changed 2012-01-27.17:53:58 by paulproteus.

Messages
msg2911 (view) Author: paulproteus Date: 2012-01-27.17:53:57
I've changed the way that we generate JSON for the /people/ so that it can be
more-readily considered an API.

We should begin by documenting the way this works, and then seeing what else
would be interesting to expose.
msg2238 (view) Author: Mark Date: 2011-08-02.13:48:51
Opening it back up.
msg2178 (view) Author: Mark Date: 2011-07-08.14:04:13
I'll take this on.  I'll get a conversation started on devel to discuss what data 
everyone thinks should be made public.
msg2140 (view) Author: paulproteus Date: 2011-07-03.01:59:30
There are bugs like issue76 that would be easy to solve if we made a few 
decisions about an OpenHatch API.

Therefore, this bug is a request for someone to write a specification for 
the kind of API OpenHatch could have.

An easy first API would be to export most of the site's data in JSON format. 
Which data? At what URLs?

(Anyone can submit a proposal here.)

If we agree on a specification, we can start filing bugs indicating that the 
spec isn't fully-implemented. Then we can actually have an API.
History
Date User Action Args
2012-01-27 17:53:58paulproteussetassignedto: paulproteus
title: Write a specification for the kind of API OpenHatch could have -> Write public API docs for the /people/ JSON API
messages: + msg2911
milestone: later
2011-08-02 13:48:51Marksetassignedto: Mark -> (no value)
messages: + msg2238
2011-07-08 14:04:13Marksetstatus: unread -> chatting
assignedto: Mark
messages: + msg2178
nosy: + Mark
2011-07-03 01:59:30paulproteuscreate