[wp-meta] [Making WordPress.org] #222: Endpoint to retrieve all upcoming events
Making WordPress.org
noreply at wordpress.org
Tue Nov 12 18:06:38 UTC 2013
#222: Endpoint to retrieve all upcoming events
---------------------------+--------------------------
Reporter: markoheijnen | Owner: iandunn
Type: enhancement | Status: accepted
Priority: normal | Component: wordcamp.org
Resolution: | Keywords:
---------------------------+--------------------------
Changes (by iandunn):
* owner: => iandunn
* status: new => accepted
Comment:
We've already got one that serves an ICS file for the next 15 days. You
can access it at http://central.wordcamp.org/calendar.ics and see the code
at
http://meta.trac.wordpress.org/browser/sites/trunk/wordcamp.org/public_html
/wp-content/plugins/wc-calendar/wc-calendar.php.
What kind of use cases are you looking at for this?
Most applications would probably want JSON instead of ICS, so I can see us
rolling the ICS code into your plugin and then doing any future endpoints
in JSON. It'd probably be good to keep the ICS stuff in a separate class,
though.
We store lots of meta data about WordCamps in a custom `wordcamp` post
type and treat it as canonical, so it'd probably be better to query that
in `get_wordcamps()` instead of the sites themselves. There are sites like
http://central.wordcamp.org and http://plan.wordcamp.org that aren't
WordCamps. I'll be moving that plugin to the Meta repo in the next few
weeks as part of #221.
I'd probably want to rename the plugin to something like 'WordCamp API' or
'WordCamp Endpoints', since 'WordCamp App' isn't very descriptive, and
we'd need to wait for the JSON API to land in Core, but overall I like the
idea.
--
Ticket URL: <http://meta.trac.wordpress.org/ticket/222#comment:1>
Making WordPress.org <http://meta.trac.wordpress.org/>
WordPress blogging software
More information about the wp-meta
mailing list