Summary of 5/28 dev chat (IRC log):
- @nacin and @tellyworth have been working on the .org API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. side for i18n and plugins page improvements respectively and should be ready for work on the core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. side soon. Be on the lookout for tickets and discussions.
- @ericlewis has been working through the Media component in Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and will be holding weekly scrub in #wordpress-dev alongside media grid chats, Fridays at 17:00 UTC.
- @wonderboymusic has been evaluating various oEmbed endpoints as we add and remove them. Some services need some more evaluation: #28379.
- The JSON REST API came a long way in the past week, especially on the documentation front, and is being placed onto the roadmap for the 4.1 release. From @nacin:
1.0 is a great step in the right direction; let’s push it hard; let’s put it squarely, loudly, and officially on the 4.1 roadmap (I’m comfortable doing that); let’s get a lot of core contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. focusing on it for the final mile, especially when it comes to internals
let’s get a lot of people to build things on it, including inside automattic, mobile apps, even wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ stuff; let’s branch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". off 1.0 so we can decide paint and carpet colors on the master branch
- And finally, several people were added to various Trac components as component maintainers. You can be added at any time, or get on the road to becoming one by signing up for granular notifications on the components page.