REST API meeting agenda: August 9

We’ve been remiss about posting these, but discussion has been ongoing in #core-restapi over the past few weeks. We’ve seen a lot of discussion of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. priorities and compatibility issues, and have also been discussing the need for more robust authentication and considering future improvements to register_meta.

This week, the agenda for our scheduled REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) component meeting today (2018-08-09 17:00 UTC) is:

  • register_meta: discuss and prioritize future enhancements
  • Gutenberg: call for volunteers to assist with priority tickets
  • 5.0: Discuss what our component priorities should be leading up to 5.0
  • Open floor / bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.

As always, if you have a REST API related ticketticket Created for both bug reports and feature development on the bug tracker. you would like to bring to the component team’s attention, please join us or leave a note in the #core-restapi channel. Hope to see you all later today!