Agenda:
News
Jenkins is a Google Summer of Code 2023 organization
Twice a week sessions introducing the project ideas
Very active conversations in the gitter channels
Project count will be limited by the number of lead mentors available
Jenkins 2.387.1, 2.375.4, and 2.394 release March 8, 2023
Security release announcement
February newsletter being prepared
Action items
Rework press contact page on jenkins.io - Alexander Brandes
Create and distribute election badges for 2022 elections - Mark Waite
No progress, do the research
Open badge hosted by the Linux Foundation (Oleg can guide Mark)
EasyCLA to be documented by Oleg
No progress, no requests pending
Mark Waite create an empty agenda entry for the next meeting after each meeting
Working well, continue doing it
Mark Waite submit jenkins.io pull request to combine subprojects and SIGs into a single concept - “working groups”
No progress, Mark to complete before next meeting
Roadmap update pull requests, needs to be update
Retire the Chinese Jenkins site
Rick recommends that we redirect the chinese pages to English equivalents
Kevin Martens (Docs Officer) tracking help desk ticket to replace the Chinese pages with redirects to the English pages
Mark Waite and Gavin “halkeye” Mogan archive the governance meeting notes to a GitHub repository, use the Google doc as the working document, then publish final notes
Gavin has prepared the archive, need a destination repository
Alexander Brandes has something in mind how to structure things.
Infra team raised about the repository location as a question
Oleg prefers jenkinsci rather than jenkins-infra for a governance repository (this is not about the archive repository!)
Mark check the infra team preference, discuss if not jenkinsci
Build Monitor View plugin repository transfer to jenkinsci org @Basil
Jan Molak published an issue stating he agreed to incorporate his plugin in the jenkinsci org: https://github.com/jan-molak/jenkins-build-monitor-plugin/issues/656
What’s the current status?
Reminder of board member role in the Jenkins code of conduct
board members are:
“responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.”
Happy to have recommendations for improvements based on recent gitter chat messages
User expressing comments with offensive words and harsh phrasing, responded positively to code of conduct mention
Jira license changes affect the Jenkins project on or before Feb 2024
Atlassian has approved our continued use of https://issues.jenkins.io
Linux Foundation will continue to host us
Further discussions in progress to assure all are aligned
CDF topics
Jenkins project presentation to the CDF Technical Oversight Committee
Mark Waite plans to present Jenkins status report at a future session
LFX Tools working group starting based on last CDF TOC meeting
Noted that devstats.cd.foundation will eventually be replaced by LFX Insights
Mailing list for discussions
GitHub repository for meeting notes and more
Community activity
Artifactory bandwidth reduction project
Artifact caching proxy has nicely reduced bandwidth use by Jenkins CI servers
Largest user is an IP address in China that repeatedly downloads war file of all Jenkins releases
Abuse reports have been ignored by the ISP
Attempts to locate the owner have failed
Abuse reports to other locations are in progress
Working with JFrog to see if there is a way to block that IP address
Log files provided weekly by JFrog
Log file analysis tool from Basil Crow places log records in SQLite database
Jenkins project at SCaLE 20x March 10-12
Booth staffed by Mark Waite and Alyssa Tong
CDF Jenkins Awards nominations