5 open source questions developers are asking in 2026

The OCX Webinar Week brought practitioners from Deutsche Bahn, IBM, SignPath, the Eclipse Foundation, EclipseSource and research institutes across Europe to share what they have learned.

This blog post groups their talks around five questions: how to let AI agents work safely, how to trust what you ship and install, how safety-critical industries adopt open source, how to share data and prove identity without losing control, and how to join and sustain an open source project. Every recording is on YouTube.

1. How do I let AI agents work without losing control?

The short answer: the three sessions below point to one approach: put a boundary around the agent at each layer where it can act: the machine it runs on, the code it belongs to and the infrastructure it manages. Keep people in the decisions that matter.

Eclipse Enclave: run AI coding agents in an isolated container

Isolating AI Agents with Eclipse Enclave: Claude Code, Codex, OpenClaw and more | Philip Langer, CEO and Principal Software Architect, EclipseSource. Watch the recording.

Eclipse Enclave is an open source runtime that runs each AI coding agent session in its own container. Agents such as Claude Code and Codex CLI work best when they run commands and install packages without asking, and that freedom is also the risk. Philip Langer described the setup most developers have today: the agent runs on the developer machine, right next to the developer’s credentials, SSH keys and secrets, with full internet access, which is very dangerous.

With Enclave, the agent sees only the project folder. All network traffic passes through a gateway with an allow list, and secrets are masked with a placeholder that is swapped for the real value only on requests to the API you configured. In the live demo, a request to send data to an outside domain failed until that domain was added to the allow list. In his words, the setup adds no friction to your workflow, yet you can show the agent only what it needs and let it talk only to services you approved. Enclave is at its first preview and has been an Eclipse Foundation project since May 2026. A stable release is the next goal.

Jakarta Agentic AI: build AI agents in Java

The Jakarta Agentic AI Specification: Status and Future | Reza Rahman. Watch the recording.

Jakarta Agentic AI is a specification for building AI agents in Java. In the specification, an agent is a CDI (Contexts and Dependency Injection) bean that perceives its environment, plans, acts and adapts. The example in the talk is fraud detection: an LLM call decides whether a bank transaction looks fraudulent, the agent alerts bank security or the customer, flags the transaction, and queues its decisions for a human to review.

The specification does not try to standardise an LLM API. It offers a minimal facade and leaves fuller needs to LangChain4j and Spring AI. The roadmap lists a workflow API to change agent behaviour at runtime, a session API, human in the loop, observability with OpenTelemetry and an A2A binding. Reza Rahman acknowledged that the runtime part is not there yet.

Intent-driven orchestration across the computing continuum

Orchestration challenges in the Computing Continuum: the role of Agents | Anastasios Zafeiropoulos, NTUA. Watch the recording

Intent-driven orchestration lets you state a goal, what you want to achieve, without specifying how to implement it. The team’s design turns a natural language intent into a specification, deploys the application, applies corrective actions at runtime and checks over time whether the intent is met, with a knowledge graph behind all three control loops. In their open source simulation kit, adding agents reduced intent violations. Those results come from simulation. The team plans for as much automation as possible, and Anastasios Zafeiropoulos was clear that in some critical decisions humans should stay part of the decision.

In a lightning talk, Ignacio Lacalle Úbeda covered the placement side: a meta operating system that runs containerised workloads across cloud, edge and IoT with energy use in mind. It started as a research project and moved into an Eclipse Foundation project, Eclipse aeriOS, for neutrality and long-term sustainability. Watch from 4:38.

Resources: try Eclipse Enclave on a side project, then read the Jakarta Agentic AI tutorial. For the research side, see Eclipse aeriOS.

2. Can I trust what I ship and what I install?

The short answer: a signature shows who published a release, but it does not show that the release matches the reviewed source, so signing needs the same level of controls as the rest of the release pipeline.

Code signing for open source projects

Who can sign open source software? Solving the trust challenges behind packaged releases | Stefan Wenig, SignPath, and Mikaël Barbero, Eclipse Foundation. Watch the recording.

Code signing attaches a verifiable signature to software so users can see who published it. Stefan Wenig started with the obstacle most community projects hit: the traditional model of code signing is not very open source friendly. A certificate authority wants to identify a person, and somebody has to pay.

