JavaScript Chat Summary – January 8th

Below is a summary of the discussion from this week’s JavaScript chat (agendaSlack transcript).

Have a topic for discussion for the next meeting? Leave a suggested edit on the next meeting’s agenda.

Revisiting Note Takers for 2019

A rotating set of volunteers are responsible for publishing these chat summaries. The topic was raised as an opportunity to make additions or removals from the rotation. Thanks to @ajitbohra and @jorgefilipecosta for adding themselves to the rotation!

In addition, there was some question to the intended format of the summaries. @nerrad has since added a new “Guidelines for Note Takers” section to the same Note Takers document.

Reviewing Documentation for Accuracy Post-5.0

It was briefly discussed in our previous meeting that it may be worth auditing older documentation to ensure that the content remains accurate, particularly with consideration of the substantial JavaScript changes and patterns which had been introduced as part of 5.0.

It was suggested to coordinate with the docs team to better understand where to start, and what documents might be relevant for auditing.

Ideas for Handling Future Deprecations

A preliminary discussion was held to surface ideas for how deprecations may be handled in the future. This has been discussed in previous meetings, and in the post Technical Organiziation Post-5.0. This discussion was more on the point of anticipating the challenge, moreso than addressing specific deprecations.

A few ideas were raised / recapped:

  • Using script versioning such that a plugin author opts in to the newest version, dropping deprecations out of the fact that they are no longer referenced by any plugin or core code.
    • There are significant technical challenges involved in this approach.
  • More communication over that which has been part of Gutenberg’s approach to deprecations.
    • More visible messaging as a “deadline” approaches (e.g. notices)
    • Integrating with upgrade process for WordPress, identifying conflicts between plugins and newer versions

Transparency was noted as critical to any process changes here, particularly in education and communication in how and when these deprecations occur.

Finalizing Standards Revisions

Revisions to the JavaScript Coding Standards has been a long-held discussion for prior meetings, culminating in a proposal published mid-December.

There was a recap of comments made to the proposal, summarized as largely favorable.

The revisions are planned to be applied to the coding standards today, after a small suggested clarification is made.