Documentation office hours - April 04, 2024

2024-04-04 (EU/US)

Attendees

  • Mark Waite
  • Kevin Martens
  • Bruno Verachten
  • Akash Mishra

Agenda

  • LTS 2.440.3 to be released on Apr 17, 2024
  • Weekly 2.452 built and delivered successfully
  • New blog post from Kris Stern regarding GSoC application period conclusion
    • Kevin to review, Bruno & Jean-Marc have already reviewed/provided feedback
  • Contributor spotlight
    • Hervé Le Meur will be featured next
    • Received review from Bruno & Kris
    • Mark Waite will be next after Hervé
  • Jenkins Community Awards
    • Voting has concluded
    • CDF has been notified
    • Announced at cdCon the week of April 15, 2024 in Seattle
  • Google Summer of Code
    • Latest status and upcoming plans
    • Review process has closed, moving into the application receipt phase
    • April 2 was the deadline for application
    • Project plans submitted, arrive at the Jenkins
    • Jenkins project members review the proposals
    • Jenkins selects projects and sends to Google
    • Google decides how many projects will be funded in the Jenkins community
    • Google pays the stipend in phases throughout the project
    • Mentors need to finish grading projects by the 19th (then send the selections to Google)
  • Versioned docs project
    • Demonstration next week with versioned docs
    • Infrastructure is blocked on the update center move from AWS to Cloudflare
      • Planned to be completed by April 30, 2024
      • Highest priority, reduce cloud costs for sponsors
    • Vandit has worked on the blog posts
    • Next week we can see a demonstration
    • Work on the Gatsby site is continuing
      • Added the blog teaser page and the blog landing page
    • Kris Stern will work on the security advisories soon
      • Generated from a data file
    • Will need to do a detailed check to compare the existing pages with the new pages
  • Docker compose update
    • Recent fix introduced in Docker Compose v 2.24.7 has rendered our existing docker-compose.yaml invalid.
    • Bruno has created PRs to fix the issue once they are okay to merge and will need review prior when they are ready for it.
    • Bruno saw that 40 people had forked the repo, indicating that people are trying the tutorials
    • Users have reported issues that it is not working due to the Docker Compose update (node tutorial)
    • Need to use a profile extensively
    • Discussed with Damien Dupoortal earlier
      • Okay with use of profile, hardcoded data is the “overly complex” piece
  • Technical review/validation for pull requests
    • Reaching out to community for volunteers to assist with technical validation of pull requests
    • Adding people to existing copy-editor team
    • No immediacy or urgency to requests for review, can be done when someone has the free time and capacity to assist
    • Not something that should take a lot of time (ideally 30-45 minutes at most if needed)
    • Only requested for further review after Kevin has done thorough review of content and tested as much as possible
    • Kevin would tag copy-editors, provide summary/steps of what has been done already
  • Documenting Pipeline libraries with markdown or plain text or HTML
  • Additional permissions for the wiki-docs repository
    • Mark Waite learned that docs team didn’t have permissions on the wiki archive repository
    • Fixed by Tim Jacomb and infra team
    • Don’t really make changes to that repo
    • In this case, we had a plugin that had documentation in the wiki, but needed to mark the plugin as deprecated.
    • By editing the files in the wiki archive