The talk then walked through the XZ Utils attack, where the released source tarballs were changed and signed while the repository still looked clean, so code review saw nothing. SLSA (Supply-chain Levels for Software Artifacts) attestations help protect the integrity of a release, but Stefan Wenig put the weight on signing: the hard security today comes more from the code signing side than from the attestation side.

Two practical points came out of it. On Windows, Smart App Control checks signatures on every launch, so every exe and DLL needs signing, not only the installer. And the SignPath Foundation provides free code signing certificates to community open source projects. The free certificates work for Windows and Java, and the service supports GitHub and GitLab in the cloud.

Eclipse Foundation projects are moving from the legacy signing service, which can only be reached from the Foundation’s own Jenkins, to SignPath. The migration tools are open source in the Eclipse Common Security Infrastructure project, with a Maven plugin, a CLI and a Java API that work with Jenkins, GitHub Actions and GitLab. Committers ask for access through the Eclipse Foundation Help Desk. Both services run side by side for now.

Open VSX: the open extension registry for AI developer tools

Open VSX: Scaling for Critical AI Developer Infrastructure | Brian King and Manpreet Kaur, Eclipse Foundation. Watch the recording.

Open VSX is an open extension registry and an Eclipse Foundation project. It has grown in 2026 into critical infrastructure for developer tools as AI coding tools and agents become more common. The speakers explained how the Eclipse Foundation scaled development, processes and infrastructure for organisations adopting it and for commercial customers, what publishers and extension consumers gain, and which recent security changes protect the integrity of extensions. They also covered what still needs to be done and the features that are coming.

Resources: If you ship Windows or Java software, check what the SignPath Foundation requires of a project. Eclipse committers can start with the Eclipse code signing tools. Extension publishers can start at the Open VSX Registry.

3. How do industries that cannot fail adopt open source?

The short answer: start collaborating where no single company can solve a problem alone, and test on real hardware.

OpenRail: open source collaboration across the railway sector

OpenRail: Open Source Collaboration in the Railway Sector | Max Mehl, Deutsche Bahn. Watch the recording.

The OpenRail Association is a not-for-profit organisation, founded in January 2024, that brings open source collaboration to the railway sector. About 500,000 freight wagons, owned by different companies, run across Europe and are coupled by hand. Wagons converted to the digital coupler cannot couple with unconverted ones, so deciding which wagons to convert and when is a software problem that sits across companies. Max Mehl called it a perfect example of where collaboration is needed: no single company can do anything about it alone, so they have to work together.

The association hosts projects such as the Open Source Railway Designer (OSRD), which is in production at SNCF, plus LibLRS and OSCAL4Rail. Its technical committee, which includes a delegate from each new project, works as the bridge between large railway organisations and open source working methods. Starting a project is, in his words, basically creating a pull request.

Eclipse ThreadX on RISC-V: test on real boards

Beyond the Basics: Elevating Eclipse ThreadX to a First-Class RTOS for RISC-V | Akif Ejaz, 10xEngineers. Watch the recording.

Eclipse ThreadX is a certified open source real-time operating system (RTOS), and it now covers 32-bit and 64-bit RISC-V with GNU, Clang and IAR toolchains. Continuous integration runs simulation tests on every change. The memorable lesson came from real hardware. Tests that passed in the QEMU simulator started failing on a physical board: 24 of 95 RISC-V tests. The cause was a mismatch in the size of the trap frame, which stores a thread’s registers during an interrupt. The frame had grown from 520 to 528 bytes to keep the stack on a 16-byte boundary, while the board support package still reserved 520. The fix was to export the number from one shared header.

The team’s next step is hardware-in-the-loop testing, where a GitHub Actions job would run the built binary on a real board. That is planned, not live yet.

Resources: see how a mixed-owner industry organises itself at the OpenRail Association and run the QEMU example from the Eclipse ThreadX repository.

4. How do we share data and prove identity without giving up control?

The short answer: share a proven foundation, keep personal data under the control of the person it belongs to, and start with one small use case.

Eclipse Tractus-X KITs: dataspaces you can start small

Dataspaces at scale: Eclipse Tractus-X KITs (Keep it Together) | Mathias Moser, Catena-X Association. Watch the recording.

