Documentation office hours - July 10, 2025

Community
,
1

2025-07-10

Attendees:

  • Kevin Martens
  • Birajit Saikia
  • Kris Stern
  • Meg McRoberts
  • Mark Waite
  • Bruno Verachten

Agenda

  • Contributor spotlight
    • Latest spotlight, featuring Meg McRoberts, published
      • 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!
      • Lance Albertson from OSUOSL as potential spotlight
      • Mentors from GSoC (Berviento, V Sreenias, Vihbav, Phillipp Glanz)
  • Java 25 documentation
    • Thanks to Kris Stern for creating this issue
    • Kevin creating list of areas that will need Java 25 update when it is available
    • Java 21 updates have helped spotlight areas that will need to be updated
    • Java 25 support planned for Fall ‘25
  • 2025 Jenkins Community awards
    • Winners announced via blog post & cdCon
    • 3 Categories:
      • Most Valuable Contributor - Jan Faracik
      • Most Valuable Advocate - Stefan Spieker
      • Security MVP - Daniel Beck
    • Congratulations to the winners and thanks to the community for voting
  • YourKit & JetBrains sponsorship blog posts
    • Thanks to Alexander Brandes for writing these up and working with both parties.
    • Thanks to YourKit for providing free licenses for the YourKit Java Profiler
    • Thanks to JetBrains for providing free annual All products Pack subscriptions
      • For Jenkins core maintainers & active contributors
      • To request a license/access, reach out to Alex via his email (in his GitHub profile)
  • Google Summer of Code 2025
    • All 5 projects are currently in the Standard Coding Period, with work currently underway
    • July 14 - 18 UTC mid-term evaluations to be conducted by mentors (still about 2+ weeks to go)
    • Projects all making great progress and looking forward to midterm presentations
  • 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 (July)
    • 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
  • LTS and Weekly releases
  • Introducing the header redesign as part of the July LTS
    • Lots of changes to be aware of
    • Benefit from a blog post pointing out the new header
    • What’s new LTS broadcast informing users (next .1)
    • Entries in the upgrade guide reflecting the updated header
    • Screenshots will need to be updated to reflect new UI
  • Recent work
  • New success story & adopter
  • Wiki migration redirect instructions
    • Currently, developer docs instruct users to create a redirect for the content migrated
      • No instructions on how to actually create the redirect
      • Kevin partnering with Mark Waite & Damien Duportal on what the process involves and steps needed to create and test
      • Once there are multiple examples, instructions will be updated to include more direct steps/information.
      • Redirects do not account for URL variation so trying to figure out the best way to capture these and redirect as intended.
      • Kevin has created a couple redirects, but has found that if there are multiple URLs that contain the same string, it may confuse the redirect behavior
        • Had to pause for a bit to address updated header documentation/screenshots
  • Potentially removing Java 11 upgrade instructions
  • 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.
  • 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