[wp-hackers] GSoC Proposal: JSON REST API
bryan at ibaku.net
Sat Apr 13 05:29:43 UTC 2013
On Fri, Apr 12, 2013 at 10:03 PM, Mike Schinkel <mike at newclarity.net> wrote:
> The 2 month single developer constraint of the GSOC process is the issue.
No-one has even proposed what the project requirements and
deliverables would be for the end of the GSoC project, either from any
possible mentors or from Ryan (which would happen during the
application period). How can you know time is going to be an problem
without even knowing what the scope of the project is?
He's just here to discuss it as a possible project, and what everyone
thinks those requirements could possibly be, not to get shot down
before he's even written up the proposal.
For example, if the end goals were only a public API covering just
posts and post types (and not taxonomies, media, users, comments,
options, categories, tags, pages, menus, widgets or anything else you
can think of) with no requirements on OAuth 2.0, and only covering GET
endpoints (since POST/PUT/PATCH/DELETE would be authenticated
endpoints), this is well within reach given the time constraint. In
fact, it's probably too little for a GSoC project really, especially
given what Ryan has already put together. Even that would get us
started and going somewhere though.
It all depends on what goals are set for the project, and those
haven't been laid out. I believe this is what Marko means by unhelpful
So it would be really nice if everyone would stop speculating on *if*
a REST API project should be accepted for GSoC, and actually discuss
what *could* be possible as a GSoC project, and what you might like to
see out of such a project, assuming it was feasible and acceptable.
If Ryan's proposal appears to be a problem, there is a special period
of the GSoC program specifically reserved to work out those issues
before proposals are even accepted, but it's not right now (it's just
before and after the student application deadline). Also, that's for
the core team running the program to decide anyway.
More information about the wp-hackers