Eclipse Tractus-X is an open source project for sovereign data exchange across supply chains. Its KITs are documentation and reference material, described in the talk as a Lego set with an instruction booklet and the bricks. Each KIT covers three views: adoption (why invest), development (how to implement) and operation (how to run it). Other industry dataspace initiatives, including Factory-X, Semiconductor-X and Construct-X, adopted at least the foundational KITs so that partners share a base for exchanging data. Mathias Moser’s advice for newcomers is to start with a simple use case such as certificate exchange and build from there.

LICORICE: self-sovereign identity and privacy tools

LICORICE: Open-Source Showcase: SSI & Privacy Tools | Diana Jimenez, Trialog. Watch from 20:07, part of a three-talk lightning talk recording.

LICORICE is a European innovation action with 12 partners and around ten cryptographic tools for self-sovereign identity (SSI) and privacy. The tools are validated in two pilots, cyber threat intelligence and e-health. In the first, sensitive queries are sanitised before they reach an external AI model, while keeping enough context for the analysis to stay useful.

Consent-based data access under the GDPR

Privacy and consent-based data access in cybersecurity context | Luigi Briguglio, CyberSocial Lab. Watch from 35:09.

Under the GDPR, a person can withdraw consent at any time, so personal data does not belong on an immutable ledger and needs a conventional database instead. Luigi Briguglio showed how a smart contract can act as the gate: if consent is given, the contract opens access to the data. The mechanism is implemented in CyberNEMO. In the Q&A, he said it is not yet implemented in any industry.

Resources: read the Eclipse Tractus-X KITs, and look at CyberNEMO for the consent work.

5. How do I get in and contribute to open source?

The short answer: contribute in ways maintainers can absorb, and give maintainers the practices that keep them going.

Beyond Borders: contribute beyond code

Beyond Borders: India’s Role in the Open Java and Eclipse Ecosystems | Manoj Nalledathu Palat, IBM. Watch the recording.

The first Eclipse Foundation team in India started in Bangalore around 2008 and grew to take over responsibility for Eclipse JDT. Today, IBM committers in Bangalore and Kochi work on the Eclipse Platform, Eclipse PDE and Eclipse JDT. The Eclipse compiler for Java, which is separate from javac, keeps pace with the six-month Java release cadence and has the first part of value types support. The team delivered every release on time while working fully remote during the pandemic. Contribution here goes beyond code: the Kochi Java User Group, founded in May 2024, has more than 900 members, and committers also take part in councils, program committees and working groups.

Human Skills & Digital Future: translating research into industry

Human Skills & Digital Future | NCSR Demokritos, the coordinator of DeepTechSeeds. Watch the recording.

DeepTechSeeds covers five deep tech domains: AI, quantum computing, mobile network technologies, robotics and advanced materials. Its Talent Ecosystem Platform, still in development, includes a self-assessment that backs skills with evidence such as publications, patents and GitHub repositories, an AI matchmaking engine with an explainable ranking, and a skills translation toolkit that helps early career researchers turn academic CVs into industry terms.

The Challenges of Being Human: the maintainer side of AI contributions

The Challenges of Being Human | Shelley Lambert, IBM. Watch the recording.

Shelley Lambert described what AI tools do to a project like Eclipse Adoptium: more pull requests and reports, with the same number of active reviewers. She cited a survey from the end of 2024 in which 82% of developers used AI code assistants and 45 to 58% of maintainers had experienced severe burnout. In the Temurin repository, 95 empty release checklists came from 95 brand-new GitHub profiles within a few months, and maintainers report AI-generated vulnerability reports that are often about a thousand lines long and not vetted by a human.

Her practices for projects are concrete: keep contributions small and tested, discuss before opening a pull request, require two-person reviews, hold community calls and set up workflows that block noisy empty issues. She also suggested a built-in waiting period between an issue and a pull request, and Adoptium is writing an AI policy for both humans and agents. Her advice to contributors is to be kind and take action, so the next person who is handed the thing has less work to do.

Resources: see the Eclipse Adoptium project, explore Eclipse JDT, and follow DeepTechSeeds.

