Summary of last week’s dev chat on 4…

Summary of last week’s dev chat on 4/30 (IRC log):

Announcements

Features as plugins

  • Met on 4/29 (IRC log)
  • Current potential considerations seem to be WP APIAPI 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. and media grid.
  • Press This is getting some attention from an early stages working group, which could also be a part of the 4.0 release.
  • Adminadmin (and super admin) Help is poised to shift into more of a continuous testing and advisory group, which is awesome.
  • Front-end editor is making good progress, but has UXUX User experience issues that are getting worked on, needs iteration and experimentation and probably won’t be ready by 4.0, but should continuously be worked on, as is the goal of features as plugins in the first place. Developers needed.

Potential ideas and their suggesters:

  • TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. and query components (@wonderboymusic, @nacin)
  • Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site improvements (@johnbillion, @jeremyfelt)
  • More mobile attention (@rboren)
  • Taxonomy roadmap up through stopping the creation of new terms, possibly splitting existing shared terms.
  • oEmbed caching (@markjaquith) and oEmbed representation in the media modal -> insert from URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org pane and in wpviews in TinyMCE (@avryl, @wonderboymusic)
  • API/architecture improvements to post/comment types/statuses (@nacin)
  • PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party installer improvements as it crosses over with dotorg (showing reviews, ratings, etc.) (@nacin)
  • Small screen capabilities for media modal (@gcorne, @melchoyce, @avryl, @rboren)
  • Continue widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. improvements, e.g. Backbone representation (@westonruter)
  • Editor toolbar experience (@markjaquith)

Summary: we have good things in mind about more media improvements, more editing experience improvements, more visual media grid and better plugin installer experience (following in the footsteps of themes), and behind the scenes wins in taxonomy, multisite, and post type and comment APIs.

If you’re interested in any of the above or have other ideas, please sound off in the comments.

Getting involved

  • We are always looking for more people to be involved with TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. gardening, patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. review, patch writing, or some combination thereof.
  • Component pages are running well, and most could still use the caretaking of a component owner or somebody who’d like to become well-versed in a particular area of core. To get started, just sign up for component notifications at https://make.wordpress.org/core/notifications/. No need to be an expert now – learning and persistence is more important.To help with a specific plugin, join their weekly chats and/or follow along wherever they post. See the Features as Plugins page for more information.
  • A reminder from @matt to always be dogfooding the product – use WordPress every day.

Bonus punnage, to the lead’s chagrin:

wonderboymusic will makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). a t-shirt for anyone who gets all 16 of those Cache tickets closed 🙂
> sams: “Cache Master”?
> wonderboymusic: Johnny Cache
> jorbin: If you fix the Cache, you’ll get the Credit. That Checks out.
> MarkJaquith: I’d put in a cache pun, but I don’t want to be sent to purgetory.
> johnbillion: You would have to be a cache machine to fix all 16

#4-0, #dev-chat