[wp-hackers] GSoC Proposal: JSON REST API

Marko Heijnen mailing at markoheijnen.nl
Fri Apr 12 16:57:30 UTC 2013

I didn't read the whole story yet but please Mike this isn't helpful. I don't think that it is a bad idea. I think in two months we do get something done. Obviously not a full implemented JSON/RESTful API but that isn't needed at all. Also a Trac ticket doesn't help at all. You will get a lot of responses an opinions and it hard to filter it out. I do believe a small group can help out starting this idea.

Obviously 1 student and 1 mentor isn't really a group but there are other people that can help out. If I'm not a mentor on this idea I do help out and I'm sure a lot of other people like Bryan and Eric will do too and probably this will also includes you. So the code will get many eyes on it. I also think that someone like Max Cutler will look into it and after talks I had with him I'm sure he gives good feedback.

I never going to say no to something like this since if we are going to wait core to do something then we can wait a long long time.


Op 12 apr. 2013, om 18:47 heeft Mike Schinkel <mike at newclarity.net> het volgende geschreven:

> On Apr 12, 2013, at 4:23 AM, Bryan Petty <bryan at ibaku.net> wrote:
>> Which is why it's not even being considered for merge to trunk during
>> (or for quite some time after) GSoC.
> I will repeat: Implementing a JSON API as a GSOC project is a BAD idea.  
> To constrain the architecture decisions to 2 months minus the time required to fully implement is a BAD idea.  To effectively have one person with one mentor choose the architecture for a JSON API that could affect 70 millions sites is a BAD idea.
> A GSOC JSON API will be treated as the defacto-standard JSON API implementation planned for WordPress core and thus more than a few people will use it. Implemented API code has great inertia. Architecture choices will quickly be "baked in" from usage and the cry to halt change in the API will be great, especially is someone influential with core builds to this API.
> A JSON API has attributes that other GSOC projects will not have.  APIs are different from UX; people can adapt to a changing UX[1]; programs written to API cannot adapt unless someone devotes time or funds to modify them. 
> Please do not do this; make it a Trac ticket instead. Organize a KickStarter campaign if it's about the money; I'll back it.
> -Mike
> P.S. Again, this is not personal. I have great respect for both you Bryan and Ryan and I hope my objection to this does not sour you on me personally. This is because I truly believe a JSON API is too important for the GSOC process.
> [1] http://wordpress.org/extend/plugins/mp6/
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list