JavaScript Chat Summary for June 20th

Below is a summary of the discussion from today’s JavaScript chat (agenda, Slack transcript):

WordCamp Europe Summary

  • Contributor day drew 500 attendees and included two JavaScript-focused sessions
  • Sessions overflowing-packed, indicating huge and growing interest in using JavaScript in WordPress
  • Anyone involved in JavaScript is encouraged to consider giving a WordCamp talk to share your experience
  • During community summit, recap of framework discussion and review of recent core chats
  • Notes from Community Summit will be posted soon, including a decision surrounding the recent framework selection discussions and the rationale leading to it

Increasing JavaScript contributions in core

  • Observed very small number of contributors
  • Introduction of a new #core-js Slack channel toward goal of engaging new contributors looking to become involved in WordPress JavaScript (link to 300 open tickets)
  • Question: What factors increase developer involvement and how can we increase involvement?
  • Contributor experience: Workflow of using Trac and exchanging patches not welcoming to new generation of (JavaScript) developers using Git and GitHub
  • Gutenberg as as an example of a WordPress project being built in GitHub, easy way to become involved
  • Previous efforts relating to GitHub pull request integration with Trac (#34694, rmccue/github-to-patch)
  • Increase involvement by sharing generic modules in a WordPress modules monorepo, drawing awareness from developers engaging in these ecosystems (npm, etc)
  • In-progress side project from @atimmer to parse and publish documentation to DevHub using documentation.js
  • Lack of documentation cited as pain point for new contributors. Should improve overview-type developer guides for using and extending core JavaScript.
  • New contributors would like quick start tasks to work on. “Good First Bugs / Tasks” exist in Gutenberg and in Trac (filtered to JavaScript focus)
  • Contributions are slow to be reviewed or committed, perhaps discouraging new contributors
  • Yoast has started efforts to improve documentation for media library. We might consider moving these discussions into Trac to surface and organize them as core issues.
  • Is WordPress’s image in JavaScript communities as “old” (or otherwise undesirable) as being a deterrent? Possible solutions: Blogging about innovations, sharing useful utilities in broader JavaScript community, evolving foundation for JavaScript with efforts like Gutenberg, highlighting JavaScript improvements in release notes
  • New contributors might consider simply reviewing existing tickets, testing whether they’re still valid, taking screenshots, and commenting

Administrative

  • Weekly meeting agendas will become more minimal over time with focuses on bug scrubs and deciding larger item tickets (dates, hooks, etc)

#javascript, #summary