2022-11-14T18:00:00Z
November 14, 2022
Participants: Mark Waite, Bruno Verachten, Basil Crow, Gavin Mogan, Oleg Nenashev, Suresh
Agenda:
- News
- 2.361.4 released today with a fix for an issue that was blocking some large scale use of Jenkins at high visibility
- 2.375.1 is the next LTS baseline, scheduled to release Nov 30, 2022
- Ideas:
- Setup empty agenda for next meeting at end of previous meeting
- Allows for people to add stuff whenever ready
- Mark Waite action item to create an empty agenda entry
- Review Jenkins.io subprojects - Jenkins Sub-projects (and dropdown)
- Do subprojects ever become deprecated?
- Move jenkins-x to cdf menu?
- Remove blueocean?
- Remove it from the subprojects list, archive
- Remove jenkins operator?
- Remove it from the subprojects list, archive
- Notify maintainers, issues raised on jenkins.io
- Virtus Labs has not been responding recently
- Had two operators at one point, Red Hat and Virtus Labs
- Trademark approval to Virtus Labs with open governance
- If open governance is not being applied
- Needs a group of 3, Board member, Red Hat, Virtus Labs
- Virtus Labs may have moved the operator community elsewhere?
- Last commit to the repository was 5 months ago
- Suresh is a user of Jenkins operator, hoping for Dec release
- Gavin thinks he may have seen mention of an upcoming release
- Oleg’s proposal to explicitly ask to have the maintainer list extended
- Encourage adoption of the project, if not adopted, then archive it
- Future board meeting topic
- Remoting and configuration as code subproject content is outdated
- Should they remain on the subproject list?
- Should we redirect those pages to the associated GitHub README?
- Remoting project was a location to list the remoting consumers
- Put that listing in the remoting README?
- Drop the remoting gitter chat channel
- Remove meetings that no longer occur, mailing lists that are unused
- Consider combining subprojects and sigs into “working groups”
- Single concept for subteams, create and archive as needed
- Action item - propose a transition to working groups and restructure of Jenkins.io site to implement it
- Unify subproject & SIG concepts to “working group”
- If modifying the navigation bar, tag Gavin for web components
- GSOC projects?
- Remove outdated
- Infrastructure and gsoc are both sigs and sub projects?
- Subprojects page is generated manually
- Menu is generated automatically
- Should remove Blue Ocean from the subprojects page
- Create an archived projects list to retain links and keep content
- Separate difference between subprojects and SIGs
- Should we create a single list - yes working groups
- Archive inactive SIGs
- Cloud native, pipeline authoring, chinese localization, …
- Retain the content, but note that the SIG is not active
- Other site improvements
- Retire the Chinese site because it is so badly outdated?
- Oleg to send proposal to Rick
- Remove the redirect from www.jenkins.io
- Should we continue hosting the Chinese site content?
- Retire the Chinese site because it is so badly outdated?
- Gavin is exploring options to make it clear which chat rooms are active
- Will propose it as an infra project
- Wants a way to centralize online chat access (considering Matrix hosted namespace)
- Should Meeting agenda be truncated. It takes a while to load.
- Mark Waite has archived older notes in a copy and created a link in the working document to the archive
- See Archive 01 for the proposed technique
- Propose to remove the content of Archive 01 from this document
- Export to markdown and place it on a new meetings archive repository
- Create a governance repository in jenkinsci
- Mark discuss with Damien as part of meeting archive recovery
- Gavin is willing to help with the export into desired format
- Consider a repository per working group
- Mark Waite has archived older notes in a copy and created a link in the working document to the archive
- How aggressive should I get contacting algolia - Gavin
- Mark and Gavin do not have access to the Algolia dashboard currently
- Gavin will look for help from others to get access to our Algolia search dashboard for www.jenkins.io
- Need the new Algolia implementation for the web components
- Need to update based on their current
- Setup empty agenda for next meeting at end of previous meeting
- Action items
- Mark Waite to use community.jenkins.io for the Jenkins Docs SIG mailing list
- Consider asking Kevin Martens to take the lead on this one
- EasyCLA needs to be documented by Oleg
- Mark Waite to propose a pull request documenting the web application server support policy (similar to browser support, Windows support, and Linux support)
- Many people are saying that “should work” but we don’t test them
- JENKINS_HOME is different in newer Tomcat
- No support for multiple Jenkins in a single Tomcat
- No Java EE 9 support
- All web containers moved to tier 2 except bundled web container
- Can declare “known broken” conditions (Java EE vs. Jakarta EE)
- Pull requests considered so long as they don’t harm tier 1
- Many people are saying that “should work” but we don’t test them
- Mark Waite to use community.jenkins.io for the Jenkins Docs SIG mailing list
- Elections
- Timeline reminder
- Nominations have closed for elections
- Nominee list sent to board
- Mark Waite’s proposed change of election phrasing
- See pull request 5689 with the proposal to allow up to 2 elected members of the board from a single company
- Board member nominees
- Have nominees, need confirmation before Nov 17, when voting starts
- Mark seek confirmation from board nominees
- Have nominees, need confirmation before Nov 17, when voting starts
- Officer nominees
- Release officer
- Tim Jacomb
- Security officer
- Wadeck Follonier
- Infrastructure officer
- Damien Duportal
- Documentation officer
- Kevin Martens
- Events officer
- Alyssa Tong
- Release officer
- Board vets the nominees in the board mailing list
- Complete before voting starts Nov 17, 2022
- Timeline reminder
- Forums and community topics - Gavin
- Insert newsletter link