Documentation office hours - April 18, 2024

2024-04-18 (EU/US)

Attendees

  • Kevin Martens
  • Bruno Verachten

Agenda

  • LTS 2.440.3 released on Apr 17, 2024
    • Kris Stern was the release lead
      • Container image upload for the last several weeks has been disrupted by an HTTP 529
        • Damien has worked with Docker Inc, ultimately split to use multiple IP addresses for upload
        • Check the weekly build Tuesday to see if uploads without issue
        • Run the container build again, containers upload as expected
        • Work in progress from Bruno & Hervé on the controller to use fewer layers when building the images.
          • 5 or 6 PRs in the docker repos accordingly
          • After they are merged, we should see less layers being pulled and pushed to Dockerhub
  • Weekly 2.454 built and delivered successfully
    • Changelog was updated
  • Next LTS baseline is 2.452 (Discussion in developer mailing list)
    • 2.452.1 needs a release lead, release checklist
    • Planned, but not yet completed
  • New blog post from Kris Stern regarding GSoC application period conclusion
    • April 19 (tomorrow) is the completion of grading, proposals are sent Google
    • Google announces their selections May 1, 2024
    • Now in the grading period, preparing our submission to Google
      • 75+ submissions to grade, great to see so much activity
    • Alyssa returns from time off just in time to submit to Google
      • Any necessary followup for grading will happen next week before everything is submitted.
  • Versioned docs project
    • Progress continues thanks to Vandit Singh and Kris Stern
    • Working on the Gatsby site, waiting for news from the infra team on the final site
    • Gatsby site is in progress, slowed because the versioned docs site is not yet hosted
      • Infra team needs to provide the hosting location
      • Proposed URL was docs.jenkins.io for the versioned documentation
      • Security advisories still need attention on the Gatsby site
      • Kevin reviewing site areas and navigation
  • Contributor spotlight
  • Technical review/validation for pull requests
    • Reaching out to community for volunteers to assist with technical validation of pull requests
    • Let’s add those people to the copy editors group so they can review and he can @mention them.
      • Kris Stern, Mark Waite, Meg McRoberts, Bruno Verachten, and Kevin Martens
      • Have already tried tagging asking for review, worked very well and thanks to Kris for continued review and support.
      • Plugin development topics go to specific people after Kevin has reviewed
  • Documenting Pipeline libraries with markdown or plain text or HTML
  • cdCon 2024 just wrapped up in Seattle
    • CDF and Jenkins awards will be announced
    • Blog post to come to announce Jenkins winners
      • Most Valuable Advocate: Darin Pope
      • Most Valuable Contributor: Stefan Spieker
      • Security MVP: Yaniv Nizry
      • CDF Continuous Enthusiast: Alyssa Tong
  • Deprecation of Blue Ocean & documentation tasks
    • Update status/note at top of page
    • Look for potential replacement documentation (extended pipeline graph view documentation, other documentation)
      • Unless it’s best to just remove/redirect away from it
    • Potentially move the blue ocean documentation to a different area
    • Would the version documentation take care of this problem for us if it is not part of ‘latest’
    • Quite a few tutorials & documentation linked to Blue Ocean
      • Things that were written recently have had the Blue Ocean reference removed in favor of Pipeline Graph View
      • Basic usage of Pipeline Graph View covers what Blue Ocean offers. There are some things Blue Ocean can do specifically, but this does not necessarily mean the Pipeline Graph View is not enough.
      • Infra still uses it as well at this time, so it is very clear how important Blue Ocean is for some users
      • New users should start with Pipeline Graph View (for a better experience)
  • Asia Docs office hours for 4/19 canceled, resume week after