# Documentation office hours - April 05, 2024

**URL:** <https://community.jenkins.io/t/documentation-office-hours-april-05-2024/13981>\
**Category:** Community\
**Tags:** meeting, sig-docs\
**Created:** [April 5, 2024, 4:11am UTC](https://community.jenkins.io/t/documentation-office-hours-april-05-2024/13981 "2024-04-05T04:11:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [April 5, 2024, 4:11am UTC](https://community.jenkins.io/t/documentation-office-hours-april-05-2024/13981/1 "2024-04-05T04:11:07Z")

</div>

2024-04-05T02:30:00Z

[![](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/3/3fec64afc252272d438267edcbbad3600c7db8e8.jpeg "2024 04 05 Docs Office Hours") ](https://www.youtube.com/watch?v=H0Hrm-01iMM)

## 2024-04-05 (Asia)

Attendees

- Mark Waite
- Meg McRoberts
- Kris Stern

Agenda

- LTS 2.440.3 to be released on Apr 17, 2024
  - [Pull request for changelog & upgrade guide](https://github.com/jenkins-infra/jenkins.io/pull/7218)
  - [Release candidate build](https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.440.3-rc34568.387f5a_600b_ee/jenkins-war-2.440.3-rc34568.387f5a_600b_ee.war) available for testing
  - Announcement had some surprises, tag is placed correctly but the linked build is incorrect
  - Will update with a most recent link in the [GitHub release note](https://github.com/jenkinsci/jenkins/releases/tag/jenkins-2.440.3-rc) when available

- Weekly 2.452 built and delivered successfully - proposed as the next LTS baseline
  - Current front runner for next LTS baseline selection
  - [Discussion in developer mailing list](https://groups.google.com/g/jenkinsci-dev/c/O1eiOF6vz54/m/At30OOuxAAAJ)

- New [blog post from Kris Stern regarding GSoC application period conclusion](https://github.com/jenkins-infra/jenkins.io/pull/7230)
  - Kevin to review, Bruno & Jean-Marc have already reviewed/provided feedback
  - Merged, needs a fix in the title

- Contributor spotlight
  - [Hervé Le Meur](https://github.com/jenkins-infra/contributor-spotlight/pull/113) will be featured next
  - Received review from Bruno & Kris
  - Mark Waite will be next after Hervé

- Google Summer of Code
  - Review process has closed, moving into the application receipt phase
  - Blog post is out for the closing of applications
  - Now in the grading period, preparing our submission to Google
  - Alyssa returns from time off just in time to submit to Google

- Versioned docs project
  - Progress continues thanks to Vandit Singh and Kris Stern
  - Working on the Gatsby site, waiting for new from the infra team on the final site
    - Infra team is still loaded with keeping costs under control
    - $60000 donation from AWS, need to change infra to use it
    - Mark needs to submit the donation application for 2025 AWS donation
      - Donation recipients will be decided in June 2024

- Docker compose update - tutorials and Docker install instructions
  - 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](https://github.com/jenkins-infra/jenkins.io/pull/7228) once they are okay to merge and will need review prior when they are ready for it.
    - Instead of “docker compose up -d maven”, it will be “docker compose up -d –profile maven”

  - GSoC 2023 project that is helping Jenkins users now

- 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

- Documenting Pipeline libraries with markdown or plain text or HTML
  - Markus Winter proposed to support markdown for Pipeline library documentation ([PR-117](https://github.com/jenkinsci/pipeline-groovy-lib-plugin/pull/117))
  - Mark Waite has [converted](https://github.com/MarkEWaite/pipeline-library/commit/42ae6f93f294da9eabf361dc5167afe9d1a6348a) his [branch of pipeline-library](https://github.com/MarkEWaite/pipeline-library/tree/my-own-master) to use markdown, works well
  - Requires [markdown formatter plugin](https://plugins.jenkins.io/markdown-formatter/) installed on the Jenkins controller
  - If we update the [ci.jenkins.io Pipeline library](http://ci.jenkins.io), then markdown formatter plugin needs to be installed on [ci.jenkins.io](http://ci.jenkins.io)
  - Mark [introduced topic in IRC](https://matrix.to/#/!JLUOInpEYmxJIYXlzs:matrix.org/$EC0d-Aq35sgTC7xviPMa8Vu_QgY4OzCWnd3yMdyNUXk?via=g4v.dev&via=gitter.im&via=matrix.org)

- Additional permissions for the wiki-docs repository
  - Mark Waite learned that docs team didn’t have permissions on the wiki archive repository
    - Permissions also granted to copy editors

  - 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
