Documentation office hours - August 21, 2025

Community
,
1

2025-08-21

Attendees:

  • Kevin Martens

  • Bruno Verachten

  • Meg McRoberts

  • Mark Waite

Agenda

  • Contributor spotlight

    • Latest spotlight, featuring Jay Francis, published

      • One response currently being transferred into an .adoc for submission.

      • Discussed with Advocacy & Outreach about potential spotlights

        • Provided updated list of top contributors, Alyssa will follow up with people

        • Thanks to Bruno for providing the data!

      • Have received several responses from those asked, thanks to those who have submitted responses

  • Java 25 documentation

    • Thanks to Kris Stern for creating this issue

    • Kevin created list of areas that will need Java 25 update when it is available

      • Based on Java 21 updates, may need further additions if discovered

    • Full Java 25 support planned for Fall ‘25

    • Java 25 early access now in use on ci.jenkins.io and available in agents

      • If you want to explore with Java 24, make sure to use latest

  • Jenkins Board & Officer Elections

    • Nomination period currently open until September 22

      • Anyone can nominate anyone

    • 2 governance board positions & all officer positions are eligible for nomination

    • Key time frames for election

      • Nomination of candidates (August 8 - September 22)

      • Voter registration (September 16 - October 31)

      • Voting (November 1 - November 30)

      • Results announcement (December 1)

    • Voting does require registering an account and we encourage people to contribute as part of the process.

  • Redesigning Jenkins pt 2

    • Jumbotron updated to include this as first item

    • Second blog post from Jan Faracik on redesigning Jenkins/UI updates for Jenkins

    • Highlights the changes to the UI brought with 2.516.1 & previous weekly releases

    • Shares link for the livestream that Jan & Darin Pope hosted

      • Kevin currently working on updating images in documentation to reflect updated UI

  • Google Summer of Code 2025

  • Chinese documentation site and Chinese localization plugin

    • Planned to retire it, but there are 58,000 installations of the Chinese localization plugin

    • Runxia Ye and Mark discussed at FOSDEM

      • Check the actual usage of the Chinese with analytics

      • Check the actual usage of Chinese localization

    • Alternative would be to find a funding source to translate latest messages to Chinese

      • Kris has created a new issue to initiate adding native Chinese (both traditional and simplified) localization to Jenkins core natively

      • The localization is planned to start sometime Summer 2025

    • Kris recently adopted the Chinese docs site

      • Modernization and updates will happen along with localization efforts starting in summer 2025

      • Will need to have a meeting with Mark Waite to discuss details later when Mark will be free

      • Planning to happen in parallel to the GSoC jenkins.io retooling project, as we will need to match in terms of tech stack for the versioned docs capability, or have some variants of this.

      • May not use the exact same tooling as the docs.jenkins.io site, but will follow as much as possible what can be done. Propose to use Docusaurus – https://docusaurus.io/ for the revamped Chinese site.

      • Planning on starting later this month (August, relative to work being done in GSoC)

    • Are the Jenkins users already English speakers and don’t need Chinese localization?

    • Potentially include Chinese localization in core and deprecate/disable plugin once it is complete

    • Not enough data to determine one way or another just yet

  • Good first issues on Jenkins.io

    • Looking to restock the good first issues

    • A number of work in progress pages

    • Thanks to Meg for creating some good first issues

    • Need to review feedback to see if there are any additional good first issues

  • LTS and Weekly releases

  • IRC Bot documentation removed

  • Recent work

  • LInux Foundation, scarf.sh and tracking documentation page reading

    • LF has a contract with scarf.sh

    • Would we (as a group) be okay with documentation reader tracking

      • Based on public data (nothing spooky or nefarious happening)

    • OK that Mark Waite submits a test pull request to the www.jenkins.io repository to test the idea

      • Mark then invite Docs SIG members to click the link so that we can confirm the tracking works

  • Docs feedback thread from gitter

    • Feedback/issue would not be connected to anyone (no way to confirm the issue is resolved)

    • Feedback submitted for steps would be unhelpful in jenkins.io repo (would need to be pushed/moved to respective plugins and then have maintainers fulfil requests [not ideal])

    • Forcing readers to create a github account to submit feedback so that it is connected would cause users to disengage/not submit feedback

    • A lot of feedback asking for examples (needs extensive knowledge of the plugin/workflow and ability to create said example)

  • Plugin Developer documentation

    • Topic brought by Antoine Neveux at previous office hours

    • Lots of warning signs in the documentation saying “work in progress”

    • How can this be updated/enhanced and provide a more confident experience

    • What would be the best way to address this?

      • Improve a plugin tutorial helps, but does not address the developer documentation directly

  • Blue Ocean Deprecation

    • Work to remove Blue Ocean from documentation has begun

    • Tutorials moved towards bottom of page and includes status note

    • Status notes have been updated to indicate alternatives/replacements for pipeline visualization.

    • Not likely to happen until end of 2025/beginning 2026