OCX Webinar Week at a glance

  • Isolating AI Agents with Eclipse Enclave | Philip Langer, EclipseSource: each AI coding agent runs in its own container with a network allow list. Watch
  • The Jakarta Agentic AI Specification | Reza Rahman: agents as CDI beans in a vendor neutral Java specification. Watch
  • Orchestration challenges in the Computing Continuum | Anastasios Zafeiropoulos, NTUA: intent-driven orchestration with agents and a knowledge graph, shown in simulation. Watch
  • Orchestration of containerised workloads across the Cloud-Edge-IoT continuum | Ignacio Lacalle Úbeda, Universitat Politècnica de València: energy-aware workload placement with Eclipse aeriOS. Watch
  • Who can sign open source software? | Stefan Wenig, SignPath, and Mikaël Barbero, Eclipse Foundation: signing needs the same controls as attestations. Watch
  • Open VSX: Scaling for Critical AI Developer Infrastructure | Brian King and Manpreet Kaur, Eclipse Foundation: an open extension registry scaled for AI developer tools. Watch
  • OpenRail: Open Source Collaboration in the Railway Sector | Max Mehl, Deutsche Bahn: collaborate first on problems no single company can solve. Watch
  • Eclipse ThreadX for RISC-V | Akif Ejaz, 10xEngineers: tests that pass in a simulator can still fail on a real board. Watch
  • Dataspaces at scale: Eclipse Tractus-X KITs | Mathias Moser, Catena-X Association: reusable KITs let a dataspace start small. Watch
  • LICORICE: SSI & Privacy Tools | Diana Jimenez, Trialog: identity and privacy tools validated in two pilots. Watch
  • Privacy and consent-based data access in cybersecurity | Luigi Briguglio, CyberSocial Lab: consent stays withdrawable, so personal data stays off the ledger. Watch
  • Beyond Borders: India’s Role in the Open Java and Eclipse Ecosystems | Manoj Nalledathu Palat, IBM: contribution grows from relationships as well as code. Watch
  • Human Skills & Digital Future | NCSR Demokritos (DeepTechSeeds): skills need evidence and translation to move from research to industry. Watch
  • The Challenges of Being Human | Shelley Lambert, IBM: small, tested, discussed contributions keep maintainers going. Watch

What the five questions have in common

Several sessions pointed to the same three practices. Set a boundary before something can go wrong, whether that is a container, a signature or a consent policy. Test against the real environment, as the ThreadX team did on real boards. And collaborate with the people who share your problem, because some of the hardest ones, from freight couplers to supply chain trust, do not fit inside one company.

These conversations continue in person. OCX, the Open Community Experience, is the Eclipse Foundation’s flagship open source developers conference. OCX takes place from 13 to 15 April 2027 at Tour & Taxis in Brussels, with tracks covering areas such as developer tooling, AI, automotive, open source compliance and research.

Join us in Brussels, 13–15 April 2027.

Registration is open, with early bird rates available until 21 February 2027.

Red Hat is a sponsor of OCX 2026

Red Hat

Red Hat is the world’s leading provider of enterprise open source software solutions, using a community-powered approach to deliver reliable and high-performing Linux, hybrid cloud, container, and Kubernetes technologies. Red Hat helps customers develop cloud-native applications, integrate existing and new IT applications, and automate and manage complex environments.

 A trusted adviser to the Fortune 500, Red Hat provides award-winning support, training, and consulting services that bring the benefits of open innovation to any industry. Red Hat is a connective hub in a global network of enterprises, partners, and communities, helping organizations grow, transform, and prepare for the digital future.

ADEPTIC Reply is an OCX 2026 sponsor

ADEPTIC Reply

At ADEPTIC Reply, part of the Reply Group, we are pioneering innovation in the Cloud‑Edge Continuum and next‑generation robotic and autonomous systems orchestration.
We design and deliver advanced architectures that seamlessly connect cloud intelligence with edge autonomy, enabling high‑performance, resilient, and scalable robotic applications.
From distributed orchestration to real‑time decision making on edge devices, we drive the future of robotics and autonomous mobility with cutting‑edge technology and a vision for the next era of intelligent systems.

Adeptic Reply is actively involved in the EU IPCEI-CIS program, with a strong focus on Cloud computing at the edge for data network services. Through close collaboration with key European partners, the company contributes to build a secure, resilient and sovereign intelligent ecosystem, where AI, Cloud and orchestration converge.

Adeptic Reply strongly believes in the value of open communities as key drivers of innovation through collaboration and knowledge sharing.

Follow them on LinkedIn.