Summary of Docs Team meeting November 4, 2025

Housekeeping

• Where: #docs  channel on Slack
• When: Tuesday, 04 November 2025, 3PM UTC
• Meeting Facilitator: @milana_cap
• Note Taker: AI 🤩

Find the complete Transcript of the meeting on Slack.

Next meeting:

• Where: #docs channel on Slack
• When: Tuesday, 11 November 2025, 2PM UTC

1. Meeting Time Confusion

• The meeting began one hour later than planned due to daylight saving time changes.
• Action:
  • @milana_cap will update the global calendar to reflect the new time.

2. Contributor Recognition Initiative

• Discussion focused on improving recognition for contributions and clarifying the process for tracking them.
• Reference post: Rethinking Contributor Recognition in Documentation Team.
• A new contribution form was introduced to capture contributions not recorded anywhere else.
  • Demo shared: Slack thread + video demo.
• Proposal:
  • Contributors to submit their activities every week via the form.
  • Meeting leads will collect and announce the contributions during the meeting.
  • Weekly contributor badges will be issued and announced.
  • Contributions will be gamified: each submission earns points and titles, contributing to a leaderboard.
• Action:
  • Contributors are asked to submit their contributions via the form.
  • @milana_cap to publish a detailed post explaining the recognition workflow and gamification proposal.

3. Regular vs. Release Contributions (led by @estelaris)

• Continuing previous discussions around defining regular and release contributions.
• Regular contributions include:
  • Attending meetings, writing up meeting notes, or leading meetings.
  • Attending contributor days (e.g., WordCamp, Meetup, external events).
  • Submitting issues to update documentation articles.
  • Note: Fixing typos is important but does not count as a regular meaningful contribution.
• Release contributions refer to tasks related to specific WordPress version releases (e.g., the current 6.9 release). These contributions include:
  • Creating and managing project repositories (e.g., WP 6.9 documentation).
  • Updating articles, submitting new screenshots, reviewing documentation.
  • For developer docs, interacting with the release team, ensuring devnotes are documented (though not writing them).
  • Final tasks are done during the release party (see: Documentation process during a major version release).
• Discussion around devnotes:
  • Currently, responsibilities for devnotes are unclear and need to be revisited after the 6.9 release.
• Action: Clarify and document the specifics of release contributions after the 6.9 release.

4. Conclusion & Next Steps

• Action items:
  • All contributors should submit their contributions using the form on the Docs blog.
  • The team will review feedback and questions over the next week.
  • A follow-up discussion about contributions will take place in the next meeting.
• Next Meeting:
  • Date: November 11, 2025
  • Time: 14:00 UTC (new time due to daylight saving time).

#docs, #summary