# Jenkins Contributor Summit on Jan 30, 2026 - Call for topics and ideas
**URL:** https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773
**Category:** Community
**Tags:** events, contributor-summit
**Created:** [October 31, 2025, 10:17am UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773 "2025-10-31T10:17:25Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@poddingue](https://community.jenkins.io/u/poddingue)
#### Post date: [October 31, 2025, 10:17am UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/1 "2025-10-31T10:17:25Z")
We are delighted to announce that we will be hosting a **Jenkins Contributor Summit** in Brussels on Friday, January 30, 2026, preceding FOSDEM.
## Event Details
We will update this post with more specific information as soon as we can confirm the details of the day.
## Call for Participation
If you’re interested in:
- Attending the summit
- Presenting during the meeting
Please reply to this post to let us know!
We’re looking forward to your participation and contributions. 🙌
In the meantime, here’s a draft of the proposed agenda.
Feel free to suggest changes: add new ideas, reorder topics, or adjust the structure.
It’s still very much a work in progress!
Morning session
| Time | Topic | Description & rationale |
| --- | --- | --- |
| **09:00 – 09:15** | **Welcome & practical details** | Opening Remarks, Schedule Overview, and Logistics. Builds community energy and sets expectations. |
| **09:15 – 10:00** | **Board & officer reports: The present and the future** | Officers or ceremony host provide short presentations covering: **Infrastructure** (budget and sponsorship changes; migration to Azure and cost‑control projects like JFrog bandwidth reduction); **Release** (summary of 2025 LTS and weekly release cadence; highlight adoption of JDK 21 baseline and schedule for Java 25 support); **Documentation** (progress on UI redesign documentation, and [jenkins.io](http://jenkins.io) retooling); **Events & Advocacy** (FOSDEM/SCaLE experiences, contributor spotlight, Hacktoberfest, new contributor onboarding); |
| **Security** (key advisories). | | |
| **10:00 – 10:20** | **UX SIG update** | Demonstrate the new header and navigation introduced in LTS 2.516.1 and subsequent refinements (dropdown fixes, skeleton outlines, icons). Present the plugin health‑score display and search improvements[[](https://community.jenkins.io/t/user-experience-sig-april-9-2025/29616).. Outline plans for 2026: improving plugin manager sorting, enhancing the pipeline graph view, and integrating design‑library components. |
| **10:20 – 10:30** | **Platform SIG update** | Summarize Debian 13 (Trixie) adoption, Windows 2025 migration, and the deprecation schedule for Windows 2019. Report progress on container image updates. Provide statistics from Java 25 plugin‑compatibility tests and detail the timeline for switching Jenkins core to Java 25 (targeting spring 2026). |
| **10:30 – 11:00** | **Coffee break** | Networking opportunity. |
| **11:00 – 11:30** | **Java 25 support plan** | Present the readiness plan for Java 25: summary of plugin‑testing results, work remaining in core (Jetty 12, Winstone updates), and the timeline for removing JDK 17 compatibility. Engage maintainers to commit to Java 25 readiness by March 2026. |
| **11:30 – 12:00** | **Plugin modernization & OpenRewrite** | Showcase the OpenRewrite‑based plugin modernizer recipe for upgrading plugins to Java 25, summarize the GSoC project results, and discuss how maintainers can use the tool. Provide case studies of plugins successfully upgraded. |
| **12:00 – 13:00** | **Lunch break** | Informal networking and birds‑of‑a‑feather sessions (e.g., plugin maintainers meet‑up, docs contributors meet‑up). |
Afternoon session
| Time | Topic | Description & rationale |
| --- | --- | --- |
| **13:00 – 13:30** | **Documentation** | Present progress on the [jenkins.io](http://jenkins.io) retooling project; share metrics on improved navigation and search. Invite volunteers to contribute translations and documentation updates for Java 25. |
| **13:30 – 14:00** | **User experience evolution** | Discuss future UX projects: refining plugin health scores, improving the pipeline graph, enhancing the design library, and consolidating UI components. Solicit feedback on pain points and suggestions for user experience. |
| **14:00 – 14:30** | **Infrastructure & hosting update** | Provide a deep dive into infrastructure initiatives: status of migrating [ci.jenkins.io](http://ci.jenkins.io) and other services to Azure; progress reducing Artifactory bandwidth and storage costs; and outlook for 2026 budgets |
| **14:30 – 15:00** | **Advocacy & Outreach: community building** | Highlight successes from 2025: GSoC projects and final presentations, contributor spotlight stories, and new contributor onboarding proposals. Preview 2026 events: **FOSDEM 2026** (booth planning), **Hacktoberfest 2026, ScaleX,** and other conferences. Discuss content ideas (e.g., top plugins guides, beginner tutorials) to maintain competitive visibility. Explain the election process and encourage community involvement in governance. |
| **15:00 – 15:20** | **Coffee break** | Refreshments. |
| **15:20 – 15:45** | **Open discussion & roadmap** | Encourage attendees to propose new initiatives. |
| **15:45 – 17:00** | **Workshops** | Break into small groups for hands‑on sessions: |
| • **Plugin modernization coding session** : upgrade sample plugins to Java 25 using the OpenRewrite recipe; test with the new platform images. | | |
| […] | | |
| • **New contributor onboarding:** pilot a structured onboarding workshop as proposed by the Advocacy & Outreach SIG. | | |
| **17:00 – 17:30** | **Closing remarks and next steps** | Summarize outcomes, assign owners for action items (e.g., Java 25 adoption, plugin modernization), thank participants and close the summit. |
_The Jenkins Outreach Team_
---
### Author:  [@strangelookingnerd](https://community.jenkins.io/u/strangelookingnerd)
#### Post date: [October 31, 2025, 2:12pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/2 "2025-10-31T14:12:00Z")
I’m looking forward to attend again!
---
### Author:  [@panicking](https://community.jenkins.io/u/panicking)
#### Post date: [November 1, 2025, 9:56am UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/3 "2025-11-01T09:56:32Z")
I think that I will attend
---
### Author:  [@NotMyFault](https://community.jenkins.io/u/NotMyFault)
#### Post date: [November 1, 2025, 5:55pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/4 "2025-11-01T17:55:00Z")
I’ll be there as well 🙂
---
### Author:  [@uhafner](https://community.jenkins.io/u/uhafner)
#### Post date: [November 3, 2025, 5:01pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/5 "2025-11-03T17:01:11Z")
I hope that I can attend this year.
Are the recommended hotels the same as in the last years?
---
### Author:  [@poddingue](https://community.jenkins.io/u/poddingue)
#### Post date: [November 3, 2025, 7:54pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/6 "2025-11-03T19:54:18Z")
As far as I know, yes.
---
### Author:  [@jimklimov](https://community.jenkins.io/u/jimklimov)
#### Post date: [November 10, 2025, 2:48pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/7 "2025-11-10T14:48:06Z")
I hope to be there during the day, but maybe will spend the evening with another community to catch up with all the friends 🙂
Which ho(s)tels are the recommended ones?
---
### Author:  [@timja](https://community.jenkins.io/u/timja)
#### Post date: [November 10, 2025, 4:40pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/8 "2025-11-10T16:40:09Z")
I plan to attend 🙂
(more more chars to allow me to post)
---
### Author:  [@janfaracik](https://community.jenkins.io/u/janfaracik)
#### Post date: [November 11, 2025, 10:56am UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/9 "2025-11-11T10:56:20Z")
I also plan to attend 🙂 Looking forward to this years UX Sig update!
---
### Author:  [@jonesbusy](https://community.jenkins.io/u/jonesbusy)
#### Post date: [November 11, 2025, 1:16pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/10 "2025-11-11T13:16:47Z")
I’ll be there! See you soon!
---
### Author:  [@wfollonier](https://community.jenkins.io/u/wfollonier)
#### Post date: [November 24, 2025, 2:24pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/11 "2025-11-24T14:24:22Z")
Teaser on the security side: I should be able to present some data around our brand new Bug Bounty program. (public announcement coming soonish)
---
### Author:  [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)
#### Post date: [November 24, 2025, 2:37pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/12 "2025-11-24T14:37:29Z")
> [@wfollonier](#):
>
> new Bug Bounty program. (public announcement coming soonish)
It is also looking quite good that Content Security Policy will optionally be available for Jenkins users as part of the January LTS baseline thanks to the work from @danielbeck and @Kevin-CB . More details in the pull request:
>
>
> See \[JENKINS-76263\](https://issues.jenkins.io/browse/JENKINS-76263).
>
> This PR …implements the \`Content-Security-Policy\` header in core. Previously, users had to install the \[Content Security Policy Plugin\](https://plugins.jenkins.io/csp/) to get this protection.
>
> This feature is \*\*opt-in\*\* for now, given it is a major change and \_will\_ break some plugins. Their compatibility is tracked in \[JENKINS-60865\](https://issues.jenkins.io/browse/JENKINS-60865). Per \[this tracking spreadsheet\](https://docs.google.com/spreadsheets/d/1nSx4gQ2YUl-sKdY5u6biXmyDnkQ26wTaMBLSR8gr\_-A/edit?gid=0#gid=0), all popular maintained plugins are expected to be compatible. Some plugins (those with "avatar" icons) are being adapted to be compatible using the new APIs introduced in this PR, see below for details.
>
> Additionally, this removes the \`X-Webkit-CSP\` and \`X-Content-Security-Policy\` headers from \`DirectoryBrowserSupport\`. Those have been obsolete since about 2013, so even backward compatibility is no longer really a relevant concern.
>
> Closely related PRs:
>
> \* User and developer documentation updates: https://github.com/jenkins-infra/jenkins.io/pull/8529
> \* Rewrite/adaptation of CSP plugin: https://github.com/jenkinsci/csp-plugin/pull/63
> \* Avatar compatibility (using the new API to prevent broken folder or user icons):
> - https://github.com/jenkinsci/github-branch-source-plugin/pull/917
> - https://github.com/jenkinsci/oic-auth-plugin/pull/681
> - https://github.com/jenkinsci/keycloak-plugin/pull/27
> - https://github.com/jenkinsci/gravatar-plugin/pull/166
> \* Adapt \`CspRule\` in ATH: https://github.com/jenkinsci/acceptance-test-harness/pull/2269
>
> Loosely related PRs:
>
> \* Make it easier to identify the source of some \`script\` tag violations: https://github.com/jenkinsci/stapler/pull/612
>
> \## Open PR Tasks
>
> Optionally fine-tune wording on the \`CspRecommendation/index\` page, but for a weekly it seems fine as is IMO.
>
> \## Overview
>
> \### Deciding which header to set
>
> \
>
> There are four basic configurations/states controlling which header (CSP or CSP-Report-Only) is set. These are checked in order. See \`CspHeaderDecider\` for details.
>
> 1. The system property \`jenkins.security.csp.CspHeader.headerName\` is set to either of the two values. This hides/disables the configuration UI and sets the configured header.
>
> \
> (ignore the outdated header name on the screenshot)
>
> \---
>
> 2. \`Main#isUnitTest\` or \`Main#isDevelopment\` are true. This works similarly to the previous one, just a different message on the placeholder UI, and will always set \`CSP\`. Disable by setting \`jenkins.security.csp.impl.DevelopmentHeaderDecider.DISABLED\` to \`true\`. The idea here is that developers should be the first to encounter compatibility problems, ideally fixing them rather than ignoring them / disabling this behavior.
>
> \
>
> \---
>
> 3. The regular configuration, which either sets the \`CSP\` header (checked, "enforcing") or \`CSP-Report-Only\` (unchecked), if configuration is enabled.
>
> \
>
> \---
>
> 4. Lastly, the "fallback" is to set \`CSP-Report-Only\` and to show a placeholder UI that recommends enabling CSP configuration. This is what most users of Jenkins see first (besides the admin monitor).
>
> \
>
> \---
>
> There are two different terms here: One is that \_configuration is enabled\_, the other that it is \_enforcing CSP\_. The latter just means we set the CSP header, not CSP-Report-Only. The former means that an admin chose to configure this. This two step process is needed to support the admin monitor showing while an admin has not made a choice yet; otherwise "blindly" submitting \_Manage Jenkins » Security\_ would look like the admin opting out of protection.
>
> Now the usual journey to enabling this option is as follows:
>
> 1. Admin sees admin monitor or the placeholder text from fallback on \`/configureSecurity/\`
>
> \
> \
>
> \---
>
> 2. They choose the button/link that takes them to the \`CspRecommendation/index.jelly\` view that explains the functionality and caveats.
>
> \
>
> \---
>
> 3. They click \_Set up Content-Security-Policy\_ which enables the configuration by setting it to disabled (but not yet saving it), and taking them to \`/configureSecurity/\`.
>
> \
>
> \---
>
> 4. Special form validation tells them that just saving will leave it not enforced, they need to check the box themselves. That may also recommend to set up Resource Root URL it it's not currently configured.
>
> \
>
> \---
>
> 5. Once they check the box and save the form, it's now permanently enforced.
>
> At each step, there's a way to opt out:
> \* They can choose to "Dismiss" the admin monitor or ignore the placeholder text on \`/configureSecurity/\`
> \* They can click "Cancel" on the separate page explaining caveats.
> \* They can leave protection disabled (explicitly), which will basically disable the admin monitor but otherwise behave as before.
> \* They can just not submit the form before restarting Jenkins, which resets it to the default state. \`/configureSecurity/\` submission is needed to persist the state from "enabling" the configuration.
>
> \
>
> \## Interaction with Resource Root URL
>
> Unfortunately, serving user-generated resource files from the same origin is a problem. \`script-src 'self'\` is satisfied by \`/job/whatever/1/artifacts/lol.js\`. So users who want good protection definitely need to set up Resource Root URL, which is why this is called out in the form validation, and on https://github.com/jenkins-infra/jenkins.io/pull/8529/files#diff-2fdabed902fd1d2d7e1ee4cafa034e3c3733979b50b0cd949bc1f4d1589b84a1R42-R44.
>
> \## CasC support
>
> See https://github.com/daniel-beck/csp-plugin/blob/v2/README.adoc#configuration-as-code for what it looks like with the CSP plugin installed (otherwise there's just \`enforce\`).
>
> \## \`DirectoryBrowserSupport\` and Resource Root URL
>
> The header is not being set for RRURL requests, same as CSP plugin 1.x.
>
> Otherwise, DBS's more restrictive (e.g., \`sandbox\`) CSP takes precedence, and if disabled through \`hudson.model.DirectoryBrowserSupport.CSP\` system property will also remove the regular header. See \`ContentSecurityPolicyTest\` for where all of this is being tested.
>
> \## Known potential problems
>
> Besides the previously known problems of inline scripts etc. that need code restructuring to make work, the following more general features are inherently affected:
>
> \* The extension point \`UserAvatarContributor\` is likely to result in broken image references unless the basic implementation in this PR takes care of everything.
> \* Similarly, \`AvatarMetadataAction\` in \`scm-api\` defines a similar feature for org folders, and either that will need to be adapted generally, or implementations need to add support for these new core APIs.
>
> These plugins need to implement \`Contributor\`, or call \`AvatarContributor#allow\` (or locally cache avatar images). This is newly being documented by https://github.com/jenkins-infra/jenkins.io/pull/8529.
>
> Current status of plugins known to implement these extension points:
>
> \### \`UserAvatarResolver\`
>
> 🚧 https://plugins.jenkins.io/oic-auth/ - https://github.com/jenkinsci/oic-auth-plugin/pull/681
> ✅ https://plugins.jenkins.io/azure-ad/ - \[caches avatar images locally\](https://github.com/jenkinsci/azure-ad-plugin/blob/0ac48a9179b34b86d48bd0e45e20766cdeca7c1f/src/main/java/com/microsoft/jenkins/azuread/avatar/EntraAvatarProperty.java#L34-L36)
> 🚧 https://plugins.jenkins.io/keycloak/ - https://github.com/jenkinsci/keycloak-plugin/pull/27
> 🚧 https://plugins.jenkins.io/gravatar/ - https://github.com/jenkinsci/gravatar-plugin/issues/166
> ✅ https://plugins.jenkins.io/avatar/ - \[only renders locally uploaded files\](https://github.com/jenkinsci/avatar-plugin/blob/2e722a1e67ea55155cd2ea1e57d8bd1ae284c26a/src/main/java/net/hurstfrost/jenkins/avatar/user/AvatarProperty.java#L49-L5)
>
> \### \`AvatarMetadataAction\` (\`scm-api\`)
>
> 🚧 https://plugins.jenkins.io/github-branch-source/ - https://github.com/jenkinsci/github-branch-source-plugin/pull/917
> ✅ https://plugins.jenkins.io/cloudbees-bitbucket-branch-source/ - appears to only render locally cached avatars
> ✅ https://plugins.jenkins.io/gitlab-branch-source/ - appears to only render locally cached avatars
> ✅ https://plugins.jenkins.io/gitea/ - appears to only render locally cached avatars
> ✅ https://plugins.jenkins.io/gerrit-code-review/ - renders bundled avatar icons
> ❓ https://plugins.jenkins.io/tuleap-git-branch-source/ - looks incomplete: \[this\](https://github.com/jenkinsci/tuleap-git-branch-source-plugin/blob/3e97d54b114f01adbe2aff31c11b1083204cc94f/src/main/java/org/jenkinsci/plugins/tuleap\_git\_branch\_source/TuleapProjectMetadataAction.java) does not implement any of \[that\](https://github.com/jenkinsci/scm-api-plugin/blob/master/src/main/java/jenkins/scm/api/metadata/AvatarMetadataAction.java).
>
> \## Testing done
>
> Autotests, and some manual tests:
>
> \* Regular \`DirectoryBrowserSupport\` has custom CSP header if enforced
> \* Resource Root URL has no CSP header
>
> \## Delivery plan
>
> \
>
> \### Step 1 – Opt in core feature (~Nov 2025)
> \*\*Gate: \[Core PR\](https://github.com/jenkinsci/jenkins/pull/11269) done, \[CSP plugin PR\](https://github.com/jenkinsci/csp-plugin/pull/63) (for customization) done.\*\*
> Disabled by default even for new installations.
> An admin monitor encourages admins to enable it (extra visibility). Can be disabled through the UI (for all users).
> During development and testing, it’s always enabled to give an early warning to developers.
> Planned for a weekly soon, so that it’s in the next LTS.
> Set up new issue tracking (labels, Epic, separate reporting GH repo) perhaps to understand compatibility?
>
> \### Step 2 – Advertise to developers (~Nov 2025)
> \*\*Gate: Core PR is in weekly.\*\*
> Encourage plugin maintainers to adapt their plugins. Doesn’t need new core dependency, can try with CSP plugin v1.
> Maybe also publish a blog post to advertise further, including the plan?
>
> \### Step 3 – Advertise to LTS users (late Jan 2026)
> \*\*Gate: Core PR is in LTS.\*\*
> Mention it in some detail in the upgrade guide.
> Perhaps a blog post?
>
> \### Step 4 – Opt out core feature (Q2/2026, maybe?)
> \*\*Gate: Plugins are sufficiently adapted (TBD threshold etc.)\*\*
> Switch the core feature to opt out (via UI).
>
> At this point we’re basically “done” – removing the UI option to opt out can be done whenever we want.
>
> \
>
> \### Proposed changelog entries
>
> \- Allow configuring Content-Security-Policy protection for the Jenkins UI. Introduce an API for plugins to relax (or further tighten) the rules around various resources. If you have Content Security Policy Plugin (\`csp\`) installed, update it to version 2.x.
>
> \### Proposed changelog category
>
> /label major-rfe,developer
>
> \### Proposed upgrade guidelines
>
> \#### Content Security Policy support in Jenkins core
>
> Jenkins now allows enforcing Content Security Policy. This is a security mechanism that can reduce or eliminate the impact of web security vulnerabilities like cross-site-scripting (XSS). Jenkins core and most popular Jenkins plugins are compatible with Jenkins's default rule set, but for backwards compatibility, CSP enforcement is disabled by default.
>
> See \[the Content Security Policy documentation\](https://www.jenkins.io/doc/book/security/csp/) for more information.
>
> Users of \[Content Security Policy Plugin\](https://plugins.jenkins.io/csp/) are should disable it or update it to version 2.x.
>
> \### Submitter checklist
>
> \- \[x\] The Jira issue, if it exists, is well-described.
> \- \[x\] The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see \[examples\](https://github.com/jenkins-infra/jenkins.io/blob/master/content/\_data/changelogs/weekly.yml)). Fill in the \*\*Proposed upgrade guidelines\*\* section only if there are breaking changes or changes that may require extra steps from users during upgrade.
> \- \[x\] There is automated testing or an explanation as to why this change has no tests.
> \- \[x\] New public classes, fields, and methods are annotated with \`@Restricted\` or have \`@since TODO\` Javadocs, as appropriate.
> \- \[x\] New deprecations are annotated with \`@Deprecated(since = "TODO")\` or \`@Deprecated(forRemoval = true, since = "TODO")\`, if applicable.
> \- \[x\] New or substantially changed JavaScript is not defined inline and does not call \`eval\` to ease future introduction of Content Security Policy (CSP) directives (see \[documentation\](https://www.jenkins.io/doc/developer/security/csp/)).
> \- \[x\] For dependency updates, there are links to external changelogs and, if possible, full differentials.
> \- \[x\] For new APIs and extension points, there is a link to at least one consumer.
>
> \### Desired reviewers
>
> @mention
>
>
>
> Before the changes are marked as \`ready-for-merge\`:
>
> \### Maintainer checklist
>
> \- \[\] There are at least two (2) approvals for the pull request and no outstanding requests for change.
> \- \[\] Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
> \- \[\] Changelog entries in the pull request title and/or \*\*Proposed changelog entries\*\* are accurate, human-readable, and in the imperative mood.
> \- \[\] Proper changelog labels are set so that the changelog can be generated automatically.
> \- \[\] If the change needs additional upgrade steps from users, the \`upgrade-guide-needed\` label is set and there is a \*\*Proposed upgrade guidelines\*\* section in the pull request title (see \[example\](https://github.com/jenkinsci/jenkins/pull/4387)).
> \- \[\] If it would make sense to backport the change to LTS, a Jira issue must exist, be a \_Bug\_ or \_Improvement\_, and be labeled as \`lts-candidate\` to be considered (see \[query\](https://issues.jenkins.io/issues/?filter=12146)).
---
### Author:  [@lemeurherve](https://community.jenkins.io/u/lemeurherve)
#### Post date: [November 24, 2025, 2:41pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/13 "2025-11-24T14:41:24Z")
I plan to attend too.
---
### Author:  [@StefanSpieker](https://community.jenkins.io/u/StefanSpieker)
#### Post date: [November 25, 2025, 12:17pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/14 "2025-11-25T12:17:27Z")
I will also be there. A really nice agenda!
---
### Author:  [@jimklimov](https://community.jenkins.io/u/jimklimov)
#### Post date: [November 26, 2025, 9:31pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/15 "2025-11-26T21:31:23Z")
Is the location known by now? 🙂 Which hotels are recommended this year?
---
### Author:  [@oleg-nenashev](https://community.jenkins.io/u/oleg-nenashev)
#### Post date: [November 28, 2025, 4:06pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/16 "2025-11-28T16:06:07Z")
I will try to join, at least in the afternoon
---
### Author:  [@Shree](https://community.jenkins.io/u/Shree)
#### Post date: [November 29, 2025, 1:26pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/17 "2025-11-29T13:26:19Z")
I will great attending the event
---
### Author:  [@alyssat](https://community.jenkins.io/u/alyssat)
#### Post date: [December 10, 2025, 9:31pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/18 "2025-12-10T21:31:53Z")
Summit location is same as Contributor Summit 2025 - [Betacowork](https://maps.app.goo.gl/RBJmxQiraUprxUTe8)
---
### Author:  [@poddingue](https://community.jenkins.io/u/poddingue)
#### Post date: [December 10, 2025, 9:54pm UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/19 "2025-12-10T21:54:33Z")
Thank you so much for booking the room, Alyssa! 🤗
---
### Author:  [@nre-ableton](https://community.jenkins.io/u/nre-ableton)
#### Post date: [January 6, 2026, 10:47am UTC](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773/20 "2026-01-06T10:47:58Z")
I would like to attend this year as well. Looking forward to seeing you all again!
[Next page](https://community.jenkins.io/t/jenkins-contributor-summit-on-jan-30-2026-call-for-topics-and-ideas/35773.md?page=2)